> 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/0suhZ1q0uwhOXBI31wWf/explore-hyperswitch/payments-modules/vault.md).

# Vault

Hyperswitch Vault Service is a standalone vault that allows you to tokenize and secure your customers' card data in our PCI-compliant vault without having to use our payment solutions.

With Hyperswitch Vault, you can:

* Use our PCI-compliant **Vault SDK** to collect and store card data securely, ensuring sensitive information never touches your systems.
* **Tokenize** cards across multiple payment processors through a **single unified API**.
* Generate **Network Tokens** to optimize payment operations and reduce costs with **automatic network token creation and updates**, powered by Juspay’s certified **Network Token Requestor** capabilities.

### Why Hyperswitch Vault?

#### Seamless and Universal Tokenization

* **Universal PSP Tokenization** – Store card data once and tokenize it instantly across **50+ payment providers**.
* **Network Token Management** – Increase transaction success rates and reduce interchange fees with **automatic network tokenization**.
* **Customizable Vault SDK** – Securely collect card details with **ready-to-use UI components**.
* **Flexible Token Generation** – Supports both **single-use and multi-use tokens** for various payment scenarios.

#### Security and Compliance – Zero Maintenance

* **PCI DSS v4.0 Certified** – Industry-leading payment security compliance.
* **ISO 27001:2022 Certified** – Global standard for information security management.
* **GDPR Compliant** – Ensures full compliance with EU data protection regulations.
* **SOC 2 Type II Compliant** – Stringent security controls for enterprise-grade safety.
* **256-bit AES Encryption** – Bank-grade encryption to protect stored data.

#### Enterprise-Grade Performance

* **99.999% Uptime SLA** – Highly reliable service availability.
* **Scales to 50,000 Transactions Per Second (TPS)** – Designed for high-volume transactions.
* **Sub-50ms Response Time** – Optimized for ultra-fast token generation and retrieval.

**Proxy Payments support for PCI compliance**

* **No PSP re-integration needed -** Use tokens stored in Vault to make direct API calls to PSPs. Hyperswitch intercepts, detokenizes, and securely forwards requests—no need to modify existing PSP integrations or handle raw card data
* **PCI DSS scope reduction** – Raw card data stays within Vault
* **Centralized token management** – One vault, many PSPs

### How does it work?

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfjHOvBRI1bfnMRf5zmWz9_yw4ieV0v5IEJUwhnBwu6iqxoI2yvHE-gfZ-du--dwemuLMv9AemXN5k0BubnmF0fqwO8gtGCyuRBT2L5DQW5DiFYgZmZpEEgSVXHJW1hTjqZJf4S?key=wWT-6TmmgS7GMTZGEfcB38Ke" alt=""><figcaption></figcaption></figure>

#### 1. Initial Vault Setup

* The **merchant server** sends a vaulting request with **tokenization preferences**.
* The **Vault server** responds with a **secure session ID** and **client secret**.
* All communication is **protected with end-to-end encryption**.

#### 2. Secure Card Capture

* The **Vault SDK** is initialized with **merchant credentials and session details**.
* Customers enter their **card details** using **secure SDK components**.
* Card data is transmitted **directly to the Vault server**, ensuring it never touches merchant systems.

#### 3. Vault Storage and Primary Tokenization

* Card data is **encrypted using bank-grade encryption** and stored in a **PCI-compliant vault infrastructure**.
* A **unique vault token** is generated as the primary reference for future transactions.

#### 4. PSP and Network Token Generation

* **Automated PSP-specific token creation** on demand.
* **Network tokens** are generated where supported (**Visa, Mastercard**).
* **Intelligent token mapping** and **lifecycle management** ensure seamless token utilization.
* **Continuous monitoring and automatic token updates** improve security and reliability.

#### 5. Flexible Payment Processing

* Use **vault tokens** directly with **PSP endpoints** or through **Hyperswitch**.
* Supports **recurring, one-time, and marketplace payments**.
* **Real-time token status tracking and updates**.
* **Automatic card updates** and **network token refreshes**.

### How to Integrate Vault?

Hyperswitch Vault offers integration options tailored to different security and compliance needs.

#### **For Non-PCI Compliant Merchants**

Quickly integrate the **secure Vault SDK -** [**Learn how to**](/~/revisions/0suhZ1q0uwhOXBI31wWf/explore-hyperswitch/payments-modules/vault/vault-sdk-integration.md)

* Collect card details without handling sensitive data.
* Maintain **full PCI compliance** without additional certification.

**For PCI Compliant Merchants**

**Direct server-to-server integration** for greater control - [**Learn how to**](/~/revisions/0suhZ1q0uwhOXBI31wWf/explore-hyperswitch/payments-modules/vault/server-to-server-vault-tokenization.md)

* Securely send card data from your **own infrastructure** while maintaining existing security workflows.

### **Using Vault for Proxy-Based Payments**

Send payments to PSPs using Vault tokens without handling raw card data - [Learn how to](/~/revisions/0suhZ1q0uwhOXBI31wWf/explore-hyperswitch/payments-modules/vault/hyperswitch-vault-pass-through-proxy-payments.md)

* Hyperswitch intercepts requests, detokenizes on the fly, and securely forwards them—no changes needed to existing PSP integrations.

{% content-ref url="/pages/PWmlnVG825MXgAU2L6MF" %}
[Intelligent Routing](/~/revisions/0suhZ1q0uwhOXBI31wWf/explore-hyperswitch/payments-modules/intelligent-routing.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/~/revisions/0suhZ1q0uwhOXBI31wWf/explore-hyperswitch/payments-modules/vault.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.