#Hugues
1 messages · Page 1 of 1 (latest)
Hello there
There isn't really an example of this that I know of but also that isn't really a flow you should be doing... you would just set the payment method up for future use via the PaymentIntent.
Can you tell me more about what you are trying to do?
Hi bismarck, our customers would make a first payment and we'd use their payment information to charge for future monthly payments.
Great so yeah you don't need a SetupIntent in this case.
Which integration flow are you using here?
To complete the description of our need, we'd use Pre-Authorized Debit payments which require Mandates. To simplify the workflow, we'd like to have a single Mandate to include the deposit payment and the monthly payments. As far as I know, the only way to have a Mandate to aggregate many types of payments is through SetupIntents. Am I right?
Nope you should be able to do this via a PaymentIntent too. You pass those necessary mandate fields in payment_method_options.accss_debit.mandate_options (https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_options-acss_debit-mandate_options) and pass setup_future_usage
How would you specify a one-shot payment PLUS recurrent monthly payments in that mandate via a setup_future_usage?
Ah one sec let me double check
I thought you could use payment_schedule: combined but actually that might not work if you are using Subscriptions here
The reason I first mentioned about SetupIntent is because of the following example: https://stripe.com/docs/billing/subscriptions/acss-debit#save-payment-method-for-future-subscriptions
Yep
It definitely does work with a SetupIntent, I just thought that you could do this flow with a PaymentIntent.
But I could be wrong and we just didn't build it this way.
I'm double checking with a colleague.
Give me a minute
👋 hopping in here since bismarck has to head out, but they shared all the state they had - it looks like you do have to use a setup intent for this
Fine, then can you tell me how to do a setup intent and a first payment in the same customer transaction?
Will this first payment be as part of a subscription, or just a one-off?
Just a one-off: its a deposit to be followed by recurrent payments. Like I said earlier, we'd use Pre-Authorized Debit payments which require Mandates. To simplify the workflow, we'd like to have a single Mandate to include the deposit payment and the monthly payments. As far as I know, the only way to have a Mandate to aggregate many types of payments is through setup intents.
Thanks for clarifying! So yeah you'd use the instructions specified at https://stripe.com/docs/billing/subscriptions/acss-debit#save-payment-method-for-future-subscriptions to create + confirm a SetupIntent. Once that's done you'll haev a Payment Method and Mandate ID that you can use to create + confirm a Payment Intent (following these instructions https://stripe.com/docs/payments/acss-debit/set-up-payment?platform=web#charge-later)
If you'd prefer to use a one-off Invoice to colelct your deposit that would also work as well