Prepare scope
Confirm initial scope, platform status and owners.
Input: Platform stage, target market, initial game scope and owners.
Complete when: First scope, issue owner and next materials are clear.
Follow five steps for Slots API preparation, sandbox testing, catalog and wallet integration, reconciliation and launch coordination.
Follow five steps for Slots API preparation, sandbox testing, catalog and wallet integration, reconciliation and launch coordination.
Confirm initial scope, platform status and owners.
Input: Platform stage, target market, initial game scope and owners.
Complete when: First scope, issue owner and next materials are clear.
Use the test environment and confirm the wallet approach.
Input: Agreed scope, technical contact and wallet approach.
Complete when: Test scope and wallet approach are clear.
Validate catalog, game launch and applicable wallet flows.
Input: Test environment, game list, public API reference and wallet approach.
Complete when: Agreed paths reproduce in the test environment.
Cover duplicates, failures, record differences and retest.
Input: Working paths, exception cases and request or record identifiers.
Complete when: Every exception has a reproducible outcome, owner and retest conclusion.
Confirm configuration, environment, support and ownership before production.
Input: Test outcomes, open items, launch scope and contacts.
Complete when: Launch scope and continuing collaboration are confirmed.
Project-specific access and materials are provided through the controlled onboarding process. Public pages do not provide live credentials or production configuration.
Contact technical teamDiscuss the cooperation scope with our business team.