#cm

1 messages · Page 1 of 1 (latest)

buoyant houndBOT
deep basalt
#

Can you share the charge ID please? These are safe to share publicly, nobody can do anything with them without your secret key.

#

or the event id

quasi sail
#

In chronological order:
payment_intent.created: evt_3MpA6o2nDm85BVWR1iCphmf1
charge.succeeded: evt_3MpA6o2nDm85BVWR11rlM0U5
payment_intent.succeeded: evt_3MpA6o2nDm85BVWR1bUlM6Vt

The PaymentIntent was created without a payment_method, which isn't all that unexpected I guess. Five seconds later, we received the charged.succeeded event. At the time of the charge.succeeded event, the PaymentIntent did not have a payment_method. However, less than one second after the charge.succeeded event, in the payment_intent.succeeded event, the PaymentIntent does have a payment_method.

#

It just seemed a little unexpected, I think

deep basalt
#

Yea that doesn't look quite right to me either, looking at this

buoyant houndBOT
buoyant houndBOT
deep basalt
#

Just looping back here that while confusing, this is expected and normal because the invoice was paid with the default_source card

#

And it's not processed as a payment_method on the payment intent because the card is only attached as a source, not as a PM