jd_webhooks | Stripe Developers | Page 1

elfin wolfBOT May 28, 2026, 2:11 PM

#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

jd_best-practices, 2 days ago, 7 messages

#

wraith lodge May 28, 2026, 2:16 PM

#

More context:

Im working on implementing something like this, where our app is aligned to the account status shown in the dashboard to show if the connected account is ready to accept donations..

https://docs.stripe.com/connect/dashboard/review-actionable-accounts

wintry nymph May 28, 2026, 2:19 PM

#

Hello
Can you share the example event IDs for the events you're seeing? evt_xxx

wraith lodge May 28, 2026, 2:23 PM

#

I recently notice I got v2 events, when in previous days when I was still implementing it, I got v1 events and also in my stripe cli when I am testing, it is v1 events.

Im confused right now actually hehe.

#

wintry nymph May 28, 2026, 2:26 PM

#

Can you share those IDs in text?

wraith lodge May 28, 2026, 2:33 PM

#

Sorry, I was confused earlier. I now realize that stripe listen CLI was sending V1 events, but the Stripe Dashboard sends V2 events for our platform version.

I was testing and implementing around the CLI behavior and didn't realize production/dashboard-triggered events were using a different payload format.

So my current implementation was originally built around V1 webhooks, but our actual platform events appear to be V2.

My questions now are:

What determines whether Stripe sends V1 vs V2 webhook events?
Is it based on the webhook endpoint API version, the Connect application/platform settings, or the source of the account change?

Should we support both V1 and V2 events in the same webhook endpoint, or is it recommended to stay consistent with only one event version?

#

Sorry, just to add more context:

I implemented my webhook handling and account status updates around the V1 event format because that’s what I was seeing when testing locally with stripe listen. In that setup, everything worked well.

But when I tested status changes for connected accounts through the Stripe Dashboard, I started seeing issues because the Dashboard-triggered events appear to emit a different V2 payload structure than the CLI events.

So I think I may need to rework the implementation around V2 events, or possibly support both V1 and V2 in the same webhook endpoint.

Could you confirm which approach you recommend for our case: standardizing on V2 only, or supporting both V1 and V2 webhook payloads?

wintry nymph May 28, 2026, 2:39 PM

#

Have you looked at this doc yet? - https://docs.stripe.com/connect/webhooks
If not, I'd recommend reading through that because it explains this in detail.

#jd_webhooks