Skip to content

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

flowchart
  1. The customer starts a payment, on the hosted payment page or in the merchant's own checkout.
  2. Ginger checks the payment against the Ginger fraud rules of the project, then against the external integration of the project, if it has one.
  3. 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 rulesSEONCybersource
What it isA denylist per project: BINs, card countries, customer countries, IP ranges, cardsFraud scoring by SEON, with your SEON rulesCybersource Decision Manager, with your profiles and rules
Enable on your platformAlways onAdd the integration in the Admin portalAdd the integration in the Admin portal
Set per projectAdd rulesfraud_prevention_integration: seonfraud_prevention_integration: cybersource, and optionally a risk profile
You needNothingA SEON accountA Cybersource account with Decision Manager
GuideGinger fraud rulesSEONCybersource

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_prevention_integration (seon or cybersource; leave it out for Ginger fraud rules only) and the optional fraud_prevention_risk_profile. 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_prevention_risk_profile 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:

SettingEffect
decline_transaction_if_integration_is_unavailableOn (the default): decline the payment when the provider returns an error or no decision. Off: let the payment continue.
report_onlyOn: 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_only 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_prevention, and in the Admin portal on the transaction under Outcomes › Fraud prevention:

FieldMeaning
integrationseon or cybersource
statusaccepted, declined or error
scoreThe provider's score
reasonWhy the provider declined
error_descriptionWhat went wrong, when the status is error
deny_on_errorWhether an error declines the payment
report_onlyWhether the check ran in report-only mode. The provider's decision is then in report.

A declined payment also gets an event declined_by_fraud_prevention. Its source is ginger_fraud_prevention for a Ginger fraud rule and external_fraud_prevention 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