This is page 2 of:

PCI Memo To Mobile Payment App Developers: It’s Up To You

September 19th, 2012

Although the card brands’ guidance focused on retailers, neither focused on telling developers all the things they need to do to develop secure applications. The PCI Council has stepped into that void by providing some guidelines for developers. The hope is that secure payment applications will be able to compensate for the inherent insecurity of the mobile devices themselves.

The Council’s guidance is aimed straight at solution developers. Its stated purpose is to “educate stakeholders responsible for the architecture, design and development of mobile apps and their associated environment within a mobile device that merchants might use for payment acceptance.” To its credit, the Council does not overpromise, either: “No assumption should be made that meeting the guidelines and recommendations expressed in this document would cause a solution to be compliant with PA-DSS.”

The PCI Council offers guidance for transaction controls to prevent the three main risks associated with mobile payments: intercepting the card data when it is entered into the mobile device; compromising the account data while it is being processed or stored; and intercepting the data when it is transmitted. The guidance then proceeds to offer 15 security requirements that address environment controls for the mobile device and the payment application. These requirements include preventing unauthorized access (you need more than a just a “slide” to access the device), disabling the device remotely if it is lost or stolen, supporting only online transactions (no offline mode of operation), and authenticating attachments and applications (bye-bye Angry Birds, but will inventory checking be allowed?).

The next step is up to the mobile-application developers. One difficulty will be getting the word out to these developers. For example, does the PCI Council know how to reach them? I heard one story of a merchant meeting with his payment-application developers in a Chinese restaurant. That restaurant was their “office.” Getting the word out to this developer community will involve more than posting a document on the Council’s Web site.

Assuming the Council gets the word out successfully and the developers actually read the PCI Mobile Payment Acceptance Security Guidelines document, will those developers actually build secure mobile-payment applications? Without a guarantee of PA-DSS validation, will developers change their habits? If they do, will retailers be willing to pay for the secure applications? With the major card brands appearing to give retailers a pass on PCI DSS compliance, where is the incentive for a retailer to pay more for a secure payment application?

You have heard some of my questions, but I would like to hear what your questions are. Either leave a comment or E-mail me.


Comments are closed.


StorefrontBacktalk delivers the latest retail technology news & analysis. Join more than 60,000 retail IT leaders who subscribe to our free weekly email. Sign up today!

Most Recent Comments

Why Did Gonzales Hackers Like European Cards So Much Better?

I am still unclear about the core point here-- why higher value of European cards. Supply and demand, yes, makes sense. But the fact that the cards were chip and pin (EMV) should make them less valuable because that demonstrably reduces the ability to use them fraudulently. Did the author mean that the chip and pin cards could be used in a country where EMV is not implemented--the US--and this mis-match make it easier to us them since the issuing banks may not have as robust anti-fraud controls as non-EMV banks because they assumed EMV would do the fraud prevention for them Read more...
Two possible reasons that I can think of and have seen in the past - 1) Cards issued by European banks when used online cross border don't usually support AVS checks. So, when a European card is used with a billing address that's in the US, an ecom merchant wouldn't necessarily know that the shipping zip code doesn't match the billing code. 2) Also, in offline chip countries the card determines whether or not a transaction is approved, not the issuer. In my experience, European issuers haven't developed the same checks on authorization requests as US issuers. So, these cards might be more valuable because they are more likely to get approved. Read more...
A smart card slot in terminals doesn't mean there is a reader or that the reader is activated. Then, activated reader or not, the U.S. processors don't have apps certified or ready to load into those terminals to accept and process smart card transactions just yet. Don't get your card(t) before the terminal (horse). Read more...
The marketplace does speak. More fraud capacity translates to higher value for the stolen data. Because nearly 100% of all US transactions are authorized online in real time, we have less fraud regardless of whether the card is Magstripe only or chip and PIn. Hence, $10 prices for US cards vs $25 for the European counterparts. Read more...
@David True. The European cards have both an EMV chip AND a mag stripe. Europeans may generally use the chip for their transactions, but the insecure stripe remains vulnerable to skimming, whether it be from a false front on an ATM or a dishonest waiter with a handheld skimmer. If their stripe is skimmed, the track data can still be cloned and used fraudulently in the United States. If European banks only detect fraud from 9-5 GMT, that might explain why American criminals prefer them over American bank issued cards, who have fraud detection in place 24x7. Read more...

Our apologies. Due to legal and security copyright issues, we can't facilitate the printing of Premium Content. If you absolutely need a hard copy, please contact customer service.