Skip to main content
Question

Using external content links APIs for web purchase links in Android

  • February 23, 2026
  • 1 reply
  • 155 views
A
Forum|alt.badge.img+4

I’m trying to set up web purchase links in my application, which uses RevenueCat for billing. I want to make sure I abide by the App and Play Store requirements.

In the External Content Links documentation that RevenueCat links to in its App-to-web explainer, Google states that Developers participating in the program must:

Integrate with the external content links APIs, which surface an information screen, enable parental controls, and facilitate transaction reporting once required.

 

So it seems like the link that opens the web purchase flow must use a special API on Android. Does RevenueCat offer a ReactNative library to handle that requirement? For example, does the Web Purchase Button handle that for me?

Thanks

1 reply

H
RevenueCat Staff
Forum|alt.badge.img+8
  • Haley Pace
  • RevenueCat Staff
  • July 16, 2026

Hi ​@anders-leif apologies for the delay in response here, we were auditing our system and found that this was never resolved.

1) Does RevenueCat offer a React Native library for External Content Links?

Not today. react-native-purchases does not wrap Google’s External Content Links APIs (info screen, parental controls, transaction reporting). If you’re enrolled in that Play program, you’ll need to integrate those Play Billing Library APIs in your Android code yourself.

2) Does the Web Purchase Button handle that?

No. On Play Store (React Native 9.6.1+), the Web Purchase Button opens your web checkout in a browser / Custom Tab. It does not call Google’s External Content Links APIs. RevenueCat Web Purchase Buttons and Web Purchase Links handle the web checkout itself. Google’s External Content Links program is about how you open that link from a Play-distributed app.

  • WPL only outside the app (website, email, ads, etc.): you don’t need the External Content Links APIs.
  • Opening web checkout from inside your Play app (e.g. Web Purchase Button, or launching a WPL from in-app UI) for US users: Google requires you to enroll in the External Content Links program and integrate their APIs (info screen, parental controls, and transaction reporting once required) before linking users out. I recommend going through Google’s enrollment guide that you linked above as well as their in-app integration docs. Google notes a January 28, 2026 deadline for apps already using these kinds of links.

One option is a Custom checkout button with a deep-link open method so your app can run those APIs before opening the Web Purchase Link.

Let me know if you have any questions on this!

Terms & ConditionsAccessibility statement