Using Merchant SDK and External Vault

Best for merchants who need to retain a custom UI and external vault but want to drive payments via Hyperswitch.

In this approach, the merchant uses their own SDK and backend, along with an external vault for card storage and tokenization. Hyperswitch is used only for orchestration and connector execution.

The merchant backend sends payment requests to Hyperswitch using tokens issued by the external vault. Hyperswitch forwards requests to PSPs based on configured routing rules.

The Workflow:

• Client: User enters data in Merchant's Custom UI.

• Merchant Backend: Raw Card Data is sent to the Merchant Backend.

• Orchestration: Merchant Backend calls Hyperswitch API with raw card data.

• Proxy: Hyperswitch instantly forwards that data to the configured External Vault.

• Token Storage: The External Vault returns a token. Hyperswitch stores only that token.

• Why choose this? You are a PCI compliant merchant and want to use your own frontend design along with a third party vault, you only want to use the HS connectors.

Documentation: