NEXTGROUND · integration

Plug it intoyour wallet.

A seamless-wallet integration on your platform. Player funds never leave your wallet, every stake and payout is a call to your API, and we hold no balance at any point. Below is the whole of it: the five calls, what to expect, and where certification stands, written as it is, not as it will be.

18+ · Simulation · Play money · No real wagering

How you plug it in.

  1. Launch

    Your player opens the game

    Your platform calls our launch endpoint and receives a URL carrying a single-use session token, the player's currency, locale and jurisdiction.

  2. Session

    We validate and open a session

    The token is redeemed once. We check the jurisdiction against the list agreed for your account, and refuse anything outside it.

  3. Debit

    Stakes debit your wallet

    Every position opened is a debit call against your wallet API, carrying an idempotency key. A replayed call produces exactly one debit.

  4. Credit

    Payouts credit your wallet

    Closures and settled positions credit the same way. We hold no balance at any point.

  5. Settlement

    Rounds settle and reconcile

    Each round settles with a full transaction record and the revealed seed. The ledger is double-entry and reconciles to zero at every settlement.

Technically.

Integration type
Seamless wallet. Transfer wallet on request.
Launch
HTTPS, single-use session token
Transport
WebSocket for the live market at 20 Hz; REST for wallet calls
Client
HTML5, mobile-first. No download, no plugin.
Devices
Mobile, Tablet, Desktop
Currencies
Supplied by your platform in the session; the display label is configurable
Languages
English
Idempotency
Required on every wallet call. Replay-safe by design.
Geo-blocking
Enforced in our engine, per operator. Every refusal is logged.
Reporting
Per-round transaction records, and a monthly statement
Commercial
Revenue share, invoiced monthly. No integration fee.

What we need from you: your wallet API documentation, a test account, and the list of jurisdictions and currencies you serve.

Certification.

  • Where it stands

    Not certified

    No certificate is held, and none is claimed. The target scope is GLI-19 interactive gaming systems, GLI-11 where applicable, RNG certification of the keystream. Available to partners on request. Built to GLI-19 scope, not yet submitted.

  • The pack

    What a laboratory receives

    The RNG specification, the provably-fair mechanism, the mathematical model, the game rules as displayed, and a Monte Carlo simulation reproducible from a fixed seed. Available to operators and laboratories under NDA.

  • Built to certify

    The properties a laboratory tests for

    A deterministic engine, fixed-seed reproducibility, and a full audit trail. They are design constraints rather than an afterthought, which is why the same module runs the market and verifies it.

  • Per market

    Jurisdiction packages

    Derivative certificates per market, from the base report. Tell us which markets you need and we scope them with you.

The questions you would ask.

Commercial

  • How does licensing work with you?

    We supply under the operator's licence. You hold the player relationship, the wallet and the regulatory obligation; we supply the content into it. Tell us where you operate and we confirm the position for that territory.

  • What is the commercial model?

    A revenue share, invoiced monthly, with no integration fee.

  • Can we have exclusivity?

    Time-boxed exclusivity in a defined market is negotiable for a launch partner.

Technical

  • Seamless or transfer wallet?

    Seamless by default: every stake and payout is a call to your API with an idempotency key. Transfer wallet on request.

  • Who enforces geo-blocking?

    We do, in our engine, per operator. A launch carrying a jurisdiction outside the agreed list is refused and logged. We do not rely on your platform to filter for us.

  • What happens if a player disconnects mid-position?

    The position lives on the server, and stops are evaluated in the engine, so they fire whether the player is watching or not. A deadman switch closes an open position after ten seconds, on by default, and on reconnect the client receives the complete state.

  • How do we verify a round ourselves?

    The same way a player does. The commitment is published before the round, the seed after settlement, and the engine module that runs the market is the module that replays it. There is a working verifier on the fairness page.

Product

  • Why would a player choose this over a standard crash round?

    Because a bad entry is no longer the end of the round. The player steps out, waits, and buys back in, so a single decision becomes a session of decisions. Standing aside is a move, and it costs nothing.

  • Does re-entry break the mathematics?

    It would, if the game paid a multiple on re-entry. Ours reprices continuously and takes its margin as a visible spread of 3.00% plus a 2.00% retention on drift, which is why the return holds across strategies to within two points. That invariance is measured, not asserted.

  • Is it harder for a casual player?

    No. The default path is the one every crash player knows: open, watch, close. Re-entry is there when they want it and out of the way when they do not.

  • Can we see the mathematics?

    Yes. The RNG specification, the provably-fair mechanism, the mathematical model, the game rules as displayed, and a Monte Carlo simulation reproducible from a fixed seed are available to operators and laboratories under NDA.

What the FAQ does not cover, ask us.