- Card On File
Save the Card Once. Charge
It Whenever.
Securely store customer cards through your gateway’s PCI-compliant vault and turn repeat sales into one-tap charges.
Card on File is the saved-card capability that powers fast repeat checkout, recurring
billing, and back-office charges across CloudPay Mobile. Cards are tokenized at the point
of capture and stored in your gateway’s vault — NMI’s vault for NMI accounts, Dejavoo’s vault for Dejavoo accounts. The actual card number never lands in your systems.
Repeat Customers Should Be Faster, Not Slower
Asking a returning customer for their card every visit is slow and slightly insulting. Worse, if you store card data anywhere outside a PCI-compliant vault, you’re absorbing risk that doesn’t belong to you. Card on File solves both: capture the card once, store it through your gateway, and charge it whenever you need to.
Cards are tokenized at the point of capture — through CollectJS for NMI accounts, through the FTD tokenization flow for Dejavoo accounts. The card number itself never lands in your application or your database. What you store is a vault reference, and that reference is what subsequent charges use.
What the Vault Actually Does
Save During or After a Sale
Capture a card during a normal Charge flow with one tap, or save a card directly from the customer profile. Either path goes through the same tokenization.
Multiple Cards Per Customer
Customers can have more than one card on file — useful for households or businesses with separate billing methods. Set a default, view masked card brand and last 4, delete one without affecting others.
Charge a Saved Card in Two Taps
From the Charge screen, attach a customer, pick their saved card, hit Pay. No re-keying, no friction, no opportunity for typos.
Powers Subscriptions and Recurring Charges
Every Subscription charge runs against the customer’s saved card. Same vault, same tokenization, same audit trail.
Works Across Both Gateways
NMI vault and Dejavoo vault are both supported. The merchant experience is identical — your gateway is a back-end detail, not a customer-facing one.
Designed for High-Repeat Businesses
Membership and Subscription Models
Recurring customers who shouldn’t have to re-enter card details every cycle. Cards saved at signup, charged automatically by the Subscriptions feature.
Service Businesses with Repeat Clients
Salons, contractors, consultants. Save the card on the first visit; the second visit is a two-tap checkout.
Deposits and Two-Stage Payments
Take a deposit at booking, charge the balance at completion — both off the same saved card. No second card capture in the middle.
Professional Services Retainers
Save a client’s card during onboarding. Future invoices and ad-hoc charges run against it without recollection.
Faster Repeats. Safer Storage.
Card on File is the easiest way to make repeat customers feel like repeat customers —
and the safest way to store the data behind it.
and the safest way to store the data behind it.