Project planning / Arcade pinball
A planning brief for a annual licence · multi-brand operation · handover planning.
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 multi-brand operation, the game launch integration work should be evaluated during handover planning before the scope of the annual licence is accepted.
Define documentation, account ownership, secret rotation, support contacts and the acceptance record required for handover.
Playable conceptArcade pinball · Virtual-credit demo
Integration priority
Define who requests the launch, how the player reaches the game and which exact hostnames may embed it. API secrets stay on the operator server.
Test valid and expired launches, suspended licences, unauthorised games and unapproved subdomains.
Commercial scope
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
Separate each brand’s approved hostnames, catalogue access and operational contacts. Test that one customer or brand cannot obtain another customer’s credentials or sessions.
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 / Request a launch for an allowed game | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 02 / Attempt a launch after licence expiry | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Check a hostname outside the agreement | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 04 / Confirm credential revocation blocks new requests | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 05 / Test both flippers independently | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 06 / Check touch targets during ball movement | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 07 / Review bumper and end-of-round feedback | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
For this Pulse Pinball proposal, connect each agreed right to an identifiable deliverable. Keep game launch 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-4281. Requirements must be confirmed against your actual platform and agreement.