On this page

Identify the value the team wants to save

The Payment Card Industry Data Security Standard (PCI DSS), maintained by the PCI Security Standards Council (PCI SSC), classifies printed card verification codes as sensitive authentication data. Names include CVV2, CVC2 and CID.

FAQ 1280 permits collection before the specific transaction’s authorisation but prohibits later retention, including for recurring payments. Encryption and customer permission do not change that prohibition. An acquirer is the merchant bank.

Sources: PCI Security Standards Council: Selected source provisions read across the data-owner guides: Full FAQ 1280 answer, October 2023: authorisation boundary, recurring/concierge use, encryption, retrievable storage, customer permission and narrow issuing exception

Review the saved-payment promise before accepting it

Fictional example: an operator wants repeat telephone orders and proposes saving the printed code in a customer note. Before approving that design, the payment owner needs a supported alternative process.

The inventory below names business record locations to ask the responsible payment specialist about. It is not a technical search or deletion procedure, and ELN should never receive card data.

Possible retained itemOwner decision
Customer note containing the printed codeRemove the proposed post-authorisation storage from the service design and obtain an appropriate payment process.
Recorded or written order material containing the codeHave the payment owner assess the actual copies and required removal without assuming that “not in the card database” resolves them.
Encrypted stored codeDo not treat encryption as an exception to the post-authorisation prohibition.
A service claiming the code is removed but retrievable laterObtain a qualified assessment of whether it is actually still stored.

Sources: PCI Security Standards Council: Selected source provisions read across the data-owner guides: Full FAQ 1280 answer, October 2023: authorisation boundary, recurring/concierge use, encryption, retrievable storage, customer permission and narrow issuing exception

Keep convenience and permitted data distinct

The FAQ requires complete removal; a process retaining future retrieval needs assessment. Its narrow exception concerns issuers or supporting issuing services with a legitimate issuing business need.

Assign someone to approve what the repeat-payment service retains and obtain the acquirer’s actual instructions. Keep only a description of the unresolved responsibility in the launch plan. Do not copy numbers, codes or recordings into a planning tool to demonstrate the problem.

Sources: PCI Security Standards Council: Selected source provisions read across the data-owner guides: Full FAQ 1280 answer, October 2023: authorisation boundary, recurring/concierge use, encryption, retrievable storage, customer permission and narrow issuing exception

Scope

  • Selected PCI SSC FAQ 1280 only. Actual payment-programme obligations, merchant scope, retained-copy assessment and approved alternative process need the payment provider/acquirer; no technical removal or compliance certification.

Next step

Use Launch planner to assign approval of the repeat-payment data-retention process before offering it. Describe the task only; never put card details, verification codes or recordings into ELN.

Sources & review notes

Access dates show when a source was retrieved. Review dates show when its meaning was checked. Editing this guide does not recheck the law.

Can card verification codes be stored for card-on-file or recurring transactions? FAQ 1280

PCI Security Standards Council

Passage, dates and research notes

standards-body-guidance · Selected source provisions read across the data-owner guides: Full FAQ 1280 answer, October 2023: authorisation boundary, recurring/concierge use, encryption, retrievable storage, customer permission and narrow issuing exception

Accessed: 2026-11-16T20:11:57.931367+00:00 · Meaning reviewed: 2026-11-16T20:24:54.728906+00:00 · Next review target: 2026-12-16

AI-assisted review of actual retained primary body, limited to the selected provisions above and the precise per-page evidence readScope. Source text does not decide actual business coverage, validate a supplier, perform requests or grant general security/privacy/legal clearance. Inaccessible/gated candidates are excluded.

Detailed rule records (1)
A merchant cannot retain verification codes after authorisation Depends on the facts

Do not retain printed card verification codes after authorisation, even encrypted or with customer permission.

When to check: When designing saved-card, recurring or repeat-order services. Source review: 2026-11-16.

Can card verification codes be stored for card-on-file or recurring transactions? FAQ 1280
Your learning

Bookmark this guide or mark it as read.

Learning library
Progress privacy

Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.

This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.