#lilvaris1dgomillionpose_connect-webhook-monitoring

1 messages · Page 1 of 1 (latest)

sullen juncoBOT
#

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

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

shy acorn
#

Hello 👋

You are already monitoring account.updated and that is the recommended event to watch for. Specifically, you should be paying attention to the requirements property on the Account object. This will get updated with new requirements that must be fulfilled in order to keep the account in good standing.

ancient haven
#

Thanks — that helps.

Right now I’m monitoring:

  • account.updated
  • currently_due / eventually_due / past_due
  • charges_enabled
  • payouts_enabled
  • disabled_reason

I’m building a creator tipping/social platform using Stripe Connect Express and want to understand the safest compliance flow for creators receiving funds.

Questions:

  1. When requirements become due after onboarding, should platforms:
  • pause payouts only
  • pause incoming tips
  • allow balances but block withdrawals
  • fully restrict accounts until resolved?
  1. What verification states are considered safe before allowing:
  • receiving tips
  • holding balances
  • instant payouts
  • normal payouts
  1. Which disabled_reason values should trigger:
  • payout freezes
  • monetization restrictions
  • manual review
  • full account disablement
  1. What best practices reduce post-onboarding restrictions for creator/social platforms?
    Examples:
  • delaying monetization until verification completes
  • limiting transaction volume for new creators
  • collecting more profile info before onboarding
  • fraud/risk scoring
  • reserve periods

  1. How should platforms handle onboarding-complete accounts with eventually_due requirements still pending?

  2. Besides account.updated, are there recommended webhooks/events for detecting fraud risk, capability loss, verification failures, or payout reviews?

  3. What common mistakes cause Express accounts to become restricted after initially appearing active?

I’m trying to minimize creator frustration while following Stripe risk/compliance best practices from the beginning.

shy acorn
#

For other webhooks to monitor, I recommend reviewing our guide for Connect webhooks here: https://docs.stripe.com/connect/webhooks

For the rest, these are not questions I can answer as they are mostly legal/compliance questions. We specialize in helping developers code integrations with Stripe APIs and that is our focus. If you wish to discuss the potential reasons for Connected accounts becoming disabled, I recommend you reach out to our Support team here: https://support.stripe.com/contact