#joakim5983

1 messages · Page 1 of 1 (latest)

prime sorrelBOT
timber wolf
#

You should probably subscribe to payment_intent.succeeded but up to you depending on what data you need

#

Can you share the event id that wasn't delivered?

unreal pilot
#

Event ID: evt_1OXPp6AT2irRycsWRtGemneS

Webhook ID: we_1O9oZWAT2irRycsW1lAieNgA

Do you know what the actual difference is by subscribing to payment_intent.succeeded and checkout.session.completed

timber wolf
#

Different objects are sent

#

payment intent in the first one

#

checkout session object in the latter

#

Your endpoint responded with a 200 for that event id

frosty heart
#

but there's nothing in the webhook page in stripe that shows any webhooks were sent for either payment intent or checkout sessions completed

#

i'm a colleague of @unreal pilot

timber wolf
#

Ah it was sent to cli endpoints

#

Checking again

frosty heart
#

does running the stripe cli listener intercept expected webhooks?

timber wolf
#

No

frosty heart
#

ok

timber wolf
#

Oh we_1O9oZWAT2irRycsW1lAieNgA is a connect endpoint

frosty heart
#

thanks

timber wolf
#

That's why

#

It's not a connect event

#

It's an event on your platform account

frosty heart
#

ah

#

thanks, have spotted our Stripe WebhookEndpointCreateOptions object has Connect set to true

timber wolf
#

No problem

unreal pilot
#

Regarding the difference between payment_intent.succeeded and checkout.session.completed.

These only differ in the data we get back?

In this scenario, we get what we need in the metadata from both events.

And we only care about the payment being succeeded / card being charged with the specified amount.

So i guess we ourselves can choose what to subscribe to?

timber wolf
#

yes

#

Yeah either should work

#

Especially if you only process card payments

#

Some async payment methods succeed much later

#

For those pm's you'll get checkout_session.completed way before payment succeeds