CashoutGuard: fraud prevention for rewards, GPT, faucet, PTC and offerwall sites.

Fraud detection for a Flutter reward app: emulators, device farms and multi-accounts

A reward app pays real money for installs, surveys and games, and a Flutter codebase does not change who comes for it: emulator farms, cloud phones, rooted phones with hooking tools, and one person with dozens of accounts. The checks that catch them run on the device, so the question for a Flutter app is how to reach them from Dart.

Short answer

On Android, a Flutter app uses CashoutGuard's native Android SDK through a platform channel: two Gradle lines, a MethodChannel handler in MainActivity, and one call from Dart before signup, offer clicks and cashouts. The call returns a request ID that your server sends with its decision request, and it never throws: after two seconds or on any error it returns null and your server still decides.

Flutter on Android
The native Android SDK through a platform channel; no plugin needed.
Lines to add
Two in Gradle, about ten in MainActivity, one per check in Dart.
What it checks
Emulators, cloud phones, root and hooking, auto-clickers, a VPN running on the device, a device ID that survives reinstalls.
If it fails
collect() returns null after 2 seconds: the app never waits or breaks.
iOS
No native SDK yet: the server API and your offerwalls' postbacks still check every account.

Why reward apps attract device farms

An offerwall pays a reward app for each completed offer, and the app passes part of it to the user. That makes every install, survey and game level a small cash machine for whoever can repeat it. Farms do it with emulators on a PC, with Android containers rented in a data center, or with racks of cheap phones, each one opening a new account and cashing out to a wallet or gift card.

The loss arrives late. The offerwall reverses the conversions weeks later, after the app has already paid the user. An IP check alone sees little of it: farms route every device through a fresh residential or mobile IP. What gives them away is the device itself.

On a small reward app the pattern is easy to recognise once you look for it: a burst of new accounts from the same country within an hour, each one completing the same two or three high-paying offers, each one asking for the minimum cashout as soon as it is reached, and all of them on phone models that are oddly identical or oddly rare. Behind that pattern there are usually only a handful of real machines. Counting devices instead of accounts is what turns forty suspicious users into three farms you can stop.

What Dart alone cannot see

Emulator and root checks need the Android side: build properties, sensors, the graphics stack, files and processes a hooking tool leaves, whether a VPN is active on the device. Packages that read a few of these from Dart are easy to fool, because a farm patches exactly the values they read. CashoutGuard's Android SDK collects the signals natively and sends them to the server, where they are scored together with the account's history, its network and the other accounts on the same device or wallet.

The other half is identity. Reinstalling the app, clearing its data or switching to a new Google account gives a farm a fresh user ID in seconds, so an app that remembers devices only by its own install ID is counting the same phone many times. The SDK derives a device ID from several hardware and system properties that survive a reinstall, and the server links accounts by it, by their payout wallets and by their networks. That link is what lets you see that the account asking for a cashout today shares a phone with five accounts you banned last week.

The setup, step by step

1. In android/settings.gradle (or the root build.gradle), add our Maven repository, and in android/app/build.gradle the dependency. It brings the Kotlin standard library it needs.

maven { url 'https://cashoutguard.com/maven' }
implementation 'com.cashoutguard:cashoutguard-android:1.1.0'

2. In MainActivity.kt, start the SDK with your public key and answer the channel:

class MainActivity : FlutterActivity() {
    override fun configureFlutterEngine(flutterEngine: FlutterEngine) {
        super.configureFlutterEngine(flutterEngine)
        CashoutGuard.init(applicationContext, "pk_live_YOUR_PUBLIC_KEY")
        MethodChannel(flutterEngine.dartExecutor.binaryMessenger, "cashoutguard").setMethodCallHandler { call, result ->
            if (call.method == "collect") {
                CashoutGuard.collect(call.argument<String>("event") ?: "custom") { requestId -> result.success(requestId) }
            } else {
                result.notImplemented()
            }
        }
    }
}

3. From Dart, before signup, offer clicks and cashouts, ask for a request ID and send it to your server with the request:

const cg = MethodChannel('cashoutguard');
final requestId = await cg.invokeMethod<String>('collect', {'event': 'cashout'});
// your server: POST https://cashoutguard.com/v1/evaluate with this request_id

A ready Dart class with a timeout and iOS handled is in cashoutguard_flutter.dart. Your server makes the decision call with your secret key, which never goes into the app.

4. Test it on an emulator first. Run the app in the Android Studio emulator, sign up, and open the dashboard: the new event appears within a few seconds with the emulator flagged. Then run it on a real phone and compare. If no event appears, check that the public key matches the site, that the app has internet permission, and that your server sends the request_id it received.

Where to check, and what to do with the answer

  • Signup and login: links new accounts to devices and wallets already seen, so the second account of a farm is visible on day one.
  • Offer clicks: the device on the click is what the offerwall's conversion will be matched to.
  • Cashout: the check that saves money. Hold a cashout for review when the account shares a device or wallet with others, or runs on an emulator, instead of paying first and learning from the reversal.

Start in shadow mode: every decision is computed and shown in the dashboard, but nothing is blocked until you choose to. Most apps switch to enforce on cashouts first.

Each answer carries a decision (allow, review or block), a score from 0 to 100, and the reasons in plain words: emulator, rooted device, accounts sharing the device, a wallet already used by a blocked account, an IP from a data center. Your server can act on the decision alone, or keep its own rules and use the reasons. When an offerwall later reverses a conversion, report it to /v1/outcomes and the accounts and devices behind it are weighed more heavily next time.

Not ready to touch the app?

Point your offerwalls' postbacks at a CashoutGuard relay, with no app change. Each conversion is checked before you credit it (the user, the IP, the offer's own reversal history) and forwarded to your server as before. Device checks come later, when you add the SDK. See the postback relay guide.

Many reward apps start this way: the relay shows within a day which users and offers bring reversals, and the SDK is added once the numbers make the case for it. Both run on the same account and dashboard, so nothing learned from the postbacks is lost when the device data arrives.

Frequently asked questions

Is there a Flutter package on pub.dev?

Not yet. The platform channel takes about ten lines in MainActivity, and the Dart helper file does the rest.

Does it work on iOS?

There is no native iOS SDK yet. On iOS the helper returns null and your server evaluates without device data; offerwall postbacks through the relay are still checked.

Will it slow the app down?

No. Signals are collected in the background, and collect() returns within two seconds whatever happens.

Can farm owners just remove the SDK from a modified APK?

They can try, but then collect() returns no request ID, and your server sees a cashout with no device data from an app that always sends it. Treat a missing request ID on a cashout as a reason to review.

What does it cost?

Free up to 1,000 monthly active users, then from $29 a month. The 14-day Growth trial needs no card.

Keep reading