Field Definition DE49 - DE58
Field #49 - Currency Code, Transaction
Field No
Format
Attr
49
n 3
The local currency of the acquirer or source location of the transaction. This is the currency code used for the following amount fields:
· amount, transaction
· amount, transaction fee
· amount, transaction processing fee
Field #50 - Currency Code, Settlement
Field No
Format
Attr
50
n 3
A code identifying the currency of settlement. If this field is not present for a transaction, it is assumed that this field is the same as the currency code, transaction field. This is the currency code used for the following amount fields:
· amount, settlement
· amount, settlement fee
· amount, settlement processing fee
· amount, net settlement
Field #52 – PIN Data
Field No
Format
Attr
52
Hex16
The PIN data field contains the PIN (a number assigned to a cardholder intended to uniquely identify that cardholder) of the cardholder formatted into a 64-bit block and encrypted with a DES key.
Field #53 – Security Related Control Information
Field No
Format
Attr
53
Hex96
Identifies security management information used in the current transaction or specifies security management information to be used in future transactions.
In PIN change transactions, the first byte indicates the PIN to change:
· binary 0 – insecure PIN (e.g. telephone PIN)
· binary 1 – secure PIN (e.g. ATM PIN)
The following 8 bytes of this field contains the new PIN formatted into a 64-bit block and encrypted with a DES key.
In key change transactions, this field contains the encrypted key in the first 8-24 bytes (8 for single, 16 for double, 24 for triple length), followed by a 3-byte key check value (i.e. the first 3 bytes of a clear value of all zeroes encrypted with the key).
Field #54 – Additional Amounts
Field No
Format
Attr
54
LLLVAR
an…120
Information on up to 6 amounts and related account data for which specific data elements have not been defined. Each amount is a fixed length field consisting of 5 data elements:
Account type (positions 1 - 2)
Amount type (positions 3 - 4)
Currency code (positions 5 - 7)
Amount sign (position 8) - "C" or "D"
Amount (position 9 - 20)
When this field is sent by the entity that performed currency conversion this field should contain amounts in the transaction and settlement currencies if they differ.
In a response message from the NCS, this field will always contain the approved amounts and cash amounts, if applicable.
Field #55 – Integrated Circuit Card System Related Data
Field No
Format
Attr
55
LLLVAR
ANS..510
This data element contains EMV data. This EMV data in this data element is structured in the following manner:
<2-or-4-character Tag><2-character length field><variable length data>
The 2-byte or 4-byte tag is an EMV tag (in hexadecimal format) that uniquely identifies the data content of the P-55 fields, and the 2-digit length field defines the length of the variable-length data that follows it. The length specifies the number of hexadecimal values represented in the data part, the actual string is twice as long as the length specifies. The format of the length field is binary converted to a hexadecimal string, e.g., 0x1F would be represented as “1F”. A tag identifying the type of data, followed immediately by a two-digit length (LL) identifying the length of the data, followed immediately by the data itself.
The variable length data for a tag cannot exceed the maximum specified length specified for the data. When the variable length data is longer than the defined maximum length for the tag value, it is truncated. The following table describes each of the EMV tags that can be carried in the P-55 data element, the maximum length for each tag value, the transaction data elements (TDEs) to which each tag is mapped, and flags indicating whether the tag data is required (Y), optional (N), or not applicable (N/A) for requests and responses.
EMV Tag
Description
Max Length
TDE
Required
Request
Response
9F26
Authorization Request
H8
EMV Request
Y
N/A
9F27
Cryptogram Information Data
H1
EMV Request
Y
N/A
9F10
Issuer Application Discretionary data
32
EMV
Y
N/A
9F37
Unpredictable Number
H4
EMV Request
Y
N/A
9F36
Application Transaction Counter
H2
EMV Request
Y
N/A
95
Terminal Verification Result
H5
EMV Request
Y
N/A
9A
Transaction Date
H3
EMV Request
Y
N/A
9C
Transaction Type
H1
EMV Request
Y
N/A
9F02
Transaction Amount
H6
EMV Request
Y
N/A
5F2A
Transaction Currency Code
H2
EMV Request
Y
N/A
82
Application Interchange Profile
H2
EMV Request
Y
N/A
9F1A
Terminal Country Code
H2
EMV Request
Y
N/A
9F34
Cardholder Verification Method Results
H4
EMV Discretional Data
N
N/A
9F33
Terminal Capabilities
H3
EMV Discretional Data
N
N/A
9F35
Terminal Type
H1
EMV Request
N
N/A
9F1E
Interface Device Serial Number
H8
EMV Discretional Data
N
N/A
84
Dedicated File Name
H16
EMV Discretional Data
N
N/A
9F09
Application Version Number
H2
EMV Discretionary Data
N
N/A
9F03
Amount, other
H6
EMV Request
N
N/A
5F34
Application PAN Sequence Number
H1
EMV Status
N
N
91
Issuer Authentication Data
H32
EMV Response
N/A
N
71
Issuer Script
H128
EMV Script
N/A
N
72
Issuer Script
H128
EMV Script
N/A
N
9F6E
Form Factor Indicator (FFI)
H4
EMV Request
N
N
Field #56 – Message Reason Code
Field No
Format
Attr
56
LLLVAR
n..4
A code that provides the receiver of a request, advice or notification message with the reason, or purpose of that message.
For original authorizations and financial transactions, it identifies why the type of message was sent (e.g. why an advice versus a request); for other messages, it states why this action was taken.
1003
Card issuer unavailable
1006
Under floor limit
1376
PIN verification failure
1377
Change dispensed
1378
IOU receipt printed
1510
Over floor limit
1800
Negative card
4000
Customer cancellation
4001
Unspecified, no action taken
4004
Completed partially
4021
Timeout waiting for response
For place hold on card transactions, in Issuer File Update Advice (0322) or Administration (0600/0620) messages, it states why a card should be put on the hotcard list:
3000
Lost card
3001
Stolen card
3002
Undelivered card
3003
Counterfeit card
3700
Lost PIN
If a hold response code has not been specified in these transactions, the message reason code field will be used to determine which hold response code to use for the transaction. A message reason code of "3001-Stolen card" will result in a hold response code of "43-Stolen card", otherwise "41-Lost card" will be used.
In the case of a message to bank transaction, the message reason code specifies the type of message the cardholder wants to forward to the issuer. Note that in this case, the message reason code field is treated as a free-format field that the user can use for any user specific code.
Message reason codes are defined in the ISO 8583 (1993) specification, and this specification has been used as basis for the codes defined here.
Field #58 – Authorizing Agent Code
Field No
Format
Attr
58
LLLVAR
n…11
A code identifying the authorizing agent institution.
Last updated
Was this helpful?