Skip to main content

Gambling and Payment Processor Labels API

See when a wallet sends funds to a crypto casino or pays through a payment processor. Bitquery labels more than 15 million gambling and payment processor addresses across BNB Chain, Bitcoin, Ethereum, Tron and Solana.

ProductUsing this in production? See the Address Labels API page for plans, free trial and enterprise delivery options.

What it is​

Label.TypeMeaningExample Label.Value
gamblingGambling platform wallet or a player's deposit address at onestake-deposit, roobet-deposit, bcgame-deposit, primedice
payment-processorPayment gateway wallet or a deposit address it issuedbitpay, coinpayments, cobo-deposit, moonpay-deposit

How to get it​

Query the Metadata.Labels cube of the Address Labels API:

Run in Bitquery IDE

{
Metadata {
Labels(
where: {
Address: {in: [
"12ewLzzHUsGSB6MRHPabBCg2k38kG2EAo1",
"19A4oxDANskKAYPeGnfrHCSBnGCaJjUyyT",
"0x000023443f1efbbda2c9ece5e3414dd7faac4873"
]}
Label: {Type: {in: ["gambling", "payment-processor"]}}
}
limitBy: {by: [Address, Chain, Label_Type], count: 1}
orderBy: {descending: RecordedAt}
) {
Address
Chain
Label {
Type
Value
}
RecordedAt
}
}
}

The response returns a Primedice address, a BitPay address and a Stake deposit address.

How it is derived​

Bitquery's labelling pipeline compiles each label from many inputs and returns one finished result: a type, a value and the date it was recorded. Responses carry the label itself, not a per-label source reference.

Fields​

FieldMeaning
AddressThe address you queried
ChainChain the label applies to
Label.Typegambling or payment-processor
Label.ValuePlatform slug. A -deposit suffix marks a customer deposit address
RecordedAtWhen the label was added to Bitquery's label table

Examples​

Gambling exposure of a wallet​

List the wallet's outgoing transfers with the Transfers cube, label the receivers here with Label.Type set to gambling, and sum the matching amounts. The result is how much the wallet sent to gambling platforms, per platform.

Keep one platform​

Run in Bitquery IDE

{
Metadata {
Labels(
where: {
Address: {in: [
"0x000023443f1efbbda2c9ece5e3414dd7faac4873",
"12ewLzzHUsGSB6MRHPabBCg2k38kG2EAo1"
]}
Label: {Type: {is: "gambling"}, Value: {startsWith: "stake"}}
}
limitBy: {by: [Address], count: 1}
orderBy: {descending: RecordedAt}
) {
Address
Chain
Label {
Value
}
}
}
}

Pitfalls​

  • A deposit address belongs to a customer account. stake-deposit marks a player's deposit address, not a wallet the platform uses to pay out.
  • Payment processors sit between two parties. The label identifies the gateway, not the merchant behind it.
  • Slugs vary. One platform can appear under more than one slug, for example bcgame-deposit and bc-game-deposit. Filter with startsWith or includes.

Get the full dataset​

The full gambling and payment processor lists are part of the Address Labels dataset on the Bitquery Data Store, for market sizing, compliance rules and research at scale.

Frequently Asked Questions

How do I detect gambling transactions from a wallet?

Label the wallet's transfer counterparties with Metadata.Labels and Label Type set to gambling. Each returned row is a gambling platform address, named in Label.Value.

Which payment processors are labelled?

The payment-processor type includes BitPay, CoinPayments, Cobo, AlphaPo, MoonPay, Transak and others. New ones are added as the label set grows.

Build with Bitquery

Ready to run this in production?

Get an API key and run these queries in minutes, or talk to us about plans and enterprise delivery.