Project planning / Prize wheel

Jade Fortune
Licence operations

A planning brief for a custom build · platform planning · discovery.

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 discovery before the scope of the custom build is accepted.

Produce a written requirements list and identify missing information before quoting implementation work.

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

Custom build

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

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 discovery.
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 discovery.
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 discovery.
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 discovery.
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 discovery.
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 discovery.
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 discovery.

Agreement review

  • Deliverables
  • Review milestones
  • Acceptance criteria

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-0149. Requirements must be confirmed against your actual platform and agreement.