#Celsian
icy dust
gleaming geyser
We would actually suggest creating the subscription first and using its payment intent to power the payment element like in this guide: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements
When you plan to take a payment immediately we discourage using SetupIntents, it can lead to things like the user being asked to complete 3DS twice for one transaction
visual harness
We were originally doing that, but when we entered a 100% off coupon it would bypass capturing the payment information.
Entering a coupon code that is not 100% off causes the page to refresh as well (to generate the new subscription) and subsequently clearing all of the users entered data.
gleaming geyser
Do you know off the top of your head what was happening Stripe API wise when you applied that coupon? I think we would still allow payment information at that point
visual harness
Client goes to the checkout page and an incomplete subscription is generated.
Client enters a 100% off coupon, the page refreshes, generates the new subscription for $0 and completes immediately because no payment is not necessary.
I could find an example user where this has happened.
gleaming geyser
Also the reload for that second scenario can likely be avoided by fetching the updated payment intent https://stripe.com/docs/js/elements_object/fetch_updates
visual harness
Ok thank you, let me look into that.
gleaming geyser
To take another step back: is there a reason you are creating new subscriptions rather than updating the old one?
That could get rid of the non-100% off reload I believe. I think you should be able to do something similar with the coupon but will have to double check
visual harness
Ok, that is working as expected now. Thank you for that information. I will move forward with that and come back if I have more questions. Thank you again.