#devops_webhooks
narrow robinBOT
👋 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/1412965122418409572
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
dull verge
hello, give me a moment to take a look
Could you share the connected account ID that was impacted?
winter garnet
acct_1Rkro4Rh6F4BcJAO
dull verge
thanks, taking a look
sorry, could you clarify what you meant by the account being disabled? acct_1Rkro4Rh6F4BcJAO looks like its active to me
but there are three account.updated events on this connected account, and it looks like the payout schedule changed
winter garnet
"requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": null,
"errors": [],
"eventually_due": [
"person_1RksRLRh6F4BcJAOtYW1kJbz.id_number"
],
"past_due": [],
"pending_verification": []
},
this was in event with id 20fdacb1-82bc-543c-145a-ddec5168eb4e
this event happened on July 14th
since then, we were under the assumption everything was fine with the account. but the ssn was still missing
this morning, the customer told us he didn't receive his payout. we went to his connected account and saw it was restricted because his ssn was missing
our customer support worked with him to resolve it, and to change the payout schedule to deal with this issue, so now its fine
but we want to know when a connected account gets disabled before the customer having to tell us
does that make sense?
dull verge
I see, thanks for the context. I think I found the event you might be looking for
evt_1S3GGhRh6F4BcJAOp31MzUx2 (capability.updated)
winter garnet
this event looks like it was emitted after the customer supplied his ssn, no?
looking at the event, disabled_reason is null. also, previous attributes has this:
"previous_attributes": {
"requirements": {
"eventually_due": [
"person_1RksRLRh6F4BcJAOtYW1kJbz.id_number"
]
}
}
which I believe means this missing requirement was resolved beofre this event was emitted
dull verge
Hmm sorry, you are right. Please ignore evt_1S3GGhRh6F4BcJAOp31MzUx2
Based on our internal logs, the connected account's capability payout capability was disabled on 2025-07-14 19:12:59 UTC due to the pending requirement. But because this is more than 30 days ago I won't be able to locate the event for this.
Generally though, listening to the account.updated event is the correct approach to handle account status changes: https://docs.stripe.com/connect/handle-verification-updates#listen-for-account-changes After a connected account goes through onboarding, you would want inspect the currently_due and pending_verification lists in the account’s requirements hash.