StorefrontBacktalk: Mobile Payment Brawl – POS Players Vs. Reader Vendors
Through a special arrangement, presented here for discussion is a summary of a current article from StorefrontBacktalk, a site tracking retail technology, e-commerce and mobile commerce.
The battle for control of mobile payments is now pitting the POS players against the reader vendors, with large retail chains squeezed uncomfortably in the middle. It hasn’t taken long for vendor infighting to kick in following the industry’s first serious mobile payment play, from Google late last month. But the real fight–a standardization effort so retailers need only accept one mobile payment system–is still months away.
There are two elements to mobile payment that need that standardization: payment card security and other payment data. The retail need for consistency of payment security will be handled cleanly by the PCI Security Council, whenever it gets around to it, most likely before the end of this year. The more critical area, though, is all of the data involved, whether it’s CRM, giftcards, coupons or anything else.
And a later stage of the data mess will be two-way near field communication (NFC), which is when things will get both interesting and ludicrously complex. If there are multiple competing wallets–say from Google, Apple and ISIS–how easy will it be to deal with all of that data in a homogeneous fashion?
Another couple of crucial retail considerations will be “who does the work?” and “who pays for the work?” Some vendors–eager to prove their value and to make the process as easy as possible for merchants–will push a plan where they will do almost everything and they will do it all outside of the retailer’s environment. But as tempting as that might be, the wisest course for most chains may be to opt to do most of the work themselves.
Two reasons: First, on the security side, the chains will be blamed and held accountable for any breaches, regardless of what contract paperwork says. If you’re going to be blamed because customers’ data is breached after they walk into your store and beam their card information into equipment displaying your brand’s logo, you might as well at least control the operation.
Second, there is the matter of handling the data. This raises the soon-to-be-redefined question of “When is a customer a retail brand customer as opposed to a mobile payment alliance customer?” Google and the others are arguing that they are bringing huge value to retail chains in the form of new revenue. In other words, Google will talk about all of the mobile customers using their phones and their carrier partners that Google delivered to the merchant. Who’s to say that customer wouldn’t have shopped at Walmart or Macy’s anyway?
Either way, how will the chains feel about letting Google (or Apple, ISIS, etc.) have access to tons of customer CRM information? Will that data find its way to the systems of a chain’s most direct rival, even in aggregate or anonymous form? That won’t be preventable. But the more integration work the chain does directly, the more of a feeling of control its executives will have.
Discussion Questions: How much control should retailers have over security and data matters when it comes to mobile payments? Do you see any other obstacles toward mobile payments?