matt-k_webhooks

[ancient plover]

👋 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/1428823855975366749

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[vestal geode]

You should listen for account.updated events on a connect webhook endpoint: https://docs.stripe.com/connect/webhooks

The requirements hash is what you wanna examine to see if there's outstanding requirements still

As well as the charges_enabled and payotus_enabled fields

There's not really 1 field to look at

[viral portal]

Thanks! Can you say more about the requirements hash?

[vestal geode]

It's documented here: https://docs.stripe.com/api/accounts/object#account_object-requirements

[viral portal]

TY!

Is there documentation about some of the strings, such as requirements.errors.reason

Or I guess what I'm really asking, are these strings reasonable and safe to expose to users, or is best practice to keep them internal?

[vestal geode]

Oh we don't surface all possible values

[vestal geode]

Good question and i'm not sure

I recommend asking the support team

Idk if there's a scenario where you wouldn't want to expose a reason