Appendix F: Transaction Details Fields

Bill amount (in the currency of the card).

Transaction amount (in the transaction currency).

The accumulated total fee for the transaction. This includes any MCC Padding, FX Padding, Fixed and Rate fees.

The name of the cardholder.

The last eight characters of the masked PAN.

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

The expiry date of the card.

The product name the card is associated with.

The scheme the card is associated with. For example, Mastercard or Visa.

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

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

Transaction status, such as Settled.

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.

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

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 surcharge fee for the transaction.

Contains additional amount information for the transaction, if relevant. For example, for purchase with cashback transactions, the additional amounts field is present with the cashback amount. For more information, see Additional Amount field in the EHI Guide.

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"

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

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

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.

Identifies the card acceptor (such as merchant, ATM owner, or financial institution) and the point of interaction for the transaction.

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 time zone.

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

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

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

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.

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 address input by the cardholder 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

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.

The merchant's Tax ID (from Base II TCR6 31-50 (len 20), Mastercard GCMS - from IPM DE48 PDS 596 subfield 1) is the unique code assigned to a business by the processor or acquiring bank.

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

Unique Thredd identifier of the payment token. Only present if transaction relates to a payment token (for example, Apple Pay).