#DeputyCheese-webhook
meager ermine
Hi! I'm not familiar with Docker. However you can listen to webhook events locally by using the Stripe CLI as explained here: https://stripe.com/docs/stripe-cli/webhooks
gray sedge
Yes that's what I am doing
I am getting the pi created event for example
But not those deferred ones
meager ermine
Got it! Can you see these events in the Stripe dashboard? If so, can you share their event ID (evt_xxx)?
gray sedge
Where exactly do I see the event? My last test was this one https://dashboard.stripe.com/test/payments/pi_3KRv5sClDK2O5WMj16DK875Q
Ah got it, those are at the bottom
I received the event at 10:07
But not the deferred one at 10:10
meager ermine
Thanks! Give me a few minutes to look into this.
gray sedge
Thanks
meager ermine
For pi_3KRv5sClDK2O5WMj16DK875Q, I confirm that you received payment_intent.created but not payment_intent.succeeded.
Can you paste the command you are using to forward events with the Stripe CLI?
gray sedge
I am using a docker-compose.yml for this
command: listen --api-key ${STRIPE_SECRET_KEY} --skip-verify --forward-to https://[placeholder for the domain]/stripe-hooks
I think I maybe have to trigger those asynchronous events by myself here somehow
meager ermine
The command looks correct! Please give me a few more minutes to investigate this.
And can you confirm that your server and the Stripe CLI were still running when the event happened?
gray sedge
I've got it
I indeed have to call the async triggers by myself
there's a "stripe trigger payment_intent.succeeded" command for example, that worked for me now
meager ermine
Yes you can manually trigger all events for testing purposes with the CLI.
However I don't understand why you didn't receive the payment_intent.succeeded. My only guess is that at the time when the event was sent, the Stripe CLI was no longer running. So the event wasn't forwarded to you locally.
gray sedge
I can make a new SOFORT payment to test, give me a second. I think I didn't receive it because I have to send that event by myself locally?
Here's the new payment intent: https://dashboard.stripe.com/test/payments/pi_3KRvkiClDK2O5WMj0TbFXAgu
Currently it's not succeeded yet
stripe cli is running
I received payment_intent.requires_action and payment_intent.created
meager ermine
Yes, I can see that. So far so good!
meager ermine
That's not normal. I just tried to reproduce on my end (without Docker), and I see in my CLI logs:
2022-02-11 10:52:36 --> payment_intent.created
2022-02-11 10:55:51 --> payment_intent.succeeded
And ì can see the event payment_intent.succeeded in your dashboard.
gray sedge
Yes that's what I see in the dashboard too
meager ermine
So I still think your CLI stopped forwarding events for some reason.
gray sedge
Okay, let me try one thing
Maybe I have to run the listen command inside the docker image again
Nope that didn't work too
And if I'm triggering it manually I always get a new transaction inside the dashboard with 20$, I have no clue where that comes from
meager ermine
That's odd that you are getting one event but not the other.
Could you try to contact Stripe Support directly here: https://support.stripe.com/?contact=true
Make sure to include the relevant IDs (payment intent and events), and share the Stripe CLI command.
gray sedge
Okay will do