Message Field and Subfield Conditions

Code

Condition

M

Mandatory

O

Optional

SM

The subfield is mandatory when the field is specified.

02

Mandatory if information is available and not supplied in the Track 2 Data.

03

If supplied in the original Authorisation Request (01XX) or Financial Transaction Request (02XX) message, is mandatory and shall contain the same data.

05

Mandatory if the PAN Entry Mode of F-22 POS Entry Mode == “05” or “07”.

07

At least one of PAN (F2, or F61 subfield Encrypted PAN) or Track 2 Data (F35, or F61 subfield Encrypted Track 2 Data) is mandatory.

PAN is mandatory for keyed/contactless non-EMV Mode transactions (where F-22 POS Entry Mode begins with “01”).

Track 2 Data is mandatory for all transactions except keyed/contactless non-EMV mode transactions (where F-22 POS Entry Mode does not begin with “01”).

When CHD is encrypted using P2PE / DUKPT or other encryption schemes:

• PAN (if required) must be supplied in F-61 Encrypted Cardholder Data (subfield Encrypted PAN), and F2 PAN must be omitted.
• Track 2 Data (if required) must be supplied in F-61 Encrypted Cardholder Data (subfield Encrypted Track 2 Data), and F-35 Track 2 Data must be omitted.

When CHD is not encrypted:

• PAN (if required) must be supplied in F2 PAN.
• Track 2 Data (if required) must be supplied in F-35 Track 2 Data.
• F-61 Encrypted Cardholder Data must be omitted.

08

If F-48 Transaction Context Data subfield CVM Used == “04” (Online PIN):

• For Payment Cards only:
  • PIN must be supplied in F52 Payment Card PIN Data. F-123 Non-Payment Card PIN Data must be omitted.
• For Non-Payment Cards only:
  • When CHD is encrypted using P2PE / DUKPT or other encryption schemes:
    • PIN must be supplied in F-123 Non-Payment Card PIN Data(subfield Encrypted Current PIN). F52 Payment Card PIN Data must be omitted.
  • When CHD is not encrypted:
    • PIN must be supplied in F-123 Non-Payment Card PIN Data (subfield Clear Current PIN). F52 Payment Card PIN Data must be omitted.

09

• When CHD is encrypted using P2PE / DUKPT or other encryption schemes:
  • All PIN values must be supplied in the Encrypted PIN fields of F-123 Non-Payment Card PIN Data. F52 Payment Card PIN Data must be omitted.
• When CHD is not encrypted:
  • All PIN values must be supplied in the Clear PIN fields of F-123 Non-Payment Card PIN Data. F52 Payment Card PIN Data must be omitted.

10

Mandatory if using DUKPT P2PE (F-60 Security Data subfield Encryption Mode must identify the mode of encryption as DUKPT).

13

Mandatory if the reconciliation is not in balance; contains the value calculated by the host.

15

Mandatory in a response message if the original request or advice message was successfully processed by the host.

16

Mandatory in a response message if the data element was present in the original request or advice message. If present, it shall contain the same data as the original message.

17

Mandatory in an advice message if the data element was present in the original request response message. If present, it shall contain the same data as the original request response message.

18

Mandatory in a void request message. If present, it shall contain the same data as the original response message.

21

Either 64 or 128 is mandatory if using DUKPT P2PE (F-60 Security Data subfield Encryption Mode must identify the mode of encryption as DUKPT).

22

Mandatory if a second (non-payment) card participates in the request. (E.g. dual fleet card scenarios.)