<?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: Securing Customer Data: 7 Precautions For Accepting Credit Card&#160;Payments</title>
	<atom:link href="http://www.solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments</link>
	<description>Demystifying Web Site Development for Business-Minded People</description>
	<lastBuildDate>Fri, 31 Oct 2008 19:53:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Authorize.net shopping cart</title>
		<link>http://www.solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments/comment-page-1#comment-265</link>
		<dc:creator>Authorize.net shopping cart</dc:creator>
		<pubDate>Tue, 12 Aug 2008 19:26:46 +0000</pubDate>
		<guid isPermaLink="false">http://solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments#comment-265</guid>
		<description>Some of the bigger gateways call this feature a &quot;wallet&quot; and is beginning to handle functions that were once handled by the shopping cart including customer contact data.  In fact, his article mentions what to do if your credit card data is stored unencrypted--actually, according to PCI security standards, this should never be the case.  Oh and NEVER store or write down the CVV2 (security card code) from any credit card.  This is really only to be known by the card holder.</description>
		<content:encoded><![CDATA[<p>Some of the bigger gateways call this feature a &#8220;wallet&#8221; and is beginning to handle functions that were once handled by the shopping cart including customer contact data.  In fact, his article mentions what to do if your credit card data is stored unencrypted&#8211;actually, according to PCI security standards, this should never be the case.  Oh and NEVER store or write down the CVV2 (security card code) from any credit card.  This is really only to be known by the card holder.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff from Credit Card Fraud Forum</title>
		<link>http://www.solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments/comment-page-1#comment-264</link>
		<dc:creator>Jeff from Credit Card Fraud Forum</dc:creator>
		<pubDate>Mon, 11 Aug 2008 23:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments#comment-264</guid>
		<description>Yes, one of the biggest risks I&#039;ve heard from is when credit card numbers are stored. When the merchant processor stores the customers credit card info on their end, and allows you to access it only to make a refund. This takes a huge liability away from you now and believe me, I&#039;ve heard of someone on the forum that sued a store because they kept his credit card number on file. The other tips are vital too, but I think the mistake of storing numbers is usually what bites most people in the butt.</description>
		<content:encoded><![CDATA[<p>Yes, one of the biggest risks I&#8217;ve heard from is when credit card numbers are stored. When the merchant processor stores the customers credit card info on their end, and allows you to access it only to make a refund. This takes a huge liability away from you now and believe me, I&#8217;ve heard of someone on the forum that sued a store because they kept his credit card number on file. The other tips are vital too, but I think the mistake of storing numbers is usually what bites most people in the butt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: merchant services</title>
		<link>http://www.solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments/comment-page-1#comment-229</link>
		<dc:creator>merchant services</dc:creator>
		<pubDate>Mon, 10 Mar 2008 01:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments#comment-229</guid>
		<description>I would add the the best way to ensure you are fully compliant, secure, with 100% uptime is to choose a high qualify virtual terminal/gateway provider such as Authorize Net or Verisign PayFlow.  Anyone with a server can create a payment gateway but these companies have the necessary resources and experience to make sure date is secure, is processed 24x7x365 and both have APIs that are compatible with most shopping carts.  Do yourself a favor - pay a little more and invest in quality up front and you will avoid the headaches later on.</description>
		<content:encoded><![CDATA[<p>I would add the the best way to ensure you are fully compliant, secure, with 100% uptime is to choose a high qualify virtual terminal/gateway provider such as Authorize Net or Verisign PayFlow.  Anyone with a server can create a payment gateway but these companies have the necessary resources and experience to make sure date is secure, is processed 24&#215;7x365 and both have APIs that are compatible with most shopping carts.  Do yourself a favor &#8211; pay a little more and invest in quality up front and you will avoid the headaches later on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
