10/21/2025
Welcome to our first weekly Tip Tuesday series where we offer helpful advice and never-before-shared insights to optimize your chargeback management strategy.
Let’s get started.
🧠 HOW TO MATCH AN ALERT TO ITS ORIGINAL TRANSACTION
Each alert comes with information to help you locate the alert’s corresponding transaction in your CRM or order management system.
🟢 The first 6 and last 4 digits of the cardholder’s account number
🟢 The transaction date
🟢 The dispute amount
🟢 The customer name (usually only included with Verifi alerts)
🟢 The acquirer reference number or ARN (usually only included with Verifi alerts)
In most cases, it’s easy to match an alert to the corresponding transaction. But occasionally the information provided doesn’t match anything in your CRM or order management system.
🧠 HERE’S HOW TO TROUBLESHOOT THIS ISSUE:
📌 If you can’t find a transaction on the same date…
Try broadening your search to a couple days before and after the alert date.
The issuer might be using the authorization date instead of the actual processing date. Or maybe your system is tracking the authorization date, but the alert uses the settlement date.
📌 If you can’t find a transaction for the same amount…
Check the currency. You might need to convert the alert currency to the original transaction currency.
Remember “partial amount” disputes are a possibility, and the alert amount could be less than the original transaction amount. For example, if you sold a pair of shoes and a sweater, the cardholder might be disputing only the amount for the shoes.
If you are struggling to match a transaction by alert amount, try matching other variables instead — like the account number.
📌 If you can’t find a transaction with the same account number…
Cardholder account numbers commonly change when a card expires. So it’s possible that the alert and transaction aren’t using the same account number. For example, you might process a transaction with the old account number but receive an alert with the new account number.
Try locating the transaction in your gateway instead of your CRM. If your CRM has already been updated to reflect the new account number but the alert has the old number, your gateway would still have the original number used to process the transaction.
Otherwise, use a different alert data element — such as ARN (if available), cardholder name (if available), date, or amount — for matching.
📌 If nothing matches…
Maybe you are receiving alerts that don’t belong to you. Check back next week for tips on how to manage this issue.
———
Do you have a question you’d like us to answer? Let us know. Help craft our series to include information that would be helpful for your business.