#aabycereno
old tapir
hi there!
steep hare
hello
old tapir
which webhook endpoint are you listening to?
old tapir
can you share the Event ID (evt_xxx)?
old tapir
this was created by a Checkout Session, so I recommend listening to checkout.session.completed instead
steep hare
ok i will try. but what is the difference with payment_intent.succeeded? and would it still work if the payment is for a subscription?
old tapir
what is your end goal exactly? be notified when the Subscription is created, or when a recurring payment happened?
slate lionBOT
steep hare
i just want to know who completed their payment, since ehere are single payments, and there are recurring payments.
its kinda complicated based on what my client wants, he also wants to only charge the customer when they wanted the service on a specific date.
so im thinking of starting with getting the names of whoever paid, as a start.
acoustic galleon
If you're using custom_fields with Checkout they're only set on cs_xxx objects and related checkout.session.* events. You won't see them on payment_intent.* events
steep hare
yeah, so what is the difference between payment_intent and checkout.session? sorry, i just wanna understand it a bit more.
acoustic galleon
Well they're different API objects. A Checkout Session is a prebuilt UI to collect payments, but utilises Payment Intents under the hood
A Payment Intent is a lower level API object/primitive that handle the payment state
steep hare
oh ok, so basically a checkout gets more info.
thank you! might be back soon though 🙂
acoustic galleon
Yes, Checkout in a full fledged checkout UI/page that supports address collection, coupons, etc. A Payment Intent doesn't support those additional features, it just enables payments in non-Checkout flows
steep hare
yeah, i got so confused at first because im seeing a key "customer" : null,