#dmitry_api
1 messages · Page 1 of 1 (latest)
👋 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/1397573085271687238
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
I'm looking at the live mode subscription sub_1REvguRvfSBQU3HHLvB7MHYA
Can you share the sandbox subscription you were comparing to?
Since this is Portal behaviour, I may need to have you speak to support about the differences, but first I want to see if I can spot any differences between the subscription attributes/states
Sure, this is request in Sandbox: req_f2M7ALIDqqvoI5
I think it's for this subscription: sub_1RngugFtucC0nsFoqwTfRxYw
These are not quite the same, because in the live sub the invoices were updated to be uncollectible, which does not happen in the sanbox sub
So there is certainly some configuration difference between the two
Yea, your subscription handling behaviour is different in sandbox vs live
I suggest making sure all settings are the same and re-testing
I'll give it a try, thanks!
You were right, thanks!
But now I have another question.
Is there a way to achieve the same functionality for subscriptions with invoices that are marked uncollectible?
A link that consumers can open to view that the subscription is past due and update the payment instrument?
As explained here https://docs.stripe.com/billing/subscriptions/payment-methods-setting?locale=en-GB#update-payment-method, but the link should be created using the Stripe API.
I'm not sure about those single use links, but you can generate portal sessions to let the customer update their payment method using the API with the flow approach and payment_method_update:
https://docs.stripe.com/customer-management/portal-deep-links#flow-types
Yes, that's how I do it now. And it doesn't show the “Payment failed” message or the “Update payment method” prompt if the subscription is past due, but the invoice is marked as uncollectible (instead of past due).
Yes, that's how I do it now.
It doesn't look like that's wht you're doing, i don't see any use of theflow_typein the portal sesison creation request you shared
Aahh, sorry! You are right, thanks for pointing this out.