RevenueProtect includes several checks that allow you to use scores and results from other third-party risk mitigation systems.
Contact Support Team to turn on these checks and coordinate with the third-party.
Airline Perseuss External Referral Check
Perseuss is an airline-specific risk mitigation system. You can call perseuss and receive a risk score for the transaction, which affects the Adyen risk score.
- Provide your perseuss API token, username, and password.
You must have a perseuss account configured to use this function.
- Set a score to incre. The rule triggers if the risk score from perseuss exceeds that value. For example, if the perseuss score threshold is configured with 60, and the rule itself is configured with 40, if perseuss replies with a score of 65 for a transaction then the Adyen risk score for the transaction increases by 40.
Brazil CPF Check
The Cadastro de Pessoas Físicas (CPF) is the national tax registry in Brazil. This check allows merchants with Brazilian transactions to check the shopper's credentials against the CPF database.
Note that some of the data points used for this check (e.g. phone number) are optional values in the payment requests. In order for this check to work properly, a complete set of shopper data should be submitted in the payment request.
There are multiple sub-checks associated with this risk rule. Each allows for an individually configurable score to be added to the transaction score if the rule matches.
The checks are as follows:
- Invalid CPF: The shopper-submitted CPF is not a valid CPF number.
- Names not matching: The name associated with the transaction does not match with the name in the CPF database.
- Addresses not matching: The billing address associated with the transaction does not match that in the CPF database.
- Phone numbers not matching: The phone number associated with the transaction does not match that in the CPF database.
German SCHUFA Check
SCHUFA (Schutzgemeinschaft für allgemeine Kreditsicherung) is a German private credit bureau. Adyen's Risk management allows merchants with German SEPA transactions to check shoppers credentials against the SCHUFA database.
Some of data values are usually optional in payment requests (e.g.
billingAddress), but are required for this check to work properly. The
billingAddress fields are mandatory for the SCHUFA check, while providing
gender and similar information is optional (though highly recommended). Submit all the required data fields to use this check and achieve a more accurate risk score.
The risk rule has several filters, so that you can target only high-value/high-risk transactions:
Transaction Euro amount: You can indicate an amount threshold, so that only SEPA payments above the specified threshold are checked. This field's value is measured in minor units.
- Pre-authorization total risk score: Most risk rules run prior to the authorization request. Specify a threshold value for this field to initiate the SCHUFA check only when the pre-auth risk score exceeds this threshold value.
SCHUFA responds with a value associated with a shopper. The risk rule allows you to specify two separate thresholds, with a corresponding risk score for each. If both are applicable based on the SCHUFA response, the highest of these scores is used for the risk rule.
For example, in the given configuration a response of A or above is set to give a score of 10, while a response of E or above is set to give 20. With this configuration, a SCHUFA response of C returns an Adyen risk score of 10, while a response of M results in a score of 20.
|SCHUFA Response||Risk Score||Riskiness|
Contact the Adyen Support Team to turn this check on.
External Risk Score (Generic)
This risk rule intakes a score submitted in the payment request and allows the merchant to affect the Adyen risk score as they choose. The external score must be calculated before the payment request is submitted (pre-auth).
This risk provides merchants with a flexible mechanism to pass an external risk score without solution-specific configuration. This is particularly useful when a merchant has a risk system of their own, but they also want to use RevenueProtect in coordination with it.
- You can set values to receive in the external risk score and the corresponding value of the rule should be added to the Adyen risk score. For example, an external value of 5 may add 40 to the Adyen risk score. This setting is an exact match.