Project planning / Prize wheel
A planning brief for a one-time licence · platform planning · sandbox validation.
A gold-and-jade prize wheel combines twelve sectors with classic and bold play modes in a polished visual setting.
Jade Fortune combines wheel sectors and risk mode with a prize wheel concept. For platform planning, the wallet integration work should be evaluated during sandbox validation before the scope of the one-time licence is accepted.
Run the integration tests in the isolated test environment. Public demo credits and test-wallet credits are separate systems.
Playable conceptPrize wheel · Virtual-credit demo
Integration priority
Map player identifiers, currency units, transaction identifiers and response codes before connecting a casino wallet.
Run balance, debit, credit, refund, insufficient-funds and retry cases. Keep every test account separate from production.
Commercial scope
Define a right to use the agreed build, with the brands, domains and delivery scope written down. A one-time payment does not automatically transfer ownership.
Specify whether maintenance is included or separately renewed.
Channel requirements
Start with the operator’s actual browser, wallet and player journey requirements. This brief is a planning scenario, not a claim of compatibility with an unnamed casino.
Game-specific decision
Agree sector weights and mode-specific probabilities before describing an RTP or maximum win. The twelve visible sectors alone do not establish payout maths.
| Check | Evidence to collect |
|---|---|
| 01 / Compare balances before and after each transaction | Record the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 02 / Retry a transaction with the same identifier | Record the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 03 / Reject a reused identifier carrying a different amount | Record the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 04 / Confirm that a refund cannot exceed or repeat its original debit | Record the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 05 / Review all twelve visible sectors | Record the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 06 / Switch classic and bold modes | Record the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 07 / Check wheel-stop and result alignment | Record the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
For this Jade Fortune proposal, connect each agreed right to an identifiable deliverable. Keep wallet integration changes explicit in the statement of work.
The current game is a playable concept. Test wallet behaviour is available separately in the developer sandbox. Real-money wagering is disabled in that sandbox.
A live build requires server-authoritative gameplay, validated payout maths, partner-specific wallet integration and applicable testing. This brief is a planning aid, not evidence of certification or an existing platform connector.
Adjust the environments and test cases for this Jade Fortune evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0254. Requirements must be confirmed against your actual platform and agreement.