#ayeshaikh_7
quartz sentinelBOT
Hello! We'll be with you shortly. 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.
- ayeshaikh_7, 3 hours ago, 34 messages
- ayeshaikh_7, 5 hours ago, 10 messages
- ayeshaikh_7, 2 days ago, 8 messages
- ayeshaikh_7, 2 days ago, 3 messages
dim shell
Hi there 👋 I'm not sure offhand, that Sources flow is an older deprecated flow and one that I'm not as familiar with. Let me see if I can find anything on that. Is this a new integration you're building, or one you're maintaining?
I've not been able to find anything about a timeout so far.
dim shell
Gotcha. I'm not having any luck finding anything about that older flow having a timeout.
modern arch
so can micro deposits timeout be different for sources api & new payment intent api implementation?
dim shell
Possibly, I wouldn't be too surprised if there aren't timeouts with the Sources flow, it's a lot less robust than our new integrations.
modern arch
ok, I wanted some confirmation on that but couldn't find anything around it.
So, is it safe to assume that for sources api there is no timeout for microdeposit verification?
dim shell
I'd be careful assuming that. I do suspect that is the case, but would recommend having some guardrails/alerting around that just in case.
modern arch
any way I can confirm this? other than testing it on production it self
dim shell
No great options come to mind. The only thing I can think of is to try starting one in test mode, and see if it ever expires. But, I'm not sure if you'd be notified if it did expire, or if you would need to try the verification periodically to see if you can still do it, which would take a long time to test well.