#umaritis_code

1 messages · Page 1 of 1 (latest)

sudden ploverBOT
#

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

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

halcyon orbit
#

👋 Hi there!

broken tendon
#

hello,
API-based detection:
Is there an API or endpoint that allows us to check, against a list of Stripe Connect account IDs, which accounts currently have payouts disabled or paused, and the exact reason why? Our goal is to programmatically identify affected accounts so we can notify them automatically.

Webhook notifications:
Is there a webhook event that we can subscribe to which triggers whenever payouts are disabled or paused for a connected account? Ideally, we would like to receive real-time notifications so we can immediately send an automated email to the affected user explaining the cause and next steps, along with a remediation link.

Best practices:
Are there any recommended best practices for monitoring payout status changes for connected accounts and handling these cases programmatically?

halcyon orbit
broken tendon
#

When the account.updated webhook is triggered, what fields should we specifically check to determine that payouts have been paused or disabled?
Is there a reliable way to retrieve the exact reason payouts were disabled (such as missing verification requirements, compliance issues, etc.) so we can include that information in the automated email sent to the user?
can you let me know the exact events which we should listen in the case?

halcyon orbit
#

There's an example in that link there, where you can see which requirements are currently due for the connected account

broken tendon
#

Okay just read this.

The documentation at https://docs.stripe.com/connect/handling-api-verification?accounts-namespace=v1#determine-if-verification-is-needed talks about the different fields that we can look at however we don't know enumerated possible values for these fields. For example, in the errors field, the documentation tells us we can have:
{
"requirement": "company.verification.document",
"reason": "The company name on the account couldn't be verified. Either update your business name or upload a document containing the business name.",
"code": "failed_name_match"
}, However, is there any documentation that provides a complete list of possible errors? A complete list of possible requirements.currently_due? And so on?

  1. How can we programatically generate remediation links to send?
  2. How can we know against a bulk of connect account ids, which ones have payouts paused / disabled? Is there an api for that?
Handle verification with the API

Learn how Connect platforms can use webhooks and the API to handle verification of connected accounts.

halcyon orbit
#
  1. I'm not sure if we have a full list of errors, since there can potentially be new ones added, but there is a human-readable string there. The requirements typically map to properties on the Account object, e.g. company.phone would be the company.phone attribute.
  2. You can generate a URL using the Account Links API: https://docs.stripe.com/connect/handle-verification-updates?accounts-namespace=v1#send-accounts-to-collection-flow
  3. When listing Connected Accounts, you can check the payouts_enabled attribute: https://docs.stripe.com/api/accounts/object#account_object-payouts_enabled
The Account object | Stripe API Reference
broken tendon
#

We are going to try this approach. Thank you for your time

halcyon orbit
#

You're welcome!