#harshthakkar_api

1 messages ¡ Page 1 of 1 (latest)

dusky loomBOT
#

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

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

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.

strong osprey
pulsar verge
#

Thanks Orakaro will review details shared .

#

Just reviewing details in the link
https://docs.stripe.com/connect/handle-verification-updates#preview-updated-verification-reqs.
It says about checking future requirements API but in this link https://docs.stripe.com/connect/handle-verification-updates#api-version-considerations it says to check for requirements API so bit confused we still use only requirements API for onboarding and post onboarding requirements right (and not future requirements )?

Handle verification updates

Help your connected accounts maintain compliance with changing verification requirements.

strong osprey
#

Sorry not really follow the question

#

These fields are also explained that

future_requirements.current_deadline
Date on which future_requirements merges with the main requirements hash and future_requirements becomes empty. After the transition, currently_due requirements may immediately become past_due, but the account may also be given a grace period depending on its enablement state prior to transitioning.
and
future_requirements.currently_due
Fields that need to be collected to keep the account enabled. If not collected by future_requirements[current_deadline], these fields will transition to the main requirements hash.

#

So you can delay collecting future_requirements, but need to pay attention to its currently_due and currently_deadline