#qmathe
1 messages ยท Page 1 of 1 (latest)
To be clear, is our hosted onboarding page appearing differently based on which hash the individual.verification.document requirement shows up in?
I haven't tried it, that's what I'd like to know.
Is it possible to force a requirement to move from eventually_due to currently/past_due in test mode?
๐ stepping in
So you can use these trigger cards to trigger requirements: https://stripe.com/docs/connect/testing#trigger-cards
When you create your account link what do you set for collect?
Are you setting eventually_due ? See: https://stripe.com/docs/api/account_links/create#create_account_link-collect
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I'm not setting anything for collect. If I understand correctly, by setting it to eventually_due, then the onboarding form should request proactively what is listed inside eventually_due, right?
Thanks for the trigger cards, I didn't know about them, I'm going to investigate these.
Yep that's correct
ok, thanks a lot! This was really helpful.
I got another related question. I have observed that I received Stripe Connect webhook events during the onboarding. My plan is to use them to notify my users about what is needed. However I'd like to avoid notifying my users when they are still inside the form and filling it. Is there a way to do this?
From what I see, once the user enters in the page to declare an external account, account.updated events starts to be sent.
I'm sending push notifs to an iOS app.
Hmmm
You could check details_submitted for that... that property is mostly used for Standard Connected Accounts but should apply here too for any accounts within the onboarding flow. The issue though is if they leave the onboarding flow and don't complete it then that would stay false...
I think you are best off just using a certain timeframe that you allow for your users to complete the flow from when it starts before you start sending notifications.
I'll check details_submitted but giving a timeframe to complete the form sounds like the most reasonable approach. I was thinking that may be there was a standard way to do this.
Yeah I'm drawing a blank though seems like there should be a way to know. Let me check with some colleagues
ok, great, I'm going to stick around then.
Alright @wet panther my colleagues agree that a timeframe is going to be best here. There isn't really a smoother way at the moment.