bp_unexpected | Stripe Developers | Page 1

arctic ridgeBOT May 6, 2024, 10:52 PM

#

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

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

vague minnow May 6, 2024, 10:56 PM

#

So setting eventually_due will only request that they give all the info. They can still bypass that by not providing certain fields in the onboarding forms. Even if you forced collection of all the requirements up front, it's still possible for the verification to fail or for Stripe to request additional information, so you should make sure to build a system that's capable of getting notified of those updated requirements and can re-prompt the user to enter them

#

This doc goes into details about that: https://docs.stripe.com/connect/handling-api-verification

Handle verification with the API

Learn how Connect platforms can use webhooks and the API to handle verification of connected accounts.

wintry beacon May 6, 2024, 10:59 PM

#

Okay so we need to handle the ID not being requested because the onboarding flow wont always work how it should?

vague minnow May 6, 2024, 11:03 PM

#

It's working exactly as it should. Stripe just makes the onboarding process more seamless by not requiring every single possible field that could ever come up. The point of hosted onboarding is to get people up and running quickly, so they can then provide their verification later on and start getting your platform paid as fast as possible.

It's your job as the developer to make sure that system can programmatically handle additional verification after they onboard, as even if they provided everything up front, it could still fail the verification (which isn't instantaneous) and require the user to come back into the portal to update their credentials.

#

For what it's worth, Stripe calls out in the onboarding portal when they haven't provided certain things, so nobody goes through the portal without knowing that they gave incomplete verification information when eventually_due is set

#bp_unexpected