Skip to main content

Fraud Management

The payment gateway includes fraud management that screens transactions in real time before authorization.

When fraud management is active on a payment method configuration, each transaction is evaluated for potential fraud indicators before it is authorized.

How It Works​

  1. The transaction is sent to the fraud screening engine before authorization.
  2. The engine evaluates the transaction using risk rules and scoring models.
  3. Based on the result, the transaction either continues to authorization or is stopped.

Possible outcomes:

  • Accept — the transaction proceeds to authorization normally.
  • Reject — the transaction is declined before authorization. The payer cannot complete the payment.
  • Error — screening could not be completed; the transaction is marked as error.
note

Fraud evaluation runs server-side in the gateway. It does not introduce additional customer-facing steps (for example, redirects or challenges).

API Behavior​

Fraud management does not change the API request format. When it is enabled on the payment method configuration, screening is applied automatically.