Action Mapping enables you to customize the business logic associated with Berbix transactions. Action maps enable you to establish business decision to be taken following the completion of a transaction without having to write any code. By default, Berbix includes three actions:
Review transactions populate the
Default review queue.
An Action Map is associated with one or more Templates. Please create multiple templates if you need variable action mapping based on your use case or for testing purposes.
Actions are determined based on the logic defined in Flag Action Mapping. Berbix will prioritize the
reject action over a
review action and a
review action over an
Should I be consuming the flags exposed by Berbix through the API?
The Berbix API exposes the flags associated with transactions in the
flagsfield. This means that you can programmatically consume the flags associated with a transaction. However, we strongly recommend relying on the
actionfield for making business decisions, and leveraging the action mapping functionality to map flags to actions. By leveraging the action mapping functionality, you'll be able to change your mappings without having to do any code change on your end!
ID Flags indicate something of note with the photo ID verification. It doesn’t necessarily imply that the ID is fraudulent. Rather, flags indicate that there is something important to consider when writing systems to accept or reject verifications. These are items such as
A complete list of ID flags that Berbix returns can be found here: ID Flags
Flag Action Mapping lets you customize how the
flags determine the
action to take in your application. These mappings are highly dependent upon your business case and the actions you've defined. We're happy to help you define these mappings based on the best practices for your vertical and use case!
As an example, you may want to automatically
reject transactions that return the
id_under_21 flag if you're selling an age-restricted good.
On the other hand, if you wanted to accept users older than 18 but not those younger than 18, you would map
Sometimes, transactions will have more than one flag associated with them.
When multiple flags are present on a transaction, the one with the highest-priority mapping will determine the action for the overall transaction. As a result, if you'd like to prevent a flag from affecting a transaction's outcome, you should map it to
accept or remove its mapping altogether (by choosing
- in the dropdown menu corresponding to the flag).
Updated 4 days ago