Are you ready?
In this tutorial we are going to learn how to set up the blacklist rules for direct debit and card transactions.
When blacklist is enabled, traditionally, the following response codes/messages are received:
1) E05 (“Bank account is blacklisted”)
for direct debit transactions;
2) E06 (“Card is blacklisted”)
for payment card transactions.
However, you can change the message associated with this code.
Once a card/account number is marked as blacklisted, the transactions made with this card/account never get submitted/re-submitted to a processor. If the situation requires, this card/account number can be removed from the blacklist.
To work with the blacklist, proceed as follows:
1. Set a list of the response codes that are going to be blacklisted.
2. Set a blacklist policy for a certain type of transactions (direct debit, credit card or both). The policy can be set up at the following levels:
- at the portfolio level - if the blacklist policy has to be enabled for all the merchants under a particular portfolio; when set, the settings are applied to the new merchants only.
- at the reseller level - if the blacklist policy has to be enabled for all the merchants under a particular reseller; when set, the settings are applied to the new merchants only.
- at the merchant level - if the blacklist policy has to be enabled for a particular merchant.
Note that an overriding mechanism influences the blacklist policy settings within the gateway. To learn more about the overriding mechanism, review this
3. Сheck which card/account number has been blacklisted.
4. If you want a particular card/account number to be removed from a blacklist, you can do it manually on the user interface. To make a bulk remove of the blacklisted card/account number, address the issue to the gateway support.
We will use the following parameters as an example (this value is used for training purposes within this tutorial only):
Blacklist policy: ACH
Account #: 4099999992