#bumbzor
tough garnetBOT
Hello bumbzor, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• bumbzor, 10 hours ago, 80 messages
• bumbzor-webhook-apiversion, 23 hours ago, 19 messages
lucid temple
I will double check but it sounds like the bank may have requested 3DS itself
Banks can always do that on any transaction. Conversely they can also choose not to request 3DS even when you have a rule that asks them to.
solemn carbon
there are a bunch of transactions lately where I se ean initial "pi" that failed 3DS
lucid temple
Can you tell me more about that?
solemn carbon
For example this one pi_3O5Z6BBEIvddyjrE14sUrr0E
tough garnetBOT
solemn carbon
I see an initial "charge" declined ch_3O5Z6BBEIvddyjrE1FKUgxYK
Payment declined by customer's bank
The bank returned the decline code authentication_required. Learn more about declines
26 Oct 2023, 21:20
Payment created by pi_3O5Z6BBEIvddyjrE14sUrr0E
26 Oct 2023, 21:20
Payment started
26 Oct 2023, 21:20
but then again pi_3O5Z6BBEIvddyjrE14sUrr0E is ocmpleted correctly via 3DS
then another one for example pi_3O5Y2pBEIvddyjrE1vxueDkP
how can it fail 3DS then a few seconds later or a minute, same customer, same 3ds same everything works
lucid temple
Where are you seeing the ch_3O5Z6BBEIvddyjrE1FKUgxYK charge? It looks like that payment intent succeeded on the first 3DS attempt
lucid temple
Ah I do see that that charge is related to that intent. You don't need to handle those charges, they can be created automatically as a part of the payment process but from your code's perspective they aren't surfaced.
solemn carbon
but it's poissible that, that decline basically triggers our code to fail the purchase. since it works fine after the user tries again
lucid temple
As far as I can see, it is not. We don't put charges like that on the payment intent object or send you events about it
Do you know where exactly in the dashboard you saw this? I continuing to check to make sure this isn't surfaced in a way that would trip up your API code
solemn carbon
https://dashboard.stripe.com/payments/ch_3O5Z6BBEIvddyjrE1FKUgxYK
lucid temple
Do you know how you got to that page in the dashboard? I'm not sure where the ID would be surfaced before that
solemn carbon
I am going at the Customer record. then clicking on the Payment https://dashboard.stripe.com/payments/pi_3O5Z6BBEIvddyjrE14sUrr0E
I then scroll down the page and in the Related payments section
it shows
right before Metadata
I can screenshot but don't want to share it here in public. I can DM if you want
lucid temple
Gotcha, thank you. It looks like that was a very specific kind of transient error that was handled silently, so the user shouldn't see a double charge attempt or anything. I've confirmed we didn't surface it via the API or an event, so this kind of error shouldn't trip up your code. So outside of surfacing in the dashboard, this kind of charge shouldn't have other side effects.