Card on file: how one stored credential changes your questionnaire
By Sam Rivera, Founder, SentinelPanda · September 30, 2026 · 3 min read · PCI DSS
Storing a card is the single decision that most often moves a business off the shortest questionnaire, and it is almost always made for convenience rather than deliberately.
Why "card on file" is a scope question
PCI DSS scope follows the primary account number. Systems that store, process or transmit it are in scope; systems that cannot reach it are not. A one-off sale touches the number for a moment and lets it go. A card on file, by definition, keeps something so the business can charge again later — and the whole question is what that something is.
If it is the card number, you are storing cardholder data and your obligations expand accordingly. If it is a token that only your provider can exchange for a card number, you are storing a reference, and the number lives in their environment, not yours.
The test that actually settles it
Ask whether anyone at your company can retrieve a full card number from any system you operate — the application database, the admin interface, a CRM, an export, a support tool, a backup.
If the answer is a clean no, your provider is holding the data and your scope is correspondingly narrow. If the answer is "only an administrator can", or "it is in an old table we do not use", the answer is yes, and it has been yes for longer than anyone realised.
This is worth testing rather than assuming. Subscription platforms, booking systems and practice-management tools vary enormously in how they handle this, and the vendor's marketing page is not the answer — their security documentation or their own attestation is.
Where stored credentials quietly appear
- Subscriptions and memberships billed monthly, quarterly or annually.
- Deposits and staged payments for trade customers, events or high-ticket orders.
- Hotel and lodging reservations holding a card against incidentals.
- Wine clubs, box schemes and any shipment the customer does not actively reorder.
- Saved payment methods in a customer account, including the ones added before anyone thought about scope.
The failed-charge trap
The highest-risk moment in any card-on-file arrangement is not the storage. It is what happens when a recurring charge declines.
Someone contacts the customer. The customer, being helpful, replies with a new card number — in an email, a text message, a support ticket or a voicemail. From that moment the number is in your mail server, your help-desk product, your phone system and whatever backs them up, and a business that was comfortably in the lightest questionnaire is no longer eligible for it.
The fix is a rule rather than a tool: nobody takes a card number by email, message or ticket, and the only acceptable response is a link to the provider's hosted update page. Write it down, tell the people who handle billing, and audit the inbox occasionally to see whether it is holding.
What to document
Write down which system holds the credential, whether it is a token or a number, who the provider is, and what their attestation covers. Keep their AOC with it.
That single page answers the question for your acquirer and for the next person who owns billing, and it takes an afternoon. Reconstructing it under the pressure of an acquirer review, after a decline wave has already pushed card numbers into three inboxes, does not.