Card Data Record Structure

What a card data record contains

A payment card record is a set of fields with defined formats. The core identifier is the PAN, which carries an issuer identifier, an account identifier and a check digit. Around it sit cardholder-specific elements such as name, address, date of birth and personal identifiers, each with its own format and length rules.

• The PAN is the primary account number
• Issuer identifier is the leading digits
• Account identifier fills the middle
• A check digit closes the number
• Cardholder elements are separate fields with their own formats

The identifier elements

ISO/IEC 7812 defines the identifier structure. The leading digits identify the issuer through the IIN, which is allocated from a range. The following digits are the account identifier, assigned by the issuer. The final digit is a check digit computed with the Luhn algorithm over everything before it.

• The IIN is allocated as a range by the network
• The account identifier is assigned by the issuer
• The check digit is derived, not chosen
• Length varies by network: 13, 15, 16 or 19 digits
• The structure is standardised across networks

Cardholder-specific elements

Name, address, postal code, date of birth, telephone number and personal identifiers are all carried in cardholder records in formats defined by ISO/IEC 7812 and the relevant national standards. Each has a fixed length, character set and validation rule, which is what makes a record machine-checkable rather than free text.

• Each element has a fixed length and character set
• Postal codes follow the country format
• Dates follow a defined representation
• Personal identifiers are validated by check digit or format
• Validation rules are what make records machine-checkable

Validation and record integrity

A record can be checked end to end. The PAN passes the Luhn checksum, the issuer identifier resolves to a known institution, the card level matches the issuer's catalogue and the cardholder elements satisfy their format rules. Each check is independent and catches different classes of error.

• Luhn validates the PAN structure
• Issuer identifier resolves against a current dataset
• Card level must match the issuer catalogue
• Cardholder elements are format-validated
• Independent checks catch different error classes