Can Google Play developers in the US link users to buy outside the app now?

Can Google Play developers in the US link users to buy outside the app now

Yes, for some US users and some app types, but only through Google Play programs and program rules. Outside those programs, an in-app link to outside payment is still restricted.

Google’s current US policy page says developers serving US users can communicate about prices or availability outside the Play Store, provide a link to download the app outside Play, and link to transactions. That is the part people often miss, because the older blanket prohibition is no longer the full story. The policy is narrower now, not gone.

The inconvenient part is that “allowed” does not mean “anything goes.” Google’s payments policy still says apps may not lead users to a payment method other than Google Play billing unless a specific section applies. It also says this includes directly linking to a webpage that could lead to an alternate payment method, or using language that encourages purchase outside the app. That means the path matters, not just the final checkout page.

For US users, Google now supports alternative billing programs and external offers programs for eligible developers. In the alternative billing setup, users can be shown another billing option in addition to Google Play billing. In the external offers setup, Google says developers can link users out to external offers, but they must enroll in the program and follow its terms.

The biggest mistake is treating “US” as a universal yes. Google’s own pages tie the permission to eligible developers and the applicable program. If your app is not enrolled, or your use case is not covered by the program terms, the old rule still applies inside the app: do not lead users to an outside payment method.

The other part people get wrong is the difference between outside the app and inside the app. Google says developers can communicate freely with customers outside the app about offers and lower-cost options, but inside the app the linking and wording are controlled by policy and program enrollment. A website, email, or support page is not the same as an in-app purchase flow.

If you want to do this correctly, start by checking which program applies to your app, then read the matching integration guidance. Google’s documentation for external payments and alternative billing explains how the app should present the choice, how the user is routed, and what the app must report back after purchase. The flow is part policy, part implementation.

A practical example helps. If a user taps a button in your app that says “Buy on our website,” that may be allowed only when your app is enrolled in the relevant program and the flow follows Google’s requirements. If the same button appears in an app that is not enrolled, it can become a policy violation because it is an in-app route to another payment method.

Another thing that trips people up is updates. Google’s US policy language now points to alternative billing programs for eligible developers serving US users, and the payments policy also points to section-based exceptions. That means you should not rely on a blog post, a forum answer, or an old policy screenshot. The live support pages are the source of truth, and the rules are tied to enrollment status.

For app builders who only need the short answer, here it is: yes, Google Play developers in the US can now link users to buy outside the app in some cases, but only if the app and flow fit Google’s current program rules. If you want to keep the logic simple, treat “outside the app” as permitted by exception, not as the default.

If you are also testing distribution, DevConnect keeps that part separate from payments. The platform is for exchanging real test coverage, not for buying outcomes. It is free to use at https://devconnectplatform.com, and that matters because policy-safe growth is usually cheaper than policy cleanup.

The safest workflow is simple: identify the exact Google Play program, verify that your app is eligible, implement the approved link or billing flow, and test the user journey from tap to receipt. If any step falls outside the program terms, assume the link is not allowed until you confirm otherwise in Google’s current documentation.

FAQ

Is the old rule still true that Google Play apps cannot link out No. That is no longer the whole rule for US users. Google now publishes US-specific program paths for alternative billing and external offers, but only for eligible developers and only under the program terms.

Can I put a “buy on our website” button directly in the app Only if your app is enrolled in the relevant Google Play program and your implementation follows the documented requirements. Without that coverage, the payments policy still treats in-app steering to another payment method as restricted.

Can I tell users about cheaper pricing on my website Yes, Google’s US policy page says developers can communicate with users about pricing outside the Google Play Store. The key boundary is where that communication happens and whether the app flow itself leads users to an outside payment method in a way the policy does not allow.

Does this apply to every app on Google Play in the US No. Google ties these options to eligible developers, specific programs, and additional terms. The live policy pages do not say every app gets the same treatment.

Where should I check before shipping Start with Google Play’s current US policy page, the payments policy, and the relevant alternative billing or external offers setup page. Those three pages tell you whether the use case is covered and how the flow has to work.