This is a software decision. For license roles and the operating arrangement behind a complete launch, use the casino model comparison.
Name the system of record for each function
| Function | Decision before integration |
|---|---|
| Identity and account state | Does the engine own registration and verification state, or receive it from an existing PAM? |
| Player balance | Which ledger authorizes money movements and determines the available balance? |
| Game session and round | Which identifiers connect the player, game provider, debit, credit and reversal? |
| Bonus entitlement | Which system evaluates eligibility, consumption, expiry and conversion? |
| Operator reporting | Which record is authoritative when a dashboard and supplier statement differ? |
Retaining an existing component can reduce the amount being replaced, but it creates an interface that must handle changes and failures. A complete core replacement moves more records and workflows. Choose between them using the required change, dependencies and migration capacity.
Follow a round through the wallet
Ask the demonstration to connect game launch, stake reservation or debit, result credit and withdrawal availability. The record should explain what happens when a provider retries a request or a game ends after a session expires.
A repeated callback needs a stable transaction identity so that the same action can be recognized. An interrupted round needs a defined state and investigation path. Agree the expected ledger result for each case and who can resolve an exception without obscuring the history.
If you only need a content connection, the casino game API may define a narrower scope than replacing the engine.
Specify the controls your team will use
List the settings that operations may change, the changes that require supplier work and the approvals required for financial or player restrictions. Confirm how configuration versions are recorded and how a release is tested against existing integrations.
Data access, export, software licensing and source-code rights need separate terms. A right to use the engine does not establish ownership of every component. Ask how the business can retrieve the records it needs and maintain any custom work if the agreement ends.
Turn the demonstration into acceptance criteria
Use ordinary and exceptional transactions from your intended catalog and currencies. Check a duplicate callback, rejected debit, bonus expiry, restricted account and recovery after an interrupted connection. Reconcile account records with the provider report and record any remaining discrepancy.
Agree the load profile, recovery objectives, monitoring and support boundary for the production configuration. Include those requirements in the delivery scope; a general performance claim does not establish them.
Request a casino-engine discussion with your current account system, wallet, aggregation and reporting setup. Name the component you need to replace and the parts that must continue working.