> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/~/revisions/QSGzCRIrWguIX4tCwjpZ/about-hyperswitch/payment-suite-1/payment-method-management-sdk.md).

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

#### 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.).

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

#### 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 :** 

* [PMM SDK integration Guide](https://docs.hyperswitch.io/~/revisions/0suhZ1q0uwhOXBI31wWf/explore-hyperswitch/payments-modules/vault/payment-methods-management-sdk)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperswitch.io/~/revisions/QSGzCRIrWguIX4tCwjpZ/about-hyperswitch/payment-suite-1/payment-method-management-sdk.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.