#bouyyaaa_unexpected
frank wolfBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1250794048999129179
đ Have more to share? Add details, code, screenshots, videos, etc. below.
odd wraith
tawny swallowBOT
kind void
Hello, stepping in here as soma needs to step away
I don't believe this changed recently, there are select cases where Google Pay can require 3DS -- I believe it depends on if it was a browser-saved card or not. But let me double check
timid trench
Ok thanks. Because we didn't had the case until then
We always had some cases where, when they add they creditcard or try to pay with google pay, they add 3DSecure but in the google pay interface, similar as apple pay
But never a 3DS requirement outside of the google pay in app
timid trench
Ok thanks
kind void
Alright @timid trench, overall nothing is jumping out here to us that is specifically unique to this Google Pay transaction, though there are cases where Google Pay can still require 3DS (as I mentioned above).
Overall, your integration should always be ready to bring your customer back on-session when you do see a decline of this nature.
If you customer is questioning why 3DS was requested here, then the best thing to do is to have them reach out to the issuing bank as it was the issuing bank who actually responded to the authorization with an authentication_required decline. I suspect this was just a snafu on their end with the decline code that was used -- that happens somewhat often where the issuer will respond with an unreliable decline code.
Lastly, if you do see this happen consistently then please do reach out to us with several examples and we can take a deeper look from our side by digging into the actual authorization communication (we aren't experts in that part here).
timid trench
Ok thank you very much for your answer. We previously (years ago) made a dev to avoid 3DSecure on google payments as never happened and we never had this error.
We'll try to track of it and contact you if we see many cases
kind void
Yep please do