#ryanw
1 messages · Page 1 of 1 (latest)
Hi there. One moment
You can use the charge.succeeded event if you like
PaymentIntents use Charges under the hood
You would be notified well in advance when we fully deprecate charges
So for the near future it's totally fine
But with that said, I guess I'd prefer an approach that is a bit more future-proof, if we know there's a chance for deprecation eventually
Yes for sure
In that case, you could just go with payment_intent.succeeded
Would only require 1 api call
Got it, and the recommendation there would be to use the payment_method field, NOT the charges field?
(and thus that one API call to get the full data?)
Yes that's correct
perfect, that makes sense. Thank you for the insight here, super helpful!