Skip to main content
Answer

Stripe metadata and RevenueCat

  • March 8, 2025
  • 1 reply
  • 128 views
C
Forum|alt.badge.img

I am integrating Stripe with the Pricing Table component for subscription management, but I’m facing an issue: this component doesn't allow passing metadata during the checkout process. Currently, we store the app_user_id value in the metadata of the Stripe Customer.

Is there a way to pass this app_user_id or other identification values to RevenueCat after the subscription is created via the Pricing Table? We want to ensure that RevenueCat associates the purchase with the correct user using this data.

Best answer by Haley Pace

Hi, once the purchase has been completed in Stripe you can then use our post receipt API endpoint to send this purchase to RevenueCat and can pass the app_user_id there. See our docs here:

curl -X POST \
  https://api.revenuecat.com/v1/receipts \
  -H 'Content-Type: application/json' \
  -H 'X-Platform: stripe' \
  -H 'Authorization: Bearer YOUR_REVENUECAT_STRIPE_APP_PUBLIC_API_KEY' \
  -d '{ "app_user_id": "my_app_user_id",
  "fetch_token": "sub_xxxxxxxxxx"
  }'

 

This post has been closed for comments

1 reply

H
RevenueCat Staff
Forum|alt.badge.img+8
  • Haley Pace
  • RevenueCat Staff
  • Answer
  • March 13, 2025

Hi, once the purchase has been completed in Stripe you can then use our post receipt API endpoint to send this purchase to RevenueCat and can pass the app_user_id there. See our docs here:

curl -X POST \
  https://api.revenuecat.com/v1/receipts \
  -H 'Content-Type: application/json' \
  -H 'X-Platform: stripe' \
  -H 'Authorization: Bearer YOUR_REVENUECAT_STRIPE_APP_PUBLIC_API_KEY' \
  -d '{ "app_user_id": "my_app_user_id",
  "fetch_token": "sub_xxxxxxxxxx"
  }'

 

C
Terms & ConditionsCookie settingsAccessibility statement