Skip to main content
You create players from your backend with your own ID for them, and ZBD collects everything else directly from the player, in the widget. Your systems never hold identity documents, tax forms, or bank details.

​
When a player verifies

Players can hold a balance, earn, and spend without verifying. They have to verify when they:
  • Load fiat into their account
  • Sell an item for fiat in your marketplace
  • Cash out
You decide where verification appears in your game. Some studios ask at signup, so players are ready when they need it. Others wait until the first cash out. For marketplaces, we recommend asking sellers when they create their first listing, since a fiat sale fails if the seller isn’t verified.

​
Tiers

Because ZBD holds every player’s balance, verification is tiered. A player starts at a lower tier and verifies further as they need to. Their tier sets how much they can cash out and how quickly. When a cash out needs a higher tier than the player has, the widget asks for the next step at that point, so you don’t have to track tiers yourself.

​
What ZBD collects

All of this runs in the widget’s flows. See Embedding the Widget.

​
Checking where a player stands

Get a User returns kyc_status. Use it with cashable from Get Balances to decide what to show the player, like a cash out button or a prompt to verify. The widget sends browser events as a player finishes verification or adds a payment method, so your UI can update straight away.