<?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: Merchants Struggle to Comply With PCI Security</title>
	<atom:link href="http://www.merchant911.org/blog/index.php/2009/06/29/merchants-struggle-to-comply-with-pci-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.merchant911.org/blog/index.php/2009/06/29/merchants-struggle-to-comply-with-pci-security/</link>
	<description>Comments on credit card fraud from the E-Commerce Merchant point of view by Tom Mahoney, Founder and Director of Merchant911.org</description>
	<lastBuildDate>Thu, 02 Sep 2010 16:46:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Lydie</title>
		<link>http://www.merchant911.org/blog/index.php/2009/06/29/merchants-struggle-to-comply-with-pci-security/comment-page-1/#comment-2135</link>
		<dc:creator>Lydie</dc:creator>
		<pubDate>Wed, 01 Jul 2009 08:40:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchant911.org/blog/?p=383#comment-2135</guid>
		<description>I don&#039;t collect any cc data on site. That is done by a third party processor on their website. Since I process very few cc transactions a year, I confess I have basically ignored the PCI developments till now. Sounds like a lot of hassle for unquantifiable usefulness. 

However you have convinced me of the need to check it out.

Thanks Tom for keeping us informed.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t collect any cc data on site. That is done by a third party processor on their website. Since I process very few cc transactions a year, I confess I have basically ignored the PCI developments till now. Sounds like a lot of hassle for unquantifiable usefulness. </p>
<p>However you have convinced me of the need to check it out.</p>
<p>Thanks Tom for keeping us informed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.merchant911.org/blog/index.php/2009/06/29/merchants-struggle-to-comply-with-pci-security/comment-page-1/#comment-2133</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 30 Jun 2009 11:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchant911.org/blog/?p=383#comment-2133</guid>
		<description>It&#039;s working for me here.</description>
		<content:encoded><![CDATA[<p>It&#8217;s working for me here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lenito</title>
		<link>http://www.merchant911.org/blog/index.php/2009/06/29/merchants-struggle-to-comply-with-pci-security/comment-page-1/#comment-2131</link>
		<dc:creator>Lenito</dc:creator>
		<pubDate>Tue, 30 Jun 2009 06:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchant911.org/blog/?p=383#comment-2131</guid>
		<description>Tom,
  The .pdf file for the feedbacks is not working. This is what I&#039;ve got when I clicked it.

&quot;The file is damaged and could not be repaired.&quot;</description>
		<content:encoded><![CDATA[<p>Tom,<br />
  The .pdf file for the feedbacks is not working. This is what I&#8217;ve got when I clicked it.</p>
<p>&#8220;The file is damaged and could not be repaired.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
