ZBD primary sources — 2026-05-01

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is ZBD’s official website, products/about pages, docs home, llms.txt index, and Earn documentation.
• The public materials consistently position ZBD as a regulated payments stack for gaming and interactive entertainment rather than as only a Bitcoin wallet or gamer rewards gimmick.

Primary-source snapshots

1) Official homepage / Earn page

• URL: https://zbdpay.com/
• Key excerpt:
  • The main site currently redirects into the Earn product and pitches “real money engagement” for games.
  • It highlights a lightweight Unity SDK, embedded rewards, fast payouts, and case-study KPI lifts such as retention and ARPDAU changes.

2) Products page

• URL: https://zbdpay.com/products
• Key excerpt:
  • The products page says ZBD helps game studios build direct financial relationships with players.
  • It highlights three operating layers: branded debit cards, payouts, and embedded accounts.
  • It says payouts can reach bank accounts, Cash App, Kraken, Coinbase, gift cards, and more, while embedded accounts are meant for player-to-player transfers and creator economies.

3) About page

• URL: https://zbdpay.com/about
• Key excerpt:
  • The page says ZBD is a fully licensed payment service provider built for gaming.
  • It claims EMI/MiCAR-style coverage in Europe and Money Transmitter License coverage in the United States.
  • It presents the company as a remote fintech/gaming infrastructure team with millions of engaged gamers and substantial venture backing.

4) Docs home

• URL: https://docs.zbdpay.com/
• Key excerpt:
  • The docs home describes ZBD as the “global Bitcoin payments API for app and game developers” and a “Global Payment Service Provider for Gaming and Interactive Entertainment.”
  • This is the clearest current top-level technical framing of the platform.

5) Docs llms.txt index

• URL: https://docs.zbdpay.com/llms.txt
• Key excerpt:
  • The index shows a surprisingly broad surface beyond the basic SDK pitch, including app downloads, region coverage, rewarded-play guidance, OAuth2 login, SDK docs, dashboard controls, and security guidance.
  • This breadth helps explain why ZBD is better cataloged as a payments/control-plane stack than as a single app feature.

6) Earn SDK page

• URL: https://docs.zbdpay.com/rewards/sdk
• Key excerpt:
  • The page says the Earn SDK lets developers credit rewards to users at their discretion while limiting user withdrawals based on gameplay time.
  • This reveals a core product design choice: rewards are flexible on the studio side but operationally rate-limited on the withdrawal side.

7) Rewarded-play guide

• URL: https://docs.zbdpay.com/earn/knowledge-base/rewarded-play.md
• Key excerpt:
  • The guide frames rewards as a retention tool and claims some games can earn materially more per user by redistributing part of ad revenue as rewards.
  • It is notable as primary-source evidence that ZBD is selling a business-performance playbook, not only an SDK.

8) Earn SDK security page

• URL: https://docs.zbdpay.com/earn/sdk/security.md
• Key excerpt:
  • The page explains that client-side reward sending is abuse-prone and strongly recommends calling reward endpoints from the developer’s backend.
  • It says the SDK tracks “Time Alive” with backend pings roughly every 20 seconds and uses Apple/Google attestation to reduce tampering.
  • It also notes optional anti-abuse escalation such as CAPTCHAs or facial recognition during withdrawal.

Working conclusion

ZBD is best cataloged as a gaming payments and rewards control plane with Bitcoin-native and fiat-adjacent payout surfaces. The decisive signals in this pass were the combination of regulated PSP language, the breadth of the docs surface, and the way rewards, payouts, debit cards, login, and embedded accounts all sit inside one gaming-focused financial stack.