Customer API
You call us. List the game catalogue, mint launch URLs, run free round campaigns.
Wallet Callbacks
We call you. Authorize the player, debit the stake, credit the win, roll back on failure.
The whole integration in one picture
Start here
Understand the model
Read Architecture — 5 minutes, and the rest of this site stops being a surprise.
Sign your first request
Every call in both directions is HMAC-signed. Request signature has copy-paste clients in six languages, all checked against the same test vector.
Implement the wallet
Five endpoints on your side. Wallet integration covers the money rules that certification actually tests.
Launch a game
Game launch turns a click into a running session.
Certify and go live
Work through the go-live checklist.
The rules that trip people up
Amounts on the wire are decimals, not minor units
Amounts on the wire are decimals, not minor units
Callbacks exchange
12.45, not 1245. We store minor units internally; you never see them. Crypto is capped at 8 decimal places even when the chain allows more. → Amounts and currenciesA losing round still sends you a credit
A losing round still sends you a credit
Every debit is settled. A loss arrives as a credit with
payout.amount of 0. Treating that as an error is the single most common integration bug. → Wallet integrationCredit and rollback must work without a player session
Credit and rollback must work without a player session
They are retried for up to 3 days. The player may be long logged out. Do not gate them on a live token. → Errors and retries
422 and 500 on debit mean opposite things
422 and 500 on debit mean opposite things
422 = the transaction definitely does not exist, we will not roll it back. 500 = it might exist, we will roll it back. Getting this backwards leaks money. → Errors and retriesNeed credentials, a staging host, or help during certification? Write to integrations@zerodash.studio.