> 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/integrations/connectors-integrations/vault-providers.md).

# Vault Providers

Store and retrieve sensitive payment credentials through vault providers integrated with Juspay Hyperswitch.

Juspay Hyperswitch supports external vault providers for storing sensitive payment credentials — card numbers, bank account details — independently of any payment processor. This allows you to retain ownership of tokenized data and route payments across processors without re-collecting credentials from customers.

### Hyperswitch built-in vault vs external vault providers

Hyperswitch ships with its own PCI-compliant built-in vault (`HyperswitchVault`) that handles card tokenization automatically when using the Unified Checkout SDK. External vault providers offer an alternative if you have an existing vault relationship or require vendor-specific tokenization formats.

### Supported Vault Providers

| Provider                     | Vault Type | Description                                                                                                                                       |
| ---------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Hyperswitch Vault**        | Built-in   | Hyperswitch's own PCI-compliant vault. Used automatically by the Unified Checkout SDK. No separate activation required.                           |
| **VGS (Very Good Security)** | External   | External vault with tokenization and proxy capabilities. Integrates via Hyperswitch's ExternalVault interface for insert and retrieve operations. |

### When to use an external vault provider

* You already have card data tokenized in an external vault and want to use Hyperswitch for payment orchestration without re-collecting card details
* Your compliance posture requires a specific vault vendor
* You need proxy-based tokenization (VGS transparent proxy model)

### Activating an external vault provider

External vault providers are configured as connectors in Hyperswitch.

[Steps to activate a connector on the Hyperswitch control center](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md)


---

# 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/integrations/connectors-integrations/vault-providers.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.