spec 1 linked patterns checked
PCI FAQ on cardholder data storage duration
Documents that stored cardholder data must be limited to necessary purposes, protected under PCI DSS, securely deleted when no longer required, and that sensitive authentication data such as card verification codes is not stored after authorization.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Payment card entry | Choose payment card entry when the task is to charge a card, verify a card, save a card payment method, or replace a card-on-file credential. | Users can type, paste, autofill, delete, select, and correct card number, expiry, CVC, and postal code fields without losing entered values. | PCI SSC supports limiting stored cardholder data and not storing card verification codes after authorization. |
Comparisons supported by this source
- Payment card entry vs bank details vs input mask vs review before submit
PCI SSC supports limiting stored cardholder data and not storing card verification codes after authorization.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: PCI Security Standards Council. Last checked: .