> 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.md).

# About Hyperswitch

- [Exploration Guide](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/readme.md)
- [Overview](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/readme-2.md)
- [Payment Suite](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite.md)
- [Payments Suite](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1.md)
- [Orchestrator Model](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/orchestrator-model.md)
- [Hyperswitch SDK + Hyperswitch Vault Setup](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/orchestrator-model/hyperswitch-sdk-+-hyperswitch-vault-setup.md): Best for merchants seeking a pre-built, optimized payment UI backed by the full Hyperswitch stack for secure data storage and routing.
- [Hyperswitch SDK + External Vault Setup](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/orchestrator-model/hyperswitch-sdk-+-external-vault-setup.md): Ideal for teams seeking data independence in a neutral vault combined with Hyperswitch’s optimized payment UI and routing .
- [External SDK and External Vault Setup](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/orchestrator-model/external-sdk-and-external-vault-setup.md): Best for teams with strict existing vault dependencies who want to leverage Hyperswitch for payment routing.
- [Merchant SDK + Hyperswitch Vault Setup](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/orchestrator-model/merchant-sdk-+-hyperswitch-vault-setup.md): Best for PCI compliant merchants requiring full control over UI rendering while leveraging Hyperswitch Vault for secure storage and payment routing.
- [Direct Payment Control Model](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/direct-payment-control-model.md): Best for merchants who do not want to handle card data and want to maintain their current integration with the processors.
- [Using Hyperswitch SDK and Vault](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/direct-payment-control-model/using-hyperswitch-sdk-and-vault.md): Best for merchants who do not want to handle card data and want to maintain their current integration with the processors.
- [Using Merchant SDK and Vault](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/direct-payment-control-model/using-merchant-sdk-and-vault.md): Best for merchants who need to retain a custom UI and maintain their existing integrations with processors.
- [Token First Model Setup](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/token-first-model-setup.md): Best for PCI compliant merchants who wants to store the card during initial checkout phase without charging their customers.
- [Payment Method Management SDK](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/payment-method-management-sdk.md)
- [Roadmap - Q1 2026](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap.md): Jan '26 to March '26
- [Previous Roadmap - Q4 2025](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/previous-roadmap-q4-2025.md): Oct '25 to Dec '25
- [Previous Roadmap - Q3 2025](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/previous-roadmap-q3-2025.md): Jul '25 to Sep '25
- [Previous Roadmap - Q2 2025](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/roadmap-q2-2025.md): Hyperswitch roadmap (Apr to Jun'25)
- [Previous Roadmap - Q1 2025](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/roadmap-q1-2025.md): Jan'25 - Mar'25
- [Previous Roadmap - Q4 2024](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/roadmap-q4-2024.md): Hyperswitch roadmap (Oct to Dec'24)
- [Previous Roadmap - Q3 2024](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/roadmap-q3-2024.md): Hyperswitch roadmap (July to Sept'24)
- [Previous Roadmap - Q2 2024](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/roadmap-q2-2024.md): Hyperswitch roadmap (Apr to Jun'24)
- [Previous roadmap - Q1 2024](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/roadmap-q1-2024.md): Hyperswitch roadmap (Jan to Mar' 24)
- [Previous roadmap - Q4 2023](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/roadmap/roadmap-q4-2023.md): Hyperswitch roadmap (Oct to Dec'23)
- [AI Resources](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/ai-resources.md)
- [Setup MCP Server](https://docs.hyperswitch.io/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/ai-resources/setup-mcp-server.md)


---

# 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.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.