#vincent_api
midnight frigateBOT
đ 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/1349176870159126590
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- vincent_api, 38 minutes ago, 13 messages
hidden tiger
Do you collect and set business information at the time when connected account is created?
chrome jackal
We have the information on hand, so we could definitely prefill it for them. However, we would still want to be sure they can't change it once they are on the form
hidden tiger
When the business information such as legal business name (https://docs.stripe.com/api/accounts/create#create_account-company-name) is prefilled in the API, the embedded connect component will still show editable business name field. Making this field uneditable is not supported on the onboarding component.
The only way is to complete the onboarding using your own form instead of Stripe hosted/embedded onboarding
chrome jackal
Ah drat, oh well.
Does the embedded component expose any custom validation to plug into?
Otherwise, it sounds like our best option is to listen for the account.updated webhook and raise a warning if their entity name does not align with our records
hidden tiger
Does the embedded component expose any custom validation to plug into?
This is not supported as well.
So yes - the best here is to raise a warning if the entity name doesn't align with your records via account.updated event
chrome jackal
Got it, thanks!
Apologies in advance for how general this question may be, but are there any other Connect Account strategies we could use to have more control over the entity name while still enabling our merchants to complete the rest of onboarding without our intevention?
hidden tiger
Don't be sorry! We are here to help with technical questions when integrating with Stripe.
are there any other Connect Account strategies we could use to have more control over the entity name while still enabling our merchants to complete the rest of onboarding without our intevention?
Currently, the field validation logic in embedded/hosted onboarding is maintained by Stripe, and custom validation, or disabling a certain field isn't supported. Stripe hosted/embedded onboarding is meant for the merchants to collect the requirements as easily as possible, and the validation logic is abstracted away from the integration.
For custom logic, the only way is to use direct API integration that submitted the onboarding information via API with the details collected in your website.
chrome jackal
Thank you very much! If I understand correctly, we can programatically make corrections to the entity name after the merchant completes onboarding, if needed?
hidden tiger
That's possible. When the company name is changed, there might be a possibility that the connected account will need to complete the new requirements
chrome jackal
Ok got it, thanks again for the help!