About us

PayoutDB is a data product, not a review blog. The site publishes verifiable on-chain evidence about crypto-casino payouts: which operator wallets are paying out, how often, and in what amounts. Every figure on the site resolves to a transaction hash you can check on the public block explorer yourself.

PayoutDB does not currently conduct first-party withdrawal tests at scale. That part of the brand, "we tested it ourselves", would cost real money the site does not have. The team refuses to claim tests that were not run. Where a first-party test does exist, the page carries the redacted transaction hash. Where it does not, an audit-only banner says so.

Most crypto-casino affiliate sites are written first and audited second. They start from "this casino is great, here is why" and reverse-engineer the evidence. PayoutDB works the other way around. The team starts from the on-chain data: wallets attributed to operators by independent analytics, real outgoing USDT transfers, license numbers checked against regulator registries where possible. Content is written only where the data supports it.

Three consequences of that:

• An operator can appear on the leaderboard without being recommended. The leaderboard ranks by observed on-chain payout activity, not by editorial preference.
• A "Watchlist" status on this site is not necessarily bad. It means there is not yet enough independent evidence to give the operator a stronger signal. The gap is stated plainly instead of dressed up as a positive.
• Affiliate links are present on operator pages where a referral agreement exists. They carry FTC disclosure, do not affect the verdict, and are absent on Watchlist pages entirely.

PayoutDB is operated by a small editorial team with a software-engineering background. The site does what engineers do: verify operator claims against public blockchain data and regulator registries, instead of relying on editorial trust.

Every claim on the site links to its source: the operator's own page for any operator statement, the regulator registry for any license, the block explorer for every transaction hash. The methodology page describes how the team corrects anything it got wrong.

PayoutDB does:

• Track real on-chain USDT payouts from operator-attributed wallets, daily.
• Cross-check license numbers against UK Gambling Commission and Malta Gaming Authority registries where the regulator publishes one.
• Surface adverse signals when they are found: expired licenses, name mismatches, missing registry confirmations.
• Mark operators as Watchlist when the evidence is too thin to recommend.
• Disclose every affiliate relationship with rel="sponsored" and a banner.

PayoutDB does not:

• Claim withdrawal tests that were not personally run.
• Mark a license as "registry-verified" without a human who has clicked through to the regulator's own page.
• Activate a payout wallet for tracking without a person confirming the Arkham Intelligence entity label.
• Take payment for ranking position on the leaderboard. The leaderboard ranks by observed payout count and outflow only.

The fastest way to flag an error is to write to [email protected] with the page URL and the specific claim being disputed. The team reviews every message and responds when action is taken.

For operator wallet leads — addresses that are believed to belong to a specific casino not yet tracked — the wallet suggestion form captures the operator name, the address, and the source of the attribution.

PayoutDB does not take requests to remove negative information, change a verdict, or speed up a listing. The verdict logic is deterministic from the underlying data. If the data changes, the verdict changes. If the data is disputed, the team investigates and issues a correction where warranted.