Commerce around the game, not around the payment page
Publishers may sell full games, downloadable content, battle passes, subscriptions, virtual currency, creator products, and event access. The gateway plan should preserve account context while separating payment data from gameplay systems.
A hosted flow can shorten delivery time. An API-led route can provide more control over entitlements, retries, refunds, and account-level risk decisions.
Entitlements need reliable payment states
A successful checkout is only one event. The commerce service must also handle pending authorisation, failed authentication, delayed confirmation, refund, chargeback, and subscription renewal. Signed webhooks and idempotent order handling prevent duplicate items and missing entitlements.
- Game and player account references carried into payment metadata
- Clear ownership of refund and entitlement reversal logic
- Reconciliation between storefront orders and gateway events
- Local-method planning for the markets actually served
Direct sales still require merchant review
Selling outside an app marketplace changes the merchant's responsibilities for tax, customer support, fraud, refunds, and payment compliance. The access review identifies which responsibilities stay with the publisher and which can be supported by the selected gateway route.