← Production guides

Technical field guide

What your integration team needs before launch

Start with an identifiable game build and target connection. Agree session and wallet behaviour, supported configurations, failure handling, acceptance evidence and release owners. An existing adapter can reduce work; the game, platform revision and commercial route still need confirmation.

Identify the exact connection

Record the operator, platform or aggregator, environment, API revision and technical contact. Name the intended adapter and separate confirmed support from assumptions. Directory inclusion does not establish every currency, jurisdiction or feature.

For operators, identify wallet and launch ownership. For platform providers, confirm tenant configuration and game registration. For aggregators, confirm catalogue identifiers, downstream routing and the relevant staging route.

Bind the game to a reproducible version

Record the game identifier, client build version, maths/configuration version and integrity hash. Identify demonstration versus production configuration. Both teams should know which build produced a result.

A changed build needs a decision about what to check again. Keep the release artefact, configuration and acceptance record together.

Agree what happens when a request repeats

Write down session lifetime, launch and return URLs, authentication method and wallet model. Identify round and transaction IDs, expected balances, error states and reconciliation ownership. Exchange credentials privately.

Walk through a lost response: a transaction is submitted, the response disappears and the client reconnects. State how systems distinguish a retry from a new transaction and recover the authoritative result. Do the same for cancellation and rollback.

  • Expired or invalid session
  • Repeated transaction or delayed response
  • Interrupted round and reconnection
  • Cancellation, rollback and reconciliation
  • Return-to-lobby and useful error messaging

Turn support claims into a matrix

List required currencies, languages, orientations and intended jurisdictions. Mark each confirmed, pending or excluded for this connection. Assign an owner and explanation to every pending item.

Technical integration, commercial permission and external approval are separate dependencies. Identify who supplies required evidence and who makes the release decision.

Record repeatable acceptance evidence

For each scenario, capture environment, build/configuration, steps, expected result, actual result and relevant redacted identifiers. Cover normal play, interruption, errors and reporting. Keep client data and credentials out of screenshots.

Our route brief provides a field-by-field structure. It is a planning resource, not a claim that any adapter has passed a specific acceptance suite.

Name release and support owners

Identify who deploys, who can pause a launch, who receives incidents and who reconciles affected rounds. Agree support hours and escalation in the proposal.

Send your intended route, game and markets. We confirm the existing adapter, configuration and remaining acceptance work before committing to a launch plan.

Put it into practice.

Use these editable planning resources with your team. They are examples, not a quote, certified model or committed delivery scope.

Download the production handover register ↓Download a fictional slot brief example ↓Integration route brief · CSV ↓Explore integration routes ↗Technical readiness services ↗Discuss your route ↗

Your project. One shared space.

Shape your idea in Creator, review the visuals and agree the next step in your private client studio.

Ready to shapeyour project?

Bring a rough direction or a detailed brief. We’ll help define the next step.