Definition
Card on file is a stored payment credential or token used for later authorised payments, with separate storage and transaction-permission requirements.
Card-on-file supports subscriptions, one-click checkout and agreed later charges. Storing a credential does not itself authorize every future charge, and it does not determine whether a payment is cardholder-initiated (CIT) or merchant-initiated (MIT).
Storage and security boundaries
Never retain CVV/CVC after authorization. The PCI Security Standards Council's FAQ prohibits retaining card verification codes after authorization, even encrypted. A saved-card feature must not become a reason to retain that sensitive authentication data.
| Storage model | What the merchant must establish |
|---|---|
| PAN in merchant systems | Applicable PCI DSS controls, permitted use and assessed environment; storage alone does not determine Level 1 or Level 2 |
| PSP vault reference | Where PAN is collected, who can retrieve it, and the provider's supported migration process |
| Network token | Permitted domain, token-requestor/processor compatibility, lifecycle and fallback rules |
PCI SSC guidance makes scope implementation-dependent. A token in the database does not prove that the checkout or surrounding systems never handle card data. Likewise, a provider-specific token does not mean migration always requires every shopper to re-enter their card: supported export, forwarding and re-vaulting arrangements vary.
CIT, MIT and authentication
A shopper clicking Pay with a saved card is a CIT. A merchant collecting a previously agreed subscription without the shopper participating can be an MIT. These require different transaction indicators and evidence of permission; a saved card alone is not proof of an MIT agreement.
For transactions within SCA rules, check the initial setup and subsequent payment flow with the PSP. Do not treat MIT as a generic exemption that can be selected for a shopper-initiated payment, or assume an earlier authentication guarantees liability protection for later charges. The CIT/MIT guide provides the operational distinction.
A saved-card launch checklist
Hypothetical subscription: the customer agrees to a monthly service and saves a card. Keep the agreement and cancellation route, identify the credential's permitted use, send the correct transaction indicators, and define what happens after a decline or token expiry. Include a cancellation control that stops future subscription collections even if the credential remains valid.
Before launch, confirm the provider's storage and migration process, which authentication steps apply, how token updates are handled, and how consent withdrawal reaches the billing schedule. Local rules can add restrictions; neither a token nor an integration SDK is a universal compliance approval.
Continue with tokenization and network tokens for credential selection.