A reliable integration is easiest to manage as a sequence of scope and evidence gates. Each stage should produce a reviewable output before the next stage adds more configuration or operational risk.
Last reviewed: 2026-08-09
Confirm the first content set, target language and currency, intended region, wallet model, platform return path, and expected launch sequence. Organize providers and titles as a delivery list.
Evidence: a written scope, named owners, open questions, and later-phase items.
Document player identity, login and session rules, the authoritative balance, ledger writes, transaction identifiers, callback handling, logs, and support tools. The goal is to locate every system boundary that the API will cross.
Evidence: a responsibility map and the proposed mapping between platform records and API request identities.
Use the V5.0.0 public surface for orientation, then map the specification, environment information, credentials, allowlist requirements, and callback responsibilities into the project. Keep test and production values separate.
Evidence: versioned technical inputs with an owner and review date; credentials stored in the designated secret-management system.
Start with a bounded content lookup, one player session, the chosen wallet path, and a corresponding record lookup. Preserve the request identity and timestamps needed to trace that path across both systems.
Evidence: a reproducible test case that links the session, wallet event, and resulting records using redacted player data.
Exercise duplicate requests, client and server timeouts, delayed callbacks, rejected operations, unknown transaction states, session expiry, and record differences. Define when to retry, when to query, and when to escalate.
Evidence: deterministic expected outcomes and recovery steps for each material failure class.
Recheck content scope, environment separation, monitoring, alerting, access control, logs, reconciliation ownership, incident contacts, recovery, and regional launch requirements.
Evidence: a signed launch checklist and a rollback or traffic-stop decision path.
| Role | Primary responsibility |
|---|---|
| Product or platform owner | Confirm the desired content, market context, priority, and acceptance outcome. |
| Engineering owner | Implement identity, session, wallet, retry, and record behavior. |
| Operations owner | Prepare monitoring, reconciliation, incident evidence, and manual handling. |
| AG technical contact | Map the protocol, environment, account configuration, and integration findings. |
Use the integration checklist to turn these stages into an implementation and acceptance plan.