#jussch_connect-components-notification
stable vaporBOT
👋 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/1271513395346149391
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
cursive hollyBOT
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.
- jussch_best-practices, 6 days ago, 15 messages
civic turtle
Do you have an example Account ID I can look at to verify? If you're passing eventually_due and futureRequirements: 'include', then it should show future requirements
stable vaporBOT
civic turtle
Do you have a screenshot of the banner they're seeing? I would expect to see a call to action for adding an additional verification document, since that's the only future requirement on the account
sturdy rapids
Altough this is in my embedded component for account management. And then it tells me to upload id
But not in the notification banner component.
surreal pine
Hi 👋
I'm stepping in as my colleague needs to go soon. GIve me a minute to catch up
Okay, I've run into this issue with the Notification banner as well. It can be very particular about when it will render.
What happens if you remove the futureRequirements: 'include', parameter?
sturdy rapids
Thank you so much that worked :)
Also is there any possibility to show the connected account it's payment method settings in the express dashboard? I tried using the standard account with the full dashboard (the payment methods were there) but the user could do everything like creating payment links, customers, ... which he should not do (can i disable that?). Any solution to this? I am already on the waitlist for the payment method settings component.
surreal pine
I am already on the waitlist for the payment method settings component.
In that case, you have done everything I could recommend
sturdy rapids
So you can't see a way how to disable functions on the standard dashboard for connected accounts so that it is minimal?
surreal pine
You can either have full control of the payment method settings for the account, in which case they cannot see that page in their account settings, or they have full control. There isn't a middle ground
sturdy rapids
Ok, last question, how would I require payment methods for the express connected account? I tried through the dashboard and the api but it seems they have to enable it somehow no? With the last question i meant if it was possible to make the normal dashboard for standard accounts customized so that payment links are disabled.
surreal pine
I'm not sure about the Dashboard but for the API you use the capabilities parameter to request access to payment method types: https://docs.stripe.com/api/accounts/update#update_account-capabilities
Requesting new capabilities may cause new requirements for the connected accounts though, so you may need to collect more information from them in order to get these enabled.
sturdy rapids
Ok, thank you! Have a nice day :D
surreal pine
You too 👋