Vault Deployment Models

Choose the right Vault deployment model based on your hosting preference and PCI compliance posture

Juspay Hyperswitch supports multiple vault deployment models to match your PCI profile and infrastructure preferences. The table below summarizes each option; click a row to read the full integration guide.

Deployment Model: Standalone Vaulting Service

Vault Options	PCI Ownership / Scope	Example Use Case
SaaS Hyperswitch Vault	Merchant PCI Environment	Financial institutions requiring full data sovereignty and PCI control with raw payment method responses
SaaS Hyperswitch Vault	Non PCI Scope	Merchants wanting to avoid PCI scope while maintaining existing PSP relationships via Proxy API
Third-Party Vault	Merchant PCI Environment	Merchants already using third-party vault providers like VGS, TokenEx, or similar services

Deployment Model: Self-Hosted Payments Orchestrator with Vaulting Service

Vault Options	PCI Ownership / Scope	Example Use Case
Self-Hosted Hyperswitch Vault	PCI Environment	Large enterprises requiring full control over both orchestration and payment data
SaaS Hyperswitch Vault	Non-PCI	Mid-size merchants needing orchestration flexibility without PCI burden
Third-Party Vault	Non-PCI	Businesses with existing vault investments (VGS, TokenEx) adding orchestration

Deployment Model: SaaS Payments Orchestrator with Vaulting Service

Vault Options	PCI Ownership / Scope	Example Use Case
SaaS Hyperswitch Vault	Managed by Hyperswitch	Growing businesses seeking fully managed payment infrastructure
Third-Party Vault	Shared / External PCI Responsibility	SaaS companies with compliance requirements for specific vault providers

All deployment models share the same payment_method_id token standard and are compatible with the Vault-Then-Pay payment flow.