#ChocobO-3ds2
1 messages · Page 1 of 1 (latest)
yes, sec
setup intent id - seti_1Jjm8w2mjH4XVMmx2NbPeE3W
payment method - pm_1JjmA52mjH4XVMmxfwndlEjZ
Another case:
"id": "seti_1JpTsS2mjH4XVMmx2tU3aedM", "object": "setup_intent",
Sorry, closed the tab with 3rd case it seems.
From Stripe's log I only see that the SetupIntent is attempted to confirmed, Stripe responded with instruction to use our client SDK to display the 3ds2
How does your client code look like?
Also, does this happen randomly, or with everyone has 3ds2?
client side is front end stripe lib
maybe a bit outdated
about randomly or not - I cannot look it up. we tried several of our own cards - it worked
on Stripe event logs - I am not sure how to search for that kind of info
Any SetupIntent ID that you believe it worked, can prove
is there a way to search for setupintent logs in the stripe dashboard??
this one seems to have succeeded - "id": "seti_1JsMVn2mjH4XVMmxv1OeK22A",
"type": "use_stripe_sdk", "use_stripe_sdk": { "type": "stripe_3ds2_fingerprint",
yes, should be example of successful attempt.
Okie I can confirm that it succeed
And the response is similar, means your client code is definitely working
This often means the SetupIntent that failed due to the issuer bank of that card 🤔
Anw can you show me how your client is handling this?
I only have some screenshots from the clients
basically, I know that they are supposed to see a popup in which they can proceed and make 3DS authorization, but they don't - just immediately get the error
How about your client code?
Could you paste in your js code around the place handling it? I know it is working but just want to double check
I think we are using some sort of lib. React-stripe-elements from node?
https://github.com/stripe/react-stripe-elements
I guess this is an old lib
Moved to stripe/react-stripe-js. Contribute to stripe-archive/react-stripe-elements development by creating an account on GitHub.
Hmm okie
I would suggest to
- Ask your customer contact their bank to see if they acknowledge anything
- Plan to upgrade to the newer react-stripe-js library
3DS2 is quite new and maybe the old library just didn't support it
Kinda strange that it works on some cases and doesn't work for others
we do plan to upgrade it now
if the issues is with the customer's bank - what could it be?
in one case the card was expired, so I guess they just prolonged it (last4 digits seem to be the same, but expiration dates are different) - so I guess it is literally the same card, which worked a year ago, but not now
Does all the failed payment come from expired card?
no
some cards are just new
at least last4 digists are different
but, yes, most of the time we ask customers to change cards if they have expired
It's hard to say exactly what was the problem with issuer bank. There could be a lot of issuer bank and each of them has different implement for their 3DS page. For example some might expect the request comes by redirection but it came from a modal, or some just bugged on headers etc... Honestly it's vary though all the issuer banks
(Or, we are suspecting the old library has some incompatibility)