USDC network evidence

Polygon USDC Casinos

This preview covers USDC transferred over Polygon. Other USDC networks remain separate routes and separate evidence.

Deposit and withdrawal are separate facts. A relation on this network does not establish support on another USDC route.

Polygon can have distinct native and bridged USDC forms. Confirm the exact token and network shown by the operator cashier before sending funds.

4operators with current relations
4verified Polygon relations
3with both directions verified
2026-08-23last data check
Directionality and scope

USDC on Polygon

Current verified relations are shown individually; missing withdrawal support stays visible.

Current verified USDC Polygon relations; token and network scope remain explicit.
CasinoDepositWithdrawalMinimum withdrawalFee
CloudbetVerifiedVerifiedNot verified · scope not establishedNot verified · scope not established
ShuffleVerifiedVerifiedNot verified · scope not establishedNot verified · scope not established
Sportsbet.ioVerifiedUnknownNot verified · scope not establishedNot verified · scope not established
StakeVerifiedVerifiedNot verified · scope not establishedNot verified · scope not established
Method

How this network evidence is assembled

Scope rules

  • USDC and the network are both fixed in every row.
  • Deposit support does not imply withdrawal support.
  • Asset-scoped values are not presented as network-specific.
  • Stale, unknown, and conflicting records do not enter current rows.

Questions

Does USDC support mean this network is supported?

No. This page requires an explicit USDC relation for Polygon.

Does network support mean no KYC?

No. Payment support and operator KYC policy are separate facts.

Evidence

Source records

7 source records support the displayed relations.