Events, rewards and trust
How accepted activity can contribute without granting client authority.
Acceptance is not a payout
The API persists a valid event before the reward worker handles it. For signed-in players the accepted event snapshots published rules, eligibility and bonuses, and schedules durable processing. Guests receive event acceptance without account rewards. The parent polls completed/failed run status and sends server receipts back into the game.
Rules and limits
Staff-authored rules can use conditions, fixed rewards, thresholds, counters, milestones, repeat windows, cooldowns, daily limits and budgets. They may require verified activity or manual review. The browser may not choose currency amounts, entitlements or verification status. Existing missions and achievements consume configured server activity; no universal XP-per-minute or coin-per-score rule is part of the SDK.
Trust levels
Browser events and scores are unverified. The platform also implements a signed server endpoint, but only an authoritative game server can provide meaningful stronger evidence. Signing browser-reported numbers without validating them does not establish trustworthy gameplay. High-value rewards must follow server policy.
UI behavior
Keep 'run accepted' separate from 'reward issued'. A pending receipt can later be issued, capped, no_reward or held_for_review; the full receipt may carry additional fields. Do not optimistically increment platform balances. On a failure, retain your game result UI and let the platform communicate the final server decision.