#leahhannahceramics
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- leah-customconnect-embeddedcomponents, 2 days ago, 19 messages
- leahhannahceramics, 3 days ago, 15 messages
Hi 👋
I am reviewing the docs for Connect embedded components and I don't see any parameters where you could specify you wish to collect all eventually_due requirements.
Also, it should be noted, that not all requirements will be populated immediately as the account is created
Thanks for getting back to me.
Can the Account Link API be used when working with the Connect embedded components?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
No, I don't think so. The account link performs a full redirect to a Stripe hosted interface.
Got it! Thanks for confirming.
Would you happen to know what logic is used to determine what requirements are collected upfront when using the Account Onboarding Connect embedded components?
Only currently_due requirements?
Wait a sec, I see that we support collecting eventually_due in this doc: https://stripe.com/docs/connect/supported-embedded-components#requirements-collection-options
Oh, it looks like you specify that on the front-end in this scenario
Look at the table of parameters in this section: https://stripe.com/docs/connect/supported-embedded-components#integrate-the-account-onboarding-component