cristian_subscription-updatelimits

[rotund trench]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1305602123668394098

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[leaden nymph]

@rain flame we don't document hard/exact numbers unfortunately because this can be abused by attackers and the numbers fluctuate. But it's abnormal to update the same Subscription say 20 times an hour except in Test mode. And in Test mode the easiest is to just create a new Subscription each time

cristian_subscription-updatelimits

[rain flame]

We had to build a complex subscription management system on our end since Stripe doesnt allow us to differentiate between product quantities in a single subscription.

We can have multiple subscriptions for a single customer (with different payment methods) in some scenarios and they should be able to move the quantities from one subscription to another.

So it would be common to update those subscriptions multiple times in an hour if they are moving stuff around

We can have this scenario in prod that could trigger the rate limit error and it would block a customer from proceeding