Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Data Elements Presence

List of Data Elements in ISO Messages

The following table shows the presence of each field across the four ISO messages.

Field
Description
1100
1110
1120
1130

02

Primary Account Number — Token value

M

C5, C4, C1

02

Primary Account Number — PAN value

M

C5, C4, C1

03

Processing Code

M

—

M

—

04

Transaction Amount

M

—

M

—

07

Transaction Date and Time

M

—

M

—

12

Date and Time Local Transaction

O

C9

O

C9

14

Expiration Date — Token Expiration Date

M

C5, C4, C1

14

Expiration Date — PAN Expiration Date

M

C5, C4, C1

18

Merchant Type

M*

—

M*

—

19

Acquiring Institution Country Code

M*

—

M*

—

22

POS Data

M

—

M

—

23

Card Sequence Number

C6

—

O

—

35

Track2 Data — Token-based PAN + token CVV

O

C3, C4

35

Track2 Data — Accurate PAN + PAN CVV

—

37

Retrieval Reference Number

M

C8

M

C8

39

Action/Response Code — TSP processing result

—

M

M

39

Action/Response Code — Issuer Authorization Response

M

42

Card Acceptor Identification Code

M*

—

M*

—

43

Card Acceptor Name and Address

M

—

M

—

48

Additional Data, Private

M

M

M

M

49

Transaction Currency Code

M

—

M

—

55

Chip Related Data

C2

—

—

—

56

Token Related Data

—

C7

—

C7

64

Message Authentication Code (MAC)

M

M

M

M

Field Presence Legend

Code
Meaning

M

Mandatory

M*

Currently mandatory. Proposal: may be removed or made optional if unused.

O

Optional

—

Not present

C1

Present only when Cloud TSP processed the request without error.

C2

Required when transaction uses a chip payment application (Field 22 pos. 1 = 05, 07 or 08), except for "Type 2" transactions (see section 6.1.1) where presence is optional.

C3

Present when Track2 Data is in the 1100 message. Value is either the echoed PAN from the request or the detokenized PAN.

C4

Must be set to the value of the equivalent parameter present in the 1110 de-tokenization response.

C5

Always present. Value may be either the echoed request value or the PAN-related value from detokenization.

C6

Presence recommended when Field 55 is present (when not present, TSP uses '00' default in cryptographic algorithm).

C7

Presence depends on project business requirements.

C8

Presence depends on project business requirements.

C9

Present in response if present in request; value is verbatim.

Last updated

Was this helpful?