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

Re: Browser Payments API proposal

From: Alex MacCaw <maccman@gmail.com>
Date: Sat, 16 Jun 2012 14:16:22 -1000
Message-ID: <CAGcWc_YcmgQ-z+Eer-HTbrcFi-i9y-UMWgvVxM98u0+Ep4QGzw@mail.gmail.com>
To: public-webapps@w3.org
The blog article link has changed to:

A few people have raised (rightfully) security considerations. From the

Getting the security considerations right is key to making this work. As
browsers already store (and encrypt) credit card data, I feel that aspect
is less of an issue. Rather, it's more of a usability concern, as people
tend to blindly authorize permissions. Perhaps the answer is requiring the
card's CVC, or a countdown forcing users to read the infobar.


On Fri, Jun 15, 2012 at 6:05 PM, Alex MacCaw <maccman@gmail.com> wrote:

> I've been working on a way of integrating one-click payments (and signup)
> into the browser, and I wanted to put it in front of a few people to get
> some feedback.
> The API I was playing about with was pretty simple, and is documented here:
> http://blog.alexmaccaw.com/preview/MjQxMDcwOTcwNjAYz14YvbdZWrrVg
> It's basically an API to autocomplete data, already stored in the browser
> and containing things like credit card number and name.
> For example:
> navigator.requestProfile(['firstName', 'email', 'cardNumber'], function(
> profile){ console.log('Your name is:', profile.firstName); /* ... */ });
> I've also created a Chrome extension<https://github.com/maccman/request-profile> demonstrating
> the API. I think the key thing to getting adoption for something like this
> is to keep it really simple.
> Cheers,
> Alex
> --
> Alex MacCaw
> +12147175129
> @maccman
> http://alexmaccaw.com

Alex MacCaw


Received on Sunday, 17 June 2012 00:16:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC