Skip to main content
Question

web billing paywall with custom success page, app_user_id param

  • December 4, 2025
  • 3 replies
  • 34 views

Forum|alt.badge.img+8

Based on the docs of a web billing paywall + custom success page, it looks like the app_user_id URL param is automatically appended. However, I am not seeing this when testing...the sandbox URL maybe does not know the different of environments, so the ID does not get passed back to complete the test?

 

Is this an issue because I am using a custom paywall also?
 

I am now nervous to launch my renewal subscription to 2k users.  I tested on production too, with the same outcome.  How can I get the app_user_id?

 

3 replies

guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • December 15, 2025

Hey ​@lucksp !

That should indeed worked as described, so there could be something else happening if you aren’t able to see the appended ID. If you log the URL all the way through the testing steps, does the URL at any point contain the ID? Are you able to enable and share the SDK debug logs that you get in your flow?

Also, would you be able to share and confirm:

  • your RevenueCat project ID
  • your RevenueCat account ID (email of the project owner)

for us to try and replicate the exact configuration and see if anything odd jumps out?

If you prefer to open a ticket via our Support From (instead of sharing them here), that would work too! Make sure to link this community thread and even referencing myself to help in triaging this through internally.

Thanks,


Forum|alt.badge.img+8
  • Author
  • Helper
  • December 15, 2025

It looks like this is a bug in your system, based on this email from your support team:

 

Is there a way for you to check on the status for this??

 

Phil


guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • December 22, 2025

Looping back here for transparency, as we’ve also been tracking this via Support internally. We shipped an update that should address the sandbox behavior, but we’re still verifying everything is working end-to-end - no updates required, as this was an internal fix, so it should just work!

And in case anyone else stumbles on this thread and sees similar issues, please reply with details/repro steps so we can compare.