AML Transactions (Daily)
This report is generated based on desired thresholds configured by the merchant.
AML Trigger Codes
When these triggers are flagged, they are reported in the AML Transactions and AML Summary reports. These reports list relevant information regarding the suspect transactions including the masked card number, cardholder name, amount, and the associated AML trigger. Merchants are advised to leverage these daily reports to identify anomalous activity for further investigation.
| Trigger | Entity | Event | Description |
|---|---|---|---|
| 1001HT | Transaction | High transaction amount exceeded | A maximum transaction amount is established - above which this trigger is hit and reported - merchant should block and not send above the limit |
| 1001L | Card | 1 day $ limit exceeded | A maximum 1-day, aggregate transaction amount is established for a given card - above which this trigger is hit and reported. This limit does not span merchants |
| 1003L | Card | 3 day $ limit exceeded | A maximum 3-day, aggregate transaction amount is established for a given card - above which this trigger is hit and reported. This limit does not span merchants |
| 1007L | Card | 7 day $ limit exceeded | A maximum 7-day, aggregate transaction amount is established for a given card - above which this trigger is hit and reported. This limit does not span merchants |
| 1030L | Card | 30 day $ limit exceeded | A maximum 30-day, aggregate transaction amount is established for a given card - above which this trigger is hit and reported. This limit does not span merchants |
| 1101L | Card | 1 day # limit exceeded | A maximum 1-day, aggregate transaction count is established for a given card - above which this trigger is hit and reported. This limit does not span merchants |
| 1103L | Card | 3 day # limit exceeded | A maximum 3-day, aggregate transaction count is established for a given card - above which this trigger is hit and reported. This limit does not span merchants |
| 1107L | Card | 7 day # limit exceeded | A maximum 7-day, aggregate transaction count is established for a given card - above which this trigger is hit and reported. This limit does not span merchants |
| 1130L | Card | 30 day # limit exceeded | A maximum 30-day, aggregate transaction count is established for a given card - above which this trigger is hit and reported. This limit does not span merchants |
| 1201C | Card | Name change on card used >1 | If TabaPay detects a different name using the same card and the number of different names exceeds this value, then a trigger is hit and reported |
FAQs
1. Will these limits result in hard stops?
No, the limits set in the AML Transactions report are soft limits that generate alerts when cardholder activity crosses the thresholds you've set. These limits do not result in declined or failed transactions. Your company is still responsible for and expected to implement its own velocity limits.
2. I haven't received a AML Transactions daily report (or I'm not receiving it consistently) but I am receiving my settlement and reconciliation reports. Why?
You will only receive the AML Transactions report when there is something suspicious to report based on the expected activity you've set.
3. How do I make changes to limits I've set for the AML Transactions report?
To make adjustments to the AML monitoring spreadsheet, please email [email protected] with your request, including “AML Report - [MERCHANT]” in the subject line with an updated AML monitoring spreadsheet. If you don't have a copy of the AML monitoring spreadsheet, just let us know in the email and we'll send one over to you for you to complete.
Have more questions? Check out our FAQs here and if you still don't have the answer, please reach out to [email protected]
Updated about 1 year ago