<?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>The Merchant Account Blog &#187; Industry News</title>
	<atom:link href="http://www.merchantequip.com/merchant-account-blog/category/news/feed" rel="self" type="application/rss+xml" />
	<link>http://www.merchantequip.com/merchant-account-blog</link>
	<description>Merchant Accounts, Ecommerce, Processing Equipment</description>
	<lastBuildDate>Thu, 17 May 2012 20:08:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>MasterCard Security Alert</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1674/mastercard-security-alert</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1674/mastercard-security-alert#comments</comments>
		<pubDate>Thu, 17 May 2012 20:08:37 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Data Security]]></category>
		<category><![CDATA[Industry News]]></category>

		<guid isPermaLink="false">http://www.merchantequip.com/merchant-account-blog/?p=1674</guid>
		<description><![CDATA[MasterCard has alerted that some merchants have recently received fraudulent “MasterCard Security Alert” e-mail messages. These e-mails ask merchants to conduct payment card test transactions followed by a refund to a different payment card. These e-mails also instruct merchants to send the details of the transactions to an e-mail address not affiliated with MasterCard. This [...]]]></description>
			<content:encoded><![CDATA[<p>MasterCard has alerted that some merchants have recently received fraudulent “MasterCard Security Alert” e-mail messages. These e-mails ask merchants to conduct payment card test transactions followed by a refund to a different payment card. These e-mails also instruct merchants to send the details of the transactions to an e-mail address not affiliated with MasterCard. This scam is being perpetrated by criminals in order to gain merchant transaction information so they can attempt to make fraudulent purchases and refunds using stolen payment card information.</p>
<p>If any business receives an unsolicited phone call, e-mail message, text message, or social media request from an individual claiming to be a MasterCard Security representative,<strong> do not to respond</strong>. Report the fraudulent inquiry to MasterCard using the following e-mail address: <a href="mailto:datasecurity@mastercard.com">datasecurity@mastercard.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1674/mastercard-security-alert/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Data Breach + Media = Disaster</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1658/data-breach-media-disaster</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1658/data-breach-media-disaster#comments</comments>
		<pubDate>Fri, 30 Mar 2012 20:19:24 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Data Security]]></category>
		<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantequip.com/merchant-account-blog/?p=1658</guid>
		<description><![CDATA[There was a large data breach announced today by Visa and Mastercard. I think more than ever, this breach shows how dangerous the media is at blowing a story our of proportion before anyone actually know what the details are. What is known&#8230; Most likely a parking garage, or network of parking garages, suffered a [...]]]></description>
			<content:encoded><![CDATA[<p>There was a large data breach announced today by Visa and Mastercard. I think more than ever, this breach shows how dangerous the media is at blowing a story our of proportion before anyone actually know what the details are.</p>
<p>What is known&#8230;</p>
<p>Most likely a parking garage, or network of parking garages, suffered a data breach, most likely in the state of New York. Global Payments was most likely the processor for this business. That&#8217;s about it!</p>
<p>Here&#8217;s what the media shows:</p>
<p><img class="alignnone size-full wp-image-1661" title="2012-03-30_1512" src="http://www.merchantequip.com/merchant-account-blog/wp-content/uploads/2012/03/2012-03-30_1512.png" alt="" width="610" height="543" /></p>
<p><img class="alignnone size-full wp-image-1662" title="2012-03-30_1512_001" src="http://www.merchantequip.com/merchant-account-blog/wp-content/uploads/2012/03/2012-03-30_1512_001.png" alt="" width="229" height="231" /></p>
<p>Point being, that some publications like to blow the proportions of a story out of the water before there&#8217;s any fact to the story. Time will tell what has actually happened and it may be a very bad situation. But, the difference between 50,000 cards as <a href="http://online.wsj.com/article/SB10001424052702303816504577313411294908868.html">reported in the Wall Street Journal</a>, and 10,000,000 cards as reported in <a href="http://redtape.msnbc.msn.com/_news/2012/03/30/10940640-mastercard-visa-confirm-credit-card-data-theft-described-as-massive">MSN&#8217;s red sheet</a>, is incomparable.</p>
<p>And consumers and the government wonder why businesses don&#8217;t always come right out and tell everyone.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1658/data-breach-media-disaster/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>You&#8217;ll love Visa&#8217;s new FANF fee, thanks Con&#8230;.s&#8230;</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1622/youll-love-visas-new-fanf-fee-thanks-con-s</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1622/youll-love-visas-new-fanf-fee-thanks-con-s#comments</comments>
		<pubDate>Wed, 29 Feb 2012 23:16:30 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantequip.com/merchant-account-blog/?p=1622</guid>
		<description><![CDATA[I I&#8217;ll avoid stating why I think they&#8217;re doing this, cough&#8230; Durbin&#8230; cough, cough&#8230;., but starting in April 2012, Visa has added a new charge to all merchant accounts. These additional fees are fixed per month, and are based on a merchant&#8217;s business type and the number of location or volume they process. In the mix [...]]]></description>
			<content:encoded><![CDATA[<p>I I&#8217;ll avoid stating why I think they&#8217;re doing this, cough&#8230; Durbin&#8230; cough, cough&#8230;., but starting in April 2012, Visa has added a new charge to all merchant accounts. These additional fees are fixed per month, and are based on a merchant&#8217;s business type and the number of location or volume they process.</p>
<p>In the mix Visa is lowering their network acquirer processor fee from $0.0195 to $0.0155 per authorization. They are also adding a $.10 fee to some debit transactions that don&#8217;t meet certain processing criteria.</p>
<p>However, all businesses can expect to see the following changes.</p>
<table width="75%">
<thead>
<tr>
<th colspan="2">Card present (non high-volume MCC&#8217;s)</th>
</tr>
</thead>
<tbody>
<tr>
<td># of locations</td>
<td>$ per location per month</td>
</tr>
<tr>
<td>1</td>
<td>$2.00</td>
</tr>
<tr>
<td>2</td>
<td>$2.00</td>
</tr>
<tr>
<td>3</td>
<td>$2.00</td>
</tr>
<tr>
<td>4</td>
<td>$2.90</td>
</tr>
<tr>
<td>5</td>
<td>$2.90</td>
</tr>
<tr>
<td>6 &#8211; 10</td>
<td>$2.90</td>
</tr>
<tr>
<td>11 &#8211; 20</td>
<td>$4.00</td>
</tr>
<tr>
<td>21 &#8211; 50</td>
<td>$4.00</td>
</tr>
<tr>
<td>51 &#8211; 100</td>
<td>$6.00</td>
</tr>
<tr>
<td>101 &#8211; 150</td>
<td>$8.00</td>
</tr>
<tr>
<td>151 &#8211; 200</td>
<td>$10.00</td>
</tr>
<tr>
<td>201 &#8211; 250</td>
<td>$14.00</td>
</tr>
<tr>
<td>251 &#8211; 500</td>
<td>$24.00</td>
</tr>
<tr>
<td>501 &#8211; 1000</td>
<td>$32.00</td>
</tr>
<tr>
<td>1001 &#8211; 1500</td>
<td>$40.00</td>
</tr>
<tr>
<td>1501 &#8211; 2000</td>
<td>$50.00</td>
</tr>
<tr>
<td>2001 &#8211; 4000</td>
<td>$60.00</td>
</tr>
<tr>
<td>&gt; 4000</td>
<td>$65.00</td>
</tr>
</tbody>
</table>
<table width="75%">
<thead>
<tr>
<th colspan="2">Card not present, Fast food, and Aggregators</th>
</tr>
</thead>
<tbody>
<tr>
<td>Monthly Sales Volume</td>
<td>$ per month</td>
</tr>
<tr>
<td>&lt; $50</td>
<td>$2.00</td>
</tr>
<tr>
<td>$50 &#8211; $199</td>
<td>$2.90</td>
</tr>
<tr>
<td>$200 &#8211; $999</td>
<td>$5.00</td>
</tr>
<tr>
<td>$1,000 &#8211; $3,999</td>
<td>$7.00</td>
</tr>
<tr>
<td>$4,000 &#8211; $7,999</td>
<td>$9.00</td>
</tr>
<tr>
<td>$8,000 &#8211; $39,999</td>
<td>$15.00</td>
</tr>
<tr>
<td>$40,000 &#8211; $199,999</td>
<td>$45.00</td>
</tr>
<tr>
<td>$200,000 &#8211; $799,999</td>
<td>$120.00</td>
</tr>
<tr>
<td>$800,000 &#8211; $1,999,999</td>
<td>$350.00</td>
</tr>
<tr>
<td>$2,000,000 &#8211; $3,999,999</td>
<td>$700.00</td>
</tr>
<tr>
<td>$4,000,000 &#8211; $7,999,999</td>
<td>$1,500.00</td>
</tr>
<tr>
<td>$8,000,000 &#8211; $19,999,999</td>
<td>#3,500.00</td>
</tr>
<tr>
<td>$20,000,000 &#8211; $39,999,999</td>
<td>$7,000.00</td>
</tr>
<tr>
<td>$40,000,000 &#8211; $79,999,999</td>
<td>$15,000.00</td>
</tr>
<tr>
<td>$80,000,000 &#8211; $399,999,999</td>
<td>$30,000.00</td>
</tr>
<tr>
<td>&gt; $400,000,000</td>
<td>$40,000.00</td>
</tr>
</tbody>
</table>
<p>For some businesses this may result in reduced fees but it&#8217;s likely that many businesses will see an increase in their monthly bill as a result of the FANF fee. MasterCard will be introducing new and similar fees as well starting in July. Stay tuned to see what those turn out to be.</p>
<p>I hate to say I told you so, but once again the Walmart&#8217;s and super retailers got their wish and the rest of the businesses out there end up with a higher cost. It&#8217;s unfortunate that organizations like the NRF don&#8217;t have the foresight to stop lobbying for super retailers at the expense of the businesses they supposedly represent. Thus far, the Walmart lawsuit a few years ago and the Durbin debit regulation have drastically increased the complexity and the costs to most merchants in the US.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1622/youll-love-visas-new-fanf-fee-thanks-con-s/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>IRS reporting, just how bad is it?</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1580/irs-reporting-just-how-bad-is-it</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1580/irs-reporting-just-how-bad-is-it#comments</comments>
		<pubDate>Wed, 13 Jul 2011 16:00:59 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantequip.com/merchant-account-blog/?p=1580</guid>
		<description><![CDATA[By now, the majority of merchants in the US have been informed of some impending IRS reporting requirements for their merchant account. I blogged about this congressional mandate several years ago and since we&#8217;re finally past the day of reckoning, let&#8217;s revisit how this is exactly going to affect your merchant account and your business. [...]]]></description>
			<content:encoded><![CDATA[<p>By now, the majority of merchants in the US have been informed of some impending IRS reporting requirements for their merchant account. I blogged about this congressional mandate <a href="http://www.merchantequip.com/merchant-account-blog/233/government-toying-with-the-bankcard-business">several years ago</a> and since we&#8217;re finally past the day of reckoning, let&#8217;s revisit how this is exactly going to affect your merchant account and your business.</p>
<p><strong>An Overview</strong></p>
<p>Some time back, the IRS decided that they wanted to see a report of <a href="http://www.law.cornell.edu/uscode/26/usc_sec_26_00006050---W000-.html">all the money that a merchant processes through their merchant account</a> over the year. </p>
<p>While this is a nearly useless number because as we all know, most businesses also accept cash, checks, and other currency, it will in theory catch the most egregious tax evading businesses. Basically, the few fractions of a percent of businesses that grossly cheat on their tax returns &#8220;could&#8221; get caught. Regardless of the absurdity of requiring the entire country disclose their processing volumes, here we are&#8230;</p>
<p>Now for this to work, your processor has to file a 1099 form with the IRS. This is a seemingly simple task. However, for this to actually work, your business information with your processor must exactly match what the IRS has on file. This includes business name, address, your tax id, etc. Things as simple as capitalized letters, a single space, and punctuation will cause a mismatch. You get a new tax id after opening up a merchant account. You signed your application with only your SSN and not your tax id number. Things like this will cause errors. Since it&#8217;s rare that merchants fill out their merchant applications with the exact same business information, with the exact same capitalization, and spaces as they do when they fill out their tax information, and nothing changes with their business-IRS relationship, it&#8217;s fair to say a lot of tax reporting information will not be valid.</p>
<p><strong>So, what if the tax information is not valid?</strong></p>
<p>So, here comes the nasty part. The IRS mandates that your processor will withhold 28% of all credit card payments until the errors are corrected. Yes, <strong>28% of all of your credit card sales with be held</strong> until you fix whatever information is incorrect. And, even if you fix the problem, you wont get that 28% back until the end of the year.</p>
<p><strong>More fees</strong></p>
<p>Most likely you have or will receive notice that you are going to be charged for the work required to verify and prepare this massive undertaking. I&#8217;ve seen everything from several hundred $ per year, to a few $ per month. The reason you are being charged this fee is that it actually requires a lot of work to verify and prepare one of these documents for a merchant. Processors often have thousands, or tens of thousands of merchants, which translates into thousands of man hours in just the initial verification, not even taking into account contacting every merchant that has errors to obtain the correct information. If you didn&#8217;t authorize e-file for your 1099, your processor needs to mail you a physical form.</p>
<p><strong>Exceptions</strong></p>
<p>The exceptions to the filing requirements are:</p>
<p>1. a merchant&#8217;s total payment transactions for the year does not exceed $20,000, and<br />
1. the total number of transactions does not exceed 200</p>
<p>In which case your processor will not need to file a report. This may consist of a good percentage of businesses out there, but most full-time businesses process more than $20,000 per year.</p>
<p><strong>Conclusion</strong></p>
<p>It&#8217;s unfortunate that the reporting regulation was ever passed. It&#8217;s a useless piece of legislation that creates a lot more work for small businesses and it&#8217;s unlikely that the reporting will catch any but the worst tax offenders. But, it&#8217;s passed and taking effect and there&#8217;s not much any of us can do about it at this point. No matter who you process credit cards with, keep a close eye on the mail and your processing statements for instructions on how to verify your information. My recommendation is to take it very seriously to avoid the 28% withholding.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1580/irs-reporting-just-how-bad-is-it/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Payment Industry Changes &#8211; Debit Interchange Regulation</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1574/payment-industry-changes-debit-interchange-regulation</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1574/payment-industry-changes-debit-interchange-regulation#comments</comments>
		<pubDate>Fri, 01 Jul 2011 14:44:51 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantequip.com/merchant-account-blog/?p=1574</guid>
		<description><![CDATA[First off, I wish everyone a great 4th of July weekend. Banks will be closed on Monday and it looks like most people are starting their weekend today anyway. Be safe this weekend and be very careful with fireworks if you live in one of the drought stricken areas like myself. The past month has [...]]]></description>
			<content:encoded><![CDATA[<p>First off, I wish everyone a great 4th of July weekend. Banks will be closed on Monday and it looks like most people are starting their weekend today anyway. Be safe this weekend and be very careful with fireworks if you live in one of the drought stricken areas like myself.</p>
<p>The past month has brought monumental changes to the payment processing industry.</p>
<p><strong>Mobile frenzy</strong></p>
<p>Mobile payments seem to be on the fast track with just about every tech related company steaming ahead at trying to be the first with a workable and widely adopted mobile payment method. Even Google has jumped in, despite Paypal&#8217;s arguments, and hopes to be a major player in mobile payments. If the Google Checkout service is any indicator of Google&#8217;s success in mobile payments, they simply aren&#8217;t going to make it. However, with their success in the mobile android operating system, and their already massive relationship with businesses, Google may have a chance at something.</p>
<h2>Debit Interchange Regulation</h2>
<p>The biggest news of the month, is the regulation of debit interchange. After fierce battling for more than a year, debit interchange is to be regulated to $.21 per transaction and .05% per transaction. As written, this applies to all debit card transactions, PIN or signature as well as Ecommerce/MOTO transactions. It&#8217;s not entirely clear when and how this will take effect but stay tuned over the next months. </p>
<p>The biggest winners in this regulation are once again the super retailers who process millions of transactions per year. Small and medium size merchants can expect savings, but it will not likely be anything as monumental as the Walmart&#8217;s and Amazon.com&#8217;s out there. There&#8217;s going to be a lot of misinformation flying and aggressive marketing over the next year as many processors will take advantage of the turmoil, misinformation, and instability in the merchant account industry. I would strongly suggest exercising caution in anyone making sensational claims about lowering your rates. Major industry changes offer the greatest opportunity to get scammed into a bad merchant account. Just remember that almost every processor has roughly the same hard costs, so if they are unrealistically lowering fees in one place, they have to make them up somewhere else.</p>
<p><strong>Expect major checking account changes</strong></p>
<p>As a result of banks losing roughly 50% of their revenue from debit cards, we should all expect <a href="http://www.merchantequip.com/merchant-account-blog/1552/you-cant-spend-more-than-50-on-your-debit-card">drastic changes</a> to our personal and business checking accounts over the next year. I know that all of my business and personal debit rewards have been canceled over the past 3 months. I think that debit rewards are the tip of the iceberg, and we should expect changes in debit and checking account fees and overall debit availability over the coming months. Some smaller banks have rumored that they will be dropping debit cards completely, so it will be interesting to see where this all ends up a year from now.</p>
<p>It&#8217;s a mute point to argue <a href="http://www.merchantequip.com/merchant-account-blog/1243/debit-interchange-regulation-is-already-going-to-hurt-consumers">my position on the interchange regulation</a> at this time. Retailers may be chocking this up as a victory, but don&#8217;t start celebrating yet. This regulation may seem like a small amount. Personally I think this regulation will change the way we do banking in the US, and could very well effect the entire retail economy, not necessarily in a good way. The next few years will give us a better picture of what these regulation have done to the retail industries and checking accounts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1574/payment-industry-changes-debit-interchange-regulation/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>You can&#8217;t spend more than $50 on your debit card!</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1552/you-cant-spend-more-than-50-on-your-debit-card</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1552/you-cant-spend-more-than-50-on-your-debit-card#comments</comments>
		<pubDate>Thu, 10 Mar 2011 15:03:43 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Industry News]]></category>

		<guid isPermaLink="false">http://www.merchantequip.com/merchant-account-blog/?p=1552</guid>
		<description><![CDATA[Chase just release information that they are considering capping all debit transactions to $50 maximum. This is in response to the $.12 debit card interchange regulation battle that is waging between banks and retailers. I will refrain from commenting on the debit card regulation at this point. I&#8217;ve made my views and concerns known to [...]]]></description>
			<content:encoded><![CDATA[<p>Chase just release information that they are considering <a href="http://money.cnn.com/2011/03/10/pf/debit_cards_limit/index.htm">capping all debit transactions to $50 maximum</a>.</p>
<p>This is in response to the $.12 <a href="http://www.merchantequip.com/merchant-account-blog/1243/debit-interchange-regulation-is-already-going-to-hurt-consumers">debit card interchange regulation</a> battle that is waging between banks and retailers. I will refrain from commenting on the debit card regulation at this point. I&#8217;ve made my views and concerns known to the federal reserve board. What I will end with is that the entire debit and credit regulation concept is far more complicated that many would like to believe. It cannot be simply capped without major repercussions perhaps large enough to hurt the entire US and world economies. Something as important as this should not be attached to major bills and should be voted on separately as this specific regulation was not.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1552/you-cant-spend-more-than-50-on-your-debit-card/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The credit card terminal monopoly is official</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1465/the-credit-card-terminal-monopoly-is-official</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1465/the-credit-card-terminal-monopoly-is-official#comments</comments>
		<pubDate>Wed, 17 Nov 2010 15:24:19 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Credit Card Equipment]]></category>
		<category><![CDATA[Industry News]]></category>

		<guid isPermaLink="false">http://www.merchantequip.com/merchant-account-blog/?p=1465</guid>
		<description><![CDATA[It just goes to show that US government anti-trust regulations do not apply to B2B organizations! Verifone just acquired Hypercom corporation. This effectively removes all legitimate competition from the US credit card terminal market. Verifone&#8217;s own products have suffered a decline in reliability and quality starting 5 or 6 years ago, so naturally Verifone began [...]]]></description>
			<content:encoded><![CDATA[<p>It just goes to show that US government anti-trust regulations do not apply to B2B organizations!</p>
<p>Verifone <a href="http://techcrunch.com/2010/11/17/verifone-acquires-electronic-payments-company-hypercom-for-485-million/">just acquired Hypercom corporation</a>. This effectively removes <strong>all</strong> legitimate competition from the US credit card terminal market. Verifone&#8217;s own products have suffered a decline in reliability and quality starting 5 or 6 years ago, so naturally Verifone began purchasing competitors. They started with wireless leader Lipman, and then acquired Way Systems, and now have taken down the last barrier, Hypercom. Verifone stated that this acquisition was to expand their presence in the European market, but make no mistake it removed their last competition from the US market completely.</p>
<p>I don&#8217;t want to forget Ingenico whom is one of the worlds largest terminal manufacturers, however they are a mere drop in the bucket in the US and sell almost exclusively to large chains and direct placement deals that normal mom and pop merchants will never see.</p>
<p>I&#8217;m personally appalled that the government allowed this transaction to take place. On the bright side, if Verifone cannot produce a higher quality product, there&#8217;s several smaller manufacturers that are already gaining serious ground, most notably Dejavoo, ready to replace Hypercom. This will provide the perfect avenue for Dejavoo and others to become much larger terminal brands <em>(until Verifone purchases them of course)</em>. <a href="http://www.merchantequip.com/processing-equipment/dejavoo/">Dejavoo&#8217;s product</a> is far superior to Verifone or Hypercom and is cheaper than either.</p>
<p>I&#8217;m seriously holding back words on writing this. The impact of this on the credit card terminal industry would be comparable to Walmart purchasing Target or Microsoft purchasing Apple. This sort of acquisition is the reason that anti-trust laws exist. It&#8217;s unfortunate that the government&#8217;s priorities are so far removed from the B2B industries of the country.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1465/the-credit-card-terminal-monopoly-is-official/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Debit Interchange Regulation is Already Going to Hurt Consumers</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1243/debit-interchange-regulation-is-already-going-to-hurt-consumers</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1243/debit-interchange-regulation-is-already-going-to-hurt-consumers#comments</comments>
		<pubDate>Thu, 17 Jun 2010 18:39:41 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Industry News]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=1243</guid>
		<description><![CDATA[About a week ago, the US Government passed financial reform bills that included regulating debit card fees and regulating merchant&#8217;s ability to surcharge or set minimum and maximum purchase amounts. What congress has never look at is the repercussions of regulating something like interchange, even if it&#8217;s just for debit. Recent events have shown us [...]]]></description>
			<content:encoded><![CDATA[<p>About a week ago, the US Government <a href="http://www.federalreserve.gov/newsevents/press/bcreg/20100615a.htm">passed financial reform bills</a> that included regulating debit card fees and regulating merchant&#8217;s ability to surcharge or set minimum and maximum purchase amounts. What congress has never look at is the repercussions of regulating something like interchange, even if it&#8217;s just for debit. Recent events have shown us a glimpse at the future of debit cards.</p>
<p>I read a great <a href="http://paymentsviews.com/2010/06/14/getting-real-about-durbin/">article about Durbin&#8217;s amendment</a> in which I found out that free checking accounts were virtually non-existent before the invention of signature (or offline) debit. Signature debit is where a merchant processes a debit card like a credit card without requiring a PIN number. With the invention of signature debit, banks had a steady source of income from debit interchange that was directly attached to their customer&#8217;s bank accounts. With this additional income, came the invention of the free checking account. Right now most consumers and small businesses use free checking accounts, which are partially subsidized by fees the bank receives from signature debit interchange. These fees also help pay for chargeback investigations, and help pay for account features that you would have had to pay for before there were free checking accounts.</p>
<p>Now that congress is capping debit interchange, we can expect changes with regard to free checking account practices. Since these accounts can no longer be subsidized by signature debit interchange, banks are going to have create monthly fees for checking accounts. Chargeback investigations also cost banks huge amounts, so we can expect further fees will be charged to cover the additional costs for these. Right now, BOFA and others have announced that <a href="http://online.wsj.com/article/SB10001424052748703513604575311093932315142.html">they plan on charging fees for checking accounts</a> once the new regulations go into effect. Goodbye, free checking&#8230;</p>
<p>What I think is the biggest flaw to the debit regulation, and of much greater significance in the overall picture, is the double standard that congress has proposed. The law limits the amount banks can charge for debit interchange. At the same time, it exempts financial institutions with less than $10B in assets in attempt to help these smaller institutions out, but at the same time allows merchant to discriminate against types of payment at their discretion. A thoughtful move, but because of the second part it will have a near 100% opposite effect than planned.</p>
<p>Merchants will now inherently be more inclined to, and be allowed to, accept debit cards with the lower rates, which will be the big bank&#8217;s cards! Instead of helping credit unions and small banks, congress instead created the perfect avenue to put them out of the debit card picture. While it&#8217;s unrealistic to assume that the smaller banks will not be issuing debit cards at all, it is completely reasonable to assume that retailers <em>(especially the large ones)</em> will favor and may only accept cards from large banks that they pay less for. We&#8217;ll start seeing signs like only Bank of America debit cards are accepted here, and congress not only made it completely legal for merchants to do this, but they created the system to facilitate it!</p>
<p><strong>With one swipe the future shows the end of free checking accounts, and the end of credit union&#8217;s issuing their own debit cards.</strong></p>
<p>I&#8217;ll readily admit that I am partial when it comes to regulation of my industry, but how could congress have created something so blatantly damaging to credit unions and small banks in the US. As soon as the credit unions learned about the details of the rules , <a href="http://www.digitaltransactions.net/newsstory.cfm?newsid=2550">they began lobbying</a>. However, the wording and details were published after the rules were passed, so to stop it now is more a prayer than anything else. It doesn&#8217;t take an expert to know that large retailers follow the savings, just like consumers&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1243/debit-interchange-regulation-is-already-going-to-hurt-consumers/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fraud as a Service</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1191/fraud-as-a-service</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1191/fraud-as-a-service#comments</comments>
		<pubDate>Thu, 03 Jun 2010 17:22:09 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Industry News]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=1191</guid>
		<description><![CDATA[First Data published an incredible paperPDF regarding the sophistication of electronic fraud. I highly recommend taking a look at it for anyone in the payments or IT industries, and anyone interested in learning about how advanced and organized cyber-crime has become. More than any resource I&#8217;ve seen before it, this paper gives a clear and [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.merchantequip.com/merchant-account-blog/wp-content/uploads/2010/06/fraud-report.jpg" alt="" title="fraud-report" width="350" height="459" class="alignright size-full wp-image-1195" />First Data published <a href="http://www.firstdata.com/downloads/thought-leadership/fraudtrends2010_wp.pdf">an incredible paper</a><sup>PDF</sup> regarding the sophistication of electronic fraud. I highly recommend taking a look at it for anyone in the payments or IT industries, and anyone interested in learning about how advanced and organized cyber-crime has become.</p>
<p>More than any resource I&#8217;ve seen before it, this paper gives a clear and easy to understand description of the current state of electronic crime. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1191/fraud-as-a-service/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI-DSS compliance becoming justifiable?</title>
		<link>http://www.merchantequip.com/merchant-account-blog/1115/pci-dss-compliance-becoming-justifiable</link>
		<comments>http://www.merchantequip.com/merchant-account-blog/1115/pci-dss-compliance-becoming-justifiable#comments</comments>
		<pubDate>Thu, 13 May 2010 17:49:47 +0000</pubDate>
		<dc:creator>merchant account blog</dc:creator>
				<category><![CDATA[Data Security]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Merchant Accounts]]></category>

		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=1115</guid>
		<description><![CDATA[Since I have became involved with PCI-DSS several years ago I have always had a major complaint about PCI-DSS. Merchants do not have protection from liabilities if they take the steps to become compliant! Now before QSA&#8217;s light their torches, let me just say that I completely understand and agree that PCI Compliance &#8800; Security. [...]]]></description>
			<content:encoded><![CDATA[<p>Since I have became involved with PCI-DSS several years ago I have always had a major complaint about PCI-DSS.</p>
<p><strong>Merchants do not have protection from liabilities if they take the steps to become compliant!</strong></p>
<p>Now before QSA&#8217;s light their torches, let me just say that I completely understand and agree that <strong>PCI Compliance &ne; Security</strong>. Nevertheless, from a business perspective it&#8217;s hard to take a program like this seriously when there is no real benefit from becoming compliant. One can always argue that security is a benefit, but in reality it&#8217;s not unless you actually prevent a data loss with it, and there&#8217;s no measurable monetary benefit of something that you don&#8217;t know was prevented.</p>
<p align="center"><img src="http://www.merchantequip.com/merchant-account-blog/wp-content/uploads/2010/05/pci-stamp.png" alt="" title="pci-stamp" width="420" height="344" class="alignnone size-full wp-image-1132" /></p>
<p>I do have a strong belief, which I think is further illustrated by the slow adoption rates of level 3 and level 4 merchants, that most merchants don&#8217;t take PCI seriously. Losing customer data is nothing to be joking about, but they way PCI has been implemented with liability dumped on merchants and processors, and the fact that compliant businesses get no protection over non-compliant ones, is laughable. Independent of the PCI Council which they helped start, MasterCard now requires security scans for all merchants even if they don&#8217;t process on the Internet or over an IP connection. How can PCI possibly be taken seriously if the founding companies create independent standards after they start an organization specifically to make sure they all have the same standards?</p>
<p><strong>So what&#8217;s the big news?</strong></p>
<p>Washington state <a href="http://www.storefrontbacktalk.com/securityfraud/washington-states-new-data-breach-law-says-assessor%E2%80%94not-visa%E2%80%94has-the-final-word/">just passed a law</a> (<a href="http://apps.leg.wa.gov/documents/billdocs/2009-10/Pdf/Bills/Session%20Law%202010/1149-S2.SL.pdf">HB 1149 <sup>pdf</sup></a>) that effectively legitimizes PCI, or at least legitimizes much of the cost in becoming compliant. What this law will do is grant a merchant safe harbor from liabilities resulting from a data breach, provided that the merchant was PCI compliant when the breach occurred. It also states that the breached organization&#8217;s compliance cannot be revoked as a result of a breach. Basically, if you were compliant at the time of the breach, you are still compliant after the breach. This sort of retroactive revocation of PCI compliance has occurred in several major breaches. From my observation, this law is the first breath of reason that I have seen pushed towards PCI compliance.</p>
<p>Business owners <em>(at least in Washington)</em> can look at PCI and assume, if we become secure and become PCI compliant, we&#8217;re no longer as-liable if some extraordinary circumstance results in us losing data. The proactive response is: let&#8217;s get this taken care of, lets make sure that our data is secure, and let&#8217;s get compliant!</p>
<p>Currently that same business owner is checking [YES] to all the boxes and emailing in their questionnaire. They&#8217;re asking, so it doesn&#8217;t matter if I&#8217;m PCI compliant, I&#8217;m still fully liable for any costs and damages if someone steals my data? Hmm&#8230; [YES] to all&#8230; DONE!</p>
<p><strong>The pitfalls</strong></p>
<p>With legislation like this there are pitfalls, and probably some big ones.</p>
<p>First off, the law states that merchants must be validated compliant within 1 year of the breach occurring. 1 year is far too long for a business that was compliant to be assumed to be still compliant. Additionally, this doesn&#8217;t address the fact that the business could quite easily take steps to actually become secure, but intentionally remove them for operations sake once they pass a security scan or self assessment.</p>
<p>Second, the law is only for Washington which makes it worthless in all practicality. However, the fact that one state is passing it may push Visa/MC/AMex/Disc to look at adding real protection to PCI.</p>
<p>Third, the law doesn&#8217;t address actual costs to consumers such as fees from bounced checks or other bank and credit associated fees. Merchant&#8217;s would most likely still be liable for many of these fees <em>(assuming that there are some)</em> if they suffered a breach.</p>
<p>Lastly, the law would justify costs for becoming compliant, but could put huge costs on someone else <em>(and it&#8217;s unclear who)</em>. If the merchant does suffer a sizable breach, it&#8217;s clear that there are real costs in re-issuing cards. What&#8217;s not clear is who would end up paying for them if this law is passed.</p>
<p><strong>Meaningless?</strong></p>
<p>Until this law is adopted by the issuers or put into effect on a national level, the benefits from it on a widespread scale, are going to be little to none. I&#8217;m openly against government regulation in any industry, yours or mine, so I do hope that card issuers and PCI security council take a serious look into adopting similar measures directly into PCI. I think that providing some sort of protection like this would greatly legitimize PCI especially in the minds of the business owners that are forced to become compliant and feel that PCI does not give them any benefit. It&#8217;s time for PCI to give small business owners a real reason to become secure and to become PCI compliant. A measure like this law is that reason!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.merchantequip.com/merchant-account-blog/1115/pci-dss-compliance-becoming-justifiable/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

