#vinicius-martins_unexpected
grave torrentBOT
👋 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/1253436462158843945
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
open snowBOT
sullen willow
Hi there 👋 it can be a bit misleading, but the future_requirements hash isn't necessarily requirements due at a future date. Instead it's showing you a preview of requirements that will be added to the account at some point in the future, typically due to changing KYC requirements. Those new requirements may be due as soon as they're added.
Do you have an example of an Account that you can share the ID for where you're seeing this?
supple sundial
Sure, this is the account I'm looking at acct_1PEcOXPwDCaCteup
I'm trying to understand how would be the best way to interpret this data points in order to warn users that they need to access hosted onboarding and provide additional information
Specially the transition between future_requirements and requirements
sullen willow
Oh, I think I see what's going on here. The requirement in future_requirement.eventually_due looks like it is a threshold based requirement, that will become due once a certain threshold is crossed. Those are typically time-based, or volume-based thresholds.
I believe you can provide an Account Link to your accounts as soon as you see requirements added there, but will need to set collect to eventually_due to force our flow to collect those requirements to.
https://docs.stripe.com/api/account_links/create#create_account_link-collect
supple sundial
By requirements you mean the requirements hash specifically?
I'm asking because there are some examples I've seen that we have currently_due data but the current deadline is null
sullen willow
Nope, I meant any requirements in requirements or in future_requirements
supple sundial
I see
And in this case should I always "merge" both together in order to check if there's any new requirement and its deadline?
sullen willow
Yeah. I do think it's a bit odd to see a future_requirement.current_deadline date in the past, and I'd recommend reaching out to our Support team to look into that in more detail. My suspicion is that the enforcement date for those new requirements may have been pushed back, but I'm not exactly sure.
https://support.stripe.com/?contact=true