#Fabien-PI

1 messages · Page 1 of 1 (latest)

orchid helm
#

Hi! Can you share the PaymentIntent ID (pi_xxx)?

jaunty ivy
#

Hi,

We received a payment_intent.payment_failed event pi_3KjNf7IXfdh5sBfa1rESlCtu and we have reasons to believe that this event arrived two days after the actual event:

  • In the timeline we see 3D Secure attempt failed on March 31 at 3:03pm
  • In the event activity at the bottom of the page we see the event evt_3KjNf7IXfdh5sBfa1beiqO0W being sent April 4th at 4:26am

Could you confirm that the event evt_3KjNf7IXfdh5sBfa1beiqO0W does indeed describe what happened on March 31st at 3:03pm and is not the reflection of something new that would have happened at 4:26am on April 4th ?

orchid helm
#

Thanks! Give me a few minutes to look into this.

jaunty ivy
#

Thank you so much

jaunty ivy
#

Hi Soma, just checking in 🙂

orchid helm
#

Sorry for the delay, still looking into this with a colleague.

jaunty ivy
#

Okay thank you, no rush

orchid helm
#

Okay, I think we know what happened. Basically we agree with you:

the event evt_3KjNf7IXfdh5sBfa1beiqO0W does indeed describe what happened on March 31st at 3:03pm and is not the reflection of something new that would have happened at 4:26am on April 4th
The issue is that on Stripe end we had an incident related to 3DS around that time, and this probably caused your event to be delayed by a few days.

jaunty ivy
#

Ah okay sounds good, that's what we assumed but we just wanted to conform

#

So the event should have been sent when in normal confition ?

#

I do see the status on stripe status page about the 3DS issues on March 31

orchid helm
#

The event should have been sent when the 3DS flow failed, so on March 31.