roulette api: Track En Prison Stakes Across Spins

A roulette api integration can settle ordinary wins correctly and still mishandle money when a wager survives into another spin. This matters on tables offering en prison, where an eligible even-money bet may remain locked after zero instead of settling immediately. The practical integration challenge is preserving that financial obligation across spins, disconnects, and table changes without charging the player again or releasing the stake prematurely.

This guide focuses on accepting and settling carried wagers. It is not a general roulette payout guide: the launch decision is whether your platform can account for money that remains committed after the original spin ends.

Why a finished spin may not mean a finished wager

On a conventional single-zero roulette table without a special zero rule, zero loses for even-money bets such as red/black, odd/even, and low/high. With la partage, eligible bets generally return half the stake when zero appears. With en prison, an eligible stake can instead remain committed for resolution on a subsequent spin.

Under a common en prison rule, a later favorable result returns the imprisoned stake without an additional win; an unfavorable result loses it. Repeated zero outcomes require particular attention because their treatment varies by table rules. Some tables also offer choices after zero rather than applying one automatic treatment.

Never infer those rules from a game name, language, or visual table layout. Obtain the exact provider rules for the specific game version.

The accounting distinction is simple: a completed spin does not necessarily extinguish every wager associated with it. A player can have an old imprisoned stake and a new wager exposed to the same next result.

Define the roulette api carried-stake contract

Before implementation, ask how the provider represents imprisoned wagers. They may be exposed as individual bet events, carried inside a longer logical round, or reflected only through aggregate settlement callbacks. Do not assume a dedicated en prison endpoint exists.

Document these points for each supported table:

• Which bet types qualify, and whether the rule is automatic or player-selected.
• What happens after the first zero and after consecutive zeros.
• Whether an imprisoned stake can be surrendered or otherwise released.
• How stakes resolve when the player leaves or the table closes.
• Whether callbacks identify the originating wager and subsequent resolving spin.
• Whether settlement amounts mean gross wallet credits or net winnings.
• Which event makes the wager financially final, including corrections.

Separate spin identity from wager identity

If the integration exposes sufficient detail, retain an originating wager reference alongside each linked spin reference. A reference to the latest spin must not overwrite the wager's history.

A useful internal record includes the provider, table, player, currency, originating wager, original stake, committed amount, rule version, linked events, and financial state. These are your accounting fields, not assumed GamingAPI or provider payload names.

If callbacks expose only aggregate round totals, ask for a report or support trace that explains carried-stake resolution. Do not manufacture wager-level detail from animation events. The evidence must still let you reconcile debits, credits, and any remaining committed amount.

Model the obligation without inventing wallet movements

Treat imprisonment as a change in wager state, not automatically as a new debit. Where the original wager has already reduced the player's wallet balance, carrying that same stake forward should not reduce it again.

An illustrative lifecycle is:

1. Accepted: the original stake is successfully debited.
2. Carried: zero triggers the applicable en prison rule; the stake remains committed.
3. Resolved: a subsequent result determines the amount returned, if any.
4. Corrected: an authoritative adjustment changes the prior resolution, with an auditable financial effect.

Use the provider's actual contract to implement transitions. Your internal state names need not match its event vocabulary.

Keep available balance and committed stake distinct

A €10 imprisoned stake is not automatically €10 available for withdrawal. Equally, it should not vanish from your player-support records simply because the originating spin is marked complete.

Keep committed exposure visible in reconciliation and support tooling. If the provider owns the game display, confirm how players can see an unresolved stake after reconnecting. Avoid implying your platform can render detailed carried-bet information unless the integration supplies it.

Walk through the money before writing acceptance tests

Assume a player starts with €100 and places €10 on red. The accepted bet reduces the available balance to €90. Zero appears, and the documented rule imprisons the stake.

At this point, the expected position is €90 available and €10 committed. There is no second €10 debit merely because another spin begins.

If the next result is red and the agreed rule returns only the imprisoned stake, the wallet receives €10 and returns to €100. Crediting €20 would incorrectly treat the old wager as an ordinary winning red bet.

If the player also places a fresh €5 red bet before that next spin, keep its economics separate. The balance falls to €85. A red result produces a €10 return for the imprisoned stake plus a €10 gross return for the fresh winning bet, leaving €105.

These examples assume gross settlement credits and no unrelated wallet activity. If the provider uses net-result fields, translate them according to the contract rather than copying the example amounts into callback handling.

Build a focused acceptance matrix

Use a provider-supported sandbox, controlled results, or approved event fixtures. Do not rely on waiting for a convenient sequence during casual play.

Test outcome sequences

Include at least:

• Zero followed by a favorable result: return only the amount specified for the imprisoned stake.
• Zero followed by an unfavorable result: clear the obligation without an unwarranted refund.
• Consecutive zeros: match the documented rule rather than a guessed default.
• Old imprisoned and new ordinary bets resolving together: keep their return calculations distinct.
• Multiple eligible bets imprisoned simultaneously: preserve each obligation or a provably equivalent aggregate.

For each case, record starting balance, accepted debits, settlement credits, ending balance, and remaining committed stake.

Test interrupted lifecycles

Disconnect after the first zero, reconnect, and verify that the obligation survives. Then repeat with session expiry and a provider-side table interruption.

Also replay settlement notifications. A repeated notification must not release the stake twice. Deliver related events in the ordering permitted by the contract and confirm your system does not mark the obligation final before it has sufficient evidence.

Test the provider's documented correction process after a carried wager has resolved. Preserve both the original result and the adjustment; silently rewriting history makes financial investigation harder.

Protect existing wagers during operational changes

A table configuration change must not silently rewrite the terms of an already accepted wager. Associate existing obligations with their applicable rules and obtain the provider's transition policy before changing a table's zero treatment.

For a planned removal, stop new entries only through supported controls and identify outstanding committed stakes. Agree how those stakes will resolve if no further live spin takes place. Do not assume closing a table authorizes the operator to refund, forfeit, or manually settle them.

An exception queue should show the obligation, its age, the last authoritative event, the currency, and the support owner. An aging threshold should trigger investigation, not automatic financial finality.

Set a clear launch gate

Approve a table only when evidence establishes that:

• Every accepted stake is accounted for as resolved or still committed.
• Replayed messages do not change money twice.
• Consecutive-zero behavior matches published rules.
• Support can explain a carried wager across sessions.
• Table interruptions have a documented resolution path.

GamingAPI offers 16,000+ games from 150+ studios through one API, with seamless wallet and multi-currency support. That catalog scale is not evidence that every roulette title supports en prison or exposes identical settlement detail. Use the docs to guide integration questions and contact to confirm the specific table's rules and available test evidence.

FAQ

Does every roulette table support en prison?

No. Check the specific table rules and version. A single-zero wheel alone does not establish that en prison or la partage applies.

Should the wallet debit an imprisoned stake again?

Not merely because it carries into another spin when the original stake was already debited. Any additional debit needs a distinct, contract-supported financial reason.

Can we launch without individual carried-wager callbacks?

Potentially, if authoritative aggregate settlement and supporting records prove balance correctness and outstanding obligations. If unresolved exposure cannot be explained or reconciled, keep that table out of production.