Fraudulent payments can lead to chargebacks, network fines, and inclusion in card network monitoring programs. Antifraud helps reduce these risks by screening payments before authorization.

Antifraud checks each payment against your lists and rules and returns a decision to pass, reject, require 3DS , or review the payment. You can manage your lists and rules in the Solidgate Hub .

Antifraud screens card payments, including Apple Pay and Google Pay.

The screening process unfolds as follows:

  1. A payment is initiated.
  2. Solidgate checks it against lists and rules before sending it to the bank.
  3. Antifraud returns a decision, and Solidgate acts on it.
  4. The decision appears as the Antifraud result on the order in Hub.

Overview in Hub

The Antifraud overview page in the Solidgate Hub gives you a summary of your fraud protection activity and payment screening results. It brings together key metrics from your lists, rules, and payment decisions, so you can monitor how Antifraud is performing over time.

Go to Antifraud > Overview to view fraud protection performance and payment decisions. Use the date range selector to choose the dates and the currency selector to set the currency.

Active rules

Rules that are active, including the Solidgate-managed ones.

Lists

Number of default and custom lists.

List items

Total number of values stored across all lists.

Decisions

Amount and number of payments that were passed, sent to review, forced to 3DS, or blocked, compared with the previous period. Blocked labels the result of the Reject decision.

Fraud & disputes

Fraud rate, dispute rate, and VAMP ratio for the period, calculated according to the formulas in Fraud overview and monitoring programs.

Decisions

Based on the screening results, four decisions are possible:

Decision Description
Pass The payment continues without any additional action.
Reject The payment is stopped and never reaches the bank. You receive error code 4.09 .
Force 3DS The payment goes through 3D Secure verification, whatever your 3DS settings are.
Review The payment continues as usual, and the order gets a review marker.

When several rules or lists match one payment, the decision with the highest priority applies.

Decision priority

Pass

Allows payment

Reject

Stops payment

Force 3DS

Adds verification

Review

Marks for review

Highest priorityLowest priority

To find orders marked for Review , go to Payments > Orders and filter by the antifraud decision.


Lists

A list is tied to one field, such as card ID, cardholder name, customer account ID, customer email, or payment IP. All items in a list share that field, so, for example, a list cannot mix emails and IPs. Every list is either default or custom.

List type Decision Use it to
Default For example, Pass or Reject Apply the decision to every payment that matches a value in the list.
Custom None, the rule that references the list carries the decision Reference the list in a rule condition.

Each value in a list is an item. An item can have a description and an expiry date. Expired items no longer apply the list’s decision to payments.

Lists apply only within your account. Payments are matched against the values you add, so add them in the same format they appear in payment data. Emails are matched after normalization, so John.Doe@gmail.com and johndoe@gmail.com count as the same address.

API To create a list, send a request to the create antifraud list API v2 endpoint with a name and field . The list is ready to receive items immediately. To rename a list without recreating it, send a request to the update antifraud list API v2 endpoint.

To add a list item, send a request to the create antifraud list item API v2 endpoint with the list_id and field_value . Optionally, set expired_at so the item stops matching after a certain date, and description for internal reference.

To view existing lists, call the list antifraud lists API v2 or get antifraud list API v2 endpoint, and retrieve the values on a list with the list antifraud list items API v2 endpoint.

To remove a value from screening so it no longer applies the list's decision to payments, send a request to the delete antifraud list item API v2 endpoint with the item id . Hub To create a list

  1. Go to Antifraud > Lists.
  2. Click on Create list.
  3. Enter the list Name.
  4. Select the Field the list contains.
  5. Select the Decision, or leave it empty for a custom list.
  6. Click on Create.

To add items

  1. Go to Antifraud > Lists and click on the list.
  2. Click on Create item.
  3. Enter the value, and, optionally, a description and an expiry date.
  4. Click on Create.
To find a list, use the filters by ID, name, field, or decision. The list page shows each item with information about who added it and when.

Rules

A rule checks a payment against a set of conditions and applies a decision when all conditions match.

A condition compares a field with a value, another field, or one of your custom lists. All conditions in a rule must match. Rules do not support OR logic. To cover alternatives, create separate rules with the same decision or use the in operator with multiple values. For example, a rule that matches the cardholder name against a list and applies a Reject decision stops the payment before it reaches the bank.

Condition fields are of two types:

Direct

Direct type uses values from the current payment, such as:

  • card country
  • IP address
  • payment amount

Aggregation

Aggregation type calculates values over a time window, up to 90 days, such as:

  • number of chargebacks linked to the same email address in the last 30 days
  • number of distinct cards linked to the same device ID in the last 30 days

Each rule has a decision, which is Pass , Reject , Force 3DS , or Review , applied according to the priority order.

The list of rules shows both your rules and the rules Solidgate manages. The Managed by column shows who owns each one. You can view Solidgate-managed rules but not change them.

Hub To create a rule

  1. Go to Antifraud > Rules.
  2. Click on Create rule.
  3. Enter a Name and, optionally, a Description.
  4. Select a Decision.
  5. Under Conditions, select a field, an operator, and a value.
  6. To add another condition, click on AND - add condition.
  7. Check the rule in Preview.
  8. Optionally, turn on shadow mode.
  9. Click on Save.

To view a rule

  1. Go to Antifraud > Rules.
  2. Use the filters by ID, name, fields, decision, or state to find the rule.
  3. Click on the rule.
    The rule page shows the version, description, decision, conditions, and Rule hits.

To edit a rule

  1. Open the rule and click on Edit rule.
  2. Change the details and click on Save.
Every edit creates a new version of a rule. The rule ID stays the same.

Shadow mode

A shadow rule runs on every payment like a normal rule, but Antifraud does not apply its decision. Payments proceed as if the rule does not exist.

Use shadow mode to see how often a rule would trigger before it affects real payments. Open the rule and check Rule hits, which shows the number of matches per day for the period you select.

Shadow mode can only be turned on when you create a rule.

Recipes

Each recipe shows what to set up and in which order. Test new rules in shadow mode before you let them affect payments.

Let a trusted customer through

Use when a customer or partner keeps getting stopped by other checks.

To create a rule that lets a trusted customer through


  1. Create a default list with the Pass decision for the field you use to identify them, for example, customer email.
  2. Add the customer as an item. Optionally, set an expiry date.
Pass overrides Reject , Force 3DS , and Review from other matches.

Block a customer Use when a customer has caused fraud or chargebacks.

  1. Create a default list with the Reject decision for the field that identifies them.
  2. Add the identifying value as an item and add the reason in the description.
Blocking works for one field at a time. If a customer can change their email, add the card or payment IP to a list as well.

Limit repeated failed attempts Use when you see card testing: many attempts on one card in a short time.

  1. Create a rule with the Reject decision.
  2. Add a condition on the number of failed payments for the same card. Set the period to a few minutes.
  3. Turn on shadow mode and check Rule hits for a few days.
  4. When the hit count matches your expectations, create the rule again without shadow mode.
Start with a loose threshold and tighten it as you learn what normal traffic looks like.

Ask for 3D Secure in a risky region Use when a country or region has a high fraud rate.

  1. Create a rule with the Force 3DS decision.
  2. Add a condition on the card country.
  3. Test in shadow mode, then turn off the shadow mode.
Force 3DS shifts liability to the issuer in most cases and does not block the customer.

Mark large payments for review Use when you want to look at large payments without stopping them.

  1. Create a rule with the Review decision.
  2. Add a condition on the payment amount.
  3. Go to Payments > Orders and filter by the antifraud decision to see the marked orders.