Project planning / Premium cinematic slot

Solar Vault
Wallet integration

A planning brief for a custom build · desktop web · prototype review.

Your project scenario

A cinematic five-reel slot with winning cascades, reactor wilds, vault free spins and original action sounds. Customise your edition in Game Studio.

Solar Vault combines cascades and reactor wilds with a premium cinematic slot concept. For desktop web, the wallet integration work should be evaluated during prototype review before the scope of the custom build is accepted.

Play the concept with representative users from your team and record the difference between preference changes and defects.

Solar Vault concept artworkPlayable concept

Explore Solar Vault ↗

Premium cinematic slot · 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

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

Desktop web

Cover mouse and keyboard input, different window sizes and browser zoom. Check that the main action remains clear on both small laptops and larger displays.

Game-specific decision

Cascades and reactor wilds

Three winning cascades charge the reactor; initial vault keys trigger free spins. Customer presentation settings do not change the mathematical model.

Acceptance checklist

CheckEvidence to collect
01 / Compare balances before and after each transactionRecord the Solar Vault build, desktop web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
02 / Retry a transaction with the same identifierRecord the Solar Vault build, desktop web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
03 / Reject a reused identifier carrying a different amountRecord the Solar Vault build, desktop web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
04 / Confirm that a refund cannot exceed or repeat its original debitRecord the Solar Vault build, desktop web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
05 / Check autoplay stop and loss limitsRecord the Solar Vault build, desktop web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
06 / Verify event-synchronised action soundsRecord the Solar Vault build, desktop web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
07 / Verify customer edition isolationRecord the Solar Vault build, desktop web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.

Agreement review

  • Deliverables
  • Review milestones
  • Acceptance criteria

For this Solar Vault 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 Solar Vault evaluation. Start with the checklist above, then add partner-specific cases.

21 planned test executions.

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