Win

155 calls your wallet (signed with X-Marbles-Signature) to register a win or loss — the settlement of a bet. For winning bets, add the win amount to the player's balance. For losing bets, the amount is 0.

Endpoint

POST /win

Request

POST /win HTTP/1.1
Host: your.game.api
X-Marbles-Signature: <signature>
Content-Type: application/json

{
  "requestId": "8df0475e-5069-483a-8205-f6089997abc9",
  "transactionId": "9ea48131-3a0f-4067-94d0-3212e7e25abb",
  "referenceTransactionId": "ea0240f5-483d-434b-a8d4-04dabf61cde3",
  "clientSessionId": "0k3cz83bb3h2vn53ocnc7pxw9",
  "clientPlayerId": "02mnrpyv2qd9jbwhoniyimxsy",
  "roundId": "17cc81fd-df13-4ca4-857d-de0f766dc372",
  "gameId": "f1c0b104-f29d-44a9-ae93-e8afcbe3feb9",
  "amount": 1000000,
  "currency": "USD",
  "roundClosed": true,
  "timestamp": "2025-06-15T14:30:00Z"
}

Request Fields

Round Lifecycle

On /win, roundClosed is always true — each /win settles and closes its own per-bet round, and no further transactions follow for that bet. (The true/false distinction only matters on /rollback.)

Win vs Loss

• Win: amount > 0 - Add this amount to the player's balance
• Loss: amount = 0 - No balance change needed (bet was already deducted)

Freebet Results

When the original bet was a freebet, the request includes:

{
  "requestId": "...",
  "transactionId": "...",
  "referenceTransactionId": "...",
  "amount": 1500000,
  "currency": "USD",
  "isFree": true,
  "rewardUuid": "promo-winter-2025-001",
  "roundClosed": true
}

• isFree is true to indicate the original bet was a freebet
• rewardUuid contains your clientRewardId for tracking which promotion this freebet belongs to
• For wins: Credit the amount as real money to the player
• For losses: amount is 0, no action needed

Response Contract

Always respond HTTP 200; put the outcome in status. We read the status field, not the HTTP code, to decide what happens to the settlement.

The full status set lives in Error codes — that is the canonical home for the enum across all callbacks. For /win the relevant outcomes are:

/win recognises only SUCCESS and DUPLICATE_TRANSACTION_ERROR as applied. Any other status — including BONUS_ERROR — or a non-200 or timeout means the settlement was not recorded: the same /win, with the same transactionId, will be re-sent periodically until you accept it. Re-sends can continue for hours, and a settlement can also be re-delivered much later (e.g. after an outage) — your transactionId dedupe must not expire quickly. See Settlement timing & retries.

Idempotency

Networks retry, so 155 may resend a callback it isn't certain landed. Dedupe by transactionId so a retry never moves money twice. The returned status for a replay differs by callback — this is the most common point of confusion:

The asymmetry is deliberate. A replayed /bet is surfaced as DUPLICATE_TRANSACTION_ERROR — a duplicate is not a new bet, and flagging it tells 155 the stake was already debited. A replayed /win or /rollback returns plain SUCCESS: the settlement is simply re-confirmed, the money already moved once, and there is nothing to flag. In both cases the balance is unchanged — return success without crediting again; do not credit the win a second time and do not cancel the original credit.

Worked Examples

Success — first /win

The win settles and the player's balance reflects the credit.

HTTP/1.1 200 OK
X-Marbles-Signature: <signature>
Content-Type: application/json

{
  "status": "SUCCESS",
  "requestId": "8df0475e-5069-483a-8205-f6089997abc9",
  "clientPlayerId": "02mnrpyv2qd9jbwhoniyimxsy",
  "currency": "USD",
  "balance": 1000000
}

Replayed /win — same transactionId

155 resent the callback. You return the original settlement result: still SUCCESS, balance unchanged (you do not credit the win again).

HTTP/1.1 200 OK
X-Marbles-Signature: <signature>
Content-Type: application/json

{
  "status": "SUCCESS",
  "requestId": "8df0475e-5069-483a-8205-f6089997abc9",
  "clientPlayerId": "02mnrpyv2qd9jbwhoniyimxsy",
  "currency": "USD",
  "balance": 1000000
}

Response Fields

Error Response

HTTP/1.1 200 OK
X-Marbles-Signature: <signature>
Content-Type: application/json

{
  "status": "UNKNOWN_ERROR",
  "requestId": "8df0475e-5069-483a-8205-f6089997abc9",
  "clientPlayerId": "02mnrpyv2qd9jbwhoniyimxsy"
}

Common Mistakes

• Rejecting a /win replay. A replayed /win returns SUCCESS (preferred) — DUPLICATE_TRANSACTION_ERROR is also accepted as applied. What you must never do is treat the replay as a failure (see Idempotency).
• Re-crediting on a replay. The money already moved on the first /win; a replay must not add the win amount again, and must not reverse the original credit.
• Returning a non-200 HTTP status (or a bare error body). Always respond 200 with the outcome in status.

See the Response Contract above for what 155 does with each status, and Error codes for the canonical enum.