<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Solo Signal &#187; Security</title>
	<atom:link href="http://www.solosignal.com/category/security/feed" rel="self" type="application/rss+xml" />
	<link>http://www.solosignal.com</link>
	<description>Demystifying Web Site Development for Business-Minded People</description>
	<lastBuildDate>Mon, 13 Aug 2007 19:22:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Securing Customer Data: 7 Precautions For Accepting Credit Card&#160;Payments</title>
		<link>http://www.solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments</link>
		<comments>http://www.solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments#comments</comments>
		<pubDate>Mon, 09 Jul 2007 20:10:31 +0000</pubDate>
		<dc:creator>aaron</dc:creator>
				<category><![CDATA[E-Commerce]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Tips]]></category>
<category>credit cards</category><category>ecommerce</category><category>encryption</category><category>security</category><category>tips</category>
		<guid isPermaLink="false">http://solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments</guid>
		<description><![CDATA[Making the decision to accept credit card payments through your web site is a major step forward and with it comes a lot of responsibility. Rich over at Aiming for Independence has posted a great article outlining the seven actions you should take immediately if your business accepts credit cards. Here are some&#160;excerpts:
#2. Make sure [...]]]></description>
			<content:encoded><![CDATA[<p>Making the decision to accept credit card payments through your web site is a major step forward and with it comes a lot of responsibility. Rich over at <a href="http://richgilchrest.com/aim/" title="Aiming for Independence">Aiming for Independence</a> has posted a great article outlining the <a href="http://richgilchrest.com/aim/seven-actions-you-should-take-immediately-if-your-business-accepts-credit-cards/" title="Seven actions you should take immediately if your business accepts credit cards - Aiming for Independence">seven actions you should take immediately if your business accepts credit cards</a>. Here are some&nbsp;excerpts:</p>
<blockquote><p>#2. Make sure that any credit card information being transferred across the Internet is encrypted.<br />
#5. Set a short time limit on storing unencrypted customer information</p></blockquote>
<p>In addition, I would suggest that, if possible, you avoid storing users&#8217; credit card numbers all together. Often your merchant processing company will store the required information and  allow you to issue refunds with only the unique transaction identifier. This ensures that you will never be at risk of compromising your users&#8217; credit card information. Ideally your website will simply serve as a conduit for transferring payment information between the customer and the <a href="http://www.cardservicesales.com/">credit card processing</a>&nbsp;company.</p>
<a href="http://www.solosignal.com/tag/credit-cards" rel="tag">credit cards</a>, <a href="http://www.solosignal.com/tag/ecommerce" rel="tag">ecommerce</a>, <a href="http://www.solosignal.com/tag/encryption" rel="tag">encryption</a>, <a href="http://www.solosignal.com/tag/security" rel="tag">security</a>, <a href="http://www.solosignal.com/tag/tips" rel="tag">tips</a>]]></content:encoded>
			<wfw:commentRss>http://www.solosignal.com/securing-customer-data-7-precautions-for-accepting-credit-card-payments/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
