W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: Browser Payments API proposal

From: Yaar Schnitman <yaar@chromium.org>
Date: Tue, 19 Jun 2012 10:15:02 -0700
Message-ID: <CA+KV223q8KHAOUjcO7S3WKGKdhyb=r-yG39+SMcuy+Y-LBO7wA@mail.gmail.com>
To: Alex MacCaw <maccman@gmail.com>
Cc: public-webapps@w3.org
Nice idea Alex!

I have done some work on this in the past, but it didn't go very far. A few
tips:
1. As long as many users don't have this, websites would still have to do
form-based credit-card forms. But browsers and extensions are getting
pretty good at auto-filling these forms. So you have a tough competition
from the entrenched technology and there are ways websites can help the
auto-complete work even better (e.g. proper element names).

2. The permissions dialog needs to be more visible and proactive. Users
(even advanced ones) often miss the permissions prompts.

3. Requiring the user to type a security code / pin every time you give a
site your credit card info might increase awareness and security.

4. Can we do something that doesn't require scripting? Maybe a new tag? The
motivation for that is embedding one click payments in emails where
scripting is disabled.

5. Minor things: How to deal with multiple credit cards? What if a site
only suports AmEx but not Visa?


On Sun, Jun 17, 2012 at 5:34 AM, Arthur Barstow <art.barstow@nokia.com>wrote:

> On 6/16/12 8:16 PM, ext Alex MacCaw wrote:
>
>> The blog article link has changed to: http://blog.alexmaccaw.com/**
>> preview/**Pc1LYBw4xDT95OPWZGihod7z8Whrnf**AdXMjQxMDg3MTc5NDIaXNjA1p<http://blog.alexmaccaw.com/preview/Pc1LYBw4xDT95OPWZGihod7z8WhrnfAdXMjQxMDg3MTc5NDIaXNjA1p>
>>
>
> Alex - perhaps this API will be of interest to the Web Payments Community
> Group <http://www.w3.org/community/**webpayments/<http://www.w3.org/community/webpayments/>>.
> -AB
>
>
Received on Tuesday, 19 June 2012 17:15:52 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT