Stored cards that never go stale
A saved card quietly decays — it expires, it gets reissued after a breach, the number changes and the next charge fails. Acquira replaces the raw number on file with a network token that the card networks keep current, so your repeat customers keep paying without lifting a finger.
From number on file to a credential that keeps itself current
A network token is not a copy of the card — it is a credential issued by the network, tied to your customer and your business, that the issuer trusts more than a bare card number. Here is the path a saved card takes once it becomes one.
Card saved at checkout
A customer chooses to save their card for next time. Nothing about that moment changes for them — the same one-step checkout, the same confirmation.
Consent capturedProvisioned as a network token
Acquira asks the card network to issue a token for that card, scoped to your business. The raw number is never the thing you charge again.
Token issuedAuto-updated on reissue
When the card expires or is reissued, the network refreshes the token in the background. The credential you hold stays valid without a single customer action.
Credential refreshedAuthorizes at a higher rate
Each subsequent charge runs on the token, which issuers approve more readily than a stored number — so repeat payments clear more often than the very first one did.
Higher approvalThe repeat charge that beats the first
Issuers treat a network token as a stronger, fresher credential than a card number sitting in your database. Because the network vouches for it and keeps it current, the bank approves it more readily — and it survives the events that quietly kill stored cards.
- Survives expiry and reissue — refreshed by the network, so a renewed card keeps charging.
- Higher authorization rate — issuers approve tokens more readily than a stored number.
- No re-entry for the customer — repeat purchases and subscriptions just keep working.
- Works across your routes — the same token authorizes wherever Acquira sends the payment.
Same customer, same card — two very different outcomes
The only thing that changes is what you store and re-present to the issuer. One ages; the other keeps itself current.
Raw card on file
You store the bare card number and re-present it on every charge. It works until the day it does not — the card expires, gets reissued, and the next payment is declined for a reason the customer never sees coming.
Network token
You store a token the card network keeps alive. When the card is reissued, the token is refreshed for you — so the same customer keeps paying, and the issuer approves the charge more often because the credential is current and trusted.
Renewals that used to fail, quietly clearing
The payments most likely to break are the ones you never see your customer make — the silent subscription renewal, the saved-card reorder, the next installment. When those run on a network token, a reissued card no longer ends the relationship: the token is updated and the charge simply goes through.
- Renewals keep their cadence instead of lapsing on a card change.
- Recovered renewals are labelled so you can see what the token saved.
- Fewer dunning emails because fewer cards fall out from under you.
What tokens do to repeat payments
Questions about tokenizing saved cards
Is a network token the same as the card number?
No. A network token is a separate credential issued by the card network, scoped to your business and your customer. The real card number is not what you re-charge — you charge the token. That is what lets the network keep it current and what makes it harder to misuse if it ever leaks.
What happens when a customer's card is reissued?
The network updates the token in the background. The credential you hold stays valid, so the next charge — a renewal, a reorder, an installment — clears without asking the customer to re-enter anything. The card change that would normally cause a decline becomes invisible to both of you.
Do my repeat customers have to do anything?
Nothing. Saving the card at checkout is the only step they take, and it looks exactly as it does today. From then on, tokenization, refreshes and the higher approval rate happen behind the scenes — your customers just keep paying as if nothing ever changed about their card.
Turn your saved cards into credentials that keep paying
Book a revenue review and we will estimate the repeat-approval lift hiding in your stored cards — and the renewals a token would have saved.