#Altrollique - RN + 3DS
daring estuary
Hi 👋
So for starters, I know zero about React Native but let's see if we can still address the issue.
So you are attempting to test 3DS in your RN app?
And are you following our recommended RN integration?
https://stripe.com/docs/payments/accept-a-payment?platform=react-native
quaint kelp
yes. I do it by creating a webview (basically opening a webbrowser in my app) with th eurl returned by paymentIntent.next_action.redirect_to_url.url
daring estuary
Yeah that won't work
quaint kelp
In fact it worked until now.
We don't use the classic payement flow.
daring estuary
Why not?
quaint kelp
we save credit card information at the begining, our customer use our service and then we make the payment at the end depending the use. We are e-bike rental service
we don't ask for customer to give credit card info after each ride
daring estuary
Okay. But you don't put a hold on the funds up front? That might help relieve the whole situation.
That's how hotels and other businesses that charge at the end of service often do it
It means you collet the authorization up front but wait until the end of the service to charge the user
The auth is what triggers the 3DS so you can keep the user in a normal payment flow
quaint kelp
we do that but as a deposit in case the user have bad behavior with the bike.
In production we store the credit card and the 3dsecure show only on card registration and after that I don't alway show up
Here I'm in test with credit card that always ask for 3DS.
but It's the first time I got this error and I want to understand why
I don't want this to happen in production
never got this before, I just tried to upgrade stripe api version.
quaint kelp
to test our 3ds integration
it's the stripe 3ds web view. Very different than bank one.
just two button to trigger succes or failed attempt
I can't say how it is concidered for 3DS1 or 2
daring estuary
Can you specify exactly what isn't working? How are you configuring your web view?
What loads in the web view doesn't really matter, it's just that you can see the interface that is returned.
quaint kelp
Hum I don't don't relly know wht to add.
The webview is basically a web page. I give it the url
paymentIntent.next_action.redirect_to_url.url
Instead of showing me the usual page with my two button to trigger success or failed attempt I got a white screen with the error
ERR_TOO_MANY_REDIRECTS
try it yourself
it as the same behaviour on a desktop web browser
daring estuary
Can you share the code you are using to create the webview
quaint kelp
<WebView
onLoadStart={() => {
setVisible(true)
}}
onLoad={() => {
setVisible(false)
}}
style={{flex: 1}}
source={{uri: uri}}
hidesWhenStopped={true}
/>
here uri is the url I shared you
daring estuary
That URL loads just fine for me. The webview configuration appears normal too. Do you see the redirect error on Desktop browsers as well?
Could you provide a screenshot of the error as well?
quaint kelp
ok if the url work fine for you it should be something on my network. I'll look into it. thank you, I'll come back if I need more help.
deft pumice
Why are you redirecting yourself instead of using our real/official integration and letting us do all of this for you?
quaint kelp
Because I already had issue with your integration in production and basically the only solution you provided me is to do it this way
and for payment we don't want to ask for credit card. We register the information before hand.
polar sentinel
Hello! Can you clarify if you're only seeing this issue with this URL in your React Native Android app, or if you're also seeing it on desktop and/or iOS?
polar sentinel
Interesting. We're unable to reproduce this on our end. What's in the URL bar of your desktop browser when this happens?
This is what we're seeing on our end:
quaint kelp
quaint kelp
This is what we're seeing on our end:
this is what I'm used to see indeed
polar sentinel
Can you copy and paste that URL here? It looks different than the one we're seeing.
quaint kelp
polar sentinel
Hm, let me try a couple of things, hang on...
quaint kelp
ok
polar sentinel
I still can't reproduce on my end, tried different browsers and URL variations. Can you open the developer tools in your browser, go to the Network tab, then try to load the URL again? The redirects should show up in the list there, and once the error appears can you provide a screenshot of what's shown in the dev tools?
polar sentinel
Looks like this might be a redirect issue on our end. Can you click on one of the 301 lines and give me the full URL, and do the same for one of the 307 lines?
polar sentinel
Oh, wait, I think we're able to reproduce, hang on...
quaint kelp
ok
polar sentinel
Okay, we've identified the issue on our end and are working on it now.
It's nothing to do with your app or anything on your end.
Entirely on our end, sorry about the trouble, and thanks for providing the details which helped us find the issue!
We're hoping to have this resolved in less than an hour, but that's a rough estimate and subject to change. Wanted to give you a rough timeframe though.
quaint kelp
ok thank you for your help and your quick answers. I'll probably go to sleep now so no hurry on my side now.
Good luck with this
polar sentinel
Have a great evening, and thanks again!
polar sentinel
@quaint kelp We were able to resolve this issue; if you're around can you confirm it's working as expected on your end?
deft pumice
Amazing!!!