> 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/~/revisions/QSGzCRIrWguIX4tCwjpZ/about-hyperswitch/payment-suite-1/orchestrator-model.md).

# Orchestrator Model

In the Orchestrator Model, Hyperswitch acts as the central intelligence layer. You interact with a single unified API, and Hyperswitch manages the entire payment lifecycle across multiple processors.

#### How it Works

1. **Unified Request:** Your backend sends a generic payment request to the Hyperswitch API.
2. **Smart Routing:** The Hyperswitch Orchestrator evaluates your configured business rules (e.g., routing by volume, cost, or region).
3. **Execution:** Hyperswitch transforms the request into the specific format required by the target Connector (Stripe, Adyen, Braintree, etc.).
4. **State Management:** Hyperswitch maintains the payment state machine, handling webhooks, retries, and status updates automatically.

#### Technical Advantages

* **Abstracted Complexity:** You do not need to write or maintain processor-specific code.
* **Dynamic Routing:** Switch traffic between processors in real-time via the Hyperswitch dashboard or during payment initiation API calls.
* **Unified Reporting:** Transaction data across all processors is normalized into a single schema.
* Every transaction is processed via a PSP and based on the API calls you can have -  zero dollar validation, multi-stage manual capture, or sophisticated recurring logic payment flows.

#### Choose the Right Orchestrator Setup

Depending on your UI strategy and data sovereignty requirements, the Orchestrator Model offers multiple implementation patterns. Each option is designed to help you balance user experience, engineering complexity, and PCI compliance scope in a way that best fits your business.

The four primary patterns are:

* **Hyperswitch SDK + Hyperswitch Vault** — *Unified Flow*:\
  The quickest path to launch, offering a fully integrated experience with zero PCI scope.
* **Merchant SDK + Hyperswitch Vault** — *Headless Flow*:\
  Enables a fully custom UI while retaining secure vaulting, giving you greater control with added implementation effort.
* **Hyperswitch SDK + External Vault** — *Hybrid Flow*:\
  Combines Hyperswitch-managed UI with third-party data storage for teams with specific vaulting requirements.
* **External SDK + External Vault** — *External Vault Flow*:\
  Provides maximum decoupling and flexibility, ideal for advanced setups that demand full control across the stack.


---

# 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/~/revisions/QSGzCRIrWguIX4tCwjpZ/about-hyperswitch/payment-suite-1/orchestrator-model.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.