Integration

Two integration paths for storing payment methods in Juspay Hyperswitch Vault: Server-to-Server API or the Vault SDK

Juspay Hyperswitch Vault supports two integration paths. Choose the one that matches your architecture:

Server to Server

Your backend directly calls the Vault REST API with raw card data. Requires your own PCI DSS compliance to handle card data on your servers.

SDK (Vault SDK)

Card data is collected and tokenized entirely within Hyperswitch's PCI-compliant SDK iframe — no raw card data touches your servers.

Prerequisites (both paths)

Before integrating, complete the following on the Hyperswitch Control Centre:

1. Generate your Vault API Key and note your Profile ID — see Vault Configuration.

2. Create at least one Customer record in the Vault so that saved payment methods can be associated with a customer_id.

Which path should I use?

	Server to Server	SDK
PCI scope	You handle raw card data → full PCI DSS required	Hyperswitch iframe handles card data → minimal PCI scope
Frontend dependency	None — pure backend API calls	Requires loading HyperLoader.js or the React/npm packages
Best for	B2B flows, migrations, batch tokenization, existing PCI-certified merchants	Consumer-facing checkout, fastest time-to-market
Customer-facing UI	Build your own	Pre-built, customizable Payment Methods Management widget