Merchants with 2+ PSPs
Route, fail over or switch providers without moving cards or asking customers to re-enter them.
Card vault · forward to any PSP
Plainvault keeps your customers' cards and forwards them to whichever gateway, acquirer or endpoint you choose. Public pricing, no contract, and free export of your cards whenever you want.
{ "route": "rt_adyen_auth", "body": { "amount": 4900, "card": "tok_7Hq2xVb9Lr4K" } }
{ "amount": 4900, "card": "tok_7Hq2xVb9Lr4K" }
How it works
We don't build PSP integrations one by one. If an endpoint takes an HTTPS request, you can forward to it.
Tokenising is free. Tokens are random and reveal nothing about the card.
→ POST /v1/cards ← tok_7Hq2xVb9Lr4K
Target URL, auth headers or mTLS, and where the card fields go in the payload.
target: api.psp.example/pay auth: header X-API-Key inject: $.card → $.paymentMethod
We swap in the card, forward the request, and pass the PSP's response back unchanged.
→ POST /v1/forward ← PSP response, as-is
The price
Most vaults start at $750–1,000 a month, and many only tell you on a sales call. Here's what each one charges, from their own pricing pages, checked .
"From" figures are the lowest bill each vendor's published prices allow. Usage they don't publish isn't included, so their real bills are likely higher. Details and caveats are on the pricing page.
Who it's for
Route, fail over or switch providers without moving cards or asking customers to re-enter them.
Keep card data out of your systems, and let each seller or region use the gateway that fits.
A vault you don't have to build or certify yourself, with cards you can take with you.
Plain by design
A vault holds your customers' cards, so leaving it should never be expensive. We put that in writing.
Plainvault is in early access and hosted in Singapore. Design partners shape the product, get early access, and keep the published price. Our PCI DSS Level 1 assessment is in progress; read about our security.