search
Explore with DeepWikiJoin Slack CommunityContact Us

Payment Method Management SDK

The Hyperswitch 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.

hashtag
Why Integrate the Management SDK?

  • Zero-Footprint Compliance: Captures sensitive data within a secure iframe hosted by Hyperswitch. Your servers never touch raw card numbers, significantly simplifying your PCI DSS compliance journey.

  • Self-Serve Management: Empower your customers to add, update, or delete their own payment methods. This reduces customer support overhead and gives users full control over their billing profile.

  • Frictionless "One-Click" Checkout: Returning customers can checkout instantly using stored credentials, which is proven to reduce cart abandonment.

  • Agnostic Vaulting (No Lock-in): Hyperswitch allows you to store card data in a neutral environment. Unlike processor-specific storage, Hyperswitch tokens can be routed to any supported provider (Stripe, Adyen, Worldpay, etc.).

hashtag
Vaulting Flexibility

Hyperswitch provides the unique ability to choose where your sensitive data lives. You are not forced into a single ecosystem:

  • Hyperswitch Vault: Use our native, secure infrastructure for a seamless, unified experience across all processors.

  • External Vaults: If you already have a preferred third-party vaulting service, Hyperswitch can integrate with it, acting as the orchestration layer to route those existing tokens to any processor.

hashtag
How it Works: The Secure Handshake

The SDK connects your application to the secure storage layer using a three-step flow:

  1. Session Initiation: When a user accesses their "Saved Cards" page, your backend requests a secure session from Hyperswitch linked to a unique customer_id.

  2. Vaulting & Tokenization: When a card is added, the data is encrypted and saved in your chosen vault (Hyperswitch or External). A secure token (e.g., pm_token_123) is returned to your system.

  3. Self-Service UI: The SDK automatically retrieves these tokens and renders them as visual cards. Customers can independently delete expired cards or add new ones entirely within the UI, without any manual intervention from your team.

Integration Documentation :

Last updated

Was this helpful?