#Edi-react-native-attach-card
1 messages · Page 1 of 1 (latest)
Hi, we're using Expo 45, so we're locked on 0.6.1, but I've also just tested with the latest version 0.12.0 and the outcome is the same.
We've had this issue for months, and I've also wrote here, a few months ago, about some Finnish banks, but a colleague of yours said that he was aware of other Stripe developers complaining about the same issue with scandinavian banks, but that the banks don't implement 3ds properly, so it was their fault
I've had a hard time believing that 4 of the biggest banks in Finland, all have the same issue with 3DS
So, after months, I've managed to get my own card at one of the banks with the issues
I've successfully added the card on web (via stripe's js sdk)
Successfully linked it on iOS (with the same react native sdk version, 0.6.1, as well as the latest one, 0.12.0)
But, on android, it always returns: unhandled error: requires_payment_method
Can you provide the request ID?
Sure
Thanks!
req_SAhfofimbCJ8Av
req_LzoNjy6alsmY3l
req_7kSaC1CPbEhvHm
We have thousands of these, per week.
Where our customers in Finland are unable to add their card, since 70% of the user base there is on Android
And so, it's a big problem.
Last time, stripe was blaming the banks, but now I can prove it's not.
Thanks for the details. I need to step away but my colleague is going to step in to investigate.
Sure
This is the failure on Android
Whereas on iOS with the same exact source code, it properly goes through with the 3DS and attaches the card.
Hi there. Stepping in for bismarck. Give me a moment to catch up
I've also created an online snack (which can be checked via Expo) so you can test on your own, I could give you my card's details in private.
It's something to do with these 3DS verifications, as other cards work just fine. But these banks in Finland, may be requiring something which is not supported on Android, in the background, dunno.
https://snack.expo.dev/@swup/stripe-react-native-example
Example can be edited to use your own Glitch server code, with your own public / private keys if you want to debug.
Same goes for the glitch backend here:
https://glitch.com/edit/#!/voracious-bronze-accordion
You can "remix" (edit) it however you want.
Here's a recording of the Android process, which for some reason fails to get to the 3DS verification, which does happen in iOS, and on web. Ignore the aspect ratio .. i've converted it to MP4 from MOV .. you get the point.
Ok thank you for all the details. Going to check with a colleague. Will get back to you
And to confirm that video above is Android, not iOS right?
Yeah, sorry, I've already edited the typo
Ah I see you edited the message
Damn Discord really upped the brightness on that one.
Uploading original here.
Here you go
Note that you can always request my card details (privately), since it has just a few bucks on it, if you want to test with it ...
No I am not allowed do that. I appreciate it though
I have a colleague looking into this
If you can't reproduce it with another card though, let me know, I can do it via Expo for you then.
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Thanks
In case you can also see events:
- successful verification and attach (evt_1L7jWJFEYYjHn8Dy70A3QraL)
- successful detach, 1 minute late (evt_1L7jXcFEYYjHn8DyU9hh2vXG)
Trying to give as much info as possible.
Ok so they looked into this further. You'll have to write in to support here: https://support.stripe.com so we can track this and get to the bottom of it. It's either a bug in the Android SDK or a bug with the Issuer. Either way, you'll have to write in so we can fix this
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
And provide all the info you've given me in here
Alright
I doubt it's a bug with the issuer since it works just fine on iOS and on Web, and the very same thing happens on 3 other banks in Finland.
They can't all have the same bug.
Yeah seems like it's most likely an issue with the Android SDK