> 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/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1.md).

# Payments Suite

Integrating a payment layer is a significant milestone. That is why Hyperswitch is modular by design: you can adopt the full stack for a unified experience, or selectively integrate specific modules like Vault or Smart Router.

Navigating these choices is easier when you view the ecosystem as four main blocks. By defining who owns which block—Hyperswitch or your team—you can quickly identify the architecture that suits your needs.

#### **The Four Core Components**

**1.The SDK (Frontend) :** The entry point for your payment flow. It resides in your frontend and is responsible for securely capturing sensitive payment information.

**2. Intelligent Routing & Orchestration (Backend) :** The core of the operation. It manages the payment lifecycle, executes routing logic, and handles post-payment operations like refunds.

**3. Acquirer & Processor Connectivity (Connectors) :** The actual pipelines that process the transaction (e.g., Stripe, Adyen, Worldpay).

**4. Vault (Card Data Storage) :**  The secure locker for sensitive card data to enable "One-Click" recurring payments without the user re-entering details.

Each Component can be handled by Hyperswitch, managed by your own team, or even sourced from a third-party provider(e.g. Vault).

#### **Integration Architecture**

With the components defined, the next step is to select your integration architecture. This choice hinges on a single question:  *Who controls the orchestration and processing logic and when the card is stored?*

There are two primary integration models:

**1.** [**Orchestrator Model** ](https://docs.hyperswitch.io/~/revisions/QSGzCRIrWguIX4tCwjpZ/about-hyperswitch/payment-suite-1/orchestrator-model)**:** You leverage Hyperswitch’s intelligent core to manage the payment lifecycle. Hyperswitch route payments dynamically to global processors (Stripe, Adyen, etc.) using the pre-built Connectors.

**2.** [**Direct Payment Control Model**](https://docs.hyperswitch.io/~/revisions/QSGzCRIrWguIX4tCwjpZ/about-hyperswitch/payment-suite-1/direct-payment-control-model)**:** You utilize Hyperswitch strictly as a secure infrastructure layer (Vault & Pipe). You act as the orchestrator, defining the specific destination yourself, while Hyperswitch securely forwards the payload along with sensitive card data via a Proxy API.

**3.** [**Token First Model** ](https://docs.hyperswitch.io/~/revisions/QSGzCRIrWguIX4tCwjpZ/about-hyperswitch/payment-suite-1/token-first-model-setup)**:** In this model you store the card first during initial checkout without charging the customer and later leverage Hyperswitch’s intelligent core to manage the payment lifecycle.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.