#Lukas_4774-subscriptions
1 messages · Page 1 of 1 (latest)
👋 happy to help
you could always use SetupIntents to attach a payment method to a customer and set that as being the invoice_settings.default_payment_method
Thank you for answering so quickly. Can the setup intent be connected to the product such that the user can verifies what he or she is paying for?
no not really
SetupIntents is just asking the user to collect their Payment Method for future usage
I see. It might be that later authentication in the off-session case is required, right?
it's up to the discretion of the issuing bank yes
I hope I could create a normal subscription as proposed in the integration guide and in the same step update the subscription schedule to be in the future. However, I do not know what the invoice would contain
Does this mean in our use case, that we set the billing cycle anchor to a very future date such that we know when the actual subscription starts will be accordingly updated?
If it was me I wouldn't even create the subscription
like my colleague said, you can collect the payment details now with e.g. a SetupIntent, and you can create the actual subscription later when you know when it should be created
Okay, thanks for the hint. This means however that the user a) won't see the subscription prices in the stripe checkout process and b) might need to verify the payment details?
a) true
b) true , when you actually start the subscription there is a payment for the initial billing period and that might require authentication or be declined