Wallet, on your server
wallet.loss
Tells you a round ended with no win.
Who calls it
We → you
POST {your server}/v1/wallet.lossWe send it when a round ends with no win. You end your own round record and raise your own “round completed”. We sign the call with our private key. Check it with our public key for the environment. See Signing calls. You answer within 5 seconds.
Request
| Field | Type | What it is |
|---|---|---|
transactionId | string | The same call again moves no money. |
roundId | string | Links the stake to its win, loss or refund. Store your own round with it. |
sessionId | string | Links the money to our session. |
casinoSessionId | string | Links the money to your own session. |
playerId | string | Whose balance. |
currency | string | Which money. |
traceId | string | One search finds the whole chain on both sides. |
Answer
Accepted: "ok": true. There is no balance in this answer.
If you do not answer
- We send the same wallet.loss again with the same transactionId, until you accept it.
- After 1 hour it goes on the stuck list. See Retries.
Errors
- You must accept it. Always, even after the session closed, the player was blocked, or during maintenance.
duplicate_mismatch: the item goes on the stuck list. No retry.already_endedoralready_refunded: a bug on our side. The item goes on the stuck list.
Example
Request
{
"transactionId": "t-01JC92…",
"roundId": "r-01JC93…",
"sessionId": "s-01JC8Z…",
"casinoSessionId": "c-5531",
"playerId": "p-82731",
"currency": "EUR",
"traceId": "tr-01JC…"
}
Answer
{ "ok": true }