#moustache_api

1 messages ¡ Page 1 of 1 (latest)

ebon havenBOT
broken fulcrumBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

ebon havenBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252335981537923114

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

golden olive
#

To be more specific, the bank account was setup with a missing mandate (we are away of that have have since updated our system to setup the correct mandate when adding payment methods) but until recently, these bank account payments just started failing on subscriptions. Any clarification to a change on Stripe's side would be helpful.

proper shadow
#

Hello, taking a look

#

Can you try explaining the mandate piece until further? Was this working before without mandates being set up?

golden olive
#

yes, nothing has changed on the bank account or the subscription but last month it worked, and this month is never attempted a charge and immediately cancelled the subscription.

image.png
#

I noticed this message on the payment: pi_2PSkc6wPNbMMXFhm0yeFK77E

#

I just don't know why suddenly we suddenly require confirmation and last month it worked

proper shadow
#

Thanks for the info, I am still looking in to this. I have not spotted the specific difference yet

golden olive
#

Thank you! Standing by.

proper shadow
#

I have not been able to find an explanation for the difference in behavior. I will consult my colleagues and get back to you

golden olive
#

ok, great should I keep this chat window open?

proper shadow
#

Yep yep, I will follow up in here. Shouldn't be too long

#

We found a change on our side that is causing this difference and are pulling in others to take a closer look. I will keep you updated as we find more

golden olive
#

awesome, thank you.

proper shadow
#

@golden olive after further investigation, we found that this happened because your integration made an API call that set this bank account as the default_payment_method on the account. Before it was just the default_source and sources do not require a mandate, but when it is set in the invoice_settings.default_payment_method field we charge it as a PaymentMethod which does require a mandate. If you unset invoice_settings.default_payment_method on that Customer, we should be able to charge that bank account automatically again.
https://dashboard.stripe.com/logs/req_rHQKK0dpxDYmzS

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.