Skip to content

Frontend release checks

Use this checklist for a complete frontend. A successful SDK call or documentation build does not certify a game.

Integration inputs

Record the deployed engine version, archive version, SDK version, operator protocol, currencies, jurisdictions, and product classifications. Retain approved rules and translations.

Resolve every applicable contract gap. The frontend must have a defined behavior for each setting in the reference.

Shared acceptance matrix

AreaRequired cases and expected behavior
LaunchValid launch, missing parameters, expired token, refresh, and wrapper setup. Exactly one launch exchange.
LoadingSlow assets, failed assets, localization, loadMsg, minimum duration, entry paytable, and restored round. No early paid input.
StakesMinimum, maximum, below/above bounds, custom list, empty list, range input, invalid saved stake, and forced default. Validate all input routes.
CurrencyAt least two currency multipliers, custom/social display, complete buy cost, and bought-round recovery. No double conversion.
RequestsDouble click, held key, touch repeat, wrapper spin, and autoplay. At most one money request at a time.
TimingFast network, slow network, hidden tab, pause during animation, turbo, stop, and report failure. No early cycle start.
MoneyLoss, equal-stake return, win, cap, partial bank, full collect, and lost credit response. Balance matches the server.
RecoveryReload during base spin, cascade, feature, choice, gamble, and collect. Continue the existing round without another debit.
ErrorsInsufficient balance, processing, rate limit, session expiry, reality check, network loss, and unknown code. No automatic money retry.
Operator InterfaceEvery required incoming event, notification ordering, pause acknowledgement, navigation, promotion, and error dialog.
Audio and deviceLocal and operator mute/unmute, audio unlock, hidden tab, orientation, fullscreen restriction, resize, and teardown.
RulesEvery enabled mechanic, paytable variant, feature RTP, maximum win, required odds, and missing information.
Responsible gamblingReminder offset, elapsed time, net position, financial limit, inactivity, required break, and reload persistence.
FreeplaysMultiple ticket types, fixed stake, wrong currency, final ticket, feature ticket, expired availability, and reload.
PromotionsDiscount expiry, refreshed eligibility, package mapping, and correct accounting.
AccessibilityReadable required text, keyboard focus, touch targets, scrollable rules, and non-dismissible mandatory acknowledgement.

Slot outcome fixtures

Use approved test outcomes in a test environment. Do not wait for rare outcomes to occur naturally. Never enable outcome forcing in production.

Exercise every mechanic present in the archive:

  • Base loss, small return, stake-equivalent return, large win, and exposure cap.
  • Every pay mode, override win, multipay breakdown, and feature payline override.
  • Expanding wilds, substitutions, duplication, sticky changes, and book expansion.
  • Cascades with no continuation, multiple nested steps, and changing multipliers.
  • Freespin trigger, retrigger, re-entry, and different feature dimensions.
  • Hold and Win locks, boosters, cell modifiers, collector sweeps, full grid, and exhausted lives.
  • Wheel result, random feature entry, collector levels, and accumulated multipliers.
  • Persistent counters, cash awards, feature awards, and mixed player choices.
  • Within-round jackpots and their reset at the next round.
  • Card colour/suit gambles, ladder climb/bust/top, and bank-then-lose.
  • Consolidated and non-consolidated scenarios, with reload at each decision boundary.

Verify displayed breakdowns against final totalWin and wallet settlement. Presentation values must not create duplicate credits.

Every creator mode

The creator exposes 14 modes. Each needs the shared acceptance matrix plus these cases:

Mode and guideInputs, results, and extra checks
SlotStakes, bonuses, scenarios, and all enabled mechanics above.
ProgressiveNo initial buy; survive/bust, player cashout decision, absolute multipliers, final auto-close.
PlinkoReturned row/risk table ID, bucket index, multiplier, and one-round settlement.
Hi/LoOriginal higher/lower/skip choice indexes, card odds, skip behavior, collect, and bust.
Over/UnderDirection/threshold table, boundary numbers, roll, and settlement.
FroggerRisk table, progression, collect-or-continue, and final step.
MinesEvery call's pick, duplicate/invalid pick, mine-count table, board reveal, and collection.
KenoManual/automatic numbers, distinct valid picks, pick-count/risk table, matched numbers, and paytable.
MatchBall count, exact/at-least target, arrangement, one-based matched slots, and per-bet odds.
BingoTicket count, both variants, free cells, daubs, contained patterns, and full debit.
CrashShared request/event socket, multiple bets, auto/manual cashout, reconnect, and final balance.
RouletteEvery offered bet shape, total stake, zero handling, wheel rules, and each settlement.
BlackjackAvailable actions, side bets, split/double/insurance costs, hidden dealer card, and final settlement.
Blank/importedVersioned custom schema, unknown-type rejection, and its declared input/recovery contract.

Jurisdiction evidence

Test every named preset that the release supports. Include player-specific overrides and markets without presets. Read the jurisdiction inventory.

For UKGC slots, test the £2 and £5 player tiers. For other casino classifications, test the applicable five-second cycle interval. Test the absence of autoplay, rapid reveal, simultaneous play, and inappropriate celebrations.

For Germany, test the agreed reminder and break across refresh. For Brazil, test paytable on entry, translated errors, and demo-balance behavior. For Ontario, test the required odds, net position, and inactivity policy.

Obtain the operator's acceptance of the complete integration and its jurisdiction configuration. Record the game certificate and approved messages. Do not mark a missing required odds value or session service as “passed”.

Documentation example checks

This repository runs npm run check:sdk-examples. It compiles the public examples against SDK 0.2.18 and runs deterministic request tests.

Those checks cover guards, metadata, timing, and transport envelopes. They do not exercise a live wallet, certify rules, or replace operator-wrapper tests.