#samina_unexpected
jagged dawnBOT
👋 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/1478401342463545485
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
boreal thorn
hey there, do you have example accounts showing the different behaviour? ie, before and after some shift you noticed.
Broadly speaking I don't believe we have any specific timelines for the async review states for those test values.
Can you also share some context about your integration and how this is affecting it? ie, what are you trying to do?
tepid fox
so, when users sign up, they enter last 4 digits of ssn and full ein as part of the kyc flow.
when stripe marks them as wrong, we also immediately show on our dashboard UI that they entered the wrong information
however, we noticed that it is in this in review state for 45+ mins
it used to take no longer than 2 or 3 mins before
i am noticing this delay since yesterday
boreal thorn
Ok thanks, I do see the review details are still pending on this example test account. do you have an example test account from yesterday showing the previous timing you observed?
jagged dawnBOT
tepid fox
there are many examples, here is one
boreal thorn
Ok thanks, yea I see that lead to the account.updated event relatively soon after you submitted the SSN and owners_provided
tepid fox
yeah, could you please look into why this is happening and when we can expect this to get fixed
chrome galleon
hi there, I'm taking over for synthrider as they had to step away. I will reach out to our internal product team for this and let you know what they find
tepid fox
thank you
tepid fox
do you have an update on this
chrome galleon
hi there, still waiting on a result from the investigation
chrome galleon
ok, I think this is going to take longer than a Discord session can handle, so I'm going to convert this into a support case. you'll receive a DM that will instruct you on how to do this, and we can follow up with you through email based on the product team's investigation
jagged dawnBOT
Hello @tepid fox, we have sent you a direct message, please check it at https://discord.com/channels/@me/1463239118392656108
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
tepid fox
Btw, is this affecting production customers or only happenign on sandbox
chrome galleon
I have not seen reports of this affecting production customers