8 Viewing Transactions

The type of transaction, such as an authorisation or presentment.

The unique token number associated with the transaction.

The expiry date provided at the time of the transaction (useful to check in case the cardholder has entered an incorrect expiry date).

How the transaction was created, for example, contactless at a machine, ecommerce, online, ATM. ICC indicates the card was physically inserted into a machine and the PIN entered.

The Network Reference ID (NRID) is a numeric ID generated by DCI and remains unchanged for the life of the Card Transaction.

The date of the transaction. Format YYYY-MM-DD HH:MM:SS:MS.

The Message Reason Code data element provides the receiver of a request, advice or notification message with the reason, or purpose, of that message.

The status sent back to the merchant, for example, 05 - do not honour. Click the arrow next to this field to see more information.

System Trace Audit Number. This links the authorisation and presentment (note this number is not unique).

Indicates the type of transaction, for example, a debit.

Contains additional amount information for the transaction, if relevant. For example, for purchase with cashback transactions, the additional amounts field will be present with the cashback amount.

Code relating to the specific Point of Sale (POS) terminal.

Merchant’s details.

Visa’s Additional Response Data, exactly as provided from Visa to Thredd. This will only be present for transactions received by Thredd from Visa Base1, if DE44 was present.

It provides information on Visa’s validation checks of data in the message. This will only be set for Visa online authorisation transactions.

Time provided by the merchant (can be incorrect but matches what is on the receipt).

Uniquely identifies the terminal which accepted the card. Always present if the card data was read by a terminal.

Indicates which system sent the 0110 or 0210 response to the terminal. Normally present only for some Authorisation advices and Authorisation reversals.

Indicates the reason why the Response Source sent a response to the terminal. Normally present only for some Authorisation advices and Authorisation reversals.

Identifier for tracing a specific transaction and narrowing a search. This a unique identifier generated by Thredd to help identify and search for transaction in the Thredd platform.

Transaction amount and currency.

Settlement amount and currency.

Amount applied to the account in the currency of the card.

Code that describes a merchant's primary business activities.

A unique reference to the transaction assigned by the acquirer. All messages related to the same transaction (reversals, presentments, chargebacks) should have the same RRN; however, this may not be enforced.

Acquirer Reference Number/Data. ISO 8583 field 31.

The acquirer reference number exists for clearing messages only (Financial advices/notifications, and Chargeback advices/notifications (and reversals of)).

Acquirer ID found in the Acquirer Reference Number (ARN). Provided for financial messages only.

Acquiring Bank ID as assigned by the network. Note that the format differs depending on whether this is an Authorisation or a Financial type message.

For Authorisation messages:

• 2 digits length of Acquirer ID (01 to 09)

• Acquirer ID

For Financial messages:

• 6 digit Acquirer ID (possibly with leading zeros)

Identifies the acquiring institution forwarding a Request or Advice message.

Authorisation code generated by Thredd for approved and declined authorisation requests.

The network that processed the transaction.

The time when Thredd receives this authorisation, in the local time zone of the Thredd servers.

The time when Thredd sends the response (the difference between the request and response times is shown below in milliseconds), in the local time zone of the Thredd servers. Note that the response time in milliseconds is the time for the entire transaction to complete across all parties.

The difference, in milliseconds, between the request time and the response time of the transaction.

Data from the card’s chip. Click the arrow next to this field to see more information, for example, you can check whether the online and offline PINs were verified when making a transaction.

Information about 3D Secure (payer authentication) for online transactions. Click the arrow next to this field to see more information.

Shows any fees applied to this transaction.

The Function Code data element is the code indicating the specific purpose of the message within the message class.

This field contains the data to support transaction-level information when a Service Establishment assesses a surcharge on a Card Sale.

This data element contains multiple tags with unique functions. Please refer to the table for details.

The Transaction Destination Institution Identification Code (IIC) data element is the code identifying the institution that is the transaction destination.