<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><entry xmlns='http://www.w3.org/2005/Atom' xmlns:georss='http://www.georss.org/georss'><id>tag:blogger.com,1999:blog-5803106625832520676.post-7953663811276202896</id><published>2009-03-15T14:13:00.000-07:00</published><updated>2009-05-09T08:47:14.869-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='pci'/><category scheme='http://www.blogger.com/atom/ns#' term='payment card industry'/><category scheme='http://www.blogger.com/atom/ns#' term='credit card processing'/><category scheme='http://www.blogger.com/atom/ns#' term='pci compliance'/><title type='text'>How to make your software application PCI compliant.</title><content type='html'>If your a developer who maintains a software application that accepts credit card payments you may be wondering how to make your program &lt;a href="http://www,paymentcardindustry.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;PCI&lt;/span&gt;&lt;/span&gt; compliant.&lt;/a&gt; Your not alone, every piece of software that accepts credit card payments or stores credit card numbers is now forced to become &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;PCI&lt;/span&gt;&lt;/span&gt; complaint or be fined. &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;PCI&lt;/span&gt;&lt;/span&gt; or the Payment Card Industry regulates the storing and transmission of credit card numbers.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Your options&lt;/strong&gt;&lt;br /&gt;There are two ways to become &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;PCI&lt;/span&gt;&lt;/span&gt; compliant.&lt;br /&gt;1. Subject your software application to a &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;PCI&lt;/span&gt;&lt;/span&gt; audit. Representatives from the Payment Card Industry will review your application and make recommendations for the storage and transmission of credit card data. The audit will be intensive and costly and will need to be redone annually.&lt;br /&gt;2. Rework your application to stop the storage and transmission of credit card numbers. At first this sounds &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_5"&gt;foreign&lt;/span&gt; but read on.&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;Removing the storage and transmission of credit card numbers from your application.&lt;/strong&gt;&lt;br /&gt;Lets say for example you have a software application that accepts rent. Landlords use it on their desktop computers. They select a renter and charge their credit card.&lt;br /&gt;We need to remove the portion that stores the credit card and replace it with a payment token. The token is generated when the landlord enters the credit card on a &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;PCI&lt;/span&gt; certified site from your payment processor. Once you have the token you can store it in your application instead of the credit card number. When your ready to charge the renter you send the token along with the amount. Its that simple, your now &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;PCI&lt;/span&gt; complaint.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;PCI&lt;/span&gt; &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_8"&gt;compliance&lt;/span&gt; in a few steps.&lt;/strong&gt;&lt;br /&gt;It doesn't have to cost a fortune to become &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;PCI&lt;/span&gt; compliant just a small change your application can make all the difference. Often the change can be made in a way that your customers won't even notice.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5803106625832520676-7953663811276202896?l=www.acceptpayments.org' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://www.acceptpayments.org/feeds/7953663811276202896/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=5803106625832520676&amp;postID=7953663811276202896' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5803106625832520676/posts/default/7953663811276202896'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5803106625832520676/posts/default/7953663811276202896'/><link rel='alternate' type='text/html' href='http://www.acceptpayments.org/2009/03/how-to-make-your-software-application_15.html' title='How to make your software application PCI compliant.'/><author><name>Avani</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='08403427484284998926'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></entry>