Recurring billing without storing card numbers
Charge card-on-file tokens from a European PCI DSS Level 1 vault for subscriptions, memberships and instalments — with network tokens and an account updater to keep success rates high, all while staying on SAQ A.
Bill again and again — never hold a card number
A stored token lets you charge a returning customer without keeping the real card. You get reliable recurring revenue, fewer declines and a tiny PCI footprint.
Charge stored tokens
A token represents a saved card you can charge for subscriptions, memberships and instalments.
Network tokens
Network tokens stay current as cards are reissued, lifting authorisation rates on recurring charges.
Account updater
Refresh expired or replaced cards before you bill to cut avoidable declines and involuntary churn.
Stay on SAQ A
Cards are captured by hosted fields into the vault, so your systems stay out of PCI scope.
Any processor
Independent tokens route to your chosen gateway or our acquiring engine — no processor lock-in.
EU custody
Card data lives only in European data centres under PCI DSS Level 1, with GDPR-aligned residency.
From first payment to every renewal
Capture once
The customer enters their card in hosted fields; it goes straight to the vault, which returns a token.
Store the token
Your billing system saves the token against the customer — never the real card number.
Charge on schedule
Send the token to charge for each renewal or instalment; the vault uses the stored card.
Keep cards fresh
Network tokens and the account updater keep stored cards current so renewals don't fail.
Recurring billing, answered
01 How does recurring billing work without storing card numbers?
The customer's card is captured into a PCI DSS Level 1 vault, which returns a token representing a stored card. To bill again, you send the token to charge — the real card number stays in the vault, never in your systems, so card-on-file and subscription payments stay out of PCI scope.
02 Can I keep success rates high as cards expire?
Yes. Network tokens stay current automatically as cards are reissued, and a card account updater refreshes traditional stored cards before you bill. Together they cut avoidable declines and reduce involuntary churn on recurring payments.
03 Does recurring billing keep me on SAQ A?
Yes. Because cards are captured by hosted fields and stored as tokens in the vault, card data never touches your systems. Most merchants running recurring billing this way qualify for the much shorter SAQ A.
04 Can I use my stored tokens with any processor?
Yes. PCI Proxy tokens are independent of any single processor, so you can route recurring charges to your chosen gateway or our acquiring engine — and switch later without re-collecting cards.
Reliable recurring revenue, tiny PCI footprint
Tell us about your subscription and card-on-file flows and we'll map a tokenized setup that keeps you on SAQ A.