#john-l_stripe-cli-connect-vs-account-webhooks
drifting ruinBOT
👋 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/1359655110552195264
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
lofty snow
Hi! You mean through stripe-cli, ya? It looks like you have Stripe CLI listening for both Account and Connect events, so you're getting both - one via the Account webhook endpoint which has no user_id, and one via the Connect webhook endpoint which does have a user_id.
You also seem to have connected your Platform to itself, which is why both of these types are coming in for your Stripe Account. You'll want to disconnect that as it can cause weird issues.
wild leaf
oh ...thanks... Is that a stripe cli option?
lofty snow
You likely want only the former, but also definitely disconnect your account from itself and create a new separate test account to test Connect with.
wild leaf
got it ... I've been using : stripe listen --skip-verify --forward-to https://app.jerseywatch.localhost/webhooks/stripe/connect\?api_version\=2020-08-27
lofty snow
Yup, that's forwarding non-Connect events to your URL; you likely want --forward-connect-to in this case.
wild leaf
thanks! ...that's been causing all sorts of confusion
lofty snow
You're very welcome - glad I got you moving forward again! 🙂