#dalma.kameleo
crisp sage
hi there!
what do you mean by "it doesn't work"?
can you share a PaymentIntent ID (pi_xxx) with this issue?
ruby sinew
we have a current ticket
ID: 11635143
We continued the testing today. Now we try to pay with the same account the same order in chrome -> id: pi_3OmXnNK6zP0rzoRM0SmkWbn0, it failed by the 3D secure. When I changed the browser to Firefox, the payment was successful. -> id: pi_3OmXxcK6zP0rzoRM02VrsmFX I could accept this in the mobile app. Maybe it will helps to you.
crisp sage
please answer my questions directly in this thread
ruby sinew
there are the IDs in my message. you can read it above.
pi_3OmXnNK6zP0rzoRM0SmkWbn0
pi_3OmanzK6zP0rzoRM1uTA915s
crisp sage
one ie enough, having a look
crisp sage
for the first PaymentIntent you shared, you can find the exact error message here: https://dashboard.stripe.com/logs/req_G2YfTUpGhzITiB. Looking into this...
ruby sinew
could you need any more info?
crisp sage
no, still looking
modest lark
👋 taking over for my colleague. Let me catch up.
do you happen to have more examples, was this reproducible with other cards/payments?
because sometimes it's just a one-off issue
modest lark
I mean past that period of time
ruby sinew
since yesterday. and I already reported it through the normal stripe support, but I did not receive an update from there
modest lark
with the same card?
ruby sinew
yes
modest lark
both on chrome and firefox?
undone joltBOT
spice harbor
👋 stepping in
Give me a moment to catch up
The question here is around why the Charge was declined?
Looks like a normal bank decline to me where they returned an incorrect_number decline response.
We have no control over that response -- we just relay what the issuer tells us.
ruby sinew
The question here is around why the Charge was declined?
NO
not this is the questions
spice harbor
Ah you are worried about 3DS
One sec let me look at the initial PaymentIntent you shared
spice harbor
You have been doing a lot of manual testing with that card?
I'm seeing that it is getting some flags for behavior that looks like card testing.
Which can lead to these declines and 3DS failures that you are seeing.
You really shouldn't be testing in live mode at all.
Does everything work as expected in test mode?
Have you had any complaints from live customers about this type of 3DS failure?
ruby sinew
Let me start from the beginning 🙂 We have a SaaS and our customers reported that they can't pay with credit cards anymore. Recurring payments work fine, but all of the new purchases made with Chrome browser, where there is a 3DS payment, are declined. I tried it with my own card so I can make the screenshots.
spice harbor
Can you share one example PaymentIntent from your customer that reported this?
ruby sinew
just to mention a few
pi_3Olee8K6zP0rzoRM0w9KmSv1
pi_3OmGDNK6zP0rzoRM0WQ7GVmK
pi_3OlyjXK6zP0rzoRM0v2q6ius
pi_3Ols2BK6zP0rzoRM1PVQ5DjZ
spice harbor
What does your customer report seeing when this happens?
ruby sinew
that he cant pay., write us a support ticket. but we only get this one screenshot
spice harbor
That just looks like a normal 3DS decline though
Like for each of the PaymentIntents you are sharing I see different things happening
It isn't the same exact thing for each -- mostly they are varying 3DS declines.
That isn't abnormal, really.
ruby sinew
i dont think so. it affects more than 14 of our customers.
And when i check this with my card. i see tha same issue. when i try the same card in chrome it dont work, when i try to use my card in firefox it's working
and we tried to reproducate this issue wit our cards with my collegues and noone work. I have 3 credit cart, and no one of them is working in crhome.
here you can see the bug codes
I sent to you the loom video. did you watch tat?
I sent you our log files. Did you see that?
ruby sinew
i dont think so. it affects more than 14 of our customers.
in one day
with this ID you can see my previous messages with the stripe support team: ID:11635143
spice harbor
I already told you why the PaymentIntent from your own test failed. At this point you will indeed need to work via that ticket if you believe there is a bug. You need to provide specific PaymentIntent IDs and if you believe there is unexpected client-side behavior then you need screenshots/videos of what is happening. It is not unexpected that customers fail 3DS or have 3DS declines, but with explicit evidence we would be happy to look into it further via the ticket you already have open.