ZBD

• Name: ZBD
• URL: https://zbdpay.com/
• Category: gaming payments control plane / Bitcoin rewards-and-payout operator / licensed gaming fintech
• Tags: bitcoin-ecosystem
• Summary: ZBD is a gaming-payments operator that happens to use Bitcoin as the reward and payout rail. The important surface is developer-issued rewards, hosted balances, withdrawal policy, OAuth identity, and licensed cash-out routing, not a wallet.
• What it does:
  • Provides an Earn SDK for apps and games to issue real-money Bitcoin rewards and manage player withdrawal limits
  • Offers login and OAuth flows so games can authenticate ZBD users and retrieve user and wallet data
  • Supports payout infrastructure that lets users and creators withdraw to bank accounts and other endpoints such as Cash App, Kraken, Coinbase, and gift cards
  • Markets branded debit-card infrastructure that converts everyday spending into in-game virtual-currency rewards
  • Markets embedded accounts for player-to-player transfers, creator economies, and licensed in-game financial accounts
  • Positions itself as a regulated payments layer for gaming and interactive entertainment across the US and Europe
• Key claims:
  • The docs home describes ZBD as the “global Bitcoin payments API for app and game developers” and as a “Global Payment Service Provider for Gaming and Interactive Entertainment”
  • The products page says ZBD helps studios build direct financial relationships with players through payouts, branded debit cards, and embedded accounts
  • The about page says ZBD is a fully licensed payment service provider, licensed in Europe as an EMI/MiCAR-compliant operator and in the United States with Money Transmitter Licenses across states
  • The Earn SDK docs say developers can credit rewards at any amount and any time, while user withdrawals are limited by a threshold tied to gameplay time
  • The rewarded-play guide claims developers can sometimes earn 80% to 200% more per user by spending 10% to 20% of ad revenue on player rewards, and emphasizes that rewards are mainly a retention tool
  • The security docs say the SDK pings the backend roughly every 20 seconds to measure “Time Alive,” uses Apple and Google attestation systems, and strongly recommends calling reward-sending endpoints only from the developer’s backend server
  • The security docs also note optional additional withdrawal verification such as CAPTCHAs or facial recognition for abuse mitigation
• Whitepaper: No canonical standalone ZBD whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, products/about pages, docs home, llms.txt index, and Earn-SDK/security docs; see ../whitepapers/zbd-primary-sources-2026-05-01.md.
• Sources:
  • https://zbdpay.com/
  • https://zbdpay.com/about
  • https://zbdpay.com/products
  • https://docs.zbdpay.com/
  • https://docs.zbdpay.com/llms.txt
  • https://docs.zbdpay.com/rewards/sdk
  • https://docs.zbdpay.com/earn/knowledge-base/rewarded-play.md
  • https://docs.zbdpay.com/earn/sdk/security.md

Internal linkages

• Best upward reads when hosted balances, payout routing, and operator policy matter more than the front-end wallet: blink, galoy, and open-payments.

• Last reviewed: 2026-05-27 UTC