1.3 Transaction Matching

All transactions reported to Thredd via the card schemes (Visa and Mastercard) are included in both the EHI The External Host Interface provides a facility to enable exchange of data between Thredd and external systems via our web services. All transaction data processed by Thredd is transferred to the External Host side via EHI in real time. For certain types of transactions, such as Authorisations, the External Host can participate in payment transaction authorisation. data feed and transaction XML reports. You can use the information in the XML reports to match and reconcile against data received via EHI, check for any duplicate records, and match authorisation records (e.g., authorisation advices and authorisation reversals) to financial records (e.g., presentments and chargebacks).

1.3.1 Matching Authorisations to Financial Records

Within the transaction data reports, you can use the following fields to match records:

Field Type	CardAuthorisation Record	CardFinancial Record
Unique identifier of an authorisation transaction	AuthId	AuthId
Approval code generated by the issuer and printed on the receipt	ApprCode	ApprCode
Unique identifier of a financial record	-	FinId
Unique identifier of a presentment record	-	PresentmentId

You can use the following fields to match Transaction XML records to EHI records:

Field Type	Transaction XML Record	EHI Record
Unique identifier of the card linked to the transaction	PAN	Token
Unique identifier of an authorisation transaction	AuthId	TXn_ID
Unique identifier of a financial record	FinId	TXn_ID

For details of EHI fields, refer to the External Host Interface (EHI) Guide.