#AVGErikDahlstrom
1 messages ยท Page 1 of 1 (latest)
Not sure what you mean by 'URL handling'?
In the docs, https://stripe.com/docs/payments/accept-a-payment?platform=react-native&ui=payment-sheet#react-native-set-up-return-url, there's this bit about handling incoming deep links with some "fill in the blanks" stuff
basically, do I need to set up handleURLCallback in order for deeplinking to work? I guess I wouldn't have this question if I understood how to test the integration, right now I can't seem to find a test card that forces the user outside of our app so that I can see the linking working/not working
Which card(s) have you tried?
A couple of different ones, I thought the 3DS cards seemed to be a good place to start. 3DS2 gives different behavior than 3DS. For 3DS, the "return to merchant" button does nothing. For 3DS2, the in-app browser/modal closes automatically. I can see no difference in behavior for either card when I pass returnUrl or not
I assume that sometimes the user will have to, for example, authenticate their payment using an electronic ID. I guess stripe passes the return url as a part of the auth url to these services so that the user can be automatically returned to the app after authenticating. This is the type of flow I'm trying to verify that it's working before testing in our pre-production environment.
Hello ๐
IIRC you can also just use the return URL in your mobile browser and it should redirect back to the app
that way you can test if you've configured it correctly
Hello! ๐ ๐
Our return url works for other services in the app (logging in using eIDs for example). Also just clicking the link wherever also prompts the user to open the app. Are you saying that if these things work, I can be certain it will also work for Stripe payments?
And just to be certain, are you also saying that only passing the link in the returnUrl prop in initPaymentSheet is enough, the deeplink handling is only if I want to perform some action when the user is returned to the app?
All right
initPaymentSheet is enough, the deeplink handling is only if I want to perform some action when the user is returned to the app?
I believe so
All right, I guess I can ask my QAs to test it thoroughly in smoke test just to be certain it works before release. Thanks!