#nukesforbreakfast_api
1 messages ¡ Page 1 of 1 (latest)
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.
- nukesforbreakfast_docs, 3 days ago, 16 messages
- nukesforbreakfast_docs, 5 days ago, 36 messages
- rc_account-country, 6 days ago, 8 messages
đ 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/1239411347570163772
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
connected account ID acct_1PEGWrPctytVkKwP
In https://dashboard.stripe.com/test/logs/req_XhfoZppD1PtaaR, the controller.requirement_collection is set to Stripe, so the information should be collected from Stripe. Since there is no Dashboard, embedded component should be used to collect the relevant information: https://docs.stripe.com/connect/get-started-connect-embedded-components
so is support_address not an updatable value when controller.requirement_collection is Stripe?
Yes, after the connected account has been onboarded
ok
so that is only editable by the account owner via stripe embedded components.
is there a document that lists what fields become uneditable when controller.requirement_collection equals stripe after onboarding?
Except for capabilities, not much fields can be updated after onboarding. Could you share what you would like to achieve?
well, I was kind of expecting to be able to update the support info if the user changed their plan from DIY to fully managed. As, in that case, the support info would go from being their info to being our info (address, email, phone).
But I have no desire to take full responsibility for collecting all the verification info Stripe needs. I'd rather let the embedded components do that.
Hi @mellow valley I'm taking over this thread. let me know if you have any follow-up questions.
hello @patent condor, I responded to this question:
Could you share what you would like to achieve?
is what I want to achieve not possible when using stripe as the information collector via embedded components?
I believe river has already answered this question, you should use embedded component since controller.requirement_collection is set to Stripe
right, but what if I want to change the support info on behalf of the customer?
Then you should set controller.requirement_collection to application
does that still work with embedded components or no?
Yes you can use embedded component.