Production public key missing for RevenueCat Billing (only sandbox rcb_sb_ available)

Question

There is no production public key for our RevenueCat Billing app — only a
sandbox key (rcb_sb_...). Checkout renders correctly but shows the yellow
SANDBOX banner, so no real payments are possible.

Diagnosis
Our two web apps point at different Stripe accounts:

[App Name] (RevenueCat Billing) type rc_billing acct_...(sandbox) created Aug 22
[App Name] (Stripe) type stripe acct_...(live) created Aug 27

The live Stripe account is fully verified (KYB complete, live mode accessible).
Because the acct_ IDs differ, the Billing config appears to be tied to a
separate Stripe sandbox account, which by design only exposes a sandbox key.
The Billing config was created 5 days before our live Stripe account was
connected.

Setup we want to preserve
- 42 RevenueCat Billing products
- each attached to its entitlement
- each in the "default" offering's packages alongside the App Store products

Questions
1. Can the existing Billing config's Stripe account be switched to our live
account in place? If so, what happens to the Stripe-side product/price
objects — our 42 were created in the sandbox account and do not exist in
the live account.
2. If instead we must create a new production Billing config, do the 42
products have to be re-attached to entitlements and re-added to the
"default" offering's packages from scratch?
3. Is the intended end state to keep BOTH configs permanently (sandbox +
production), using a different public key per environment?
4. Is there an API (v2) endpoint to bulk-create RevenueCat Billing products
and attach them to entitlements?

Note: I first reported this by email to RevenueCat Support over a month ago
and also tried the Help Center AI assistant and the official "Contact
Support" form in the dashboard — all three attempts failed to produce a
tracked ticket (the form itself returns "Failed to create support ticket").
Posting here because the private support channels appear to be broken.

hafizrahman · Answer

Hi there,Thank you for reaching out!To answer your questions:1. Can the existing Billing config's Stripe account be switched to our live account in place?Yes. In the RevenueCat dashboard, open your project, go toWeb, open theRevenueCat Billingconfig, and select theBillingtab. UnderPayment gateway, theStripe accountdropdown lists your connected Stripe accounts. Select your live account and save (note that only the project owner can do this).After the switch, this config is your production config, and the production key (rcb_) should appear next to the sandbox key. It keeps a sandbox key as well, because your live Stripe account has test mode access, so you can still make test purchases from the same config with Stripe test cards.As for the products, with RevenueCat Billing your 42 products, the entitlement links, and the offering packages all live in RevenueCat (as you can check inProduct Catalog > Productsin the dashboard). This means there are no Stripe-side objects to move or recreate when you switch to the live account.2. If instead we must create a new production Billing config, do the 42 products have to be re-attached to entitlements and re-added to the "default" offering's packages from scratch?Yes, you would have to recreate the products and re-do all the steps again, so I do not recommend this. Follow the switch method on the first answer above instead.3. Is the intended end state to keep BOTH configs permanently (sandbox + production), using a different public key per environment?In my check your live Stripe account has test mode access, so one config is enough after the switch. Thercb_key charges real payments in live mode, and thercb_sb_key makes test purchases in test mode on the same account. Two configs are only needed when testing runs through a separate Stripe Sandbox. See "Working with Stripe Test Mode & Sandboxes" inConnect to your Stripe account.4. Is there an API (v2) endpoint to bulk-create RevenueCat Billing products and attach them to entitlements?No, at the moment they can only be created in the dashboard. API v2 can attach existing products to entitlements (Attach a set of products to an entitlement) and to packages (Attach a set of products to a package), so the attach step can be scripted once the products exist.Finally, as for the failed attempts to contact support, can you please check whether your email system sends an automated reply to messages from@revenuecat.com? If it does, please turn it off and reply here to confirm and I will check further. Automated replies to support emails can cause this problem in my experience.Best regards,

Sign up

‏‏‎ ‎

Log in to the Community

‏‏‎ ‎