Know who justdeposited.

No. Players deposit exactly as they do today. You send us the deposit event over a webhook or API call, and we hand back the verdict. Nothing about your cashier, your wallets, or the player experience changes.

The deposit event: the wallet address, the chain, the amount, a timestamp, and your own player reference. That is enough for us to read the wallet and return value and risk. Your player reference can stay pseudonymous if you prefer.

No. Whal3Core sits alongside whatever you already run. It does not migrate data or take over any function. Run it standalone next to your current platform, or as the wallet-intelligence layer inside WAG3R.

You can be live in weeks, not quarters. Once your deposit events are connected, we spend roughly one to two weeks calibrating the engine to your geos and seeding the cross-casino registry, then you go live on every deposit.

Three ways, usually together: the full dossier in the console, scores and segments exported to your CRM, and alerts to the in-console inbox and email — or an alert webhook you point at Slack or another ops tool.

Never. Whal3Core is read-only intelligence. We never hold, move, or have access to funds, keys, or wallets. We read public on-chain data and return a verdict, nothing more.

We work from the wallet, not the person. We read public blockchain data plus the deposit event you send. We do not need player names, emails, or documents, and your player reference can be pseudonymous. Your data stays yours, and we never sell or share it.

Designed with it in mind. You remain the controller of any player data you send; we act as processor. Data processing is Schedule 3 of the service agreement, with SCCs and the UK Addendum incorporated, so there is no separate DPA to sign. Because we lean on public on-chain data and a player reference you control, the personal-data footprint is deliberately small.

We read public on-chain data, enrich each wallet through a blockchain-intelligence feed, and score it with our own engine and casino registry. A verdict reflects the wallet at the time of analysis. Coverage tracks what that feed and our registry can see on each supported chain — ETH, BSC, TRON, and BTC.

The verdict is a probability and a risk read, not a guarantee, and every dossier carries a confidence level so your team knows how much weight to give it. Accuracy sharpens once we calibrate to your geos and player base. We would rather tell you confidence is low than hand you a number we cannot stand behind.

A wallet with little history gives us less to read, so we return a lower confidence instead of inventing a verdict. As that wallet builds a footprint, later reads get sharper. We are explicit about this rather than pretending every wallet is fully knowable.

From the on-chain footprint. We see funds moving to and from wallets we have attributed to other crypto casinos, and cross-reference them against our registry. That is what powers the cross-casino view and your share of a player's wallet.

A determined player can split funds across wallets, and we are honest that a clean, freshly funded wallet is the hardest case. We counter it by tracing funding hops and surfacing linked accounts that share on-chain infrastructure, which is how multi-accounting and wallet farms tend to give themselves away.

No, and we never blend them. Value and risk are scored separately and shown side by side, because a player can be both highly valuable and high risk at once. Collapsing them into one number hides the exact cases you most need to see.

No. It does the AML work in full: source of funds, sanctions and mixer exposure, with risk scored on every deposit. The difference is it does not stop there. The same read also tells you who the player is worth, across every casino, from the wallet, so one verdict drives both compliance and revenue. AML-only tools answer whether funds are dirty; we answer that and who the player is.

Not really, because they do a different primary job: compliance and forensics. We overlap on the source-of-funds read, but our reason to exist is player value and cross-casino intelligence, which they do not provide. You can run a compliance suite and Whal3Core side by side; they solve different problems.

We read the native coin and the major tokens on each chain, including the stablecoins that make up most casino deposits. USDT and USDC are covered in their ERC-20, BEP-20 and TRC-20 forms.

We add more chains on a regular basis, so coverage keeps widening.

Whal3Core is crypto-native. It reads on-chain wallets, so a fiat deposit with no wallet behind it is outside what it can see. For fiat players you lean on your existing tooling; for crypto deposits, this is the layer.

Per active player each month, counted once per player by wallet, with unlimited checks inside that month, and never a cut of your revenue. Plans start at $250 a month, which covers your first 100 active players.

A unique player wallet that you check in a given month. You are charged once for that wallet no matter how many times you query it that month, so re-checking a returning player costs nothing extra.

Micro through Growth can choose a 12-month term or rolling month-to-month (rolling is billed at a higher monthly rate and ends on 30 days' notice). Pro and Scale are 12-month only. A 12-month term does not renew automatically. No setup fee at any tier.

It's live now. Connect your deposits and start getting verdicts in weeks.