Fraud prevention
Screen payments before authorisation with Ginger's rules, SEON or Cybersource, per project.
Ginger screens payments for fraud in real time, as part of the payment flow. The check runs before authorisation: a payment that fails it is declined before it reaches the processor and the card schemes. You choose per project how payments are screened: with Ginger's own rules, with an external provider, or both.
How it works
- The customer starts a payment, on the hosted payment page or in the merchant's own checkout.
- Ginger checks the payment against the Ginger fraud rules of the project, then against the external integration of the project, if it has one.
- Only a payment that passes goes to the processor for authorisation. A declined payment gets a reason and an event that say why.
Choose an integration
| Ginger fraud rules | SEON | Cybersource | |
|---|---|---|---|
| What it is | A denylist per project: BINs, card countries, customer countries, IP ranges, cards | Fraud scoring by SEON, with your SEON rules | Cybersource Decision Manager, with your profiles and rules |
| Enable on your platform | Always on | Add the integration in the Admin portal | Add the integration in the Admin portal |
| Set per project | Add rules | fraud_: seon | fraud_: cybersource, and optionally a risk profile |
| You need | Nothing | A SEON account | A Cybersource account with Decision Manager |
| Guide | Ginger fraud rules | SEON | Cybersource |
Ginger fraud rules always apply. A project uses at most one external integration next to them.
When the external check runs
Today, Ginger asks SEON or Cybersource for a decision on:
- Card, Apple Pay and Google Pay payments processed through Silverflow, after 3-D Secure authentication, or when dynamic 3-D Secure rules skip it.
- Card payouts (OCT) with a stored card.
Other payments only go through the Ginger fraud rules.
Project fields
Two fields of the project select the external integration: fraud_ (seon or cybersource;
leave it out for Ginger fraud rules only) and the optional fraud_. Only an admin can set
them, with an update of the project in the Boarding API.
The integration must also be enabled on your platform, or the project's payments aren't screened by it.
Risk profiles
A risk profile lets one integration decide differently per project, for example stricter for a merchant with a high fraud rate. You create the profiles in the provider's own tools, then set the profile name in fraud_ of the project. Ginger passes the name with every check of that project.
- Cybersource: the name of a Decision Manager profile.
- SEON: Ginger doesn't send a risk profile to SEON today. Use the merchant and project fields that Ginger sends to build per-project rules in SEON.
When the provider can't decide
Two platform settings of each integration decide what happens when the provider can't give a decision, and while you test:
| Setting | Effect |
|---|---|
decline_ | On (the default): decline the payment when the provider returns an error or no decision. Off: let the payment continue. |
report_ | On: always let the payment continue, and record what the provider decided. Off (the default): the provider's decision counts. |
When Ginger can't reach the check at all, for example because the project's integration isn't enabled on the platform, the payment continues.
Start in report-only mode
Turn on report_ when you add an integration to a live platform. Compare the recorded decisions with your real fraud before you let the provider decline payments.
Review the result
The result of the external check is on the transaction, in outcomes.fraud_, and in the Admin portal on the transaction under Outcomes › Fraud prevention:
| Field | Meaning |
|---|---|
integration | seon or cybersource |
status | accepted, declined or error |
score | The provider's score |
reason | Why the provider declined |
error_ | What went wrong, when the status is error |
deny_ | Whether an error declines the payment |
report_ | Whether the check ran in report-only mode. The provider's decision is then in report. |
A declined payment also gets an event declined_. Its source is ginger_ for a Ginger fraud rule and external_ for SEON or Cybersource, and its detail holds the value that led to the decline. The transaction's reason explains the decline, such as Blocked by external fraud prevention: <reason>. Follow declines across your platform with the Search API or the Stream API.
Next steps
- Ginger fraud rules: block BINs, countries, IP ranges and cards.
- Set up SEON or Cybersource.
- Manage rules from your systems with the Fraud prevention rules API.