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.
