Skip to main content
Each account also records every transaction and carries the permissions that decide what the player can do.

The objects

Creating a user sets up an account for each currency your program uses, so you can credit them straight away.

Creating a user

You create users from your backend with your own identifier for the player. No identity documents or personal data are needed. Players can hold a balance, earn, and spend without verifying. Players and Verification covers when they need to verify and what ZBD collects.

How balances are calculated

A balance is the sum of every ledger entry for that account. Each entry has a source tag recording where the value came from. The total is what a player can spend. What they can cash out depends on the source tags behind it, so a player with a balance of 1,700 might be able to cash out all, some, or none of it. ZBD sets the rules for each tag, and your ZBD contact can walk you through how they apply to your program.

Your own accounts

You hold a primary account in each currency, plus an account for each game that you top up from it. Cash outs for a game are paid from that game’s account. Keeping only a game’s expected cash outs there limits how much a leaked key or fraud can reach. Top-ups are manual. Agree a warning level and a critical level with ZBD, and a webhook fires when a game’s account drops below either one.

Reading balances

Get Balances returns each of a player’s balances, with what they can spend (available) and what they can cash out now (cashable). List Transactions returns the history behind them. We recommend reading these from ZBD instead of tracking balances yourself, since source tags and conversions affect what a player can do with their balance.