{"id":415,"date":"2008-11-18T19:22:09","date_gmt":"2008-11-19T00:22:09","guid":{"rendered":"http:\/\/www.merchantaccountblog.com\/?p=415"},"modified":"2008-11-18T22:00:15","modified_gmt":"2008-11-19T03:00:15","slug":"why-cvv-is-worthless-and-why-its-not","status":"publish","type":"post","link":"https:\/\/www.merchantequip.com\/merchant-account-blog\/415\/why-cvv-is-worthless-and-why-its-not","title":{"rendered":"Why CVV is worthless, and why it&#8217;s not!"},"content":{"rendered":"<p>CVV or card verification, (also known as CVV2, CVC2, CID) is that small 3 or 4 digit number on the back of your credit card (front for AMEX) that is not encoded on the magnetic stripe, and is designed to help prevent fraud.<\/p>\n<p><center><img decoding=\"async\" src=\"https:\/\/www.merchantequip.com\/images\/logos\/all-cvv.gif\" alt=\"CVV\" class=\"noFloat\" \/><\/center><\/p>\n<p>CVV offers a little protection against fraud, but nonetheless should be used whenever possible.<\/p>\n<p><!--more--><\/p>\n<h2>Why CVV is worthless<\/h2>\n<p><strong>CVV cannot be written down, ever:<\/strong><\/p>\n<blockquote cite=\"Visa's operating regulations\"><p>Avoid CVV2 Storage. All merchants are prohibited from storing CVV2 data. When asking a cardholder for CVV2, merchants must not document this information on any kind of paper order form or store it on any database.<\/p><\/blockquote>\n<p>CVV can only be used in call centers where the card is directly keyed into a processing system that instantly authorizes the transaction. It can be used on a website where an automatic authorization is made. Other than those two circumstances, it really can&#8217;t be used. The fines for storing a CVV number are steep and could easily cost a merchant hundreds of thousands of dollars, not to mention loosing your ability to process credit cards forever. <\/p>\n<p>Just to clarify CVV must not be written down, sent in an email, stored in a database, saved for later in any way, at any time, for any reason!<\/p>\n<p><strong>CVV wears off:<\/strong><br \/>\nIt&#8217;s almost like they printed the CVV number in some special fast-fading ink. CVV numbers wear off quickly, and are often unreadable after a month or two. This creates an unnecessary burden for customers who are forced to use their CVV number for a payment. No wonder why <a href=\"http:\/\/www.merchantequip.com\/merchant-account-blog\/archives\/284\">50% of the top 100 retailers don&#8217;t use CVV<\/a>.<\/p>\n<p><strong>The CVV system isn&#8217;t always available:<\/strong><br \/>\nIf you&#8217;ve ever looked at an error log of an active payment gateway, you you see a mess of CVV not available, not supported, and other non-mismatch errors. The CVV system is definitely not rock-solid at this point, and there&#8217;s a potential to lose legitimate business due to these erroneous errors.<\/p>\n<p><strong>It doesn&#8217;t guarantee anything:<\/strong><br \/>\nMy biggest complaint, a positive CVV match doesn&#8217;t guarantee anything except that whoever placed the order had the card in hand (or wrote down the CVV number). It doesn&#8217;t automatically win chargebacks, and it doesn&#8217;t remove any accountability for a transaction from the merchant. It is strictly a preventive measure to combat fraud.<\/p>\n<h2>Why CVV is still a good system<\/h2>\n<p><strong>It&#8217;s FREE:<\/strong><br \/>\nThat&#8217;s right. Unlike the AVS system, there is no additional fee for using CVV. At the very least, there&#8217;s no reason at all not to use CVV for online processing. Whether you want to actually decline transactions based on a CVV response is a different story. <\/p>\n<p>I&#8217;ll come straight out and say, I don&#8217;t recommend requiring a positive CVV match to approve a transaction. However, if you decide not to require it, I strongly recommend implementing a transaction flagging system forcing transactions with a CVV mismatch to be manually reviewed before shipping. You can easily implement your own system using the response from a payment gateway. Most payment gateways also have additional fraud prevention tools, that will automatically flag these transactions.<\/p>\n<p><strong>It protects against skimming:<\/strong><br \/>\nIt is signifigantly more complicated for a <a href=\"http:\/\/www.merchantequip.com\/merchant-account-blog\/archives\/149\">card skimmer<\/a> to record the CVV number in addition to the magnetic stripe data. In almost all cases, using CVV will prevent fraudulent transactions from skimmed cards.<\/p>\n<p><strong>It works, when it works:<\/strong><br \/>\nCVV does actually deter and prevent fraud for unattended situations. It can completely eliminate <a href=\"http:\/\/www.merchantequip.com\/merchant-account-blog\/archives\/36\">card testing (carding)<\/a>, and does ensure that your customer had the physical card in their hand at some point. The same thing goes for call centers, where there are high fraud percentages because customers still can&#8217;t be verified.<\/p>\n<p>The bottom line is that using CVV and requiring it, or flagging mismatch transactions will save you money and will prevent fraud. Use it, if you have the option to!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CVV or card verification, (also known as CVV2, CVC2, CID) is that small 3 or 4 digit number on the back of your credit card (front for AMEX) that is not encoded on the magnetic stripe, and is designed to help prevent fraud. CVV offers a little protection against fraud, but nonetheless should be used [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,1],"tags":[],"class_list":["post-415","post","type-post","status-publish","format-standard","hentry","category-fraud","category-merchantaccounts"],"_links":{"self":[{"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/posts\/415","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/comments?post=415"}],"version-history":[{"count":20,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/posts\/415\/revisions"}],"predecessor-version":[{"id":436,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/posts\/415\/revisions\/436"}],"wp:attachment":[{"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/media?parent=415"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/categories?post=415"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/tags?post=415"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}