#lobsterpizza18
nova geyser
silent spade
Yeah charge.succeeded is not really the relevant event here
dense sentinel
but why is it triggered during subscription flow
silent spade
The recommendation generally is to listen for checkout.session.completed events. However the payment_intent_data.metadata won't be available on that object/event, instead you'll want payment_intent.succeeded there
silent spade
but why is it triggered during subscription flow
Because there was a successful Charge, sure
But the fields/parameters you're setting aren't passed to the underlying Charge object
dense sentinel
Because there was a successful Charge, sure
oh does it mean it will be triggered for both flows and its ok ?
silent spade
Yes whenever there is an actual payment, be that one-time or recurring, charge.succeeded will fire
dense sentinel
thanks for helping. just trying to understand which event I can listen for one time payments and subscription ones where i can access metadata
silent spade
mode: 'payment' -> payment_intent.succeeded
mode: 'subscription' -> customer.subscription.created
dense sentinel
I've used charge.succeded for one time payments to update my SaaS backend and allow user to access it. wonder if its the correct event and what to use for subscriptions. really need that metadata 😦
dense sentinel
`mode: 'payment'` -> `payment_intent.succeeded`
`mode: 'subscription'` -> `custo...
ok great, let me check!
silent spade
If you set subscription_data[metadata] when those key/values will be on all related invoice.* events too: https://stripe.com/docs/api/invoices/object#invoice_object-subscription_details-metadata
dense sentinel
If you set `subscription_data[metadata]` when those key/values will be on all re...
ok great, heaps! now i see metadata is set on those events. Can I treat payment_intent.succeeded and customer.subscription.created events as final events to allow customers access my saas application ? I mean as long as I receive these events means they paid successfully
silent spade
No, .created is not indicative of a successful payment. For recurring payments you should use invoice.paid as per link I sent above
dense sentinel
thank you will check those now. appreciate your help
dense sentinel
`mode: 'payment'` -> `payment_intent.succeeded`
`mode: 'subscription'` -> `custo...
just checked payment_intent.succeeded, it doesn't include metadata 😦
silent spade
What's the evt_xxx ID?
dense sentinel
evt_
silent spade
Well that's because it's a mode: 'subscription' session: https://dashboard.stripe.com/test/logs/req_5t7gGSRlSloV5T
You cannot pass payment_intent_data fields on creation. Instead you'd look at the invoice.paid event