Working principle

The rules of acceptance engine is a powerful and modular applicable unit that adapts the behaviour related to the processing to be performed on each transaction like:

  • Accept
  • Refuse
  • Accept in 3DS
  • Accept with CVV
  • One time Password
  • Alert

This service allows you to define actions to be performed on each transaction from a large list of available attributes: fraud score, holder location, cumulative sales amount over 7 or 30 days, VIP client whiteliste, specific parameter addressed by the merchant...

The transaction processing system is composed of several consecutive steps which rules are always linked together in a pre-set order:

The processing system for a transaction is split into three stages:

1White list:

They make the use of a selective rule.

For example, for identified customers, VIP customers or customers acknowledged as trustworthy that are integrated into a White list, the initially defined rule becomes ineffective.

The service therefore goes on to the next stage.

The “White list” deals with specific customer data, such as the number of their bank card or IP.

2Black list:

Black list makes possible to refuse payments.

As for White list, the Black list deals with the card owner’s specific data (Card, IP, Tel., E-mail).


This step makes possible to draw up specific rules that define the acceptance conditions of a payment.

The processing phases for transactions are always executed in this order.

  • If input data fulfil all the defined conditions of the White list, the Black list phase won’t be executed and the transaction will move directly to the Acceptance phase.
  • If the Black list phase is executed on an operation goes, in case of an input data fulfilling one of the defined Black list conditions, payment will be refused and the Acceptance phase will not be executed.
  • Each phase is executed top down with regard to the payment system actor hierarchy.

The flowchart shows the hierarchical operation of the payment system.
The transaction processing system falls within this logic of actor hierarchy.

Indeed, each "Actor” can define rules for lower entities on which they have rights. Under no circumstances may a lower entity (sub account) define, modify or consult rules dealing with a higher entity.

The rules therefore follow the same hierarchy as actors whose rules are executed bottom up.

Note: rights on rules only apply to levels N to N-1. Financial institutions with agents may therefore not access rules performed by their agents’ traders.