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