#jay_api
1 messages · Page 1 of 1 (latest)
👋 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/1282721622049947782
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
We are using the custom payment flow with the payment intent with a backend and a custom client interface on the front end. Our backend is stripe.net library
Okay and what timeout? The ACH Connections flow where your user is shown a modal to connect their bank account for ACH Debit?
Yes that’s correct the user is shown a modal to connect their bank account for ACH debit, users seem to be complaining timeout/inactivity issues to the client we build this for. Is there a way to increase this timeout?
No there isn't a way to increase that, but it should be pretty lengthy to begin with.
There really shouldn't be any issue if they are just completing the flow as they go.
If they literally abandon or leave and come back later then yeah there would be a timeout.
Do you know what sort of timeframe we are talking about here?
Because the other option is a potential bug in your code or on our end or something if the timeout is really quick
We are given estimates of about average 5-15 minutes, depending on the user who seems to be using this. It’s strange cause out of 15 users, only one managed to finish the flow and succeeded the payment. The others are cancelled and we have one failed payment
Yeah if we are talking about multiple minutes then that is expected... the idea of the flow is that the user completes it during that moment in time.
We can't keep an open-ended connection with the bank here. There will always be a reasonable timeout
Have you taken a look at this ticket ? Such as the one with the checkout.session.async_payment_failed
Maybe it could also be a bug we are overlooking too
The req is req_dMeSAFGrqxvxPy
That example looks like it worked just fine in terms of Financial Connections. The Charge was declined by the bank as you can see in the charge.failed Event: https://dashboard.stripe.com/events/evt_3PsPQJ08njICOWrD04Gllmlu
So everything worked as normal there and the customer would need to talk to their bank for why they declined the debit here.
But there was no issue with the integration
Okay thank you, sorry one last follow up question. Is there any way to fill those six bank slots on the stripe payment page through code? Such as the tiles with Wells Fargo, Chase, etc?
No, that isn't customizable
Okay thank you, you may close this thread and I will open another thread/question for any follow up questions. Thank you very much Bismarck!