ZBD company primary sources — 2026-08-09

Project status in this pass

• No canonical standalone company whitepaper or litepaper surfaced.
• The useful source bundle for the company split was ZBD’s about, products, privacy, docs-home, OAuth, and Earn-security pages.
• The current materials make ZBD look more like a regulated gaming-payments operator shell than like a neutral wallet or protocol surface.

Primary-source snapshots

1) About page

• URL: https://zbdpay.com/about
• Key excerpt:
  • ZBD calls itself a global team assembled to fundamentally disrupt payments in the gaming industry.
  • The page says ZBD is a fully licensed payment service provider operating natively in the world's top markets.
  • It highlights licensing and assurance markers including MTLs, SOC2, MiCAR, EMI, and PSD2.

2) Products page

• URL: https://zbdpay.com/products
• Key excerpt:
  • ZBD says it handles virtual currency conversion, compliance, and card management for branded debit-card flows.
  • It says users and creators can withdraw balances directly to their bank accounts in USD & EUR.
  • It lists payout destinations such as Bank deposit, Cash App, Kraken, Coinbase, gift cards, and more and pitches Licensed bank accounts built in-game.

3) Privacy page

• URL: https://zbdpay.com/privacy
• Key excerpt:
  • The footer identifies © 2026 ZEBEDEE, LLC and NMLS ID number: 2188007.
  • This is a useful grounding signal that the live operating shell is a named money-services company, not only an app brand.

4) Docs home

• URL: https://docs.zbdpay.com/
• Key excerpt:
  • The docs title ZBD as Global Payment Service Provider for Gaming and Interactive Entertainment.
  • The docs also describe the stack as The global payment infrastructure built for the speed and scale of gaming and present ZBD Earn, payments APIs, ramp, SDKs, and app surfaces under one technical shell.
  • The footer links to a ZEBEDEE EUROPE B.V. - Website Pricing Policy v1.0 document, which is useful evidence of a multi-entity operating perimeter.

5) OAuth docs

• URL: https://docs.zbdpay.com/earn/oauth2
• Key excerpt:
  • ZBD describes ZBD Login as money-enabled OAuth2.
  • It says apps can obtain ZBD gamertags, Lightning Addresses, profile data, verification status, and other permissions from a shared ZBD account.
  • This makes the company-run identity and wallet surface part of the real product boundary.

6) Earn SDK security docs

• URL: https://docs.zbdpay.com/earn/sdk/security
• Key excerpt:
  • ZBD says it geolocates users by IP and uses that to decide shown payout methods, withdrawal limits, and regional support.
  • It says VPN/proxy detection can cause SDK initialization to fail and that Time Alive is built through server pings about every 20 seconds to gate withdrawal volume.
  • It says Apple / Google device attestation is used, that developers should move reward sending to the backend and allowlist server IPs, and that CAPTCHAs or facial-recognition checks can be enabled for higher-risk withdrawals.

Working conclusion

ZBD clears the bar for a company/entity note because the practical dependency is not just a game-reward SDK or Bitcoin payout endpoint. It is a named operator that controls partner onboarding, identity, anti-fraud policy, withdrawal gating, payout-route availability, and the regulated shell around gaming money movement.