Freedom251 › Payment Tokenization Software
Hyperswitch Card Vault
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Self-Host Community Edition | Self-hosted; manage compliance end to end; 90+ payment integrations; community support | Free |
| Integrate Hyperswitch Cloud | Managed hosting; 210+ payment integrations; SLA-driven support; dedicated account manager | On request |
| Self-Host Enterprise Edition | Self-hosted; 90+ payment integrations; SLA-driven support; dedicated account manager | On request |
As github.com lists them, read 4 Oct 2026. The maker's own page has the final word.
Facts from Hyperswitch Card Vault's own pages
- AWS KMS
- The setup guide describes an AWS-specific KMS feature that adds encryption for keys and sensitive data passed to the vault during startup. · github.com, 4 Oct 2026
- Communication security
- The setup guide describes JWE encryption and JWS signing middleware for communications between tenant applications and the vault. · github.com, 4 Oct 2026
- Community support
- The pricing page lists free support through the public Slack channel and GitHub discussions for the Community Edition. · hyperswitch.io, 4 Oct 2026
- Data protection
- Hyperswitch documents signing card data before transmission, encrypting it to the vault, re-encrypting it with AES for storage, and encrypting the database at rest. · github.com, 3 Oct 2026
- Deployment
- The vault page says it can be deployed by customers on-premises or in the cloud, or used as a managed service hosted by Juspay. · hyperswitch.io, 3 Oct 2026
- Deployment and audience
- The setup guide documents running the vault in Docker or running the executable with Cargo, for teams configuring and operating their own service. · github.com, 4 Oct 2026
- Duplicate prevention
- The repository overview says internal hashing checks are used to avoid data duplication. · github.com, 4 Oct 2026
- Encryption at rest
- Hyperswitch documentation says card data is re-encrypted internally with AES and the database is encrypted at rest. · github.com, 4 Oct 2026
- Flexible data
- The vault is designed to store different types of sensitive information and supports APIs on the /data and /cards endpoints. · github.com, 4 Oct 2026
- Integration options
- The vault can be integrated through an SDK for merchants that are not PCI compliant or directly server to server for PCI-compliant merchants. · hyperswitch.io, 3 Oct 2026
- Key custody
- The optional key custodian feature requires two keys to decrypt the master key before vault functions can run. · github.com, 4 Oct 2026
- Maker headquarters
- Juspay says it is headquartered in Bangalore. · juspay.io, 3 Oct 2026
- PCI scope
- The proxy payment flow is described as reducing PCI DSS scope by keeping raw card data within the vault. · github.com, 4 Oct 2026
- Performance claims
- The product page lists 99.999% uptime, response time under 50 ms, and throughput of 20k+ transactions per second. · hyperswitch.io, 3 Oct 2026
- Processor connections
- Proxy payments are described as working with existing PSP connections without requiring PSP reintegration. · github.com, 4 Oct 2026
- Processor coverage
- The product page states that tokenization is available through 50+ processors and references network tokens across Visa, Mastercard, and Amex. · hyperswitch.io, 3 Oct 2026
- Purpose
- Hyperswitch Card Vault is an open-source Rust service for securely storing sensitive information such as payment card and bank account details. · github.com, 4 Oct 2026
- Security features
- The setup guide describes optional key custodian protection, JWE and JWS encryption middleware, and AWS KMS encryption for keys and sensitive data passed during startup. · github.com, 3 Oct 2026
- Self-hosting setup
- The setup guide documents running the locker in Docker or directly as a Cargo executable, with a database and configuration required. · github.com, 3 Oct 2026
- Standalone service
- Hyperswitch describes its Vault Service as a standalone service for tokenizing and securing customer card data without requiring its payment solutions. · github.com, 3 Oct 2026
- Storage association
- The repository overview says cards are stored against the combination of merchant and customer identifiers. · github.com, 4 Oct 2026
- Tokenization
- The product page describes storing network and processor tokens, raw card details, bank credentials, and wallet credentials. · hyperswitch.io, 3 Oct 2026
- Tokenized proxy payments
- Its proxy payment service can replace vault tokens with card data and forward payment requests to a PSP. · github.com, 4 Oct 2026
- Vaulting and forwarding
- The Vault and Forward API can tokenize and store card details, then route that data to supported processors or endpoints. · hyperswitch.io, 3 Oct 2026
Where Hyperswitch Card Vault stands on Freedom251
- Payment Tokenization Software#3 of 22