Gambling limit changes
Manage gambling activities to avoid financial and emotional harm associated with excessive gambling.
The Sumsub responsible gambling solution is designed to help businesses promote a safe and healthy gaming environment for your customers.
If you are a casino or a betting site, Sumsub helps you:
- Encourage players to adopt safe gaming practices.
- Prevent problematic gambling behavior among your customers.
- Build trust with players and enhance the reputation of your company as a socially responsible operator.
- Adhere to betting regulations and avoid fines and penalties while also demonstrating your commitment to regulatory compliance.
- Enhance customer loyalty and attract a more conscientious player base.
How it works
You can enforce several types of limits to manage your users' gambling activities better and avoid financial and emotional harm associated with excessive gambling:
Limit type | Description | Settings |
---|---|---|
Deposit Limit |
This limit restricts the amount of money a gambler can deposit into their gambling account within a specific timeframe, such as daily, weekly, or monthly limits. Once the limit is reached, the individual cannot deposit any more money until the limit resets. Gambling platform operators often impose such limits to meet licensing obligations. |
|
Loss Limit |
A loss limit sets the maximum amount of money a gambler is willing to lose within a specific timeframe. Once this limit is reached, the individual is prevented from placing more bets until the limit resets. |
|
Self-exclusion |
Self-exclusion allows the user to voluntarily exclude themselves from gambling for periods of time, ranging from hours to years. During this period, users are barred from accessing the operator's gambling services. |
|
Session time limits |
Session time limits restrict the amount of time a person can spend gambling in one session. Once the time limit is reached, the individual is logged out of their account. |
|
Wagering Limit |
The wagering limit controls the amount of money that can be wagered on a single bet or within a specific timeframe. This helps prevent impulsive or excessive betting. |
|
The process of gambling monitoring includes the following steps:
- Players participate in gaming sessions by making bets, winning, losing, thereby producing transactions.
- Sumsub performs necessary checks in accordance with the rules you activated or created.
- Depending on the checks results, each transaction receives a status:
- Normal — transaction is approved.
- Suspicious or Gambling Addiction — transaction matched a Gambling Limit rule and requires attention.
- You handle monitoring results.
Integrated checks
The following table explains the checks performed when monitoring gambling transactions:
Check | Description |
---|---|
Total deposit amount for the last 4 weeks is 2x the salary | Indicates that the user has deposited more than half of his wage. |
Total deposit amount > 10x withdrawal amount | Indicates that the user has a lot of deposits but a lack of withdrawals. |
Sessions count >7 in the last 2 weeks of duration >180 mins | Indicates that the user has more than 7 sessions in the last 2 weeks (with session durations of more than 180 minutes). |
Session duration >180 min | Indicates that the user has a huge session (more than 180 minutes). |
Session duration < 60 min and Sessions count > 9 in past 2 weeks | Indicates that the user has more than 9 sessions in the past 2 weeks (with session duration less than 60 minutes). |
Risky gambling time during working days with many sessions | Indicates that the user has bets between 10:00 and 18:00 on working days a lot (more than 3 times a week). |
Risky gambling time during working days | Indicates that the user has bets between 10:00 and 18:00 on working days. |
Limits have been removed sooner than 3 days or limits have been increased >=100% | Indicates that the user removed his gambling limit sooner than 3 days after the limit was imposed or the limit amount has been increased more than x2. |
Limits has been removed sooner than 3 days | Indicates that the user removed his gambling limit sooner than 3 days after the limit was imposed. |
Limit has been increased >=100% to the first limit | Indicates that the user increased his gambling limit amount by more than x2. |
Large bet in comparison to the last deposit made in the last 2 weeks | Indicates that the user made a large bet compared to the last deposit ( > 1/80 deposit). |
Large bet in comparison to the last big deposit made in the last 2 weeks | Indicates that the user made a large bet compared to the last deposit ( > 1/40 deposit). |
Deposit frequency time <= 60 min | Indicates that the user makes fast deposits (less than 60 minutes between deposits). |
Deposit count increased >= 50% in the past 2 weeks | Indicates that the deposit count is increasing compared to the past 2 weeks. |
Deposit amount >2000 per deposit | Indicates that the single deposit amount is more than 2000 EUR. |
Average deposit amount increased >50% during last 2 weeks | Indicates that the deposit amount is increasing in comparison to the past 2 weeks. |
Avg. bet amount increased > 50% and < 100% during past 4 weeks | Indicates that the bet amount increased in comparison to the past 4 weeks. |
Avg. deposit "failed or declined" deposits increased > 50% and < 100% during past 4 weeks | Indicates that “failed or declined" deposits increased compared to the past 4 weeks. |
Avg. bet amount increased >50% and <100% after big win (big win: betResult > = 100* betAmount) during past 2 weeks | Indicates that the bet amount increased after a big win. |
Avg. bet amount increased > 100% during past 4 weeks | Indicates that the bet amount increased significantly in comparison to the past 4 weeks. |
Avg. bet amount increased >100% after big win (big win: betResult > = 100* betAmount) during past 2 weeks | Indicates that the bet amount increased significantly compared to the past 2 weeks. |
Session duration > 180 min | ndicates the user makes bets more than 3 hours straight in 1 session. |
Manually created checks
Apart from using the gambling transaction checks Sumsub offers you out-of-the-box, you can create your own checks based on custom criteria. Here are a few examples related to gambling limits:
Condition | Action |
---|---|
If (sum (txn.data.betinfo.amount - txn.data.betinfo.resultAmount ) is in DiffInDaysFromNowLte equals 30) greater then ((sum (txn.data.info.amount ) is in DiffInDaysFromNowLte equals 30)) * -0.75 | Indicates that total player losses are more than 75% of total deposits in the past 30 days. |
If (sum (txn.data.betinfo.amount - txn.data.betinfo.resultAmount ) is in DiffInDaysFromNowLte equals 30) greater then txn.data.info.amount * 10 | Indicates that the user’s total loss in past 30 days is x10 more than the last deposit. |
if sum (txn.data.info.amount ) greater than (txn.data.info.amount ) * 0.35 | Indicates that the user’s total deposit amount is more than x3 of their total withdrawal amount. |
If txn.data.betinfo.amount greater than txn.data.info.amount 80 | Shows that the user’s bet is incomparably high compared to the casino deposit (> 1/80 casino deposit). |
If txn.data.betinfo.startdate greater than "11:00" and txn.data.betinfo.startdate less than "18:00" and txn.data.betinfo.startdate is in "working day" | Detects players who gamble during working hours (between 11:00 and 18:00) on workdays. |
If txn.data.Info.Amount greater then AVG(Σ txn.data.info.amount is in DiffInDaysFromNowLte equals 14) * 1.5 | Indicates that the user’s average deposit amount increased by more than 50% in the past 2 weeks. |
Enable gambling limit changes monitoring
To enable gambling monitoring:
- 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.
- Create the rules if needed.
- In the Dashboard, open the Rules Library, select and install the selected rules.
- Open the Rules page and enable the installed rules.
Once you enable the rules, all transactions are going to be monitored by these rules. Each transaction that matches the rule conditions will be taken care of in accordance with 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:
- Go to the Transactions page.
- Click Create transaction manually.
- From the drop-down list, select an applicant on behalf of whom you want to produce the transaction.
- Switch between the simplistic (visual representation) form and JSON payload (digital data).
- When using a simplistic form, from the Use Case drop-down list, select Gambling Limit Change.
- Provide required transaction information.
- Set the custom transaction date by selecting the associated checkbox if necessary.
- Click Create transaction.
Use API
To produce a responsible gambling transaction via API, use this API method and set the type
field to Gambling Limit Change as the following example demonstrates:
'https://api.sumsub.com/resources/applicants/631f268442d8290001e1eee9/kyt/txns/-/data' \
-H 'Content-Type: application/json' \
-d '{
"txnId": "621f268442d8290901e1eee9_newTxn",
"applicant": {
"externalUserId": "uniqueRemitterId",
"address": {
"country": "DEU",
"street": "Chauseestr. 60",
"postCode": "101115",
"town": "Berlin"
},
"device": {
"ipInfo": {
"ip": "87.141.63.133"
}
}
},
"type": "gamblingLimitChange",
"gamblingLimitChangeInfo": {
"type": "deposit", //Type of the limt could be deposit/loss/wager/session time/self-exclusion and the following parameters would vary - as per https://docs.sumsub.com/reference/expression-attributes#gamblinglimitchangeinfo
"amount": 42,
"currencyCode": "EUR",
"reverted": false,
"resolutionDate": "2024-03-04 20:53:01+0200",
"": 120,
"period": "weekly"
}
}
Handle monitoring results
Once the 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 an appropriate action must be taken.
You also receive any of the following webhooks, depending on the transaction status:
Updated 3 months ago