Field Definition DE90 - DE128

Field #90 – Original Data Elements

Field No	Format	Attr
90		n 42

The data elements contained in the original message intended for transaction matching (e.g. to identify a transaction for correction or reversal). It is a fixed length field consisting of 5 data elements:

· Original message type (positions 1 - 4) - the message type identifier of the original message of the transaction being reversed.

· Original systems trace audit number (positions 5 - 10) – the system trace audit number of the original message.

· Original transmission date and time (positions 11 - 20) – the transmission date and time of the original message

· Original acquirer institution ID code (position 21 - 31) – the acquirer institution ID code of the original message (right justified with leading zeroes).

· Original forwarding institution ID code (position 32 - 42) – the forwarding institution ID code of the original message (right justified with leading zeroes).

Field #95 – Replacement Amounts

Field No	Format	Attr
95		n 42

The corrected amounts of a transaction in a partial or full reversal (or the final amounts for the transaction). It is a fixed length field consisting of 4 data elements:

· Actual amount, transaction (positions 1 - 12) - the corrected, actual amount of the customer’s transaction, in the currency of the transaction.

· Actual amount, settlement (positions 13 - 24) - the corrected, actual amount of the customer’s transaction, in the settlement currency.

· Actual amount, transaction fee (positions 25 - 33) - the corrected, actual amount of the fee (in format x + n8) for this customer transaction, in the currency of the transaction.

· Actual amount, settlement fee (positions 34 - 42) - the corrected, actual amount of the fee (in format x + n8) for this customer transaction, in the settlement currency.

Field #98 – Payee

Field No	Format	Attr
98		ans25

A code or ID identifying the payee (recipient) of a payment transaction. This field is used in a payment transaction when the payee is an Institution defined payee. Customer defined payees do not have a payee ID.

When using this field with the NCS Payments Engine, however, it contains the ID of the payee as maintained in the payee list for a cardholder. Because the Payments Engine assigns an ID to both institution and customer defined payees, this field can be used to refer to either type of payee.

Field #100 – Receiving Institution ID Code

Field No	Format	Attr
100	LLVAR	n…11

A code identifying the financial institution that should receive a request or advice. This identification code is used when it is not possible to route a message using the account number field in the message, e.g. in a check verification message. When this field is included in a request or advice, it takes precedence over all account number fields for routing.

Field #102 – Account Identification 1

Field No	Format	Attr
102	LLVAR	n..28

A series of digits and/or characters used to identify a specific account held by the cardholder at the card issuer and if present, shall remain unchanged for the life of the transaction. This field usually contains the description of the "from" account.

Field #103 – Account Identification 2

Field No	Format	Attr
103	LLVAR	n..28

A series of digits and/or characters used to identify a specific account held by the cardholder at the card issuer and if present, shall remain unchanged for the life of the transaction. This field usually contains the description of the "to" account.

When used in payment transactions, this field specifies the bank account number of the payee.

Field #123 – POS Data Code

Field No	Format	Attr
123	LLLVAR	an15

The field is used to identify terminal capability, terminal environment and presentation security data. It is used to indicate specific conditions that were present at the time a transaction took place at the Point-of-Service. This field consists of the following sub-fields:

· The card data input capability (position 1) of the terminal.

Possible values are:

0 – Unknown

1 – Manual, no terminal

2 – Magnetic Stripe

3 – Barcode

4 – OCR

5 – Magnetic Stripe, Key Entry and ICC

6 – Key Entry

7 – Magnetic Stripe and Key Entry

8 – Magnetic Stripe and ICC

9 – ICC

A – Contactless ICC

B – Contactless Magnetic Strip

· The cardholder authentication capability (position 2) of the terminal.

Possible values are:

0 – No electronic authentication

1 – PIN

2 – Electronic signature analysis

3 – Biometric

4 – Biographic

5 – Electronic authentication inoperative

6 – others

· The card capture capability (position 3) of the terminal.

Possible values are:

0 – None

1 - Capture

· The operating environment (position 4) of the terminal.

Possible values are:

0 – No terminal use

1 – On premise of card acceptor, attended

2 – On premise of card acceptor, unattended

3 – Off premise of card acceptor, attended

4 – Off premise of card acceptor, unattended

5 – On premise of cardholder, unattended

· Indicates whether the cardholder is present (position 5).

Possible values are:

0 – Cardholder present

1 – Cardholder not present, unspecified

2 – Cardholder not present, mail order

3 – Cardholder not present, telephone

4 – Cardholder not present, standing authorization/recurring transaction

5 – Cardholder not present, electronic order

· Indicates whether the card is present (position 6)

Possible values are:

0 – Card not present

1 – Card present

· The actual card data input mode (position 7) of the transaction

Possible values are:

0 – Unknown

1 – Manual, no terminal

2 – Magnetic Stripe

3 – Barcode

4 – OCR

5 – ICC

6 – Key Entry

7 – Contactless, ICC

8 – Contactless, magnetic stripe

· The actual cardholder authentication method (position 8) of the transaction.

Possible values are:

0 – no electronic authentication

1 – PIN

2 – Electronic signature analysis

3 – Biometric

4 – Biographic

5 – Manual

6 – Others

· The cardholder authentication entity (position 9) of the transaction

Possible values are:

0 – not authenticated

1 – ICC

2 – Terminal

3 – Authorizing agent

4 – Merchant

5 – Others

· The card data output capability (position 10) of the terminal.

Possible values are:

0 – Unknown

1 – None

2 – Magnetic Stripe write

3 – ICC

· The terminal output capability (position 11) of the terminal.

Possible values are:

0 – Unknown

1 – None

2 – Printing

3 – Display

4 – Printing and display

· The PIN capture capability (position 12) of the terminal.

0 – No PIN capture capability

1 – Device PIN capture capability unknown

4 – Four characters

5 – Five characters

6 – Six characters

7 – Seven characters

8 – Eight characters

9 – Nine characters

A – Ten characters

B – Eleven characters

C – Twelve characters

· The terminal operator (position 13).

· Possible values are:

· 0 – Customer operated

· 1 – Card acceptor operated

· Terminal Type (position 14 and 15)

00 – Administrative Terminal

01 – POS

02 – ATM

03 – Home Terminal

90 – E – commerce – no encryption (no authentication)

91 – E – commerce – FET/3D Secure Encryption: cardholder certificate not used (non authentication)

92 – E – commerce – FET/3D Secure Encryption: cardholder certificate used (authentication)

93 – E – commerce – FET/3D Secure Encryption: Chip Cryptography used: cardholder certificate not used

94 – E – commerce – FET/3D Secure Encryption: cardholder certificate used

95 – E – commerce – FET/3D Secure Encryption: channel encryption (SSL): cardholder certificate not used (non – authentication)

96 – E – commerce – FET/3D Secure Encryption: Chip cryptography used: cardholder certificate not used

21 – Smart Phone

16 – Vending

15 – Public Utility

13 – Franchise Teller

09 – Coupon Machine

07 – Fuel Machine

Field No	Format	Attr
124	LLLLVAR	ans…9999

This data element carries NFC Data. This would be transmitted to the processing system as received from POS Terminal.

Field #128 – Secondary Message Hash Value

Field No	Format	Attr
128	AN	64

This data element carries the message hash value for the message, subject to at least one other secondary data element (DE65 through DE128) being included in the message. The algorithm is SHA-256.

If the message does not contain at least one other secondary data element, the hash value is placed in data element DE64.