In order to better assist our clients combat AML, TabaPay allows setting controls at our client- and sub-client- levels to block or report suspicious activity.
For more information
Please contact TabaPay for more information
New Pilot API program
All AML controls can be set/changed by talking with your TabaPay agent. For select customers, we are currently piloting a new API to programmatically retrieve information as to the status of your Controls.
For more information: click here.
|Amount Control||Control set by the Client at the Client- and Sub-client levels to specify Push and Pull limits over a number of days (1, 3, 7, and 30). Each control must be explicitly turned on in order to take action against limit-violating PAN (default is off)|
|Card Control (by PAN)||List (one or more) of PANs to be blocked from Push or Pull for a configured number of days.|
|Card Control BIN||List (one or more) of BINs to be blocked from Push or Pull for a configured number of days.|
|Retry Control||Number of consecutive transactions receiving Network Response Codes (in Group A or Group B) after which PAN is blocked.|
Group A - 03, 19, 51, 61, 62, 65, 75, 91, 93, 96, N3, N4, 14, 54, 55, 82, N7
Group B - 04, 07, 12, 14, 15, 41, 43, 46, 57, R0, R1, R3
After 16 consecutive retries receiving a networkRC in Group-A, an excessive retry fee is incurred ( $0.10 / transaction )
Refer to Transaction Integrity - Network Fees for details on Group A and Group B codes.
Please note: In Sandbox TabaPay on returns
Important: Testing TabaControls in Sandbox?
Currently, our Sandbox only returns one network response code:
This means, you have to apply your tests accordingly if you wish to see how controls are set.
- 03, 19, 51, 61, 62, 65, 75, 91, 93, 96, N3, N4, 14, 54, 55, 82, N7 (and all other ISO Response Codes not in Group B.)
- 04, 07, 12, 14, 15, 41, 43, 46, 57, R0, R1, R3
Updated about 4 hours ago