Appendix F: Transaction Details Fields

Date and time the transaction occurred. The time relates to where the Thredd servers are located, for, GMT timezone for the UK.

Transaction status, such as Settled.

Type of transaction, such as authorisation, balance adjustment, presentment, and auth reversal.

The response code that Thredd provided back to the scheme.

Transaction amount (in the transaction currency).

Bill amount (in the currency of the card).

Settlement amount and currency.

Blocked amount (pending payments) after the transaction.

Available balance after the transaction.

Actual balance after the transaction.

The ID of the network associated with the card on the transaction. For example, Visa, Mastercard, or Discover Global Network (DGN).

The combined value of all fees related to the transaction.

Financial padding applied to transactions in specific MCCs (typically used for hotels and rental cars where cardholders might be charged a little more than authorised for).

Financial padding (to allow for currency fluctuations).

Fixed fees levied against the transaction based on specific amounts.

Rate-based fee. Fees levied against the transaction based on a percentage charge.

Fixed amount to apply as a fee to a domestic transaction.

Percentage of the domestic transaction amount to apply as a fee.

Fixed amount to apply as a fee to an FX transaction.

Percentage of an FX transaction amount to apply as a fee.

Fixed amount to apply to the transaction for non-domestic transactions.

Percentage of a non-domestic transaction amount to apply as a rate fee.

The name of the merchant.

Where applicable, the city where the transaction took place.

Where applicable, the county where the transaction took place.

Where applicable, the postcode where the transaction took place.

Where applicable, the region where the transaction took place.

Where applicable, the street where the transaction took place.

The Merchant telephone number. Can include non-digits. For example, "+18001112345"

The Merchant contact details. For example, a phone number or email address.

Where applicable, the website of the merchant for the transaction.

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.

A unique identifier for a transaction, allowing for tracking and referencing during subsequent interactions, such as inquiries or disputes related to the transaction

Code that describes a merchant's primary business activities. For a full list of available MCCs, see Merchant Category Codes in the EHI Guide.

Merchant’s details.

Time of the transaction as provided by the merchant on the customer’s receipt. This value may differ from the time when the transaction is processed. This is because the transaction might be processed in a different timezone.

For Mastercard authorisation-related messages: This holds additional POS condition codes. For more information, see POS_Data_DE61 field in the EHI Guide.

For Visa Authorisation-related messages: this is empty.

For Financial and all other messages: this is empty

The 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)

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

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

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

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

The code indicating the specific purpose of the message in the message class

Transaction processing code, for example, recurring fees, balance inquiry.

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

The merchant or store where the transaction was made.

The number supplied by Thredd. Retains the original source document of the transaction and assists in locating the source document.

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

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

The settlement group number, used in the Settlement Recap ID data element for the Discover Global Network. Discover members send financial transaction data grouped under recaps

separately for each member.

The currency of the transaction (3 digit ISO currency code).

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

Response data for transactions where the content can differ depending on the network.

For example, for Mastercard, the details it provides depends on the response code only (where it is only populated in the case of a decline). For payment networks such as Visa, this field includes the response for transaction data validations.

For more information, see Visa_ResponseInfo_DE44 in the EHI Guides.

This is extra details on a transaction, which you should not use unless agreed with Thredd.

The Address Verification Service (AVS) response to the transaction. This verifies the cardholder in order to avoid fraudulent transactions by comparing the cardholder inputted address against the address on file.

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

Forwarding Institution Identification Code. Identifies the acquiring institution forwarding a Request or Advice message.

Information on the transaction at the POS terminal, including details such as how the transaction was authenticated, the cardholder present/not present status and fraud details.

Click the expand button to display the Thredd POS Data Decoded Values. The following fields display.

• Cardholder Present

• Card Present

• Card Data Input Method

• Cardholder Authentication Method 1

• Cardholder Authentication Method 2

• Cardholder Authentication Method 3

• Cardholder Authentication Method 4

• Cardholder Authentication Entity 1

• Cardholder Authentication Entity 2

• Cardholder Authentication Entity 3

• Cardholder Authentication Entity 4

• Chip Fallback

• Cardholder to Merchant Security

• 3D Secure Authentication Method

The network that processed the transaction. This field will contain data only if the Network Type is Discover.

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

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

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

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 settlement group date, used in the Settlement Recap ID data element for the Discover Global Network. Discover members send financial transaction data grouped under recaps

separately for each member.

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

Also known as DE48, this a unique transaction number that is generated by the payment network for linking authorisations and presentments.

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)).

Data from the card’s chip.

Mastercard Authorisation Advice Reason Code. Explains why Mastercard Stand-In processing (STIP) occurred or why an advice was created.

This field will only be present for transactions received by Thredd from Mastercard.

A unique Thredd identifier used to link transactions to other tables in the Thredd database.