Skip to main content

Inconsistent email field display in Web Checkout for some users

  • January 5, 2026
  • 1 reply
  • 38 views

Forum|alt.badge.img

Hello RevenueCat Support Team,

We are integrating RevenueCat Web SDK (@revenuecat/purchases-js) with Stripe Checkout for our web subscription flow.

We are passing customerEmail during purchase, like this:

 

await Purchases.configure(WEB_BILLING_PUBLIC_API_KEY, appUserId); await Purchases.getSharedInstance().purchase({ rcPackage: selectedPackage, customerEmail: subscriptionData?.email, });

Expected behavior:

  • Email field should be hidden or pre-filled for all users (since we already pass customerEmail).

Current behavior:

  • For most users, the email field is hidden / pre-filled, which is correct.

  • For some users (e.g., kavita@flunzy.ai, kruti@flunzy.ai), the email field still appears on the subscription screen.

We understand that Stripe Checkout controls whether the email field is displayed in some cases, such as existing customer state or session differences.

Questions / Request:

  1. Can you confirm whether this behavior is expected and controlled by Stripe Checkout?

  2. Is there any supported way to consistently hide the email field for all users while still passing customerEmail for receipts and billing?

  3. If not, can you provide guidance on the recommended approach to ensure a smooth subscription experience without requiring users to re-enter email unnecessarily?

Thank you for your guidance.

Best regards,
Team Flunzy

1 reply

Forum|alt.badge.img+8
  • RevenueCat Staff
  • January 15, 2026

Hi ​@flunzy-5dda29, this behavior is controlled by RevenueCat. The reason you are seeing the flunzy.ai email addresses not hiding/pre-filling is because it seems to be failing our domain validation, we were also able to reproduce this on our end. We do a validation on the email address to make sure we're able to reach the customer but it appears that with this specific domain it's failing. Can you let me know if it is only failing when you test those emails or if there are any other domains you are seeing this with?