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 or Bank Account | 1 day $ limit exceeded | A maximum 1-day, aggregate transaction amount is established for a given card or bank account - above which this trigger is hit and reported. This limit does not span merchants |
| 1003L | Card or Bank Account | 3 day $ limit exceeded | A maximum 3-day, aggregate transaction amount is established for a given card or bank account - above which this trigger is hit and reported. This limit does not span merchants |
| 1007L | Card or Bank Account | 7 day $ limit exceeded | A maximum 7-day, aggregate transaction amount is established for a given card or bank account- above which this trigger is hit and reported. This limit does not span merchants |
| 1030L | Card or Bank Account | 30 day $ limit exceeded | A maximum 30-day, aggregate transaction amount is established for a given card or bank account- above which this trigger is hit and reported. This limit does not span merchants |
| 1101L | Card or Bank Account | 1 day # limit exceeded | A maximum 1-day, aggregate transaction count is established for a given card or bank account - above which this trigger is hit and reported. This limit does not span merchants |
| 1103L | Card or Bank Account | 3 day # limit exceeded | A maximum 3-day, aggregate transaction count is established for a given card or bank account - above which this trigger is hit and reported. This limit does not span merchants |
| 1107L | Card or Bank Account | 7 day # limit exceeded | A maximum 7-day, aggregate transaction count is established for a given card or bank account - above which this trigger is hit and reported. This limit does not span merchants |
| 1130L | Card or Bank Account | 30 day # limit exceeded | A maximum 30-day, aggregate transaction count is established for a given card or bank account - above which this trigger is hit and reported. This limit does not span merchants |
| 1201C | Card or Bank Account | Multiple names for one card or account | If TabaPay detects a different name using the same card or bank account and the number of different names exceeds the threshold, 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 passive 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 an 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 reports if you have been subscribed, as it's an optional report. If you would like to begin receiving these reports, email [email protected] with the following email subject: “Subscribe [Client Name] to AML Reports”
3. Do I need to set the thresholds for all of the above triggers?
If you are subscribed to the reports but have not set custom limits, you will have default limits set. Otherwise, you can set custom limits for all of the triggers, except for 1001HT.
To request or inquire about custom or default limit values, email [email protected] with the following email subject: “Triggers for AML Reports for [Client Name]”
Have more questions? Check out our FAQs here and if you still don't have the answer, please reach out to [email protected]
Updated 2 months ago