Stripe vs Google Play Billing: which to use for in-app payments

For an Android app distributed on Google Play, “Stripe or Google Play Billing?” is not only a pricing question. Google’s Payments policy decides which one you are allowed to use, and in 2026 that policy depends heavily on where your users are. This guide explains the rules as written in Google’s official policy and help pages, the fees on each side, and how to decide.

This is a summary of public policy and pricing documents, not legal advice. Policies in this area changed several times in 2025 and 2026; check the linked pages before you build.

The rule in one paragraph

Google Play’s Payments policy says apps that charge for digital content or features (in-app items, subscriptions, app functionality, cloud software and services) must use Google Play’s billing system, unless a regional program allows an alternative. Payments that are primarily for physical goods or services (food delivery, event tickets, a physical product), credit card or utility bill payments, peer-to-peer payments, online auctions and tax-exempt donations are exempt and can use any processor, including Stripe.

So the first question is always: what are you selling?

Step 1: is it a digital good?

If everything you sell is physical or exempt, use Stripe (or any processor) and stop here.

Step 2: where are your users?

For digital goods, Google now runs several regional programs that let developers offer an alternative billing system or link to their own website.

United States

Google offers US developers an alternative billing program and an external content links program. Both are opt-in. According to Google’s help pages, enrolled developers must report transactions and pay the relevant service fee from October 1, 2026, and alternative billing transactions must be reported within 24 hours using Google’s APIs.

US service fees are split by whether the user’s install is “new” (first install or update from Google Play on or after June 30, 2026) or “existing”:

On top of this, Google charges a separate 5% billing fee only when the transaction runs through Google Play Billing. Alternative billing and external web links do not carry the billing fee.

EEA and UK

From June 30, 2026, Google’s billing choice program is open to developers offering digital content to users in the EEA and UK. Developers can offer an alternative billing system, link to their website, or present their own choice screen, subject to Google’s UX guidelines. The service fee is 10% on the first $1M of annual earnings and 10% on auto-renewing subscriptions, with the 5% billing fee applying only to Google Play Billing transactions.

India and South Korea

Google’s alternative billing help page states that developers can offer an alternative billing system in India and South Korea, with the service fee reduced by 4 percentage points (for example, from 15% to 11%).

Everywhere else

Where no program applies, the standard model remains: 15% on the first $1M of annual earnings for developers enrolled in the 15% tier, 30% above that, and 15% on auto-renewing subscriptions. In-app digital purchases must go through Google Play Billing, and the policy restricts steering users to other payment methods.

What Stripe costs

Stripe’s fees depend on the country of your Stripe account. As an example, Stripe’s Norway pricing page lists:

• 2.4% + NOK 2.00 for EEA cards
• 3.25% + NOK 2.00 for UK and international cards
• +2% when currency conversion is required
• Stripe Billing (subscriptions): 0.7% of billing volume on pay-as-you-go
• Stripe Tax: 0.5% per transaction on the no-code integration
• Managed Payments (Stripe acts as merchant of record and handles sales tax, VAT and GST in more than 80 countries, fraud and disputes): 3.5% per transaction on top of payment fees

Open Stripe’s pricing page for your own country to see your rates.

Remember the full cost of selling with Stripe: if you are the merchant of record, you are responsible for collecting and remitting VAT or sales tax, handling refunds and disputes, and customer support. With Google Play Billing, Google runs the checkout and payment flow inside the Play Store. Stripe Managed Payments takes over tax, fraud and disputes for the sales it processes, at the 3.5% premium.

Worked example: a $5/month subscription in the US

Assume a US user on a new install, a developer under $1M in annual earnings, and an auto-renewing subscription.

• Google Play Billing: 10% service fee + 5% billing fee = 15%, so about $0.75 per payment. Google runs the checkout and payment processing.
• US alternative billing with Stripe: 10% service fee to Google = $0.50, plus Stripe’s processing fees and, if you use them, Billing and Tax fees. On a $5 charge, a fixed per-transaction fee is a large share of the price.

For low-priced subscriptions, the difference is small and the extra integration (reporting to Google within 24 hours, offering customer support and dispute handling yourself) may cost more than it saves. The math improves for higher price points, annual plans, or customers who already pay on your website.

Decision rules

• Selling physical goods or services? Use Stripe. Google Play Billing is not required.
• Selling digital goods and most users are outside the US, EEA and UK? Use Google Play Billing. It is required, and it is the simplest path.
• Selling a low-priced digital subscription to US, EEA or UK users? Start with Google Play Billing. The fee gap is a few percentage points, and you avoid tax, dispute and reporting work.
• Selling higher-priced digital products, or you already run a web checkout? Consider the regional alternative billing or external links programs with Stripe. Budget time for enrollment, Google’s reporting APIs and your own support processes.
• Selling on the web only (no Play app)? Google’s policy does not apply. Use Stripe or another processor; consider Managed Payments if you do not want to handle global sales tax.

FAQ

Can I sell digital goods through my website instead? Selling on your own website is outside Google Play’s billing system. The restriction is on steering users from inside the Play app; in regions with an external links program, you can link out after enrolling and following its requirements.

Does any of this apply to ads? No. Showing ads is not an in-app purchase, so the Payments policy does not apply to ad revenue.

What if I sell the same subscription on web and Android? Many developers do. Keep one account system so that a subscription bought on either side unlocks the app, and make sure in-app prices match the Play billing interface, as the policy requires.

Implementation checklist

• Classify every product you sell as digital, physical or exempt
• List your users’ main regions and check which Google program applies there
• If using Play Billing: integrate the Play Billing Library and verify purchases on your server
• If using an alternative: enroll in Play Console, integrate the alternative billing or external links APIs, and set up reporting
• Decide who is merchant of record and how VAT/sales tax will be handled
• Write refund and subscription-cancellation instructions users can find inside the app
• Re-check the policy pages before launch; Google notes it can change or end the US program if the court order changes

Sources

1. Google Play Payments policy
2. Google Play service fees
3. Offering an alternative billing system for users in the United States
4. Enrolling in the external content links program for users in the US
5. An update regarding Google Play’s policies for developers serving users in the US
6. Understanding alternative billing programs on Google Play
7. Android Developers Blog: Expanded billing choice and lower fees on Google Play (June 2026)
8. Stripe pricing
9. Stripe docs: Managed Payments

Last verified: October 9, 2026. Prices, limits and policies come from the official pages listed under Sources, not from hands-on testing. Providers change them often, so confirm on the provider's own page before you buy. Spotted something out of date? Tell us.