#bharatkilaru
1 messages ยท Page 1 of 1 (latest)
Hi ๐ you mentioned you're building a Subscription pages, but then also mentioned you're creating Payment Intents. Those two typically don't go together, so I wanted to double check whether you were trying to create Subscriptions or one-time payments?
Hey! Yeah, I mean create subscription and expand to pass back the latest_invoice.payment_intent from the server to the client. Or is that not the best way to create a subscription via Payment Element?
๐ it is, just wanted to make sure we were thinking of the same flow.
I don't think I've tried updating a Payment Intent that was created from an Invoice for a Subscription, but I assume the update capabilities are pretty limited in that case.
Would it be possible to arrange your checkout flow so that your customers settle on what they're subscribing to before you begin rendering the Payment Element? If not, I think canceling the previously created Subscription and creating a new one would be the better approach.
Yeah, same thing I was thinking about UX wise! I think we've been choosing between Payment Element vs Stripe Checkout around this point. Basically hoping we can embed more smoothly, we have been landing on Payment Element. But have been creating a large number of incompletes on page load or rerenders as user switches between plans.
Definitely understand, I haven't looked at the Subscription-specific version of this newer flow too closely, but we released flows that allow you to defer intent creation to help avoid having those incomplete payments hanging around:
https://stripe.com/docs/payments/accept-a-payment-deferred?platform=web&type=subscription
This is super helpful! Going to try this. If we do go in the direction of a separate page (user picks subscription plan first), do you see strong reasons for using Checkout over Payment Elements to handle subscriptions?
I would recommend Elements if you're after a more embedded experience, but Checkout has some features above and beyond what is offered via the Payment Element like upsells.
https://stripe.com/docs/payments/checkout/upsells
Thanks! And if we do embedded Payment Element and go ahead with your original idea: "canceling the previously created Subscription and creating a new one" -> do you think there's any downside to repeatedly cancelling and creating new subscriptions with new intents like this?
Just the time it takes to make the requests