Project planning / Arcade pinball
A planning brief for a exclusive project · platform planning · sandbox validation.
Neon bumpers, responsive manual flippers and a fast-moving ball bring an arcade rhythm to an original casino concept.
Pulse Pinball combines manual flipper timing with a arcade pinball concept. For platform planning, the wallet integration work should be evaluated during sandbox validation before the scope of the exclusive project is accepted.
Run the integration tests in the isolated test environment. Public demo credits and test-wallet credits are separate systems.
Playable conceptArcade pinball · 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
Define the exact scope of exclusivity: game, artwork, brand, territory or channel. Exclusivity has value only when its boundaries are explicit.
Confirm ownership of third-party assets and define what may be reused.
Channel requirements
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
Decide how player input influences the commercial outcome. Visual responsiveness and a validated outcome model are separate acceptance questions.
| Check | Evidence to collect |
|---|---|
| 01 / Compare balances before and after each transaction | Record the Pulse Pinball 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 identifier | Record the Pulse Pinball 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 amount | Record the Pulse Pinball 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 debit | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 05 / Test both flippers independently | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 06 / Check touch targets during ball movement | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 07 / Review bumper and end-of-round feedback | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
For this Pulse Pinball 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 Pulse Pinball evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0266. Requirements must be confirmed against your actual platform and agreement.