itaied - payment intent source | Stripe Developers | Page 1

open bolt Jun 14, 2022, 2:27 PM

#

Good question. Checking in to it. Are you listening for subscription payments in another webhook or are you trying to do both in one event handler?

fallow wraith Jun 14, 2022, 2:30 PM

#

I'm doing it in the same event handler. My customers can both subscribe and one time purchase. I'm using the built-in checkout session, but it's not enough to listen to checkout.session.completed as capture_method of type manual require listening to payment_intent.amount_capturable_updated

open bolt Jun 14, 2022, 2:37 PM

#

So an easy way to check if the payment is from a subscription or not would be to check its invoice parameter. If the PaymentIntent is from a subscription, there will be an invoice ID in that field. Otherwise the field will be blank https://stripe.com/docs/api/payment_intents/object#payment_intent_object-invoice

fallow wraith Jun 14, 2022, 2:40 PM

#

This field won't be black only for subscriptions?

open bolt Jun 14, 2022, 2:43 PM

#

Good point. It will also be populated if you create one-off invoices

#

So you may want to retrieve the invoice and check that it has a subscription ID in its subscription field

#

Also depending on what you are doing, you may want to check the invoice's billing_reason field to see if it is for a subscription update/cycle/creation

fallow wraith Jun 14, 2022, 2:45 PM

#

OK I see.
It feels a bit of a hassle, do you think there is a better implementation path for what I'm trying to do?

open bolt Jun 14, 2022, 2:47 PM

#

Can you tell me a bit more about what you are trying to do here? So right now are you just trying to differentiate between one-off payments and your subscription payments via these webhook events?

fallow wraith Jun 14, 2022, 2:48 PM

#

yes, while also enabling manual capture (hold-capture later) and using the built-in checkout session pages

open bolt Jun 14, 2022, 2:50 PM

#

If those are all of your scenarios, you can just check that invoice field. If all of your payments are a one off manual payment or a subscription payment, that will successfully tell the difference between the two

#

Though actually in that case, you can just process invoice.paid events for your subscription payments and listen to a payment_intent event for the manual payments (checking exactly which event that should be)

#

payment_intent.amount_capturable_updated

fallow wraith Jun 14, 2022, 2:53 PM

#

ok I got it. thank you for your support

fallow wraith Jun 14, 2022, 3:17 PM

#

just sharing a thought here, I would like to hear your thoughts @open bolt .
I can listen for subscriptions using checkout.session.completed and verifying their event.data.object.mode is subscription. Right?
If a checkout session of mode subscription succeeded, then it's done, there is no pending state or something like that

open bolt Jun 14, 2022, 3:19 PM

#

Correct, you can also do that for the first payment. I was thinking first payment + subscription cycles when I said invoice.paid

fallow wraith Jun 14, 2022, 3:20 PM

#

yes but I would like to keep it as lean as possible, and I think I can avoid listening to invoice.paid events

open bolt Jun 14, 2022, 3:23 PM

#

Of course, whatever works for you

#itaied - payment intent source