shareef_highlevel

[haughty fiber]

do you have an example PaymentIntent pi_xxx where that was the case that I can look at?

[primal sphinx]

Yes i have. can i post that payment intent id here?

[haughty fiber]

yes

[primal sphinx]

pi_3NiNN4FEJ2fe4PSO07X83Lwg

pi_3NZvSFArGmZiMVQV0AIZkusp

pi_3NX8ZCFEJ2fe4PSO0uTuJwJg

[haughty fiber]

basically it's because the PaymentIntent was paid using a legacy object , a card_xxx object. You entered the customer's card in the Dashboard and the Dashboard still uses that legacy object instead of PaymentMethods.

Technically the 'correct' way to access the card details regardless of what object was used is to use latest_charge.payment_method_details instead.

Still, I would have thought we would also put the card ID in the payment_method field, since it's backward compatible. Is this is something new that you've seen and that field used to have values in the past?

[primal sphinx]

We could not find this issue previously. We are deciding the transaction status based on these values too. So some transactions still showing pending in our side due to this issue.

[haughty fiber]

interesting. Then I suppose it's just a quirk when legacy objects are used unfortunately.

ultimately the status field of the PaymentIntent is the status, and if you want to look at the details used to make the payment, that is latest_charge.payment_method_details

https://stripe.com/docs/payments/payment-intents/migration/charges#read
https://stripe.com/docs/api/payment_intents/object#payment_intent_object-latest_charge -> https://stripe.com/docs/api/charges/object#charge_object-payment_method_details

[primal sphinx]

pi_3NZvSFArGmZiMVQV0AIZkusp

Here the customer created recently. means on 30 Jun 2023, 17:47