Your customers’ cards,
not your processor’s.
Every card is saved in a secure vault that belongs to no processor. Switch gateways tomorrow, and every saved card still works.
The problem with processor-held cards
Most checkouts save cards inside the processor that took the first payment. That works until you want to leave, or the processor wants you to. Then the cards stay behind, and your customers have to type them again.
A vault that sits outside every processor flips that around. You decide where each payment goes, and every saved card follows your choice.
Why it matters
- A processor closes your account: your customers and their cards stay with you.
- A processor raises its fees: move volume to another one without asking buyers for their card again.
- You add a gateway: it can charge existing customers from day one.
Processor vault vs. your vault
With your vault
- Charge saved cards on any gateway
- Switch processors without asking buyers again
- Add a gateway that can charge existing customers on day one
With a processor vault
- Cards usable only on that processor
- Export depends on their goodwill
- An account closure takes the cards with it
Who it’s for
Questions merchants ask
Who owns the saved cards?
They are saved in a vault tied to your account, not to a processor. Any gateway you connect can use them.
Are you PCI DSS compliant?
Yes. Unlimited is PCI DSS compliant.
Can I charge a returning customer by phone?
Yes. From the customer’s profile, pick a card they already used, record how they agreed, and charge it.
Does it work with PayPal, Klarna or Afterpay?
Those are paid on their own pages, so they are not saved in the vault. The vault is for cards.