#leahhannahceramics_api

1 messages · Page 1 of 1 (latest)

exotic driftBOT
#

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

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

long arrow
#

Hi 👋

The requirements property will include details on what KYC requirements are still outstanding for this account

icy sonnet
#

Thanks for sharing - I'm specifically referring to an instance when a merchant leaves onboarding (save or later or closes browser)

#

Should I expect the past_due array under requirements to be populated? is there an instance where this array is populated but the merchant submitted info for review?

exotic driftBOT
cobalt owl
#

Hi there 👋 taking over, as my colleague needs to step away

The requirements can be in a variety of different states, depending on what they chose to enter before they left the onboarding flow. If a verification is underway, but not yet fully verified, then you'll see the pending_verification array populated with whatever verification is ongoing

icy sonnet
#

I see - I am using hosted onboarding - can I merchant complete the "Agree and submit" step and still have the past_due array populated with an item?

cobalt owl
#

Yep! Because they don't actually have to enter all info that's required. Hosted onboarding will ask for it, but some fields can be skipped. It's also possible that they put in info that's not verified by the time the hit "Agree and submit", so you need to listen for account.updated webhooks and check the requirements object for any past due requirements

icy sonnet
#

The onboarding flow I am trying to implement is supposed to ask for everything upfront (currently due, eventually due and future requirements) - confirming that merchants can still skip required fields for the card payments and transfer capabilities?

cobalt owl
#

It will ask for those things yes, but they aren't forced and (even if they were) you would still have to check that the info they submitted was verified and correct

icy sonnet
#

Thanks for sharing - I am trying to display a message for merchants who left onboarding before hitting the "Agree and submit" step. Is there something I can rely on that indicates that?

cobalt owl
#

Are you using Account Links for this?

#

You might look into setting up the notification banner on whatever your return_url is for the Account LInk: https://docs.stripe.com/connect/supported-embedded-components/notification-banner

This will display any outstanding requirements on the account, or it will show nothing at all if there are no outstanding requirements. Not sure if that helps your use-case or not, but it sounds related.

Notification banner

Show a banner that lists required actions for risk interventions and onboarding requirements.

icy sonnet
#

I'm using Account Links and I am using the notification banner

#

I was informed that the banner won't show unless the merchant hits "agree and submit" - that is why I am looking to display a message if the merchant doesn't hit that step.

cobalt owl
#

Ahhhh, I see. So your use-case is predicated on the user exiting the page? Where are you intending to display the message to them in this case?

icy sonnet
#

Correct - I'm trying to cater for merchants dropping off of onboarding - The message would be displayed on my "return_url" page

#

This is also where the notification banner is

cobalt owl
#

They wouldn't be redirected to your return_url unless they hit the back button. Closing the page doesn't result in a redirect.

#

The best thing you could do here is retrieve the Account object and inspect the requirements hash for past_due or currently_due requirements and then specify a message like, "Your account has outstanding requirements, please update" and give them a button that creates a new Account LInk

icy sonnet
#

Sounds good! I'll give this a try and see if that works.

Thanks for your help on this!