#kaladin_invoice-bacsdebit
wary sandBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1280546962650959974
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
wise portal
Hey there, to achieve this you'll likely need to set up the bac debit payment method up front: https://docs.stripe.com/payments/bacs-debit/save-bank-details
You can't control the setup_future_usage parameter within invoice-controlled payment intents
wary sandBOT
fringe wedge
Thank you. I see at the end of that article that we can then create a payment intent with the saved direct debit mandate.
If we generate a new invoice for the next payment instalment, how do we then use this payment intent to pay an invoice?
The docs here say that the payment intent is generated when the invoice is finalised. It's not clear to me how I would combine the two. Or should we not be using an invoice for this?#
dry maple
kaladin_invoice-bacsdebit
@fringe wedge you can't do that at all. It's not possible to create your own PaymentIntent and then later attach it to an Invoice today. So you'll have to create the Invoice first in that case.
What you should be able to do is update the PaymentIntent after the Invoice creates it instead of what my colleague was recommending and it should work
fringe wedge
Ok. So the direct debit mandate will be stored as a PaymentMethod, and I can update the PaymentIntent on the invoice with the id of that payment method?
dry maple
What you said is not really correct but it's likely a vocabulary issue overall.
A PaymentMethod pm_1234 represents a payment instrument such as card details or bank account details for BACS Debit.
A Mandate mandate_12345 represents the customer acceptance for a certain type of payment (once or recurring, when they approved, etc.)
Those are two separate objects in our API each representing a different thing. And you will need both to pay future Invoices yes.
fringe wedge
Ok thank you. I may have to come back to this. At the moment I am just doing initial scope and trying to understand the API, but it sounds like the thing that we are trying to do (take a direct debit mandate, store it, and use it for future payments even though we don't know the amount) is possible?