Quantcast StorefrontBacktalk » Blog Archive » Amazon Eyes In-Store Payment
advertisement
advertisement

Amazon Eyes In-Store Payment

Written by Evan Schuman
November 4th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

What do Amazon execs have in store for their company’s new PayPhrase payment system? Apparently, in-store itself.

The service today is an interesting means of allowing consumers to, in effect, subdivide their payment authorization so that a child or an employee can make purchases, but with specific dollar limits and related controls. It also allows consumers to have different addresses (home, work, the in-law residence where the holidays will be spent, etc.) associated with different phrases and potentially different payment methods (the corporate credit card for office deliveries, a personal card for home, etc.). But Amazon’s vision for PayPhrase goes beyond online; it includes mobile and, especially, in-store options, said Matt Williams, the general manager for Amazon PayPhrase.

“We want [PayPhrase] to be used anywhere they want to pay, anywhere a customer happens to be,” Williams said, although he declined to say whether it has been seriously discussed yet with any major brick-and-mortar retail chain.

As retailers struggle to explore payment alternatives, the idea of bringing such a third-party online service into the checkout aisle isn’t so far-fetched.

PayPhrase is part of Checkout By Amazon, a payment service that allows the various retailers to accept it rather than payment cards. Those retailers benefit because they never have to house any data-breach-inducing payment data. Among the retailers Amazon typically touts as using its Checkout By Amazon service are DKNY, Jockey, Patagonia, Buy.com, J&R Electronics and Car Toys.

By allowing a customer to confidentially communicate his PayPhrase and password (presumably by keying it in, as even whispering the words would present a huge security risk), chains may get help dealing with both interchange issues (if, for example, PayPal or another alternative payment method was ultimately paying) and PCI concerns (with far less data housed, there are far fewer regulatory concerns. And if the chain ever went entirely Amazon, it could theoretically ditch PCI altogether).

But there may even be a simpler route. The very nature of PayPhrase is ideal for mobile payments, and Williams confirmed that it will soon be on Amazon’s iPhone app and then likely on its BlackBerry app. “We don’t have it available on the iPhone app, but we will certainly have it available on the iPhone app in the future,” he said. When asked about BlackBerry, he said, “We’re certainly looking at both.”

It’s not hard to envision consumers using PayPhrase to authenticate a purchase and then simply have their cell phone interact with the POS (either by the phone displaying a barcode that may be swiped or a direct POS communication).

PayPhrase itself operates on different security levels. When accessed remotely, it relies on the phrase and the PIN and can perform purchases. To access administrative options, such as reviewing all of the account’s PayPhrases, the system needs to see a cookie for a third authentication. That means consumers must be using their main computers.

Neel Grover, the CEO for Buy.com, said he envisions a time when his E-tail firm may partner with a brick-and-mortar shop to give Buy.com physical distribution points. Whether or not using PayPhrase in-store is a near-term possibility is a very different issue, he said. “There can be a big gap when crossing the chasm of in-store” from online, Grover said, adding that having consolidated payment methods will prove crucial. Still, he added, “you want to tackle what the stores are ready for.”


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...