#calebr
1 messages · Page 1 of 1 (latest)
We don't recommend testing anything in live mode
You can simulate future requirements by doing this: https://stripe.com/docs/connect/custom/handle-verification-updates#test-updated-onboarding
Oh, that's new
Last time I checked here there was no way to do that. I'll look into it, thanks.
Ah sorry looks like that just moves future requirements into requirements
Let me see if there's a way to just test future requirements being populated
Thanks, that's the problem here—we're trying to figure out how to collect future requirements through the onboarding flow now (as recommended by Stripe) to avoid an interruption in payouts and confusion for our clients.
Ok so my colleague recommended you use a test account and look for some requirement on https://stripe.com/docs/connect/required-verification-information that is required before some point in the future (not first charge) like one of the time/volume requirements and request it (like tax_reporting_us_1099_k for example).
That will cause future requirements to be populated
Ok, the doc you linked doesn't actually specify how to do that that I can see
Specify how to do what?
That doc just helps you see requirements
I specified in my message
Which part are you confused about?
I'm not sure how to request a requirement for a test account?
Same way you'd do it for live too: https://stripe.com/docs/api/accounts/create#create_account-capabilities
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Oh, you mean requesting a capability. The way you phrased it sounded like adding an arbitrary requirement was possible
Ah sorry
I will see if that works
Basically just choose a capability that needs to be verified before some time/volume requirement
Okay, that works for populating future requirements. I think we must be on an outdated version of the connect components, because the setCollectionOptions function isn't working. Is there a CDN version of the JS library? Our project doesn't use NPM.
Never mind, just found that in the docs
Okay, looks like all of that works. I think the issue is resolved. Thanks for your help!
No problem. Happy to help