Epic Games Store age verification: your build checklist

Epic Games Store age verification for R18+ rated titles in Australia takes effect tomorrow, and it is worth treating as a production event, not just a policy notice, because it is the first time a major PC storefront has built age-gating directly into its purchase flow for a specific regional rating tier. Players in Australia will need to verify they are over 18 before accessing any R18+ game on the store starting September 9. Existing purchases and titles rated below R18+ are unaffected, so this is a forward-looking gate on new access rather than a retroactive lockout.

Epic says the change aligns the store with Australia's online safety regulations, and the company has been explicit that the verification data collected exists only to confirm age. That framing matters for how a studio should think about this: it is a compliance requirement layered onto an existing purchase and access flow, not a new monetisation or engagement feature, and treating it as pure overhead is the wrong instinct if you have a title in or near the R18+ tier and want the rollout to be invisible to players who clear it easily.

How the verification actually works

Epic's Kids Web Services system, which already handles a range of age-related compliance across the company's products, routes Australian R18+ access through four verification paths, and a player can choose which one to use:

• A selfie-based age estimation run through Yoti, with the image encrypted in transit and deleted once the analysis completes.
• A five-cent credit card transaction processed through Stripe, used only to validate that the card belongs to an adult; card details are not shared with Epic's KWS system.
• Government ID verification through Veriff, with the document encrypted during processing and the photo deleted once verification finishes.
• Bank-based verification through ConnectID, which Epic says will launch later in September and will not share banking information with Epic.

The range of methods is itself a design choice worth noting for anyone building a similar gate: a single verification path inevitably excludes players who cannot or will not use it, whether for privacy reasons, lack of a suitable ID, or lack of a card. Four paths, three live at launch and a fourth arriving within weeks, spreads that friction across options rather than forcing every player through the same one.

What this adds to a submission checklist

If your title carries or is close to an R18+ classification and ships on Epic Games Store, or you are watching this as a precedent for other storefronts and regions, here is what changes in a production and submission plan:

• Confirm your title's actual classification status in Australia before assuming this applies, since the gate is scoped specifically to R18+ and does not touch lower ratings.
• Build the expectation of a verification interruption into your first-session flow modelling for Australian players; a store-level identity check ahead of purchase is a new drop-off point that did not exist in your funnel before, even if Epic, not your game, owns the interaction.
• Do not attempt to route around the gate with your own age-collection mechanism inside the game client. Epic's system operates at the storefront and account level, and a parallel in-game check would be redundant at best and confusing at worst.
• Flag this to your regional marketing team specifically for Australian creative and store-page copy, since a purchase flow with an added verification step changes what a realistic conversion benchmark looks like for that market, at least through the initial rollout period.
• Watch your Australian cohort's day-one and day-seven activation numbers separately from other regions for the first few weeks after launch, since any friction the new gate introduces will show up there first, not in aggregate global numbers.

What the multi-method design tells you about building your own

Even studios with no title anywhere near an R18+ rating can learn something from how Epic structured this specifically because it is the first fully worked example of a major storefront solving age assurance for real-money purchase access rather than just a self-declared birthdate field. The four-path design, biometric estimation, payment-instrument validation, government ID, and bank verification, reflects a fairly deliberate assumption that no single method clears every legitimate adult player without excessive friction or an unacceptable privacy trade-off for at least some share of them. A studio designing its own age-gated feature, whether for a loot box disclosure requirement in one market or a real-money tournament mode in another, should expect to need a similar spread of options rather than assuming one verification vendor is sufficient for a global player base. The decision to stagger launch, three methods live immediately and a fourth, bank-based verification, arriving weeks later, is also instructive: Epic evidently judged it better to ship the requirement on time with a narrower set of paths than to delay the whole rollout waiting for every method to be ready.

Why this is a precedent worth tracking beyond Australia

Epic frames this specifically as compliance with Australian regulation, and there is no indication in the announcement of plans to extend it elsewhere. That said, age verification requirements for adult-rated digital content have been moving through legislative and regulatory processes in several markets over the past two years, and a major storefront building a working, multi-method verification system for one region creates the technical and legal groundwork to extend it faster if another jurisdiction adopts similar rules. A studio with R18+ or equivalent content in its catalogue should not wait for a second region to mandate this before understanding how Epic's system works end to end, because the operational lift of adapting to a second market's rules will be much smaller than building the capability from nothing.

The immediate task for any affected studio is narrow: confirm classification status, model the new friction point into Australian funnel expectations, and resist the urge to duplicate the check inside your own build. The larger task, watching whether other storefronts or regions follow, is one worth putting on a standing production-planning agenda rather than revisiting only when the next mandate lands.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• Google Play's Developer Verification Push: A Checklist
• Epic Games Store on Android: One Publisher's Build Notes