#chris-vr_webhooks

1 messages · Page 1 of 1 (latest)

faint veldtBOT
#

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

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

potent scarab
#

Hello 👋

Can you share the ID for the webhook event where you saw this?

#

I am looking at the Connected Account as well and I don't see any requirements listed. It may be out of date so I want to check the logs for the webhook event.

slender depot
#

hey

#

sure give me a second

#

evt_1TT3hgQeFtLTgeyLpkCXobb0

potent scarab
#

Thanks, taking a look now

#

I see what you mean but also this event was from 4 days ago. Let me check the details of this account to see if there was any updates between now and then.

#

I see a number of capabilities that went inactive on 5/3 but then went back to pending on 5/4 as a result of a new verification document being provided.

#

BTW It seems like your webhook endpoint is not successfully receiving these events. I see 7 failed deliveries for this event.

faint veldtBOT
slender depot
#

hmm

#

let me take a look at the failure

#

found the issue with the failures

#

so in conclussion there is no issue with pending verifiacation, is just the same webhook being resent by stripe because of the failure?

bold monolith
#

Hi there, taking over for @potent scarab as they had to step away

#

My understanding is that yes, the event you were initially looking at was outdated information