All articles Fraud & ATO

Fraud Prevention for Gaming: Bonus Abuse Signals

Translucent glass game controller glowing with electric blue light on a black background

Fraud prevention for gaming platforms usually gets budgeted after the chargebacks arrive, but most bonus money leaks before a single card is disputed. A welcome offer, free spins, a deposit match or a referral credit is a promise with conditions, and the cheapest way to collect is to open a second, third and tenth account that the conditions never anticipated.

The hard part is not spotting something odd. It is deciding, in the few hundred milliseconds around a bonus claim, whether this account is a new player or the same player wearing a new email. Most teams answer with rules written in marketing language — “one account per player” — and then discover nobody can measure a household, a device or a person.

This guide separates the signals that usually hold from the ones that mostly produce noise, and shows how to turn them into a policy with Prynt Control: allow, step-up or block, with a reason code your support team can read.

Why bonus abuse is a policy problem before it is a detection problem

Every rule you enforce costs something. “One account per device” blocks a family sharing a tablet. “One account per payment instrument” blocks a player who switches cards. “One account per household” blocks roommates. Decide what you are willing to lose in false positives before you look for signals, because the definition chooses the signals, not the other way around.

The three patterns worth separating

Multi-accounting is one person opening several accounts, usually on the same device or network. Bonus hunting rings are coordinated: different people, different devices, but shared payout destinations and similar timing. Automated signups are bots farming referral credits at volume. Each needs a different step-up — email verification, a card or passkey check, or a block of the bonus only.

Multi-accounting: what a device can actually tell you

A stable device identifier is the anchor. Prynt Identify returns a visitorId per browser or device, plus bot and AI-agent detection, tampering signals and VPN, proxy, Tor and datacenter flags. Two accounts claiming a welcome bonus from the same visitorId, on the same evening, from a datacenter range, is a stronger case than either signal alone. Our device fingerprinting guide covers how that identifier is built and where it breaks.

Row of translucent phone shapes with blue fingerprint patterns linked by a glowing line

Signals that hold, and signals that mostly do not

Signals that hold: the same visitorId across accounts, a tampered fingerprint payload, a datacenter IP on a first deposit, and a device already seen inside a blocked cluster. Signals that mostly do not: IP address on its own (carrier-grade NAT and mobile networks put thousands of players behind one address), email domain, country mismatch from travel or expats, and timezone. Treat each weak signal as a small weight, not a verdict.

Bonus hunting: read intent from the claim, not the signup

Bonus hunters are rarely subtle at the moment of claiming. They sign up and claim within seconds, deposit the minimum that unlocks the maximum, skip the games that do not contribute to wagering, and request a withdrawal as soon as wagering is met. Across accounts the patterns repeat: identical bet sizes, referral chains that loop back to a small set of payment instruments, and accounts that go quiet right after a payout.

Prynt Control keeps phone numbers and cards only as keyed hashes, so you can link accounts sharing an instrument without storing the raw value. Combined with device signals, that gives you a per-claim risk view instead of a per-signup one. Our post on fraud rings covers linking accounts that never share a device.

From count to decision

Do not block on the count of accounts. Use the count as a reason code and let it choose the step-up. Two accounts on one device with a shared card is usually a verify_email or card_or_passkey step-up. Four or more accounts on one visitorId, with tampering, is a block of the bonus while normal play continues.

Turn signals into allow, step-up or block

Prynt Control answers a decision request per use case — signup, free_trial, bonus, login, checkout, extra_seat, sms, paywall — and Prynt never blocks by itself: your code decides. An example bonus response, with fields simplified, looks like this:

Glowing blue network nodes converging on a frosted glass card shape

{
  "useCase": "bonus",
  "decision": "step_up",
  "reasonCode": "shared_payment_instrument",
  "suggestedStep": "verify_email",
  "vpn": true,
  "tampering": false
}

Your server writes the branch: step_up sends the player to verification before the credit lands, block denies the bonus but keeps the account playable, allow pays out. Keep the reason code in your own logs so support can explain a decision to a player without opening a fraud tool.

Watch it before you enforce it

Control starts with a 14-day mirror period: decisions come back with reasons, but nothing is blocked. Use it to count what would have happened — bonuses denied, players challenged, withdrawals delayed — and compare that against the accounts you already know were abusive. Enforce after the mirror, one use case at a time, starting with bonus rather than signup.

Cap the cheap attacks at the same time

Bonus abuse rarely arrives alone. OTP pumping drains the SMS budget, so Control caps requests per device, number and network and supports number blocks; Prynt does not send the SMS, it protects the request. Trial and paywall meters hold per device and account, so clearing cookies or opening an incognito window does not reset them. For automated account creation, see bot detection.

FAQ

Three floating translucent panels lit in increasing shades of blue

What counts as multi-accounting on a gaming platform?

It depends on your rule, not on the technology. Most platforms define it as more than one account per person, per payment instrument or per household, and each definition carries a different false-positive cost. Write the definition down before you pick signals.

Should a second account on the same device be blocked?

Not automatically. Shared devices, families and replaced phones all produce second accounts on one device. A better default is to hold the bonus and require a step-up such as email verification or a passkey, then block only when the pattern repeats with a shared payment instrument.

Do you need device fingerprinting to reduce bonus abuse?

It helps most when accounts change email and IP but keep the same device. Fingerprinting plus payment-instrument hashing covers the common cases; behavior at the claim — deposit size, wagering speed, withdrawal timing — covers the rest.

Put the bonus policy in code

If you already know what a suspicious claim looks like, Control gives you the decision endpoint and the reason codes to act on it. Start with the mirror period, watch what your rules would have done to real players, then enforce. Create your account at pryntid.com and send your first bonus decision this week.

Try it free

Prynt is device intelligence with a free plan: 5,000 identifications a month, visitor IDs with confidence and bot detection — no credit card. Upgrade to Pro for VPN, proxy, tampering and behavioral signals.

Keep reading