Keep cards on file
Keep cards on file for travel bookings: deposits, balances and later charges
Keep a guest's card for deposits, balance payments and charges after the booking. The 3D Secure data stays with the token, so the later charge can carry it. Your system triggers each charge, through each merchant's own provider.
For OTAs and booking engines, PMS and hotel tech and channel managers
In the vault
What a stored card carries
One token for the whole card
Number, CVV, expiry and the 3D Secure result, all behind one token.
The 3D Secure result
Kept with the card, so a later charge can carry it to the payment provider.
CVV kept by your rules
PCI DSS does not allow the CVV to be kept once it has been used. You decide what "used" means, for the whole account or card by card.
Current cards
Network tokens keep a stored card working when the bank reissues it. Update the expiry date yourself at any time.
Charging later
Your system decides when to charge
Any provider
Charge, pre-authorize, capture, refund or void through any of 120+ integrations, with one API.
Backup providers
If a charge fails, we retry through your other accounts, in the order you set.
Insufficient funds
Charges declined for insufficient funds can be recovered through a partner service.
Typical uses
How travel platforms use it
Deposit, then the balance
Take a deposit when the guest books and the balance later, from the same token.
Charges after the booking
Changes, extras and no-show fees, charged to the card already on file.
Refunds
Refund to the original card through the provider that took the payment.
Related: Store cards securely · Charge through any payment provider
Tell us where your cards come from and where they need to go
A solutions engineer reviews your card flows with you and shows you what the integration looks like.