Skip to main content
Question

Best Approach for Setting Customer Attributes When Using Stripe Server Notifications in RevenueCat?

  • November 19, 2025
  • 1 reply
  • 13 views
Z
Forum|alt.badge.img+1

 

I’m currently using Stripe Server Notifications in RevenueCat, and I’ve found that I cannot directly update customer attributes from this flow. Because of this limitation, I implemented the following approach and would like to get feedback on whether it’s safe, reliable, and recommended.

The approach I’m using:

  1. I create a RevenueCat customer using the user’s sessionId as the app_user_id 

  2. After creating the customer, I update their attributes—for example, adding the user’s email.

  3. In RevenueCat, I configured it so that metadata is pulled from the app_user_id assigned to the customer.

  4. During checkout, Stripe Server Notifications correctly map the transaction to the RevenueCat customer using this app_user_id.

My question:

Given that Stripe Server Notifications do not allow updating attributes directly, is this an appropriate and safe approach?

  • Are there any risks, edge cases, or potential issues with this method?

  • Would the community recommend a better alternative?

I’d really appreciate any insight or suggestions to ensure this setup is stable and optimal.

Thanks!

 

1 reply

jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • jeffrey_bunn
  • RevenueCat Staff
  • November 21, 2025

Hi ​@zodplugin! Your flow is exactly what we’d recommend if you want to ensure that any downstream integrations you enabled include the customer’s attributes in subscription lifecycle events. The only thing I’d point out is your use of the Stripe sessionId as the app_user_id. Typically, we recommend using UUID’s and/or an authentication service (Firebase, AWS Cognito, Auth0, etc) to ensure IDs are stable when users log in and never change or collide. 

Terms & ConditionsCookie settingsAccessibility statement