Frequently Asked Question
What are acceptable formats for truncation of primary account numbers?
Acceptable truncation formats vary according to PAN length and Participating Payment Brand requirements.
- A maximum of the first 6 and last 4 digits of the PAN is the starting baseline for entities to retain after truncation, considering the business needs and purposes for which the PAN is used.
- When more digits of the PAN are necessary for business functions, entities should consult the table below for the acceptable formats for each Participating Payment Brand.
PAN / BIN Length | Payment Brand | Acceptable PAN Truncation Formats |
---|---|---|
16-digit PAN (with either 6- or 8-digit BIN) | Discover | At least 4 digits removed. Maximum digits which may be retained: |
15-digit PAN | American Express | At least 5 digits removed. Maximum digits which may be retained: |
<15-digit PAN | Discover | Maximum digits which may be retained: |
When using truncation formats for purposes other than storage, or for PAN lengths not covered within this FAQ, entities should confirm that their format is compatible with each of the applicable Participating Payment Brands. Contact information for the Participating Payment Brands can be found in FAQ 1142 How do I contact the payment card brands?
Access to different truncation formats of the same PAN greatly increases the ability to reconstruct full PAN, and the security value provided by an individual truncated PAN is significantly reduced. Information about the use of different truncation formats of the same PAN can be found in FAQ 1117 Are truncated Primary Account Numbers (PAN) required to be protected in accordance with PCI DSS?
Related
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
Most Recently Updated
-
Are Mobile Payments on COTS (MPoC) solutions, Software-based PIN Entry on COTS (SPoC)™ solutions, or Contactless Payments on COTS (CPoC™) solutions eligible for a P2PE Solution approval?
-
How can an entity meet PCI DSS requirements for PAN masking and truncation if it has migrated to 8-digit BINs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
-
How does encrypted cardholder data impact PCI DSS scope for third-party service providers?
-
Does PCI SSC provide a list of PCI DSS-compliant third-party service providers?