2.2 Transaction Matching

OTHER.token=THIS.token

AND

OTHER.traceid_lifecycle = THIS.traceid_lifecycle

For an incremental authorisation, check for a transaction of Txn_Type 'A' arriving with the same traceid_lifecycle as a previous authorisation request. For more information, see What is an incremental authorisation and how do I identify it?)

OTHER.token=THIS.token

AND

OTHER.trans_link = THIS.trans_link

OTHER.mtid=’0100’

AND

OTHER.traceid_lifecycle=THIS.traceid_lifecycle

AND

OTHER.trans_link=THIS.trans_link

AND

OTHER.Ret_Ref_No_DE37=THIS.Ret_Ref_No_DE37

AND

OTHER.TXN_Time_DE07=THIS.TXN_Time_DE07

AND

OTHER.POS_Termnl_DE41=THIS.POS_Termnl_DE41

AND

OTHER.Token=THIS.Token

OTHER.token=THIS.token

AND (if THIS.traceid_lifecycle exists)

OTHER.traceid_lifecycle = THIS.traceid_lifecycle

AND (if THIS.Auth_Code_DE38 exists)

OTHER. Auth_Code_DE38 = THIS.Auth_Code_DE38

AND (if THIS.trans_link exists)

OTHER.trans_link = THIS.trans_link

Note: If neither THIS.traceid_lifecycle or THIS.trans_link is present, then there is no match. Normally traceid_lifecycle will always be present if an authorisation exists.
For most authorisation advices, Auth_Code_DE38 and trans_link will probably be missing.

OTHER.token=THIS.token

AND (if THIS.traceid_lifecycle exists)

OTHER.traceid_lifecycle = THIS.traceid_lifecycle

AND (if THIS.Auth_Code_DE38 exists)

OTHER. Auth_Code_DE38 = THIS.Auth_Code_DE38

AND (if THIS.trans_link exists)

OTHER.trans_link = THIS.trans_link

Note: If neither THIS.traceid_lifecycle or THIS.trans_link is present, then there is no match. Normally traceid_lifecycle will always be present if an authorisation exists.

OTHER.token=THIS.token

AND (if THIS.traceid_lifecycle exists)

OTHER.traceid_lifecycle = THIS.traceid_lifecycle

AND (if THIS.Auth_Code_DE38 exists)

OTHER. Auth_Code_DE38 = THIS.Auth_Code_DE38

AND (if THIS.trans_link exists)

OTHER.trans_link = THIS.trans_link

Note: If neither THIS.traceid_lifecycle or THIS.trans_link is present, then there is no match. If the reversal is due to timeout at the acquirer, THIS.traceid_lifecycle may not exist.

Note: The Auth_Code_DE38 is not mandatory for Visa authorisation reversal transactions and therefore acquirers can choose to send it or not.; In some cases, the auth code is sent in the original request but not in the authorisation reversal. In this case treat Auth_Code_DE38 = '000000' as you would do when it is blank.

OTHER.token=THIS.token

AND (if THIS.traceid_lifecycle exists)

OTHER.traceid_lifecycle = THIS.traceid_lifecycle

AND (if THIS.Auth_Code_DE38 exists)

OTHER. Auth_Code_DE38 = THIS.Auth_Code_DE38

AND (if THIS.trans_link exists)

OTHER.trans_link = THIS.trans_link

Note: If neither THIS.traceid_lifecycle or THIS.trans_link is present, then there is no match. If the reversal is due to a timeout at the acquirer, THIS.traceid_lifecycle may not exist.

This message should be ignored.  It indicates an offline transaction where Thredd has not received a previous authorisation request. See First Presentment for an Offline Transaction.

You will receive the financial notification corresponding to authorisation advice, which has all the information required.

OTHER.Acquirer_Reference_Data_031 = THIS.Acquirer_Reference_Data_031

AND

OTHER.token=THIS.token

AND

OTHER.Txn_Amt=THIS.Txn_Amt

AND

OTHER.Txn_CCy=THIS.Txn_CCy

AND

OTHER. Auth_Code_DE38 = THIS.Auth_Code_DE38

AND

OTHER.POS_Time_DE12=THIS.POS_Time_DE12

AND

OTHER.Ret_Ref_No_DE37=THIS. Ret_Ref_No_DE37

Note: In some cases both OTHER.Auth_Code_DE38 and THIS.Auth_Code_DE38 are not present.

OTHER.Acquirer_Reference_Data_031 = THIS.Acquirer_Reference_Data_031

AND

OTHER.token=THIS.token

AND

OTHER. Auth_Code_DE38 = THIS.Auth_Code_DE38

AND

OTHER.trans_link = THIS.trans_link

Note: In some cases both OTHER.Auth_Code_DE38 and THIS.Auth_Code_DE38 are not present.

As above (see MTID=1240, Txn_Type=’C’)

As above (see MTID=1240, Txn_Type=’C’), except that OTHER (the original to match) will have Txn_Type of ‘C’ or ‘H’)

As above (see MTID=1240, Txn_Type=’C’)

Rule 1: (reliable match if found, Thredd and acquirer matching data)

OTHER.token=THIS.token

AND (if THIS.traceid_lifecycle exists)

OTHER.traceid_lifecycle = THIS.traceid_lifecycle

AND (if THIS.Auth_Code_DE38 exists)

OTHER.Auth_Code_DE38 = THIS.Auth_Code_DE38

AND

OTHER.trans_link = THIS.trans_link

AND

OTHER.TXn_ID = THIS.Matching_Txn_ID

AND OTHER.Txn_CCy = THIS.Txn_CCy

(see notes below )

Rule 2: (run if no match on rule 1, AND THIS.traceid_lifecycle exists. Uses Acquirer matching data only)

OTHER.token=THIS.token

AND

OTHER.traceid_lifecycle = THIS.traceid_lifecycle

AND (if THIS.Auth_Code_DE38 exists)

OTHER. Auth_Code_DE38 = THIS.Auth_Code_DE38

AND OTHER.Txn_CCy = THIS.Txn_CCy

(see notes below too)

Rule 3: (run if no match on rule 1. Uses Thredd matching data only)

OTHER.token=THIS.token

AND (if THIS.Auth_Code_DE38 exists)

OTHER.Auth_Code_DE38 = THIS.Auth_Code_DE38

AND

OTHER.trans_link = THIS.trans_link

AND

OTHER.TXn_ID = THIS.Matching_Txn_ID

AND OTHER.Txn_CCy = THIS.Txn_CCy

(see notes below)

NOTES
1. The above rules are best advice, but there may be some instances where the authorisation and presentment do not match (due to acquirer inconsistencies).

2. OTHER.trans_link may not exist if matching to a MTID=0120.  So rule 2 is useful here.

3. Other fields that should normally match include:

• Txn_Amt (except for tips, partial approval, many-auths to 1 Presentment)

• Proc_Code (but not a 1-to-1 match)

• Merch_ID_DE42

• POS_Termnl_DE41

3. If rule 2 matches and rule 3 does not, (or vice-versa), this indicates an unreliable match. It is up to you if you use the found match or not.

4. Normally traceid_lifecycle will always be present if an authorisation exists. However, if this is a refund, then there will not be an authorisation with a matching traceid_lifecycle.

As above (see MTID=1240, Txn_Type=’N’)

As above (see MTID=1240, Txn_Type=’N’)

As above (see MTID=1240, Txn_Type=’N’)

As above (see MTID=1240, Txn_Type=’P’)

As above (see MTID=1240, Txn_Type=’P’)

As above (see MTID=1240, Txn_Type=’P’)

As 1240 Financial Reversal above (see MTID=1240 Txn_Type=’E’)

Note: If you cannot match on Acquirer_Reference_Data_031 then try matching on traceid_lifecycle and trans_link. If you cannot match on these, then try Auth_Code_DE38 and Merch_ID_DE42.

As 1240 Financial Reversal above (see MTID=1240 Txn_Type=’E’)

Note: If you cannot match on Acquirer_Reference_Data_031 then try matching on traceid_lifecycle and trans_link. If you cannot match on these, then try Auth_Code_DE38 and Merch_ID_DE42.

As 1240 Financial Reversal above (see MTID=1240 Txn_Type=’E’)

Note: If you cannot match on Acquirer_Reference_Data_031 then try matching on traceid_lifecycle and trans_link. If you cannot match on these, then try Auth_Code_DE38 and Merch_ID_DE42.

-

-

-

-

-

Process normally.

Note: if the traceid_lifecycle value matches the traceid_lifecycle value in a previous 0100 authorisation request, then this is an incremental authorisation.  (Normally a single financial, with the same traceid_lifecycle, will arrive in this case.)

Match to the original authorisation request (MTID=0100, Txn_Type=’A’) and process accordingly.

Match to see if an 0100 original message existed (see above matching criteria table.)

• If you find the 0100 original, this is the *same* authorisation. In this case, respond with the original 0100 response (and do not treat this as a new authorisation.)

• If you cannot find the 0100 original, this indicates that you did not receive the original 0100 message. In this case, treat this as a new authorisation, and process as with a 0100 message with Txn_Type=’A’.

Match to the original authorisation request (MTID=0100, Txn_Type=’A’) and process the advice normally. Before blocking any funds you should check the Resp_Code_DE39 field to determine whether the transaction was STIP The card network (Visa and Mastercard) may perform approve or decline a transaction authorisation request on behalf of the card issuer. Depending on your Thredd mode, Thredd may also provide STIP on your behalf, where your systems are unavailable. approved or declined:

• If approved, then replace the existing block for this transaction with a new block for the amount in this advice.

• If declined, then remove the block for this transaction.

• If the processing code indicates a credit, you can optionally choose to not change any blocks.

For more information, see Transaction Matching Guidelines.

Note: If a matching authorisation request exists (that needed to be cancelled), then you will separately receive a reversal (e.g. if the original response to the original authorisation request was not sent to the terminal).

The following fields give more information on the advice:

• Response_Source - indicates the system that sent the response to the authorisation message

• Response_Source_Why - indicates the reason for the message response

• Message_Source - indicates the system that sent the authorisation message

• Message_Why - indicates the reason for the message response

Match to the original authorisation request (MTID=0100, Txn_Type=’A’) and process this reversal accordingly.

Check you have not already received and processed this reversal. If so, ignore it.

Match to the original authorisation request (MTID=0100, Txn_Type=’A’) and process accordingly (unblock the reversal amount)

Note: if the Txn_Amt in the reversal matches the Txn_Amt in the original authorisation request, then this indicates a full reversal. Unblock whatever was originally blocked.  (The Bill_Amt in the reversal may slightly differ to the Bill_Amt in the original due to exchange rate fluctuations.)

Note: it is important to apply any blocks due to an 0120 Auth Advice before applying the 0400 reversal. Never unblock more than was currently blocked due to all the messages for the same transaction set.

For more information, see Transaction Matching Guidelines.

Check you have not already received and processed this reversal. If so, ignore it.

Match to the original authorisation request (MTID=0100, Txn_Type=’A’) and process accordingly (unblock the reversal amount)

Note: if the Txn_Amt in the reversal matches the Txn_Amt in the original authorisation request, then this indicates a full reversal. Unblock whatever was originally blocked.  (The Bill_Amt in the reversal may slightly differ to the Bill_Amt in the original due to exchange rate fluctuations.)

Discard – this is not needed.

(The purpose of this message is to provide a dummy authorisation to match to a financial notification.)

Match to a financial notification (MTID=1240, Txn_Type=’P’ or Txn_Type=’N’) and process accordingly

Process normally.

(Optionally match to a financial notification (MTID=1240, Txn_Type=’P’) or (MTID=1240, Txn_Type=’N’))

Process normally.

(Optionally match to a financial notification (MTID=1240, Txn_Type=’P’) or (MTID=1240, Txn_Type=’N’))

Process normally.

This reverses the effect of a chargeback (e.g., if the chargeback changed the account balance, this reverses the effect on the account balance.)

Optionally match to the chargeback (MTID=1240, (Txn_Type=’C’ or Txn_Type=’H’))

Process normally.

(Optionally match to a financial notification (MTID=1240, Txn_Type=’P’) or Chargeback (MTID=1240, Txn_Type=’H’ / ‘C’)

Match to the original authorisation request (MTID=0100, Txn_Type=’A’) and process accordingly. Note that not all financial notifications will have a matching authorisation.

Process normally.

(Optionally match to a financial notification (MTID=05pp, Txn_Type=’P’) or Chargeback (MTID=1240, Txn_Type=’H’ / ‘C’)

Process normally.

(Optionally match to a financial notification (MTID=06pp, Txn_Type=’P’) or Chargeback (MTID=1240, Txn_Type=’H’ / ‘C’)

Process normally.

(Optionally match to a financial notification (MTID=07pp, Txn_Type=’P’) or Chargeback (MTID=1240, Txn_Type=’H’ / ‘C’)

Match to the original authorisation request (MTID=0100, Txn_Type=’A’) and process accordingly. Note that not all financial notifications will have a matching authorisation.

Match to Auth request (MTID=0100, Txn_Type=’A’) and process accordingly.

Note that not all Financial Notifications will have a matching Authorisation.

Match to Auth request (MTID=0100, Txn_Type=’A’) and process accordingly.

Note that not all Financial Notifications will have a matching Authorisation.

Match to financial notification (MTID=’05’, Txn_Type=’P’ or Txn_Type=’N’) and process accordingly

Match to financial notification (MTID=’06’, Txn_Type=’P’ or Txn_Type=’N’) and process accordingly

Match to financial notification (MTID=’07’, Txn_Type=’P’ or Txn_Type=’N’) and process accordingly

Process normally.

Process normally.

Process normally.

Process normally.

Process normally.