ariela_ach-timing

[radiant tusk]

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.

• arielapaula_code, 3 hours ago, 5 messages
• arielapaula_code, 3 hours ago, 10 messages
• arielapaula_confirm-bank-account, 4 hours ago, 12 messages
• arielapaula_code, 2 days ago, 4 messages
• arielapaula_api, 2 days ago, 23 messages

[hybrid python]

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

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

[weary bough]

Is there a way to make confirmUsBankAccountPayment a synchronous call?
@signal comet no there isn't. Accepting payments with ACH Debit is always asynchronous. Success or failure happens days later in production. See https://docs.stripe.com/payments/ach-debit#timing

ariela_ach-timing

[signal comet]

Ahh I see, do you have a recommended approach on how to handle this? Maybe a webhook in the server side?

[weary bough]

yes you should listen to payment_intent.succeeded and payment_intent.failed which will happen days later (it's all in that doc too so I recommend reading it carefully)