Limits and maximum exposure
Limits are configured by Moonshot for the operator, game and currency. There is no
universal production limit table: obtain the actual settings during
onboarding. Launch does not accept caller-defined
limits or decimals.
Where limits apply
This is a conceptual acceptance checklist. Confirm the authoritative checks and payout interpretation for your operator, game and currency during onboarding. Stake checks cover asset precision, the agreed stake range and available exposure.
Stake limits control acceptance; payout caps control settlement. A callback retry must not apply a changed limit to an operation that was already committed.
| Setting | What to agree and test |
|---|---|
| Minimum/maximum stake | Asset denomination, allowed precision, boundary rejection and no debit on rejected bets. |
| Payout cap | Whether the configured game limit represents profit or gross payout; confirm the game-specific interpretation and settlement rounding. |
| Exposure | Concurrent open bets, operator treasury constraints and behavior at the cap. |
| Currency precision | Asset units are decimal strings; never assume every asset uses 2, 6 or 8 decimals. |
| Promotions | Per-play gross cap, package budget and coefficient limits are separate freeplay settings. |
Callbacks may include operatorMaxWin on a bet. Persist it with the original
accepted bet and apply the agreed interpretation during settlement. Do not derive
new limits from a frontend request or silently alter an authenticated payout.
Escalate a payout/limit mismatch and reconcile the original bet.
Request configuration changes through your Moonshot account manager, specifying the operator, environment, game, currency, requested values and expected traffic. Confirm the rollout window and retest the boundaries in sandbox. Do not assume a change is active until the effective settings have been confirmed.