#nicolas_connect-requirements
tawdry spireBOT
đ 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/1301227858810765336
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
shy fern
Hello! Can you provide more information? What type of connected account? What kind of charges? What are the specific restrictions?
devout obsidian
Hello! A custom connected account. Not charges, payouts at all
It says payout disabled and I don't find a way to enable those again.
shy fern
You should be able to use the test data here to get the account into a different state: https://docs.stripe.com/connect/testing
devout obsidian
Yes I saw that but where should I go to update that connected account info?
shy fern
Typically for Custom accounts you update it via the API.
devout obsidian
Would you be able to help me identifying the endpoint and what should I send to update that?
shy fern
It would either be the Account update endpoint: https://docs.stripe.com/api/accounts/update
Or the Person update endpoint if you need to update a specific Person on the connected account: https://docs.stripe.com/api/persons/update
As for what to send, that's up to you. I can't write code for you or anything like that. You need to use the documentation to figure out what you need to send to get into the state you want.
devout obsidian
Would you be able to send me a curl example? I just want to remove that restriction and enable payouts again for that connected account
acct_1K1WeoQssaiKvpDe
Thats the connected account id
shy fern
No, sorry. Again, we can't write your code or make your requests for you.
devout obsidian
Ok forget about teh piece of code. Which property related to the PUT endpoint of a connected account is the one I should update in order to remove that restriction
?
shy fern
There probably isn't a single property, you need to provide the information specified in the outstanding requirements of the connected account in question: https://docs.stripe.com/api/accounts/object#account_object-requirements
devout obsidian
Okay but that's the get endpint. I'm not seeing based on the PUT endpint a parameter that allows me to modify the requirements object
shy fern
Right, you first need to get the Account and look at the requirements, then you would make a POST request to update it with said requirements. Note there are no PUT requests in the Stripe API.
devout obsidian
"requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": "other",
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": []
},
That's how the requirements object is for the connected account in discussion
shy fern
Can you give me that account's ID so I can take a look?
tawdry spireBOT
devout obsidian
Thanks!!
frosty cosmos
okay so this one is quite subtle so bear with me.
The account is disabled for internal risk decisions made by Stripe which is why Payouts are disabled.
For years, when this would happen internally we would not show payout_enabled: false so platforms thought everything was fine but the connected account wouldn't get their funds. It was super confusing and we literally fixed this just last week to properly reflect payouts_enabled: false which is what you see.
Now, while it's nice to have this, it is super confusing to have nothing in requirements explaining what the issue is. We are also working on this feature and we reached out to a lot of platforms about this upcoming change. We are going to surface "risk-related requirements" in the API soon and there is a "preview" that you can opt into
We have https://support.stripe.com/questions/get-risk-related-requirements-for-connected-accounts-via-api that goes over the changes and it links to our public docs https://docs.stripe.com/connect/handling-api-verification#handle-risk-verifications with more details
devout obsidian
Okay I saw that payout_enabled
Thanks for the information.
In my case particular I was refering to the TEST account not LIVE mode
So I though it was easy to modigy that in a TEST account
frosty cosmos
modify what? Sorry I'm confused. You asked why Payouts are disabled and I explained exactly what is causing this.
devout obsidian
Yes I agree. My question was if there was an endpoint or something I can call for test environment to update that connected account and enable payouts again
frosty cosmos
gotcha, there isn't in that case you'll need to create a new account or reach out to support in that case. Sorry for the delay
frosty cosmos
sure thing!