Re: Browser Payments API proposal

The blog article link has changed to:
http://blog.alexmaccaw.com/preview/Pc1LYBw4xDT95OPWZGihod7z8WhrnfAdXMjQxMDg3MTc5NDIaXNjA1p

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

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.

Alex

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

+12147175129
@maccman

http://alexmaccaw.com