Skip to main content
Solved

Error code: 16 while purchasing from sandbox web paywall link


Forum|alt.badge.img

I am testing out web paywall buttons in Revenuecat Paywalls. While testing out the flow in sandbox url, I get an Error 16, this is the URL for paywall https://pay.rev.cat/sandbox/rzncmmyjvdmgqpaq/123

I saw a similar question 

but here the user was trying to purchase production products while stripe was in test mode, but in my case stripe is not in test mode. I followed this video about web paywall buttons https://www.youtube.com/watch?v=XF9cbvyiK48 and didn’t see him do any special config to get the sandbox paywall working 

Best answer by pol-miro

Hi,

I looked into it and looks like the new permissions needed by RevenueCat Stripe app have not yet been accepted. You should have received an email from Stripe requesting to update permissions. But if you have not you should be able to do it here.



Sorry for the cryptic error message. We will improve this soon and make it more developer friendly!

View original
Did this post help you find an answer to your question?
This post has been closed for comments

2 replies

Forum|alt.badge.img
  • Helper
  • 1 reply
  • Answer
  • May 4, 2025

Hi,

I looked into it and looks like the new permissions needed by RevenueCat Stripe app have not yet been accepted. You should have received an email from Stripe requesting to update permissions. But if you have not you should be able to do it here.



Sorry for the cryptic error message. We will improve this soon and make it more developer friendly!


Forum|alt.badge.img
pol-miro wrote:

Hi,

I looked into it and looks like the new permissions needed by RevenueCat Stripe app have not yet been accepted. You should have received an email from Stripe requesting to update permissions. But if you have not you should be able to do it here.



Sorry for the cryptic error message. We will improve this soon and make it more developer friendly!

So the problem was that we had set up Stripe long ago, and we had only installed it as an extension, we had to update it to app. It works fine now, thanks

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings