#nJoy
hoary slate
stoic frost
Are you getting the same event ID twice? Or are you getting different events?
light tartan
I can't find an event id in the return from the stripe cli
That's the first thing I looked for. I see the invoice Id I believe as the id of the webhook
"id": "in_1MgAbtE7ebVHEdGCQ3n3p6mU",
stoic frost
As far as I can see we're only generating a single webhook event for that Invoice - can you clarify what you mean by "picking up the event twice"?
ARe you listening for the event from multiple webhook endpoints maybe?
light tartan
We're not. It's going through one endpoint and one method. Do any of the fixtures I printed out above call invoice.paid? Because I don't see it even in the list above. I see stripe triger invoice.paid and then a few other fixtures.
stoic frost
The fixtures don't "call" specific events at all - the fixtures are just making API requests that will result in certain events being triggered
Since you made the command stripe trigger invoice.paid that will make a series of calls that will result in the invoice.paid event being generated
light tartan
Ah got it. Thank you for that clarification.
This may then be an internal PHP framework issue with how we are extending laravel cashier. I'll look into that.
stoic frost
Something that may be a factor here is that your account is "connected" to itself in test mode and as a result the invoice.paid webhook event is being sent to two of your webhook endpoints (both your account webhook endpoint and your connect webhook endpoint)
light tartan
that must be the issue.
Thank you for noticing that. So we should disconnect it then? How would we do that?
Because we are definitley receiving it twice. I just debugged that.
stoic frost
You'll want to revoke access through the dashboard settings (https://support.stripe.com/questions/disconnect-your-stripe-account-from-a-connected-third-party-platform)
light tartan
Just to be sure, is it the one under connect extensions that i revoke access to?
stoic frost
Yeah it'll be under Connect Extensions - but I also do want to warn you that if you have other parts of your integration that are for some reason relying on this connection then those will immediatley break
it's a bit more okay since this is a test mode connection, but there is still some risk involved
light tartan
Yes, understand. Since it says TestMode next to it: this only exists in test mode, not production, right?
stoic frost
yup!