<?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>SekureCard merchant payment services blog &#187; compliance</title>
	<atom:link href="http://blog.sekurecardservices.com/tag/compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sekurecardservices.com</link>
	<description></description>
	<lastBuildDate>Wed, 26 Sep 2012 15:43:38 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4</generator>
		<item>
		<title>PCI DSS security standards</title>
		<link>http://blog.sekurecardservices.com/credit-card-processing/pci-dss-security-standards/</link>
		<comments>http://blog.sekurecardservices.com/credit-card-processing/pci-dss-security-standards/#comments</comments>
		<pubDate>Fri, 06 Jul 2012 16:52:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Accepting Credit Cards]]></category>
		<category><![CDATA[Authorize.net]]></category>
		<category><![CDATA[Credit Card Processing]]></category>
		<category><![CDATA[Credit Card Terminals]]></category>
		<category><![CDATA[PCI Compliance]]></category>
		<category><![CDATA[Process Credit Cards]]></category>
		<category><![CDATA[Sekure Card Services Helps Merchants Avoid scams]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[DSS]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Sekure Card Services]]></category>

		<guid isPermaLink="false">http://blog.sekurecardservices.com/?p=742</guid>
		<description><![CDATA[PCI DSS (Payment Card Industry Data Security Standard) was established, and on 15 December 2004 and was initiated to define, on behalf of card issuers, the level of security required for merchants to meet basic acceptable level of data and communication security when storing and transmitting cardholder data. The Security Standards Council defined the standard to provide better data security&#160;<a href="http://blog.sekurecardservices.com/credit-card-processing/pci-dss-security-standards/" class="read-more">Continue Reading</a>]]></description>
			<content:encoded><![CDATA[<div class="bottomcontainerBox" style="border:1px solid #808080;background-color:#F0F4F9;">
			<div style="float:left; width:85px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fblog.sekurecardservices.com%2Fcredit-card-processing%2Fpci-dss-security-standards%2F&amp;layout=button_count&amp;show_faces=false&amp;width=85&amp;action=like&amp;font=verdana&amp;colorscheme=light&amp;height=21" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:85px; height:21px;"></iframe></div>
			<div style="float:left; width:80px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<g:plusone size="medium" href="http://blog.sekurecardservices.com/credit-card-processing/pci-dss-security-standards/"></g:plusone>
			</div>
			<div style="float:left; width:95px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<a href="http://twitter.com/share" class="twitter-share-button" data-url="http://blog.sekurecardservices.com/credit-card-processing/pci-dss-security-standards/"  data-text="PCI DSS security standards" data-count="horizontal"></a>
			</div><div style="float:left; width:105px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;"><script type="in/share" data-url="http://blog.sekurecardservices.com/credit-card-processing/pci-dss-security-standards/" data-counter="right"></script></div>			
			<div style="float:left; width:85px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;"><script src="http://www.stumbleupon.com/hostedbadge.php?s=1&amp;r=http://blog.sekurecardservices.com/credit-card-processing/pci-dss-security-standards/"></script></div>			
			</div><div style="clear:both"></div><div style="padding-bottom:4px;"></div><p><span style="color: #000000;">PCI DSS (Payment Card Industry Data Security Standard) was established, and on 15 December 2004 and was initiated to define, on behalf of card issuers, the level of security required for merchants to meet basic acceptable level of data and communication security when storing and transmitting cardholder data.</span></p>
<p><span style="color: #000000;">The Security Standards Council defined the standard to provide better data security protecting against credit card fraud. Compliance is very expensive and as well as the costs of the annual mandatory validation by a QSA (Qualified Security Assessor) for organizations handling large amounts of card transactions.</span></p>
<p><span style="color: #000000;">So many companies turn to third party PCI compliant payment providers like 2checkout or 1<sup>st</sup> Americard to simplify the integration of payments services with their organization. These PCI compliant services offer their platform as a service for a fee, that that make up the costs the merchants must absorb that makeup the complex set of rates, rates that are part of accepting credit card and debit card payments today.</span></p>
<p><span style="color: #000000;">Although the integration with these compliant third party providers shield the businesses from formal validation and compliance of the PCI DSS standards there are still some security associated with the handling of credit cards that must be implemented by businesses and the personnel responsible In the handling of credit cards and the information that are on these cards.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.sekurecardservices.com/credit-card-processing/pci-dss-security-standards/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
