Two Payment Exits, Two Different Risk Profiles

The Epic remedy creates two different kinds of monetization choice for eligible US apps: an alternative billing system that can operate inside a Play-distributed app, and an external content link that can send a user to another destination. Both weaken Google Play’s old control over payment or steering, but they do not solve the same problem. The useful decision is to identify where the user goes, who controls the transaction, and which obligations follow that route.

Alternative billing changes the processor, not the whole distribution relationship

Google’s alternative-billing program is for eligible mobile or tablet apps and games offering digital content or services to users in the United States. It allows a developer to offer another billing system in lieu of or alongside Google Play Billing. The program is optional: a developer that does not want to offer a US alternative does not have to enroll.

That scope makes the first distinction clear. Alternative billing changes how a purchase is processed after the user has opened an app distributed through Play. It does not, by itself, move the app to another store, remove the app from Play, or give the developer a right to ignore the platform’s other user-protection requirements. Google’s current policy says that Play Billing may remain available alongside the alternative, and when both are used, users must be able to access Play Billing in a consistent and reliable manner.

The alternative therefore creates a choice at the payment interface while preserving much of the distribution context. A developer can decide that a particular US digital purchase should use another billing system, but the developer still has to make that route accountable. Google requires enrollment and implementation through its alternative-billing APIs. If the system handles credit or debit card data, the developer must comply with the Payment Card Industry Data Security Standard. The program also requires compliance with applicable law, including rules concerning payments and the protection of minors and children.

The customer relationship changes as well. A developer using the alternative system must provide customer support for users of that system and a process for disputing unauthorized transactions. Users must have ways to see their order history, manage subscriptions sold through the alternative, initiate customer-service and refund requests, and obtain help when something goes wrong. These requirements reflect a practical consequence of changing the payment route: the party that offers the alternative must be able to explain, support, and correct the transaction.

The route is not a fee-free escape from Google’s economic model. Google’s page says that, once required, authorized US transactions must be reported through the alternative-billing APIs within 24 hours and that applicable Play service fees still apply. The fee treatment depends on whether the transacting user is associated with a “new” or “existing” Play install and on the product category. Google defines those install categories using whether the user’s first install or first update of the app from Google Play occurred on or after June 30, 2026.

That definition illustrates why a percentage or headline fee alone would be an incomplete comparison. The same alternative payment method can meet users with different installation histories, and the applicable category can affect the economics.