> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/self-hosting/hyperswitch-open-source/readme-1/local-setup-using-individual-components.md).

# Advanced Development Env Setup

{% hint style="warning" %}
These setup guides are meant for development. If you want a quick trial of Hyperswitch (without contributing), use [this guide](https://app.hyperswitch.io).
{% endhint %}

### Setup Guides

<table data-view="cards"><thead><tr><th></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Hyperswitch Backend</strong></mark></td><td></td><td></td><td><a href="/pages/1nMuNNmkFtmAsVHzW8aR">/pages/1nMuNNmkFtmAsVHzW8aR</a></td></tr><tr><td><mark style="color:blue;"><strong>SDK (Frontend)</strong></mark></td><td></td><td></td><td><a href="/pages/w9sfl9am77IkY72i4rrf">/pages/w9sfl9am77IkY72i4rrf</a></td></tr><tr><td><mark style="color:blue;"><strong>Control Center</strong></mark></td><td></td><td></td><td><a href="/pages/AO7tyHl3wNSjPGBPLI7J">/pages/AO7tyHl3wNSjPGBPLI7J</a></td></tr></tbody></table>

### **Hyperswitch Components**

Hyperswitch is built as a modular system, comprising three key components. Each component is designed for specific roles in the payment stack and has detailed development environment setup guides, linked above and also available in their individual repositories.

### [**Hyperswitch App Server**](https://github.com/juspay/hyperswitch):

The Hyperswitch App Server is the core engine for processing payments. It offers full support for various payment flows, including:

* **Core Operations**: Authorization, authentication, voids, captures, refunds, and chargeback handling.
* **Post-Payment Management**: Robust handling of disputes and reconciliations.
* **Routing Flexibility**:
  * Success-rate-based routing
  * Rule-based routing
  * Volume distribution
  * Fallback strategies
  * Intelligent retries using error-code-specific flows
* **Extensibility**: Connects with external fraud risk management (FRM) tools and authentication providers as part of the payment journey.

### [**SDK (Frontend)**](https://github.com/juspay/hyperswitch-web)**:**

The Hyperswitch SDK delivers a seamless and unified checkout experience across platforms:

* **Platform Support**: Available for [Web](https://docs.hyperswitch.io/explore-hyperswitch/merchant-controls/integration-guide/web), [Android, and iOS](https://github.com/juspay/hyperswitch-client-core),.
* **Multi-Method Support**: Handles cards, wallets, BNPL, bank transfers, and more.
* **Flow Adaptability**: Supports the nuances of different PSPs' payment flows.
* **Saved Payment Methods**: When integrated with the locker, the SDK automatically displays stored cards or other saved instruments for returning users.

### [**Control Center**](https://github.com/juspay/hyperswitch-control-center):

The Control Center is a no-code interface to manage and monitor your entire payment stack:

* **Workflow Management**: Configure smart routing, retries, 3DS invocation, fraud checks, and surcharge logic through a visual interface.
* **Operational Controls**:
  * Trigger and track refunds and chargebacks
  * View PSP-agnostic transaction logs for quick debugging
* **Insights and Analytics**: Access detailed reports and metrics on success rates, payment drop-offs, retry performance, and more.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperswitch.io/self-hosting/hyperswitch-open-source/readme-1/local-setup-using-individual-components.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.