1.3 Transaction Matching

All transactions reported to Thredd via the card schemes (Visa, Mastercard, MNE, and Discover) are included in the Clearing Report and the Non-Clearing Report, as well as 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. You can use the information in these reports to match and reconcile against data received via EHI, check for any duplicate records, and match authorisation records. When matching authorisation records, you can match advices and reversals to financial records (for example, presentments and chargebacks.)

1.3.1 Matching Authorisations to Financial Records

You can use the following fields to match records in each of the reports:

Field Type	Non-Clearing report: CardAuthorisation Record	Clearing report: 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
Information for uniquely identifying a transaction	Trace	-

You can use the following fields to match transaction records in the reports to EHI records:

Field Type	Transaction Report Record	EHI Record
Unique identifier of the card linked to the transaction (available in both the Clearing Report and the Non-Clearing Report)	PAN	Token
Unique identifier of an authorisation transaction (available in both the Clearing and Non-Clearing Report)	AuthId	TXn_ID
Unique identifier of a financial record (available in the Clearing Report)	FinId	TXn_ID

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