Fraud Management
What it is
Section titled “What it is”A menu group with three screens:
- Detections — everyone your brand is currently flagging, in one list.
- Fraud Settings — every rule behind that list.
- Bank Blacklist — destination bank accounts you have blocked by hand. It sits here because it is withdrawal fraud, but it works differently: you curate it, nothing detects it for you. It has its own page: Bank Blacklist.
The two detection features it covers are Linked Accounts and Hedge Detection. Those pages explain what each one looks for. This page is about seeing the results and setting the rules.
Detection is always on and cannot be switched off. What you choose is what happens when something is found.
Detections
Section titled “Detections”Fraud Management → Detections lists every member currently tripping something, newest and most serious first.
| Column | What it tells you |
|---|---|
| Signal | Which check fired — turnover with no risk taken, a flat betting pattern, or linked accounts. |
| Level | How much attention the row deserves. High first. |
| Member | Click through to that member. |
| Count | Risk-free rounds, flat rounds, or how many other accounts they are linked to. |
| Detail | The turnover behind it, and for a flat betting pattern the balance movement as a percentage. |
| Last seen | When it last happened. |
Read Count and Detail together. Four risk-free rounds worth 200 THB is somebody testing a game. Four worth 200,000 is somebody clearing a requirement.
There is nothing to tick off and no queue to work down. Findings are worked out fresh every time you open the page, over the period you choose, so a member who stops drops off the list on their own. That is also why the Period control matters — it is the only state this page has.
The list only ever shows your own members.
Fraud Settings
Section titled “Fraud Settings”Fraud Management → Fraud Settings. Three sections, in the order the decisions depend on each other.
1. When blocked
Section titled “1. When blocked”Tick which actions a block is allowed to take:
- Refuse the bonus — the member cannot claim a promotion or redeem a bonus code.
- Hold the withdrawal for staff — the payout is flagged, and approving it asks you to confirm once you have seen why. It is a hold, not a refusal: the money is still theirs and confirming pays it out normally.
- Refuse registration — the signup is turned away and the person is told to contact staff.
Bonus and withdrawal are on by default. Registration is off by default: a refused signup is the one thing the person cannot appeal in the moment, and shared phones and family devices are ordinary.
These three are brand-wide. They apply to every rule in the table below, not to one of them.
2. Signals
Section titled “2. Signals”Pick Flag or Block for each row.
- Flag shows the finding on the member’s page and stops nothing.
- Block applies whichever actions you ticked above.
On the member’s Linked Accounts tab this is what colours each match: red for a signal that is blocking, amber for one that is not. A signal set to Block only turns red once at least one action under When blocked is ticked — until then it is stopping nothing, and the colour says so.
| Signal | Suggested | Why |
|---|---|---|
| Same bank account number | Block | Two accounts paying out to one bank account is one person. |
| Same device | Block | The same browser on the same phone signed into both. |
| Same browser signature | Flag | Survives clearing browser data, but identical handsets collide. |
| Same account holder name | Flag | Common names repeat. |
| Same IP address | Flag | Mobile networks hand out addresses in rotation. |
| Turnover with no risk taken | Flag | See below. |
The Members affected count beside each row tells you how many of your members it currently touches. Read it before switching anything to Block — if Same IP shows hundreds, blocking on it would refuse hundreds of real people.
Changes save immediately. A changed rule can take up to a minute to start applying.
Turnover with no risk taken is the odd row out. Every signal above it is something two accounts share; this one is measured from a single member’s own betting. Because there is nothing shared to point at, it can only ever hold a withdrawal — it will never refuse a bonus or a signup, whatever those switches say.
3. Flat betting thresholds
Section titled “3. Flat betting thresholds”Two numbers, and they only affect turnover with no risk taken.
A member who covers every outcome of one round is caught exactly, by arithmetic, and needs no threshold at all. These numbers catch the harder version: betting that only partly covers the outcomes, spread over many rounds, so the balance barely moves. Real play has to move a balance around; farming turnover does not.
- Balance movement at or below — how flat is too flat. Ordinary play sits near 1.0. A member covering everything is 0.0. Default 0.35.
- Minimum rounds — how much play there has to be before the number means anything. Default 20.
Both are typed and saved with a button, unlike every other control here, because a half-typed number should not commit.
Like a rule change, a saved threshold takes up to a minute to reach the Detections page, a member’s Hedge Detection tab, and the withdrawal hold. The field itself shows the new value straight away.
Leave them alone until you have watched the Detections page for a while. They start at values that have not been tuned against your own players, which is exactly why the rule starts on Flag.
Paying out a held withdrawal
Section titled “Paying out a held withdrawal”A held payout appears in Transaction -> Withdrawals with On hold - staff review under its status, naming the reason.
Approving it shows a warning saying what was found. Confirming pays out normally — the warning is there so the decision is made with the information in front of you, not so the payout is blocked.
The flag stays on the row afterwards, as the record that the payout was held when it was requested. Who approved it anyway is in the activity log.
Who can do what
Section titled “Who can do what”Two permissions, split by who needs what.
- Fraud Management — the Detections page and both tabs on a member. Front-line work: answering “why is my withdrawal on hold” needs it. The seeded Customer Service role has it.
- Fraud Settings — the rules screen. The seeded Finance role has it, along with the write permission, because Finance is the desk that sees the held payout and has to decide whether the hold was right.
An owner always has both. For any other role, an owner grants writing by ticking Change the fraud rules under Fraud Settings in the role editor.
Bank Blacklist keeps its own separate permission, so you can let someone curate blocked bank accounts without also letting them hold every payout on the brand.
Every settings change is written to the activity log.