F-123 Reserved Private - Non-Payment Card PIN Data
Description
This field contains Non-Payment Card PIN Data fields.
Note that PIN data fields are classified as Clear or Encrypted:
- Clear fields should only be used when CHD is NOT encrypted.
- Encrypted fields should only be used when CHD is encrypted using P2PE / DUKPT or other encryption schemes. (See F-60 Security Data, subfield Encryption Mode for identification of encryption scheme used.)
This is a TLV (Tag/Length/Value) encoded field, in LLLTLV format.
Attributes
V 999
Format
LLLTLV
Subfield | Description | Tag | Attribute | DUKPT Key | Conditions |
Clear Current PIN | Current PIN of the Non-Payment Card (non-encrypted CHD only). | CCP | ans ..999 (up to overall field capacity) |
|
|
Clear New PIN | New PIN of the Non-Payment Card (non-encrypted CHD only). | CNP | ans ..999 (up to overall field capacity) |
|
|
Clear Confirm New PIN | Confirm New PIN of the Non-Payment Card (non-encrypted CHD only). | CCN | ans ..999 (up to overall field capacity) |
|
|
Encrypted Current PIN | Current PIN of the Non-Payment Card, encrypted by the encryption method identified in Security Data (encrypted CHD only). Note: This data should be encoded in ASCII prior to encrypting. | ECP | b ..999 (up to overall field capacity) | P2PE |
|
Encrypted New PIN | New PIN of the Non-Payment Card, encrypted by the encryption method identified in Security Data (encrypted CHD only). Note: This data should be encoded in ASCII prior to encrypting. | ENP | b ..999 (up to overall field capacity) | P2PE |
|
Encrypted Confirm New Pin | Confirm New PIN of the Non-Payment Card, encrypted by the encryption method identified in Security Data (encrypted CHD only). Note: This data should be encoded in ASCII prior to encrypting. | ECN | b ..999 (up to overall field capacity) | P2PE |
|
On this page
- F-123 Reserved Private - Non-Payment Card PIN Data