Use this page for aggregation and game integration. If the project replaces the complete core platform, review the casino engine.
Confirm the catalog before comparing game counts
Identify priority studios and titles, player territories, currencies, devices and any required promotional functions. Confirm the relevant supplier and commercial permissions. A studio listed in a broad catalog is not a commitment that every game or configuration is available to your business.
Keep exclusions in the scope. A title that launches in demo mode may still need approval or a different configuration for real play. The provider selection page sets out the information to request for the shortlist.
Decide where the player's funds sit
| Wallet arrangement | Operational consequence | Verification question |
|---|---|---|
| Seamless wallet | Game transactions call the agreed account ledger | How are debits, credits and reversals acknowledged and reconciled? |
| Transfer wallet | Funds move between a main account and a provider balance | How are pending transfers, returned funds and provider balances recovered? |
The arrangement affects available balance, withdrawals, bonuses and support. Establish the actual behavior of each connected supplier instead of assuming every studio handles interrupted play in the same way.
Distinguish a round from its transactions
A round identifier groups the events belonging to the game round. Transaction identifiers distinguish the individual financial actions. A round may contain several credits or another sequence permitted by the game. Do not assume every round has one debit and one credit.
Define balance checks, debits, credits and reversals in the actual interface documentation. Specify which original event a correction refers to and what happens if it arrives after a later event. A retry should be recognizable as the same request, rather than interpreted as another stake or win.
The session and financial record also have different lifetimes. A player closing the browser does not prove that every round has completed. Identify the report and owner for outstanding rounds and transactions.
Agree the acceptance evidence
Test a successful launch, repeated debit, timeout after a financial action, currency mismatch and interrupted round. Include a later credit or reversal where the supplier's documented sequence permits it. Reconcile the player ledger with the provider's report using the original identifiers.
For each case, retain the request, response, expected state and actual result. Define who investigates disagreement and what allows the integration to proceed to production. Exact signing, retry, expiry and rate-limit behavior must come from the agreed documentation.
Estimate the work from your starting point
The schedule depends on your wallet, authentication, transaction history, catalog setup and testing capacity. Identify gaps in those components before quoting the integration as a fixed number of days. Keep supplier approval and technical acceptance as separate dependencies.
Request the relevant API documentation and scope. Send your operator and market information, wallet model, required studios and currencies. Include an outline of the ledger's existing retry and reversal handling so the discussion can address the difficult part early.