Project planning / Prize wheel

Jade Fortune
Licence operations

A planning brief for a annual licence · platform planning · commercial scoping.

Your project scenario

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 licence operations work should be evaluated during commercial scoping before the scope of the annual licence is accepted.

Turn the evaluation into deliverables, ownership terms, acceptance evidence and a responsibility matrix.

Jade Fortune concept artworkPlayable concept

Explore Jade Fortune ↗

Prize wheel · Virtual-credit demo

Integration priority

Licence operations

Translate the commercial agreement into a specific catalogue, approved hostnames, expiry rules and support responsibilities.

Check activation, expiration, suspension and key rotation using test accounts before handing access to the customer.

Commercial scope

Annual licence

Define a recurring annual access period and what happens at renewal or expiry. Separate the software right from hosting and operational services.

Set the agreed end date and test access after it passes.

Channel requirements

Platform planning

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

Wheel sectors and risk mode

Agree sector weights and mode-specific probabilities before describing an RTP or maximum win. The twelve visible sectors alone do not establish payout maths.

Acceptance checklist

CheckEvidence to collect
01 / Confirm the permitted game identifiersRecord the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
02 / Compare approved hostnames with the agreementRecord the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
03 / Revoke an unused integration credentialRecord the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
04 / Test account separation and access after suspensionRecord the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
05 / Review all twelve visible sectorsRecord the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
06 / Switch classic and bold modesRecord the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
07 / Check wheel-stop and result alignmentRecord the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.

Agreement review

  • Annual term
  • Renewal decision
  • End-of-term access

For this Jade Fortune proposal, connect each agreed right to an identifiable deliverable. Keep licence operations changes explicit in the statement of work.

Scope boundary

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.

Plan the test workload

Adjust the environments and test cases for this Jade Fortune evaluation. Start with the checklist above, then add partner-specific cases.

21 planned test executions.

Planning reference GQX-0484. Requirements must be confirmed against your actual platform and agreement.