- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Tue, 04 Oct 2016 11:32:32 -0700
- To: w3c/webpayments-methods-card <webpayments-methods-card@noreply.github.com>
Received on Tuesday, 4 October 2016 18:33:30 UTC
adrianhopebailie commented on this pull request. > + + <p>Additionally, web sites that call the payments API for each + transaction avoid the friction that can result when users’ credit card + numbers and/or expiration dates are updated. From a user’s perspective, + this avoids the hassle of having to update a large number of merchant + web sites any time they are issued a new card.</p> + + <p>Finally, by letting the web browser determine user authentication + information, the merchant site is relieved of the duty of ensuring that + a time-local and sufficiently strong authentication has occurred. + Additionally, browsers can make use of local affordances, such as + biometrics and hardware tokens, to authenticate users in a way that is + more convenient, more secure, and lower friction than web sites + currently can.</p> + + <p>The basic card payment method provides information to requesting You have repeated this paragraph -- 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/webpayments-methods-card/pull/17#pullrequestreview-2775246
Received on Tuesday, 4 October 2016 18:33:30 UTC