desktopVault SDK Integration

Learn how to tokenize cards at Hyperswitch Vault Service using our Vault/Payment Methods Management SDK

Secure Tokenization using Hyperswitch's PCI Compliant Vault SDK

The Hyperswitch Vault/Payment Methods Management SDK provides a secure solution for merchants to handle and store payment information without the burden of PCI DSS compliance requirements. By leveraging Hyperswitch's Vault service, merchants can securely store customer payment methods (credit cards, digital wallets, etc.) while minimizing their exposure to sensitive payment data.

Key Benefits

  • Simplified PCI Compliance: Reduce your PCI scope by outsourcing the storage of sensitive payment data to Hyperswitch's secure vault

  • Enhanced Customer Experience: Allow customers to save and reuse payment methods for faster checkout experiences

  • Reduced Cart Abandonment: Enable one-click payments for returning customers

  • Secure Token System: Access saved payment methods via secure tokens without handling raw card data

  • Customizable UI: Integrate a pre-built, customizable payment method management interface into your application

Vault SDK Integration Walkthrough

This document provides step-by-step instructions for integrating the Hyperswitch Vault SDK into your application.

1. Server-Side Setup

First, you'll need to set up your server to create payment method sessions, which establish secure connections between your frontend and the Hyperswitch Vault.

Obtaining Your API Keys

Get your API key from the Hyperswitch dashboardarrow-up-right under Developers -> API Keys section. You'll need both your API key and profile ID for server and client integration.

Creating a Payment Methods Session Endpoint

Add an endpoint on your server that creates payment methods sessions. This endpoint will return the necessary session information to your client application:

Note: Please ensure that the customer_id is included in the request body when creating a payment method session. For more details, kindly refer to the APIarrow-up-right reference documentation.

Note: Replace YOUR_PROFILE_ID and YOUR_API_KEY with your actual credentials from the Hyperswitch dashboard.

2. Client-Side Integration (React)

Once your server endpoint is set up, you'll need to integrate the Vault/Payment Methods Management SDK into your client application. The following steps outline the process for a React application.

2.1 Install Required Libraries

Install the Hyperswitch JavaScript and React libraries:

2.2 Add Hyperswitch to Your React App

Import the necessary components and hooks:

2.3 Initialize the Hyperswitch Library

Configure the library with your publishable API key and profile ID:

Security Note: Your publishable key is safe to expose in client-side code, but never include your secret API key in the frontend.

2.4 Fetch Session Details

Make a request to your server endpoint to create a new payment methods session:

Important: Replace "customer_id" with your actual customer identifier to associate saved payment methods with specific customers.

2.5 Initialize the HyperManagementElements Component

Pass the promise from loadHyper to the HyperManagementElements component along with the session details:

2.6 Store a reference to Hyper

Access the hyper-js library in your PaymentMethodsManagementElementForm component by using the useHyper() and useWidgets() hooks.

2.7 Add the Payment Methods Management Elements

Create a PaymentMethodsManagementElementForm component that includes the PaymentMethodsManagementElement:

2.8 Complete Tokenization and handle errors

After rendering the PaymentMethodsManagementElement, you must explicitly confirm the tokenization to save or update a payment method. This is done by calling hyper.confirmTokenization() when the user submits the form.

confirmTokenization() collects the data entered in the Payment Methods Management Element and securely tokenizes it. If additional authentication is required, Hyper automatically handles the redirection flow and returns the user to the provided return_url.

If there are any immediate errors (for example, invalid request parameters), hyper-js returns an error object. You should display this error to the customer so they can retry.

The PaymentMethodsManagementElement embeds an iframe with a dynamic form that displays saved payment methods, allowing your customers to view, manage, and save new payment methods securely.

Last updated

Was this helpful?