Skip to documentation
Browse documentation topics
Documentation / Payments and billing

MAKE THE NUMBERS CLEAR

Cards on file, and how card data is handled

What MegaHub stores when you save a customer's card, and what it deliberately never sees.

Public documentation5 min read
Explore Payments and billing
From invoice to a recorded payment: Payment method → Customer invoice → Payment record → Account review
Workflow illustration · From invoice to a recorded payment

A customer record can carry a card for repeat business, so a dealer who ships every week is not re-reading a card number down the phone each time.

What is actually stored

A token issued by your payment processor, plus the brand, the last four digits and the expiry — enough to show "Visa ending 4242" and to charge against, and nothing else. The token is encrypted at rest and is useless to anybody who is not your processor.

That is not only a privacy preference — it is what keeps MegaHub, and by extension your brokerage's use of it, in the lightest PCI category. A system that handled raw card numbers would pull everyone using it into a far heavier compliance regime.

Tokens belong to one processor

A token is issued by the gateway that created it and cannot be charged anywhere else. If you move from one processor to another, cards saved under the old one stop being chargeable and have to be re-entered by the customer. Your old processor can sometimes migrate tokens for you — ask them before you switch, not after.

Read next

Need a hand with this step?

Tell us what you tried and the result you received.

Contact support