#wdrisco

1 messages · Page 1 of 1 (latest)

worn parrotBOT
slow sluice
#

Hmm, unclear from the screenshot what is required here and we're not collecting?

warm wyvern
#

So the issue is that Stripe allows the user to agree and submit and return to our web application, when there is missing required information on your end, so the connect account is not setup and enabled to allow charges

#

the information that's missing is kind of irrelevant, but we've tried with missing DOB, missing business address, etc.

#

I'm not sure if this is just the case in test mode to allow us to complete your connect onboarding for testing?

#

Question 2 of 2 - We're using the connect onboaring as part of our own onboarding flow. Upon returning to our web application, the connect account complete webhook is taking sometimes up to 2 minutes to fire. This leaves our users in limbo on our page whilst we wait for the webhook response. This is in test mode. Do you have any recommendations on how to handle this? Ideally we would like a response from Stripe that the stripe onboarding is completed but awaiting your verification or similar

#

Thank you!

slow sluice
slow sluice
warm wyvern
#

I can run through and test one now, what can I share with you after, is it an event ID or something?

slow sluice
#

Please! evt_xxx

warm wyvern
#

yes we're using account.updated

#

"evt_1ORZlX4DEut9Sm2xIrRyZ4cp"

#

That was the one I used when testing most recently

#

most cases we're waiting up to 30 seconds it seems for the webhook

#

we actually received 6 webhook events for this account setup, the one above being the last. This one was the first.
"evt_1ORZjJ4DEut9Sm2xPuBQp826"

#

this one was when the account went to charges "pending"
"evt_1ORZjn4DEut9Sm2xjl2YJasN"

#

then its a 1:50 gap

slow sluice
warm wyvern
#

I think the above events will hopefully add some clarification

slow sluice
warm wyvern
#

I would assume this was when the onboarding was completed - evt_1ORZjn4DEut9Sm2xjl2YJasN

#

and then it was almost 2 mins before we received charges enabled webhook

#

so in that period we don't know if the user has
a. Not completed everything and it's really pending (see other question about limiting this)
b. Waiting on Stripe

slow sluice
#

Which data are you using to onboard test accounts?

warm wyvern
#

just random data to be honest, and test data where it seems to be required - 0000.... etc for phone numbers, etc

slow sluice
#

That's likely the issue here. If you're not using our test data (https://stripe.com/docs/connect/testing) then you're likely triggering an actual verification flow, which is async and can take time

If you use the test data then onboarding results should be immediate and the webhook events should reflect that

Testing Stripe Connect

Before going live, test your Connect integration for account creation, identity verification, and payouts.

#

Obviously it will differ in live mode where we'll need to actually verify your users, so your integration will need to account for potential delays. It won't always be immediate

warm wyvern
#

okay, so I guess the question is how to differentiate from Stripe response when the application has been completed, and when it's being verified?

slow sluice
#

Perhaps you display a different UI advising them to return later and then send an email once you've received the account.updated event to advise account is active

warm wyvern
#

That's true

slow sluice
warm wyvern
#

evt_1ORZjn4DEut9Sm2xjl2YJasN - in this one, where the charges were pending, I guess that would suggest its in verification state and all completed?

slow sluice
#

There's fields on the Account object that denote status, mostly charges_enabled, payouts_enabled

warm wyvern
#

yeah those are the ones I meant above

#

sorry these in fact

slow sluice
#

Yeah that looks to be 'pending' still but there's no requirements due to we have everything we need right now to verify the account (see requirements[pending_verification] hash)

warm wyvern
#

okay gotcha, I think we have all the info we need from here, and I'll have a read of that link. Thanks very much for your help here.

#

Would appreciate your response about the second question when you hear back

slow sluice
#

Yep, still waiting for a reply from a colleague

#

You can't configure the form to validate for required fields, but unsure if it behaves differently in live mode. Should be easy enough to test assuming your account is enabled