<?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>Approved Payments &#187; Combatting fraud</title>
	<atom:link href="http://approvedpayments.com/combatting-fraud/feed" rel="self" type="application/rss+xml" />
	<link>http://approvedpayments.com</link>
	<description>Payment Solutions for Your Business</description>
	<lastBuildDate>Fri, 14 May 2010 14:56:27 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What is PCI? Do I need it?</title>
		<link>http://approvedpayments.com/what-is-pci-do-i-need-it.html</link>
		<comments>http://approvedpayments.com/what-is-pci-do-i-need-it.html#comments</comments>
		<pubDate>Fri, 13 Mar 2009 14:40:01 +0000</pubDate>
		<dc:creator>ann</dc:creator>
				<category><![CDATA[Combatting fraud]]></category>
		<category><![CDATA[Merchant Guide]]></category>
		<category><![CDATA[cardholder data]]></category>
		<category><![CDATA[payment card industry]]></category>
		<category><![CDATA[payment security]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[PCI compliance]]></category>

		<guid isPermaLink="false">http://approvedpayments.com/?p=261</guid>
		<description><![CDATA[PCI stands for Payment Card Industry&#8211;the term is normally used in the context of PCI compliance, which means that a merchant or payment processor conforms to the security standards set by the Payment Card Industry Security Standards Council (PCI SSC).
These security standards were created to help prevent credit card fraud and hacking and to help protect against other security [...]]]></description>
			<content:encoded><![CDATA[<p><strong><span class="drop">P</span>CI </strong>stands for Payment Card Industry&#8211;the term is normally used in the context of PCI compliance, which means that a merchant or payment processor conforms to the security standards set by the Payment Card Industry Security Standards Council (PCI SSC).</p>
<p><img class="alignright size-full wp-image-460" title="what-is-pci" src="http://approvedpayments.com/wp-content/uploads/2009/06/what-is-pci.jpg" alt="Payment security" width="370" height="246" />These security standards were created to help prevent credit card fraud and hacking and to help protect against other security threats that a merchant or payment processor might face.</p>
<h3>Does PCI apply to my business?</h3>
<p>If your business accepts credit cards, then yes, you must comply with the PCI standards. Anytime anyone stores, processes or transmits credit card data, the standards apply.</p>
<h3>What if I don&#8217;t comply with PCI standards?</h3>
<p>According to the <a href="http://www.pcicomplianceguide.org/pcifaqs.php#11"><strong>PCI Compliance Guide</strong></a>:</p>
<blockquote><p>&#8220;The payment brands may, at their discretion, fine an acquiring bank $5,000 to $100,000 per month for PCI compliance violations. The banks will most likely pass this fine on downstream till it eventually hits the merchant. Furthermore, the bank will also most likely either terminate your relationship or increase transaction fees.  Penalties are not openly discussed nor widely publicized, but they can be catastrophic to a small business. &#8221;</p></blockquote>
<h3>What&#8217;s involved in PCI compliance?</h3>
<p>There are four different levels of PCI compliance:</p>
<ul>
<li><strong>Level 1 PCI compliance</strong> is the most intense and expensive level to maintain. Level 1 PCI compliant companies are very large companies who process more than 6 million major credit card transactions per year. Payment gateways (e.g., Intellivative, PayPal, Verisign, Cybersource, etc.) and other payment solution providers typically are subject to this level of scrutiny.
<ul>
<li>Level 1 PCI certification requires an annual on-site security audit and quarterly system perimeter scans.</li>
<li>If you are a large merchant who outsources their payment processing to a Level 1 PCI compliant company (like Intellivative), the effort required to validate compliance may be significantly reduced.</li>
<li>ApprovedPayments is a sales outlet for <a href="http://intellivative.com/">Intellivative Payment Solutions</a>. Intellivative consistently <a href="http://intellivative.com/data-security/">maintains Level 1 Compliance </a>and offers cardholder data management features to minimize clients&#8217; exposure to risk and greatly reduce the expense associated with validating compliance.</li>
</ul>
</li>
<li><strong>Level 2 PCI compliance</strong> applies to merchants who process 150,000 to 6,000,000 major credit card company transactions per year. Level 2 compliance typically requires quarterly system perimeter scans and an annual compliance questionnaire (unless you employ a payment processor who is Level 1 Compliant).</li>
<li><strong>Level 3</strong> PCI compliance is for merchants who process 20,000 to 1 million eCommerce transactions per year.</li>
<li><strong>Level 4</strong> is for merchants who process less than 20,000 eCommerce transactions each year or who process up to 1 million transactions per year.</li>
</ul>
<p>Regardless of size, any company that has had a security incidence may be subject to a higher level of compliance.</p>
<h3>If I outsource my payment processing, I&#8217;m covered, right?</h3>
<p>Not entirely. Outsourcing simplifies the process, but it doesn&#8217;t mean you&#8217;re automatically PCI compliant. You will still need to have sound policies and procedures for cardholder transactions and data processing and storage. Your business policies should cover how to protect cardholder data, and how to process charge backs and refunds. Also, make sure ALL the vendors that have access to sensitive cardholder data are PCI compliant, including your gateway, your shopping cart, your credit card terminal, etc.</p>
<h3>Where can I learn more about PCI?</h3>
<ul>
<li>Visit the <a href="https://www.pcisecuritystandards.org/"><strong>PCI Security Standards Council</strong></a></li>
<li>See the <a href="http://www.pcicomplianceguide.org/pcifaqs.php"><strong>PCI FAQs and Myths</strong></a> on PCI Compliance Guide</li>
<li>Register for the <a href="http://www.pciknowledgebase.com/"><strong>PCI Knowledge Base</strong></a></li>
<li>Review the <a href="http://usa.visa.com/merchants/risk_management/cisp.html"><strong>Visa</strong></a>Â®Â or <a href="http://www.mastercard.com/us/sdp/index.html"><strong>Mastercard</strong></a>Â® payment data security information</li>
</ul>
<h3>Is ApprovedPayments PCI Compliant?</h3>
<p>ApprovedPayments is a sales outlet for <a href="http://intellivative.com/payment-solutions/"><strong>Intellivative Payment Solutions</strong></a>, which are fully PCI Level 1 compliant.</p>
<p> </p>
<p><a href="http://approvedpayments.com/apply-now/"><strong>Apply today for a no-obligation quote</strong></a> for our PCI Level 1 compliant solutions. <a class="open" title="Apply Now" href="http://approvedpayments.com/apply-now/"></a></p>
]]></content:encoded>
			<wfw:commentRss>http://approvedpayments.com/what-is-pci-do-i-need-it.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to combat fraud? 5 tips</title>
		<link>http://approvedpayments.com/how-to-combat-fraud-5-tips.html</link>
		<comments>http://approvedpayments.com/how-to-combat-fraud-5-tips.html#comments</comments>
		<pubDate>Fri, 27 Feb 2009 20:24:06 +0000</pubDate>
		<dc:creator>ann</dc:creator>
				<category><![CDATA[Combatting fraud]]></category>
		<category><![CDATA[credit card fraud]]></category>
		<category><![CDATA[fraud]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[merchant]]></category>
		<category><![CDATA[protect]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://approvedpayments.com/?p=102</guid>
		<description><![CDATA[Depending on your business practices (and your business type), fraud can sometimes leave a significant dent in your business finances. Some businesses are more prone to payment fraud than others&#8211;eCommerce businesses, for example, are at a higher risk of fraud because of the anonymous nature of the Internet.
Fraudulent orders can cost your business:

the cost of [...]]]></description>
			<content:encoded><![CDATA[<p><span class="drop">D</span>epending on your business practices (and your business type), fraud can sometimes leave a significant dent in your business finances. Some businesses are more prone to payment fraud than others&#8211;eCommerce businesses, for example, are at a higher risk of fraud because of the anonymous nature of the Internet.</p>
<p><img class="alignright" style="margin: 8px;" title="The cost of merchant fraud" src="http://approvedpayments.com/images/cost-of-fraud.jpg" alt="" width="260" height="364" />Fraudulent orders can cost your business:</p>
<ul>
<li>the cost of the goods</li>
<li>any shipping costs incurred</li>
<li>cost of the employee&#8217;s time to process the chargeback</li>
<li>the chargeback fee</li>
</ul>
<p>Before you decide fighting fraud is important, however, consider what a fraudulent order costs your business vs. how much you make on each sale. If you are shipping physical merchandise where the cost of goods sold is significant, fraudulent orders are going to be more painful for you and fraud management is more important. On the other hand, if you are a business that offers an intangible product or service like music downloads, a fraudulent order may not cost you much. If the cost of a fraudulent order is negligible compared to what it would cost you to lose a legitimate sale, you may not want to worry so much about chargebacks and fraud. <a href="http://www.scmagazineus.com/Optimizing-fraud-Yes-there-is-a-silver-lining/article/109745/"><strong>Security magazine offers an excellent article</strong> </a>detailing this principle.</p>
<p>But if fraud is hurting your business, you can take measures to fight fraud using these five tips:</p>
<ol>
<li><strong>Process securely&#8211;and show it!</strong> If you&#8217;re processing payments over the internet, make sure your web site uses secure sockets layer (SSL) protection. SSL helps protect credit card numbers from being stolen en route.
<ol>
<li>On every web page where you request sensitive information like credit card numbers, make sure your web address (URL) begins with <strong>http<span style="color: #ff0000;">s</span>. </strong>Check for the lock symbol on the browser, too. These are the key things that eCommerce shoppers should be on the lookout for as they shop on your site.</li>
<li><strong>Show </strong>your visitors in a clear and noticeable manner <strong>how secure your web site is</strong>, particularly on checkout pages. This doesn&#8217;t help prevent fraud, per se, but can make a big difference in your online sales.
<ul>
<li>Consider using a security certificate on your web site that has enhanced security features, like the <a href="http://www.verisign.com/ssl/buy-ssl-certificates/extended-validation-ssl-certificates/index.html"><strong>extended validation (EV) certificate from Verisign</strong></a>. With this type of certificate, if the online shopper on your eCommerce site is using a newer browser, the address bar will turn green indicating your site is secure and safe to be trusted. It helps boost trust and increase sales.</li>
<li>Believe it or not, the usability of  your web site and a professional design affect how shoppers perceive the security of your site. If your site is usable, and the design is clean, users are more likely to trust it over a shoddy designed site with usability issues.</li>
</ul>
</li>
</ol>
</li>
<li><strong>Use address verification &amp; CVV Code</strong>, but <strong>consider other factors as well</strong> before rejecting orders
<ol>
<li>Watch for suspicious purchasing patterns. Small initial purchases, followed by very large purchases, for example, can be a sign of fraud. In the initial purchase, they are &#8220;testing&#8221; the card to see if it works.</li>
</ol>
</li>
<li> <strong>Be careful when handling customer data</strong>
<ol>
<li>The cost of stolen customer data can be great, especially when you consider the damage to your business reputation. Handle sensitive cardholder data with special care&#8211;and don&#8217;t store anything more than you have to.</li>
<li><a href="http://approvedpayments.com/what-is-pci-do-i-need-it/"><strong>PCI compliance</strong></a>&#8211;yes, you really do need to be payment card industry compliant. PCI guidelines were made to help merchants combat fraud.</li>
<li>The cost of PCI violations can be big, so make sure you are PCI compliant.</li>
</ol>
</li>
<li><strong>Use a payment gateway</strong>
<ol>
<li>A gateway provides quick, easy access to transaction detail</li>
<li>A payment gateway automatically handles the payment processing in a secured manner</li>
</ol>
</li>
<li><strong>When you get a chargeback</strong>:
<ol>
<li>Dispute whatever you can reasonably prove. If you have evidence that a chargeback is not justified, go ahead and send it in.</li>
<li>If you have a recurring business, immediately shut down recurring payments associated with chargebacks. It&#8217;s hard to prove you were justified to continue charging a customer after they&#8217;ve submitted a chargeback. Save yourself the hassle and cancel the recurring payment right away.</li>
<li>Don&#8217;t rely on reason codes alone. Make sure you investigate your chargebacks and know what happened.</li>
</ol>
</li>
</ol>
<p>Most importantly, make sure your payments provider is PCI compliant.</p>
<p>ApprovedPayments offers payment solutions via Intellivative, a PCI Level 1 Compliant provider.  <a href="http://approvedpayments.com/apply-now/"><strong>Apply today for a no-obligation quote</strong></a>, and see how our PCI compliant solutions can help your business combat fraud. <a title="Apply Now" href="http://approvedpayments.com/apply-now/"></a></p>
<p><a title="Apply Now" href="http://approvedpayments.com/apply-now/"> </a></p>
<p> </p>
<p><a title="Apply Now" href="http://approvedpayments.com/apply-now/"></a></p>
]]></content:encoded>
			<wfw:commentRss>http://approvedpayments.com/how-to-combat-fraud-5-tips.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
