New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3D secure support #217
Comments
I believe it's payment apps. Closing the issue for now. |
@ianbjacobs should i open it on dedicated repo ? |
Please do not open a new issue at this time. |
@tugal - 3D Secure will be handled in exactly the same way as it is today. If the payment method is "basic-card" then the merchant/processor must still submit the card details for processing in the same way they would if the details were submitted via a web form. If the response is a redirect then the user will be redirected. Likewise, for a payment app. If the payment is processed within the app and it is a card payment that requires 3D secure then the app must display a window that renders the redirect URL. (same as if you use an native mobile app to do a payment using 3D secure today. |
Hi,
I haven't read yet in specifications 3D secure support, so i'm trying to imagine how 3D secure should be supported in web payments.
Current version of 3D secure is handled throught redirection
3D secure authentification required
Which component should be responsible to handle 3D secure ?
A pay app could take this responsibility, but it must be connected to banks
Or should we imagine, a new process letting the merchant manage the window according PSP results (if PSP returns that 3D secure authentification is needed, merchant could redirect user in the window)..
============ 3D secure version 2
There is already a draft explaining how 3D secure version 2 works.. redirection should not be mandatory because they will supply SDK's to handle authentification.
I think, we whould not focus on this version yet.
What do you think ?
Thanks,
Nelson
The text was updated successfully, but these errors were encountered: