#stan-invoice-bank-account
1 messages · Page 1 of 1 (latest)
Hi there 👋 at first glance it looks like a mandate is missing, can you share the ID of the invoice so I can take a closer look?
Hi Toby thanks for helping! The id is in_1LDuWTKlea8x2P9F1ktRLQTw
Thank you, pulling that up.
sorry taking over and looking (channel has a few people asking for help so will take some time but I'll be back)
Okay so the problem is that you are using a Legacy BankAccount ba_123 but you made it the default PaymentMethod and when you are attempting to pay it needs a mandate adn you don't have one setup.
You have to migrate all your legacy ba_123 across your customers to have a valid mandate. See https://stripe.com/docs/payments/ach-debit/migrations#mandate-acknowledgement
https://dashboard.stripe.com/logs/req_NQE1gYbPIdsyWm this request is causing the issue
Instead of being treated via the legacy API (what existed until earlier this year) you use the new flow via the default PaymentMethod API which is a bit different and comes with different requirements
My advice is to run a "migration" where you loop over all your customers and if they have a ba_123 you create a valid mandate for them (see my link above) and then you will be unblocked
@stuck bobcat did all of that help?
yes that makes sense. I think the problem is that we are using the plaid-stripe integration for ACH so we will always get a legacy bank account. I think we just need to add an extra step to convert bankAccount id to a paymentMethod id?
no
there's no conversion per se
My advice would be to move off of Plaid and use our brand new integration https://stripe.com/docs/payments/ach-debit
but otherwise you need to do the SetupIntent trick in the doc I mentioned earlier https://stripe.com/docs/payments/ach-debit/migrations#mandate-acknowledgement