- From: Adam Solove <notifications@github.com>
- Date: Mon, 26 Mar 2018 16:09:09 +0000 (UTC)
- To: w3c/3ds <3ds@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/3ds/issues/4@github.com>
[This is a super rough draft! Comments/revisions/rewrites very welcome.] The goal of this task force is to create browser standards that allow the authentication of online credit card payments. - **Customers** want a convenient way to complete online purchases that they know they can trust. - **Merchants** want to comply with new Secure Customer Authentication standards in India and the EU, but still want to minimize the friction and conversion rate impact of extra authentication in their checkout flows. - **PSPs** want to make their existing products (like UIs to accept and tokenize card numbers) comply with SCA rules, while retaining enough control to still offer distinguishing features or UI innovations. - **Issuers** want additional data about transactions to inform their risk models and offer value-added services to their cardholders. (They also _wouldn't mind_ if their name/logo appeared prominently during the payment flow.) - **Browser authors** want to offer better web payment options to help web commerce continue to grow. But they act on behalf of users and are therefore wary of sharing personal data or executing third-party code without explicit permission. Browser authors are generally not part of the payments world and are reluctant to take on responsibility for payments-specific data or policies that may change over time. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/3ds/issues/4
Received on Monday, 26 March 2018 16:09:38 UTC