ashtray-wasp_api

[stark bridge]

👋 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/1326100675041431604

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[stray wasp]

Looking into this!

[hybrid jewel]

Hi there, you need to specify the mandate when using the API to pay the invoice https://docs.stripe.com/api/invoices/pay?lang=node#pay_invoice-mandate

[rancid ether]

Is there any way I can get the mandate ID when all I have is the payment method ID?

I'm also wondering why the issue is only with this particular payment method, haven't seen any problems with other payment methods, with mandate ID unspecified in the pay request

[bronze gyro]

no; the idea would be that you save the ID from https://docs.stripe.com/api/charges/object#charge_object-payment_method_details-us_bank_account-mandate when you process the first payment, that created it

[bronze gyro]

most payment methods don't use mandates.

personally I'd never use that invoice.pay endpoint, I would confirm the invoice->payment_intent with the PaymentIntent confirm API, which I think might not have this issue. I'm not 100% sure if passing mandate to your API call will work or if the issue is something else, but it's worth a try

[rancid ether]

It seems that there is a lot of us_bank_account payment methods with a mandate in my account, and only this one causes a problem. I'd like to avoid having to store the mandate ID.

Will try with the payment intent confirmation instead of invoice.pay. Out of curiosity, is there any reason to avoid invoice.pay?

[bronze gyro]

it doesn't handle things like 3D Secure is the main one

and yeah maybe it's a different issue, to do with the Connect on_behalf_of scenario you're using, I'm not sure. Passing it explicitly might give a more informative error message