#bharatkilaru
shy python
night meadow
Hello 👋
It depends on your usecase really. A customer can have multiple subscriptions. So there isn't a technical limitation.
However, if you're using Reporting then you might see this impact your total subscription churn metrics and all (I don't know a ton about reporting to confirm this 100%)
We have a new flow which allows you to render PaymentElement without an intent attached
https://stripe.com/docs/payments/accept-a-payment-deferred?platform=web&type=subscription
This should allow you to control the timing of subscription creation
harsh basin
Cool, thanks! Is this recommended over the approach of creating the intent first?
night meadow
It isn't the default path yet, it mostly comes down to the usecase
both flows are aimed towards enabling merchants to design their own flow and reduce complexity
harsh basin
Got it. Thanks. For some context (if helpful), we have a UX where we render the payment element and the plans on the same page. So a user might toggle between different plans and thus create a number of incomplete subscriptions
night meadow
Totally understand, in that case the deferred flow makes sense