Payments Suite 2.0

Hyperswitch Payment Suites

Hyperswitch offers three distinct integration suites, allowing you to assemble the precise payments stack required for your business model. Whether you need full orchestration, a vault-first proxy, or a standardized UI component, you can mix and match SDKs, backends, and vaults.

1. Orchestration Suite

This suite offers the widest range of architectural choices. You can utilize Hyperswitch’s full frontend and backend, or selectively integrate specific components (like the connectors) while retaining your own merchant backend or external vault.

Supported Stack Combinations :

All combinations include Hyperswitch Connectors/ Payment Routing Logic.

1. Using Hyperswitch SDK with Hyperswitch Vault

2. Using Hyperswitch SDK with External Vault

3. Using Merchant SDK with Hyperswitch Vault

4. Using Merchant SDK and External Vault

5. Using External Vault SDK with Hyperswitch Backend

2. Vault and SDK Solution

This suite is designed for merchants who want to keep their existing processor integrations (e.g., direct calls to Checkout.com or Stripe) but need to remove raw card data from their systems to reduce PCI scope.

The Workflow:

1. Tokenize: Use the Hyperswitch SDK on your frontend to collect card data and receive a secure token (payment_method_id).

2. Construct Request: Your backend constructs the payload intended for your processor, but inserts placeholders (e.g., {{$card_number}}) instead of raw data.

3. Proxy Call: Your backend sends this request to the Hyperswitch Proxy Endpoint, including the target processor's URL in the headers/body.

4. Forward: Hyperswitch swaps the placeholders with the real Card details and forwards the request to your processor.

Supported Stack Combinations :

Does not use Hyperswitch Connectors/ / Payment Routing Logic.

1. Standard: HS SDK (Frontend) + Hyperswitch Vault + Hyperswitch Proxy API for Payments

2. Headless: Merchant SDK (Frontend) + Hyperswitch Vault + Hyperswitch Proxy API for Payments

Best For:

• Merchants with "hard-coded" processor integrations who need a security retrofit.

• Teams needing to minimize PCI compliance overhead without changing their payment provider logic.

3. Payment Method (PM) Experience Suite

This suite is built on a fully native Hyperswitch stack. It utilizes the Hyperswitch PM SDK or PM Management SDK to render the frontend interface, backed by the Hyperswitch Backend and Connectors for robust processing. All sensitive card data is securely stored within the Hyperswitch Vault, while the entire integration is configured and managed directly through Hyperswitch.

Payment Methods Management SDK: Embeds a secure UI element into user settings, handling the lifecycle of saved payment methods (view, add, delete) while maintaining strict PCI isolation.