<?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>2Checkout.com &#187; credit card</title>
	<atom:link href="http://www.2checkout.com/blog/tag/credit-card/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.2checkout.com</link>
	<description>merchant account / credit card processing alternative</description>
	<lastBuildDate>Mon, 06 Feb 2012 21:37:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Clearing the Mystery of PCI Compliance (Part5)</title>
		<link>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part5/</link>
		<comments>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part5/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 14:14:55 +0000</pubDate>
		<dc:creator>bion</dc:creator>
				<category><![CDATA[2Checkout Blog]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.2checkout.com/community/?p=2661</guid>
		<description><![CDATA[Over the past four weeks we have been taking a look at becoming PCI compliant. We have set up our network, we are encrypting customer&#8217;s data, Our anti-virus program is installed and updated, and we are taking steps to make sure our network and software is secure. I feel good about this, and I think [...]]]></description>
			<content:encoded><![CDATA[<p>Over the past four weeks we have been taking a look at becoming <a href="https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml">PCI compliant</a>. We have set up our <a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-1">network</a>, we are <a href="http://www.2checkout.com/blog/2checkout-blog/e-commerce/clearing-the-mystery-of-pci-compliance-part-2">encrypting customer&#8217;s data</a>, Our anti-virus program is <a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-3">installed and updated</a>, and we are taking steps to make sure our <a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-4">network and software is secure</a>. I feel good about this, and I think we have learned some useful information. Now, we will <a href="http://www.pci-portal.com/knowledge-centre/pci-control-objectives/access-control-measures/">Implement Strong Access Control Measures</a>:</p>
<ol>
<li><strong>Requirement 7: Restrict access to cardholder data by business need-to-know</strong></li>
<li><strong>Requirement 8: Assign a unique ID to each person with computer access</strong></li>
<li><strong>Requirement 9: Restrict physical access to cardholder data</strong></li>
</ol>
<p>Here we look over who has access to customer&#8217;s information and the computers that store this information. Like many people starting an Internet business, our business computer is also used for recreation. This can pose a problem if friends or family also use our computer. The safest measure is to have a dedicated system used for processing and storing cardholder information. Let&#8217;s look at using our existing computer and how we can make this compliant.</p>
<p><span id="more-2661"></span>We need to investigate who needs access to customer information. In our example, I will be the only one who needs to access customer information, so it will be simple. In some cases we may have a business partner or, if we expand as I hope, an employee or two. These people will probably need some access to customer information, so we need to figure out who needs what data to perform their job. The person answering customer service questions may need to know our customer&#8217;s name and address, but do they need to know any part of the credit card number? What information will be needed for accounting or systems administration? This is the time to decide who has access to what information. We need to record these policies and keep written authorization for individual access to specific data.</p>
<p>While we have reason to be aware of external threats, we need to be just as secure internally. We need a system of <a href="http://www.intranetjournal.com/articles/200311/ij_11_10_03a.html">access control</a> that identifies which users have access to information, systems, resources, and which identifies the user who accessed or changed the information. This allows us to protect our customers&#8217; data from internal security leaks. Employee theft and fraud are very real crimes and Internet businesses are certainly not immune.</p>
<p>In order to be able to track who is accessing our resources, we need to assign unique logins for everyone who will use our computer. Using the access control we implemented above, these logins will allow different access to stored data. In our case, I have full access while other logins have no access (until I get a partner or employee). We can&#8217;t have any group or general logins. My initial idea of having a &#8220;Me&#8221; login with full access and a &#8220;You&#8221; login with no access will not work. Strict compliance means that each person who uses the computer needs to have a distinct username and password.</p>
<p>Speaking of passwords, we need to change the passwords every three months, a password cannot be reused for a year, the password needs to be at least seven characters long, and needs to a combination of numbers and letters (special characters increase the security of a password). Our passwords also need encrypted and we need to limit the number of user login attempts. Let&#8217;s set this to 5 attempted logins. If a login is failed 5 times we need to lock the username for at least 30 minutes, or administrator reset.</p>
<p>Physical access to credit card information needs to also be restricted and monitored. We need to have cameras recording any area that hold sensitive data, like our office. These recording need to be kept for a minimum of 3 months. Physical access to the office will need to be restricted. In our situation, we can use a locked door and a key. Access to the key will need to closely monitored and logged. Physical documentation of card holder data needs to be secured. This is independent of other security, so a safe or locked file cabinet. When the information is not needed for business purposes, it must be destroyed. Paper shredders are probably the most common and safest method of destroying the documents, but burning and pulping the data is compliant. Electronic data will need to be purged from our systems as well.</p>
<p>As we work on this portion of PCI DSS compliance, I found that we are making a number of small purchases to meet the requirements. There are a number of companies that sell computer access control programs for a reasonable amount of money for one or two computers. The larger expenses are going to be a new key less lock for the office door, a closed circuit camera set, a file cabinet. I guess I&#8217;m off to the local office supply store.</p>
<p><em><strong>Bottom Line for Step 5:</strong></em></p>
<p><strong>Cost:</strong></p>
<ul>
<li>Key less locks $200-$350</li>
<li>Locking file cabinets $200-$500</li>
<li>Camera system with 3 month storage $300-$600</li>
<li>Security software $50-$75 per computer renewed each year.</li>
</ul>
<p><strong><br />
</strong></p>
<p><strong>Further Reading:</strong></p>
<p><a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-1">Clearing the Mystery of PCI Compliance (Part 1)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/e-commerce/clearing-the-mystery-of-pci-compliance-part-2">Clearing the Mystery of PCI Compliance (Part 2)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-3">Clearing the Mystery of PCI Compliance (Part 3)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-4">Clearing the Mystery of PCI Compliance (Part 4)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part6">Clearing the Mystery of PCI Compliance (Part 6)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part7">Clearing the Mystery of PCI Compliance (Part 7)</a> <em><br />
</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Clearing the Mystery of PCI Compliance (Part 3)</title>
		<link>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-3/</link>
		<comments>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-3/#comments</comments>
		<pubDate>Fri, 20 Nov 2009 14:14:45 +0000</pubDate>
		<dc:creator>bion</dc:creator>
				<category><![CDATA[2Checkout Blog]]></category>
		<category><![CDATA[anti-virus]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[policy]]></category>

		<guid isPermaLink="false">http://www.2checkout.com/community/?p=2556</guid>
		<description><![CDATA[We are at the half-way mark in becoming PCI Compliant. We took a little break for Fraud Awareness Week and now we are ready to &#8220;Maintain a Vulnerability Management System&#8221;. Our previous efforts have been focused on Building and Maintaining a Secure Network and Protecting Cardholder Data. We now have a firewall, clear policies regarding [...]]]></description>
			<content:encoded><![CDATA[<p>We are at the half-way mark in becoming <a href="https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml">PCI Compliant</a>. We took a little break for <a href="http://www.2checkout.com/blog/knowledge-base/suppliers/fraud-bank-assisted-disputes-chargebacks/international-fraud-awareness-week-november-8-14-2009">Fraud Awareness Week</a> and now we are ready to &#8220;Maintain a Vulnerability Management System&#8221;. Our previous efforts have been focused on <a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-1">Building and Maintaining a Secure Network</a> and <a href="http://www.2checkout.com/blog/2checkout-blog/e-commerce/clearing-the-mystery-of-pci-compliance-part-2">Protecting Cardholder Data</a>. We now have a firewall, clear policies regarding the type of information we will store, and the length of time we will store it. We even have encryption software and an <a href="http://www.webopedia.com/TERM/S/SSL.html">SSL</a> certificate. Congratulations!</p>
<p>Now, we need to Maintain a Vulnerability Management Program. This comes in two parts. First, we need to use and regularly update anti-virus software. Then, we have to develop and maintain secure systems and applications. I know what anti-virus software is, so let&#8217;s start there.</p>
<p><a href="http://www.pcworld.com/businesscenter/article/172438/pci_survey_finds_some_merchants_dont_use_antivirus_software.html"><span id="more-2556"></span>Before we look into AV software</a>, I want to give one bit of basic Internet advice. If you don&#8217;t know/trust a person or site &#8211; don&#8217;t download ANYTHING they send you if you don&#8217;t have AV protection. <a href="http://www.pc1news.com/news/0544/how-you-catch-a-computer-virus.html">The most common method of catching a computer virus is still from opened email attachments</a>. Most people have some anti-virus (AV) protection for their computers, but to be PCI compliant, we need to look into software that will protect every computer and device connected to the Internet through our network.</p>
<p>There are a number of companies that make anti-virus software, compile virus databases, and offer frequent updates. Most of these companies have PCI compliant versions of their software. The standard single-PC software will cost $50 &#8211; $75 for a year&#8217;s worth of automatic updates. Unfortunately, this level of protection, while typically excellent for home users, will not meet PCI compliance. Part of the reason for this is that PCI compliance requires that your AV software be able to monitor and generate reports detailing what viruses it has caught/contained. We need to look at the more robust offerings for business networks. The range of prices in this field is vast from $350 &#8211; nearly $3,000 yearly. The top end software is really more of an anti-virus &#8220;system&#8221; that protects mainframes and large networks, so we can breathe a sigh of relief and look a little lower on the price points. For covering a network with a few devices for one year, including unlimited updates, and support, the average cost settles in at about $500-$700.</p>
<p>The next standard, &#8220;Develop and Maintain Secure Systems and Applications&#8221;, requires a little more than picking anti-virus software that will meet your needs. Looking at the <a href="http://www.pciforum.us/pci/Requirement6/tabid/91/Default.aspx">requirements</a> to meet this standard, it becomes obvious that we either need to know our way around a network, or we need to get our networking expert back to test our network after each update, make sure that we have a separate part of the network used only for testing applications, and system monitors that watch our network. Because of the scope of this requirement, the next article will be devoted to addressing the various aspects of maintaining the security of our systems and applications.</p>
<p><strong>Further Reading:</strong></p>
<p><a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-1">Clearing the Mystery of PCI Compliance (Part 1)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/e-commerce/clearing-the-mystery-of-pci-compliance-part-2">Clearing the Mystery of PCI Compliance (Part 2)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-4">Clearing the Mystery of PCI Compliance (Part 4)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part5">Clearing the Mystery of PCI Compliance (Part 5)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part6">Clearing the Mystery of PCI Compliance (Part 6)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part7">Clearing the Mystery of PCI Compliance (Part 7)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Clearing the Mystery of PCI Compliance (Part 1)</title>
		<link>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-1/</link>
		<comments>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-1/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 22:20:38 +0000</pubDate>
		<dc:creator>bion</dc:creator>
				<category><![CDATA[2Checkout Blog]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.2checkout.com/community/?p=2157</guid>
		<description><![CDATA[This is the first is a twelve-part series detailing what is involved with PCI compliance. Earlier, Warner gave a very good overview of PCI DSS compliance. &#8220;PCI DSS (Payment Card Industry Data Security Standard) is a security standard that applies to companies handling credit card numbers. The PCI level of enforcement differs based on the [...]]]></description>
			<content:encoded><![CDATA[<p>This is the first is a twelve-part series detailing what is involved with PCI compliance. Earlier, Warner gave a <a href="http://www.2checkout.com/blog/2checkout-blog/small-ecommerce-sites-facing-fines-if-compromised">very good overview </a>of PCI DSS compliance.</p>
<blockquote><p>&#8220;PCI DSS (<a href="https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml">Payment Card Industry Data Security Standard</a>) is a security standard that applies to companies handling credit card numbers. The <a href="http://usa.visa.com/merchants/risk_management/cisp_merchants.html">PCI level of enforcement</a> differs based on the volume of transactions that a company handles.&#8221;</p></blockquote>
<p>My purpose with this series is to provide the details involved in each requirement. I want to look at this from the point of view of a very small home-based business with a website selling tangible products.</p>
<p><span id="more-2157"></span>The first requirement for PCI DSS is to have a secure environment to hold credit card data:</p>
<p><strong>1) Install and maintain a firewall configuration to protect cardholder data<br />
2) Do not use vendor-supplied defaults for system passwords and other security parameters</strong></p>
<p>First, we need to make our connection to the Internet as safe and secure as we can. This involves using a  form of protection. The most common example of this is a <a href="http://www.techterms.com/definition/firewall">firewall</a>. A <a href="http://www.techterms.com/definition/router">router</a> is probably the most common device used. This will protect a network from unauthorized connections as well as keep a log of network activity.</p>
<p>A basic home use router can cost roughly $50-100+. However, as we will see in future articles in this series, these routers will not be able to provide the level of protection required to collect customer information. Based on my research, the cost of a compliant router starts at about $200 and can run into the thousands of dollars. There are significant differences between routers, and some of the more costly routers come with additional security packages from the manufacturer that includes network/technical support. Researching what router is going to work for your business is important. The firewall you choose will depend on a number of factors that only you can determine. It is important to note that laptops require a separate security device when used away from the home, and Internet cafe&#8217;s will not have nearly the security required for PCI DSS compliance.</p>
<p>Along with the router, we will need to have it connected to the network. Networking is a highly specialized, highly technical field. When was the last time you could remember terms like &#8220;internal IP address,&#8221; &#8220;network diagram,&#8221; and &#8220;network segmentation&#8221;  used in casual conversation? Since this is something that is critical to the ability to process credit cards, we want to be sure that the router (and the rest of the network) is as secure as it can be. This means we will have to pay someone who can create and manage the network. Thankfully, there are a number of people who are willing to do so. Alternately, at an additional cost, most router manufacturers will provide support and security update services. The cost for an independent networking freelancer will vary greatly from area to area (In my case, I would need to make sure I had $800-$1,000 to cover this expense).</p>
<p>Once we have the network all set up we will have to reset the username and password of the firewall. During the initial setup and testing, the device will have a preset password and username. This allows for easy troubleshooting for the manufacturer&#8217;s technical support. Since all of the devices by one manufacturer will have the same defaults, it is very important that this is changed before credit cards are accepted.</p>
<p><em><strong>Bottom Line for Step 1:</strong></em></p>
<p><strong>Time:</strong></p>
<ul>
<li> Research on the best firewall for your individual needs.</li>
<li> Research on availability of either manufacturer-provided or independent networking assistance</li>
</ul>
<p><strong>Costs:</strong></p>
<ul>
<li> Router: $200 &#8211; $3000 for the router. ($500-$800 is the average for the device alone)</li>
<li> Support: Additional security features/support (varies from company to company, $200 seems average)</li>
<li> Networking: Free if you already know how to do this.</li>
<li> $100 &#8211; $149 basic charge with $100/hour fee for additional support  (Varies from place to place, but $100 looks to be the low end of average) assuming a full day&#8217;s work minimum.</li>
</ul>
<p>We have just bought a router, hired someone to make sure our network is secure and spent roughly $1,000-$2,000. Now we have 10 more standards to meet before we are PCI compliant. Over the next few weeks we will explore topics ranging from data encryption to network monitoring, as well as realistically detail the costs associated with meeting all twelve PCI standards.</p>
<p><strong>Further Reading:</strong></p>
<p><a href="http://www.2checkout.com/blog/2checkout-blog/e-commerce/clearing-the-mystery-of-pci-compliance-part-2">Clearing the Mystery of PCI Compliance (Part 2)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-3">Clearing the Mystery of PCI Compliance (Part 3)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-4">Clearing the Mystery of PCI Compliance (Part 4)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part5">Clearing the Mystery of PCI Compliance (Part 5)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part6">Clearing the Mystery of PCI Compliance (Part 6)</a><br />
<a href="http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part7">Clearing the Mystery of PCI Compliance (Part 7)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/2checkout-blog/clearing-the-mystery-of-pci-compliance-part-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Can I have Credit Card logos on my Site or Cart?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/basic-integration/can-i-have-credit-card-logos-on-my-site-or-cart/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/basic-integration/can-i-have-credit-card-logos-on-my-site-or-cart/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Basic Integration]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[logo]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/can-i-have-credit-card-logos-on-my-site-or-cart/</guid>
		<description><![CDATA[If you are going to use a picture of a credit card or a credit card company logo on your web site, it must be clearly and immediately adjacent to the phrase &#8220;2Checkout.com is an authorized retailer for (your business name.)&#8221; Per Credit Card Association Rules, unless your company has a direct business relationship with [...]]]></description>
			<content:encoded><![CDATA[<p>If you are going to use a picture of a credit card or a credit card company logo on your web site, it must be clearly and immediately adjacent to the phrase &#8220;2Checkout.com is an authorized retailer for (your business name.)&#8221;   Per Credit Card Association Rules, unless your company has a direct business relationship with the credit card company and is authorized to display the credit card or the logo, the image must be removed from your web site.</p>
<p>Credit card association rules state that only a merchant account holder may display credit card logos on their websites. 2CO does not provide you with a merchant account. You can continue to display these logos, as long as immediately above, beside, or below the logos, there is a clear statement that 2CO is your authorized retailer.</p>
<p>Alternatively, you can display the logos shown here. Right click on the image of your choice below and choose &#8220;Save Picture as&#8230;&#8221; to save as a file on your computer.</p>
<p><img src="/wp-content/plugins/db_image_manager.php?image_id=80" alt="2Checkout.com" /></p>
<p><img src="/wp-content/plugins/db_image_manager.php?image_id=81" alt="2Checkout.com" /></p>
<p><img src="/wp-content/plugins/db_image_manager.php?image_id=82" alt="2Checkout.com" /></p>
<p>Please also see <a href="http://www.2checkout.com/blog/knowledge-base/tech-support/basic-integration/2co-certified/">2CO Certified</a> for &#8220;2CO Certified Seller&#8221; buttons.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/basic-integration/can-i-have-credit-card-logos-on-my-site-or-cart/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

