naveen87

[north cobalt]

Hi 👋 the approach that you're describing is the correct approach for working with Subscriptions and the Payment Element.

The only alternative that comes to mind is to rearrange the flow so that you collect payment method information first, and then create the Subscription later.

To do this, you would use a Setup Intent to collect the payment method details, then you would provide the created Payment Method when creating the Subscription. Similar to this flow, but you would create a Subscription rather than a Payment Intent later:
https://stripe.com/docs/payments/save-and-reuse?platform=web

There are tradeoffs with this approach though. For instance, a user's bank could require 3DS/SCA to be completed for both the Setup Intent and the Subscription payment, in which case your flow would need a way to present the challenge to your customer during the payment attempt.

[alpine wraith]

I'll look into this, thanks

[north cobalt]

Happy to help!