<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mobile Payments May Make PCI Obsolete</title>
	<atom:link href="http://storefrontbacktalk.com/securityfraud/mobile-payments-may-make-pci-obsolete/feed/" rel="self" type="application/rss+xml" />
	<link>http://storefrontbacktalk.com/securityfraud/mobile-payments-may-make-pci-obsolete/</link>
	<description>Techniques, Tools and Tirades about Retail Technology and E-Commerce</description>
	<lastBuildDate>Sun, 20 May 2012 01:49:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nealle</title>
		<link>http://storefrontbacktalk.com/securityfraud/mobile-payments-may-make-pci-obsolete/comment-page-1/#comment-63019</link>
		<dc:creator>Nealle</dc:creator>
		<pubDate>Mon, 10 Aug 2009 15:19:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=3474#comment-63019</guid>
		<description>I believe that the move to an infrastructure will make requirements like PCI more important.  As we move further away from physical instruments like cards, which at least have physical security features (for what they are worth, I know most merchants don&#039;t give them a second look).  But if data from one of my transactions was compromised and put onto someone else&#039;s mobile their is no real way for a merchant to identify one mobile from another as being the genuine payment token

The fact that the device could support features like (more) advanced encryption of the transaction data is just a bonus. 

Nealle</description>
		<content:encoded><![CDATA[<p>I believe that the move to an infrastructure will make requirements like PCI more important.  As we move further away from physical instruments like cards, which at least have physical security features (for what they are worth, I know most merchants don&#8217;t give them a second look).  But if data from one of my transactions was compromised and put onto someone else&#8217;s mobile their is no real way for a merchant to identify one mobile from another as being the genuine payment token</p>
<p>The fact that the device could support features like (more) advanced encryption of the transaction data is just a bonus. </p>
<p>Nealle</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Taylor</title>
		<link>http://storefrontbacktalk.com/securityfraud/mobile-payments-may-make-pci-obsolete/comment-page-1/#comment-62972</link>
		<dc:creator>Dave Taylor</dc:creator>
		<pubDate>Fri, 07 Aug 2009 13:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=3474#comment-62972</guid>
		<description>Eric, i agree about the value of OTU passwords, but i also believe tokens are another option.  Either way, the centralization of card data is critical from an architecture perspective, as well as simplifying compliance and minimizing data breach risk.  Good point!</description>
		<content:encoded><![CDATA[<p>Eric, i agree about the value of OTU passwords, but i also believe tokens are another option.  Either way, the centralization of card data is critical from an architecture perspective, as well as simplifying compliance and minimizing data breach risk.  Good point!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Meniere</title>
		<link>http://storefrontbacktalk.com/securityfraud/mobile-payments-may-make-pci-obsolete/comment-page-1/#comment-62970</link>
		<dc:creator>Eric Meniere</dc:creator>
		<pubDate>Fri, 07 Aug 2009 10:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=3474#comment-62970</guid>
		<description>Mobiles can leverage the global credit/debit cards infrastucture and solve many PCI DSS compliance issues; To start mobiles (or POS) should never have to store a credit/debit card number. Mobiles can be enabled to compute one-time-use credit/debit cards - a token for a single purchase. One-time-use is the best form of security (it cannot be re-used). No personal data or (plastic) credit/debit card details need to be stored in a phone, or at a TSM. Your sensitive data should remain with your Financial Institution at all times and not be shared with anyone. FI should worry about PCI DSS, no one else!</description>
		<content:encoded><![CDATA[<p>Mobiles can leverage the global credit/debit cards infrastucture and solve many PCI DSS compliance issues; To start mobiles (or POS) should never have to store a credit/debit card number. Mobiles can be enabled to compute one-time-use credit/debit cards &#8211; a token for a single purchase. One-time-use is the best form of security (it cannot be re-used). No personal data or (plastic) credit/debit card details need to be stored in a phone, or at a TSM. Your sensitive data should remain with your Financial Institution at all times and not be shared with anyone. FI should worry about PCI DSS, no one else!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Lambert</title>
		<link>http://storefrontbacktalk.com/securityfraud/mobile-payments-may-make-pci-obsolete/comment-page-1/#comment-62968</link>
		<dc:creator>Daniel Lambert</dc:creator>
		<pubDate>Thu, 06 Aug 2009 18:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=3474#comment-62968</guid>
		<description>Mobile Payment to become universal must leverage from existing payment infrastructure as much as possible. Mobile Payment and NFC will therefore never be universal and as convenient as today&#039;s credit/debit cards until it becomes PCI DSS Compliant or FSTC compliant. 
</description>
		<content:encoded><![CDATA[<p>Mobile Payment to become universal must leverage from existing payment infrastructure as much as possible. Mobile Payment and NFC will therefore never be universal and as convenient as today&#8217;s credit/debit cards until it becomes PCI DSS Compliant or FSTC compliant.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

