Your systems only ever hold tokens.
Card data goes from your customer's browser straight into the vault — never touching your servers, your logs, or your database. You store an opaque token, charge it through any gateway you configure, and your processor becomes a setting, not a commitment. PCI scope stays with us.
Free tier · API coming soon · docs.cardvault.com
Five ways in, one way out: a token
Every capture surface ends the same way — card data in the vault, a token in your hands. Pick the level of control your product needs.
REST API
Vault, verify, and charge by token from your backend. JSON in, JSON out.
Embedded fields
Iframe-isolated card inputs inside your checkout, styled to match your UI. Card data posts to the vault, not to you.
Webhooks
Signed event notifications for card lifecycle changes — expired, updated, removed — so your billing logic stays current.
Hosted form & card requests
No-code capture: a vault-hosted page, delivered by link, email, or SMS. Useful as your fallback path even in a full API integration.
Native SDKs
Coming soon — a Windows SDK for JWT-authenticated vaulting and charging from desktop and on-prem software, with signed releases. iOS, Android, and server SDKs to follow.
// Your customer's card was vaulted weeks ago. // Your database holds only this: token = "9F3A-52C1-77AD-0B64" POST /v1/payments/charge/token { "token": "9F3A-52C1-77AD-0B64", "amount": 2500, "currency": "USD" } HTTP/1.1 200 OK { "approved": true, "txId": 91042, "last4": "1111" }
The parts you'd ask about in a design review
Opaque tokens
Tokens have no mathematical relationship to the card number and are scoped to your account. A leaked token charges nothing for anyone else.
Gateway routing
The vault holds the credential; charges route to whichever configured gateway you name. Add or switch processors without re-collecting a single card.
Card-on-file semantics
Initial customer-present setup, then merchant-initiated charges against the stored credential — modeled properly, per card-network rules.
Segments
Partition one vault by property, location, or sub-merchant, with per-segment user access — multi-tenant products map onto it naturally.
Signed webhooks
Lifecycle events carry signatures you verify before trusting — standard shared-secret verification, documented with examples.
Audited operations
Every token operation — create, use, update, delete — is logged and reportable. Your compliance evidence comes with the platform.
Ship payments without inheriting PCI's deep end
With capture, storage, and transmission handled by the vault, card data never enters your environment — integrations that keep it that way can qualify for SAQ A where the eligibility criteria are met, instead of the 250+ question SAQ D. Card Vault itself is assessed against PCI DSS v4.0.1 as a service provider (SAQ D); our Attestation of Compliance is available on request. Details on the Security & Compliance page.
Independent vault, processor-agnostic tokens, and a documented migration path out — the same portability we promise against gateways, we honor ourselves.
Vault a card in the next ten minutes.
Free tier, real API, no sales call. The quickstart takes you from signup to a vaulted test card and a charge by token.
Running the business side instead? Platform overview · Industries