Project planning / Prize wheel
A planning brief for a custom build · multi-brand operation · handover planning.
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 multi-brand operation, the wallet integration work should be evaluated during handover planning before the scope of the custom build is accepted.
Define documentation, account ownership, secret rotation, support contacts and the acceptance record required for handover.
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
Agree a commissioned production against a specific brief, review milestones and acceptance criteria. Decide which work begins only after the concept is approved.
Map requested changes to the build and record acceptance evidence.
Channel requirements
Separate each brand’s approved hostnames, catalogue access and operational contacts. Test that one customer or brand cannot obtain another customer’s credentials or sessions.
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, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 02 / Retry a transaction with the same identifier | Record the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Reject a reused identifier carrying a different amount | Record the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 04 / Confirm that a refund cannot exceed or repeat its original debit | Record the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 05 / Review all twelve visible sectors | Record the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 06 / Switch classic and bold modes | Record the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 07 / Check wheel-stop and result alignment | Record the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
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-4274. Requirements must be confirmed against your actual platform and agreement.