Skip to main content
Question

RC Billing: How to update the checkout email used for lifecycle emails?

  • March 6, 2026
  • 1 reply
  • 35 views
K
Forum|alt.badge.img+3

We're using RC Billing (Web Billing) with the RevenueCat JS SDK. During the purchase flow, we pass the customer's email via the `customerEmail` parameter in `Purchases.purchase()`.

Due to a bug on our side, some subscribers had an incorrect email passed as `customerEmail` at checkout time. We've since fixed the bug, but for the affected subscribers, all lifecycle emails (subscription confirmation, renewal reminders, billing issue notices, etc.) are still being sent to the old incorrect email.

What we've already tried:

1. Updated the `$email` subscriber attribute in the RevenueCat dashboard — lifecycle emails still go to the old address.
2. Updated the email on the corresponding Stripe Customer — lifecycle emails still go to the old address.

It appears that RC Billing stores the checkout email internally, separate from both the `$email` subscriber attribute and the Stripe Customer email, and uses that internal email for lifecycle emails.

Questions:

1. Is there an API endpoint or dashboard option to update the RC Billing checkout email for existing subscriptions?
2. Does RC Billing use a separate internal email field from the `$email` subscriber attribute for sending lifecycle emails?
3. If there's no self-service option, what's the best way to request a bulk update for affected subscribers?

Any guidance would be greatly appreciated. Thanks!

1 reply

KitRCAdvocate
Forum|alt.badge.img

Good diagnosis — you're right that RC Billing stores the checkout email separately from the `$email` subscriber attribute and the Stripe Customer email.

 

As of now, I'm not aware of a self-serve API endpoint to update the stored checkout email used by RC Billing for lifecycle emails, so RC Support is the right path for backfilling affected subscribers. When you reach out, send them the affected App User IDs + correct email addresses and ask about bulk update options — they'll know the current process.

 

For prevention going forward: the `customerEmail` passed at checkout is the authoritative source for RC Billing lifecycle emails. If your app has a profile flow where users can update their email, you'd want to make sure that change surfaces to support somehow, or document it as a known gap in your flow.

 

If this affected a large number of users, flag the bulk aspect upfront when contacting support — it's a different conversation than a one-off fix.

Terms & ConditionsCookie settingsAccessibility statement