Hey all - it is maybe a stupid question, but I don‘t want to miss out things:
For my app for 3DSecure to work, I don‘t need to setup a .payments url scheme. I tried with the challenged sandbox credit card 4000 0000 0000 1091 as described in the documentations and everything works - also the return to the app. I guess it is because of 3DSecure version 2 as here all the authentication happens in the in-app browser?
If I am right - I don't need to setup a new scheme if only using 3DSecure version 2, correct? Here in Europe where our app is used, only two-factor authentication payments are allowed. So I don't see the need to setup extra configurations for 3DSecure version 1 which is not used.
Could you update the documentation on that, also that for PayPal since iOS SDK v5 it is not necessary anymore to setup a url scheme here as well as the payment flow also happens in-app.
Hey all - it is maybe a stupid question, but I don‘t want to miss out things:
For my app for 3DSecure to work, I don‘t need to setup a
.paymentsurl scheme. I tried with the challenged sandbox credit card 4000 0000 0000 1091 as described in the documentations and everything works - also the return to the app. I guess it is because of 3DSecure version 2 as here all the authentication happens in the in-app browser?If I am right - I don't need to setup a new scheme if only using 3DSecure version 2, correct? Here in Europe where our app is used, only two-factor authentication payments are allowed. So I don't see the need to setup extra configurations for 3DSecure version 1 which is not used.
Could you update the documentation on that, also that for PayPal since iOS SDK v5 it is not necessary anymore to setup a url scheme here as well as the payment flow also happens in-app.
Thanks!