Skip to main content
Question

Stripe products not appearing in getOfferings() in RevenueCat Web SDK

  • May 31, 2026
  • 3 replies
  • 57 views
H
Forum|alt.badge.img

I’m building a web-based TV app where users scan a QR code on the TV to complete payment on their phone. I’m using purchases-js and calling getOfferings() to display products for the current offering.

However, the packages array is coming back empty, even though I’ve created a Stripe product for each package under each offering.

I noticed that when I add a Web Billing product, it shows up correctly in the offerings, but the Stripe products do not appear.

Is this expected behavior for the Web SDK, or am I missing a required configuration step for Stripe products to be available through getOfferings() in a web application?

3 replies

H
Forum|alt.badge.img
  • hattapoglu
  • Author
  • New Member
  • June 3, 2026

Any help on this would be greatly appreciated. Anyone?

alejandra-wetsch
RevenueCat Staff
Forum|alt.badge.img+6

Hey ​@hattapoglu, 

Thank you for reaching out! 

That’s expected behavior. To add more context, the RevenueCat SDKs scope the Offerings and products that can be fetched based on the API Key used to configure the SDK. When you configure the Web SDK with a Web Billing API Key, you can only fetch Web Billing products. 

Given that you want to fetch Stripe Products via the Web SDK, you will need to use the Public API Key from your Stripe Billing configuration to configure the SDK. This means that instead of using an rcb_***** API Key, you will need a strp_***** one.

Hope this helps!

Alejandra, Developer Support Engineer @ RevenueCat
H
Forum|alt.badge.img
  • hattapoglu
  • Author
  • New Member
  • June 3, 2026

Hi ​@alejandra-wetsch, 

Thanks for the answer!

However, when I configure the SDK with the strp_***** key I get this error at runtime:

  ▎ RevenueCat: Oe: Invalid API key. Use your Web Billing API key.

The purchases-js SDK itself is rejecting the Stripe key and requiring an rcb_***** key. So either the SDK needs to be updated to accept strp_***** keys, or there's a different approach needed here. Could you clarify how to actually use Stripe products with purchases-js given this constraint?

Terms & ConditionsAccessibility statement