#digi-f_error
sweet patioBOT
đ 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/1217367618726527046
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
misty sealBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- digi-f_icplus, 4 days ago, 23 messages
runic current
Context of what we aim to do:
To upgrade the subscription, we intend to switch to a new "plan" with a different product, price, duration, and possibly a discount. This discount is applied as a direct amount reduction, with an optional duration.
More technically:
Initially, we attempt to update the subscription using the "error_if_incomplete" option. Upon encountering a 3D Secure, we inevitably encounter a "subscription_payment_intent_requires_action" error. We then retry the update with the 'pending_if_incomplete' option.
For this purpose:
We create a plan with the new product ID, amount, and duration.
We generate a coupon based on the offer, specifying its duration and amount reduction.
We retrieve the subscription and update it with specified parameters, including 'proration_behavior', 'payment_behavior', and 'coupon'.
With 3D Secure, the subscription enters a "pending_update" state. We proceed to confirm the payment by:
Obtaining the latest invoice of the subscription.
Retrieving the payment_intent of the failed invoice.
Utilizing the client_secret and default_payment_method of the customer to validate the card payment via JavaScript using "stripe.confirmCardPayment(...)".
Everything functions smoothly without a coupon. However, with a coupon, its application is not permitted in this context.
shadow crane
Hi, will be responding soon. Gimme a few mins
Can you provide the example failed request id?
Alright that's expected because coupon is not a supported parameter for pending update https://docs.stripe.com/billing/subscriptions/pending-updates-reference#supported-attributes
