Sumsub offers the functionality for monitoring and controlling users’ financial activities and analyzing their behavior to detect patterns that may indicate money laundering.

If you are a gaming platform, Sumsub helps you:

• Avoid risks and legal consequences of being involved in money laundering, including hefty fines, license revocation, and criminal charges.
• Comply with global and local AML regulations.
• Monitor user transactions for suspicious activities, such as large deposits or withdrawals, frequent transactions, and so on.
• Decline or put transactions on hold based on in-depth risk-analysis.

How it works

The process of detecting money laundering at withdrawal includes the following steps:

1. The user deposits a large amount of illicit funds.
2. The user creates a series of bets with increased amounts to simulate gambling activity.
3. The user initiates an extensive series of withdrawals to the same account within a short period.
4. Sumsub checks if similar transactions were performed within a short period and whether the withdrawal amount exceeds the limit you specified.
5. Depending on the results of the checks, each transaction receives a status:
   • Normal — transaction is approved.
   • Suspicious — transaction matched one of the selected rules and requires attention.
6. You handle monitoring results.

Checks

The following table explains the checks performed when monitoring gambling transactions to detect money laundering.

Enable money laundering prevention

To enable money laundering prevention:

1. If you have never used Sumsub, visit our website and click Get started to begin your journey or contact our sales department. If you are already a Sumsub customer, contact our customer support.
2. In the Dashboard, open the Rules Library and install the rules below.
   • Transactions made in short period of time
   • Same beneficiary for 3+ transactions
   • Rounded amounts
3. Open the Rules page and enable the installed rules.

Once you enable the rules, all transactions will be monitored by these rules. Each transaction that matches the rule conditions will be handled according to the rule configuration.

Create transactions

You can create gambling transactions in the Dashboard using a convenient constructor or with the help of the API methods.

Use Dashboard

To produce a transaction in the Dashboard:

1. Go to the Transactions page.
2. Click Create transaction manually.
3. From the drop-down list, select an applicant on behalf of whom you want to produce the transaction.
4. Switch between the simplistic (visual representation) form and JSON payload (digital data).
5. When using a simplistic form, from the Use Case drop-down list, select Gambling bet.
6. Provide required transaction information.
7. Set the custom transaction date by selecting the associated checkbox if necessary.
8. Click Create transaction.

Use API

To produce a gambling transaction via API, use this API method and set the type field to Gambling bet as the following example demonstrates:

{
  "txnId": "631f268442d8290001e1eee9_newTxn",
  "applicant": {
    "externalUserId": "uniqueRemitterId",
    "address": {
      "country": "DEU",
      "street": "Chauseestr. 60",
      "postCode": "101115",
      "town": "Berlin"
    },
    "device": {
      "ipInfo": {
        "ip": "87.141.63.130"
      }
    },
    "institutionInfo": {
      "code": "DEUTDEDB101",
      "name": "Deutsche Bank"
    },
    "paymentMethod": {
      "type": "card",
      "accountId": "eg_hash_of_credit_card_number",
      "issuingCountry": "DEU"
    },
    "counterparty": {
      "externalUserId": "uniqueBeneficiaryId",
      "fullName": "John Smith",
      "type": "individual",
      "institutionInfo": {
        "code": "CRESCHZZXXX",
        "name": "Credit Swiss (Schweiz)"
      }
    },
    "info": {
      "direction": "out",
      "amount": 101.42,
      "currencyCode": "GBP",
      "paymentDetails": "Birthday Present"
    },
    "props": {
      "customProperty": "Custom value that can be used in rules"
    }
  }
}

Handle monitoring results

Once a transaction is checked, it can be found on the Transactions page.

All suspicious transactions that get the Requires action status appear in Queues. Such transactions must be carefully evaluated by your experts, and appropriate action must be taken.

You also receive any of the following webhooks, depending on the transaction status:

• applicantKytTxnApproved
• applicantKytTxnRejected
• applicantKytOnHold