Console payouts across the major console storefronts

Shipping on console means dealing with several first-party console storefronts. Each runs its own developer payment portal, its own reporting cadence, its own minimum thresholds and its own payout currency, and the precise terms are governed by the developer agreement you sign with each console platform holder.

This guide covers the general shape of how console payouts work and, importantly, flags where exact figures vary by platform and agreement. Always confirm the specifics in each platform's own developer portal rather than relying on a general overview.

Separate portals, separate sets of rules

Unlike a single PC storefront, console revenue reaches you through several separate first-party systems. Each console platform holder operates its own developer portal where sales are reported and payments are configured, and the rules in one do not carry over to another.

That means your studio is effectively reconciling several independent payment relationships at once, each with its own reporting period, its own payout timing and potentially its own currency. Treat them as distinct streams rather than one console category.

Revenue share

The headline revenue share on first-party console storefronts is commonly around 30%, broadly in line with the standard PC and mobile rate. Some console platform holders have publicly indicated that they do not require a minimum sales level before a developer receives revenue.

Beyond that general 30% figure, the exact commission, any volume or programme-based reductions, and any conditions attached are set in your individual developer agreement. Do not assume a rate or a tier applies without checking your own contract and portal.

Cadence, thresholds and currency

As a general pattern, console payouts are periodic, typically monthly, and are made after a reporting lag rather than in real time. Each platform may also apply a minimum payment threshold below which funds roll forward, and may pay in a specific currency tied to your territory or agreement.

The precise schedule, threshold and payout currency are not uniform across the console storefronts, and reliable public figures are limited. Some platforms also report per territory, which adds further moving parts. Treat any specific number you see elsewhere as something to verify in the relevant developer portal before you build it into a forecast.

What to confirm in each developer portal

Before relying on console revenue in your cashflow, confirm four things per platform directly: the exact revenue-share rate in your agreement, the payment cadence and the reporting lag, any minimum payout threshold, and the currency you will be paid in. These are the variables that determine when cash actually arrives and how much of it is yours.

Because these terms vary by platform and by the specific agreement your studio signs, they should be read from the source rather than inferred. A short check in each portal at onboarding saves a lot of reconciliation guesswork later.

How Altery fits

Whatever currency each console platform pays you in, Altery's multi-currency business accounts can hold USD, EUR and GBP balances together, so a USD console payout and a euro one can sit side by side without forcing an immediate conversion. You convert on your own timeline instead.

Real-time balances and categorised spend help you keep separate console streams distinct and reconcile each against its portal, while multi-entity management suits studios running a company per region or per IP, and global mass payouts help you pay contributors once the money lands. Altery is not a bank and provides general information, not advice; always confirm payout terms in each platform's developer portal.

Frequently asked questions