Build a purchase flow around your players.

Connect supported payment providers, player identity, and backend purchase-handling logic in your game.
01 Authentication
02 Cloud Script
03 Analytics
Contextual draft · Release status, supported versions, and limits await owner review. identify the player, use a supported purchase flow, verify the provider result, fulfill once through approved game logic, and expose transaction status.

Workflow to evaluate

Identify the player
Step 1: pending
Use a supported purchase flow
Step 2: pending
Verify the provider result
Step 3: pending
Fulfill once through approved game logic
Step 4: pending
And expose transaction status.
Step 5: pending

Your game team’s responsibilities

Design client UX, game rules, permissions, and error recovery. Simulation, game-server hosting, moderation, and fulfillment are separate responsibilities unless explicitly included in a confirmed integration.

Service building blocks

Explore what each service contributes to this workflow, then review its integration requirements.
SERVICE 1

Authentication

Give every player a way into your game. Explore Authentication
SERVICE 2

Cloud Script

Run game logic behind your player experience. Explore Cloud Script
SERVICE 3

Analytics

Understand what happens across the player journey. Explore Analytics
SERVICE 4

Payments

Connect purchases to your player experience. Explore Payments

Before implementation

Validate access and supported versions for every required service. Test the workflow with failure, reconnection, and authorization cases before using it in your game.
YOUR NEXT CHAPTER STARTS HERE

Build the backend for your next game.

Explore the services and plan your first player experience.