Project planning / Prize wheel

Jade Fortune
Wallet integration

A planning brief for a monthly licence · platform planning · sandbox validation.

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 wallet integration work should be evaluated during sandbox validation before the scope of the monthly licence is accepted.

Run the integration tests in the isolated test environment. Public demo credits and test-wallet credits are separate systems.

Jade Fortune concept artworkPlayable concept

Explore Jade Fortune ↗

Prize wheel · Virtual-credit demo

Integration priority

Wallet integration

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

Monthly licence

Define a monthly access agreement with clear game coverage and an agreed notice process. Avoid assuming unlimited brands or domains.

Confirm the current period and the action required when access ends.

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 / Compare balances before and after each transactionRecord 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 identifierRecord 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 amountRecord 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 debitRecord 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 sectorsRecord 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 modesRecord 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 alignmentRecord the Jade Fortune build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation.

Agreement review

  • Monthly term
  • Approved domains
  • Cancellation handling

For this Jade Fortune proposal, connect each agreed right to an identifiable deliverable. Keep wallet integration 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-0264. Requirements must be confirmed against your actual platform and agreement.