W3C home > Mailing lists > Public > public-payments-wg@w3.org > April 2017

Re: [w3c/webpayments] 3D secure support (#217)

From: Adrian Hope-Bailie <notifications@github.com>
Date: Fri, 31 Mar 2017 22:51:20 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webpayments/issues/217/290897803@github.com>
@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.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Saturday, 1 April 2017 05:51:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:25 UTC