The infrastructure behind casinos
A double-entry wallet that cannot drift, native crypto custody across EVM chains, a white-label back office your team actually runs — and security designed for the day someone tries.
A ledger built like a bank's, verified like a blockchain's
When your CFO, a partner, or a regulator asks “can you prove it?”, the answer is a report — not a meeting. Every transaction is a balanced double-entry posting with a cryptographic hash chain over the history: tamper-evident by construction, verifiable on demand.
All monetary computation is integer arithmetic (BigInt) in minor units. No floating point exists anywhere in the money path — so a cent is always exactly a cent, across every currency, forever.
Daily automated reconciliation checks the ledger against cached balances and, for crypto, against on-chain reality.
- Pessimistic balance locking — negative balances are impossible, enforced at both application and database level.
- Idempotency keys on every money operation — network retries can never double-charge or double-credit.
- Real / bonus / locked balance separation with wagering-requirement tracking.
- Withdrawal locking — funds are ledger-locked the moment a player requests a payout.
- Multi-currency — fiat and crypto side by side in one ledger.
- Settlement processing and operator settlement addresses for revenue share.
Jackpot engine
Per-operator progressive pools. Contributions are posted atomically with bets in the same ledger transaction — the pool can never disagree with the books.
Bonus engine
Campaigns, wagering requirements, bonus-to-real conversion, and forfeiture handling — with bonus balances strictly separated from real money.
Withdrawal workflow
Pre-flight checks, an operator approval queue with full player context at decision time, broadcast monitoring, and stuck-transaction handling.
Native custody on EVM chains
A player sends USDT on Ethereum, BSC, Polygon, Arbitrum, Base or Avalanche at 3 a.m. The chain confirms, the balance credits, the deposit sweeps — and nobody on your team wakes up. That is what in-house custody means; this is not a third-party widget.
| Family | Chains | Assets |
|---|---|---|
| EVM | Ethereum · BSC · Polygon · Arbitrum · Base · Avalanche | ETH, BNB, MATIC, AVAX + USDT/USDC with correct per-chain contracts & decimals |
| Roadmap | Bitcoin · Solana · Tron | BTC, SOL, TRX + tokens — built and mainnet-verified, in provisioning |
| Solana | Solana | SOL + SPL tokens with ATA management |
| Tron | Tron | TRX + TRC-20 USDT/USDC |
HD deposit addresses
Hierarchically derived deposit addresses per player, per chain family — clean attribution of every on-chain deposit, automatically.
Per-chain deposit scanners
Chain-appropriate confirmation policies (e.g. 12 blocks on Ethereum, 128 on Polygon), instant player crediting on confirmation, pushed to your server by webhook.
Automatic sweeping
Deposits sweep to hot wallets automatically on the live EVM chains. Bitcoin and Tron sweeping is implemented and will activate when those chains are provisioned.
Sponsored gas, capped
EIP-1559-aware gas oracle and fee estimator per chain, TRON energy management for cheap TRC-20 transfers, and per-tenant daily gas budgets with warning and auto-pause thresholds — sponsored gas can never run away.
Institutional key management
Private keys managed via encrypted key store with cloud-KMS (GCP/AWS) signing adapters available. Cold-storage multisig workflows, hot/cold threshold monitoring, key rotation, documented disaster recovery, and an emergency pause that freezes all on-chain movement with one switch.
Provable solvency
The platform continuously verifies on-chain holdings ≥ player obligations, per currency, per tenant, with hot/cold/unswept breakdowns. Unknown-transaction detection flags any on-chain movement the ledger didn't originate.
A back office that carries your brand
Every operator gets their own branded admin panel — to your staff and your players, the platform is simply your platform. Ours never appears.
Player management
Search, profiles, balances, transaction history, notes, and per-player limits — everything support needs on one screen.
Withdrawal approvals
An approval queue that shows player context — balances, recent transactions, flags — right at decision time. Funds stay ledger-locked while pending.
Reports
GGR/financial, game performance, and player activity — on demand as CSV/JSON download, or cron-scheduled to your inbox.
Webhook console
Endpoint config, event subscriptions, secret rotation, test events, and a delivery log with per-delivery replay.
Responsible gaming
Limits dashboard, exclusions, and flagged-player review — the operator-side tools your license conditions expect.
Bonuses & branding
Bonus campaign builder with lifecycle management, plus a branding editor — colors and logo — for the white-label game UI.
First-party multi-channel delivery
Email (your own SMTP or SendGrid/AWS SES), SMS (Twilio/MessageBird), push (FCM + APNs), and in-app inboxes — with per-player preferences, templating, and priority-based channel routing. A real-time notification center keeps your operations team ahead of incidents.
Centralised monitoring
The platform includes centralised monitoring for tenant lifecycle, finance, RTP, incidents and system health — so you never host game servers, RNG, or wallets. Production support and SLA arrangements are agreed during onboarding.
Designed for the day someone tries
Factual, verifiable controls — the same list we hand to security reviewers.
Authentication
MFA with TOTP and WebAuthn/passkeys, OAuth, hardware-backed session management, brute-force lockouts, and separate admin/player token domains (RS256, JWKS-published keys).
Operator API
Hashed API keys (never stored in plaintext), optional IP allowlists, HMAC request signing, and per-environment keys. Launch tokens are single-use, 30-second, RS256-signed JWTs.
Identity never client-asserted
The API edge derives player identity from verified credentials on every request — a compromised front-end cannot impersonate another player.
Tenant isolation
PostgreSQL row-level security on every tenant-scoped table — a query physically cannot cross tenants. Isolation is structural, not procedural.
Transport & step-up
TLS 1.3 everywhere with HSTS and modern cipher suites. Withdrawal security includes step-up verification flows for high-risk actions.
RBAC & audit
Six admin roles with separation of duties, and immutable, hash-chained audit logging of every admin action — tampering breaks the chain and is detected.
Bring your CTO. We like hard questions.
Book a technical demo — ledger internals, custody architecture, solvency reporting, and the security model, live on real infrastructure.