Information on Merchant Accounts,
Ecommerce and Credit Card Processing

March 21st, 2012 by Jamie Estep

Point of Sale for your iPad

Filed in: Credit Card Equipment, Merchant Accounts | 1 comment

We recently partnered with a company, ShopKeep, to provide a point of sale (POS) program for iPad and Mac computers. It’s often a tough decision for a merchant to move up from a simple credit card terminal to a POS system as there can be significant costs and time in training and implementing a POS system. POS systems traditionally handle inventory and pricing in addition to acting as a businesses cash register. They are often locked into specific credit card processors that don’t always have good customer service or reasonable rates. The ShopKeep POS system is a great stepping stone for merchants that are looking to move up to an entry level POS system.

ShopKeep Overview:

ShopKeep POS is built to use an Apple iPad as the base computer for the system. It is essentially a web based software service that performs the normal functions of a point of sale system. From there a magnetic credit card reader is added in addition to a stand and a cash register for most merchants. This system tracks inventory and will support bar code readers, printers and a variety of other traditional POS requirements. Currently ShopKeep is only available to merchants located in the US and Canada.

Hardware:

The magnetic card reader is the Magtek idynamo or dynamag which are completely secure card readers that encrypt a transaction as the card is being swiped. Printers, bar code scanners, display stands, cash drawers, and other traditional peripherals can be added to an iPad allowing ShopKeep to replace most traditional POS systems.

Since ShopKeep is built using an iPad, it makes a very sleek, compact, and high tech looking POS system.

Software:

The ShopKeep software is easy to use and can be customized to fit a business’s specific requirements even with multiple locations. ShopKeep processes credit card transactions over the internet by connecting to a payment gateway. This facilitates near-instant processing times as long as an active internet connection is available. It also enables inventory and pricing to be controlled centrally if a merchant has more than 1 location. ShopKeep handles sales tax and tips and other common functions as it should.

Like most Apple software, and unlike many POS systems, the merchant interface is well thought out. Screens are clean, easy to read, and easy to advance or back out of. User priviledges can be controlled for greater security. Sales and inventory reports can be built, and customized down to individual inventory items. ShopKeep can export several file types into quickbooks accounting software. The software should meet the requirements of most small to medium size retail merchants.

If you’re in the market for an entry POS system, or you have an iPad that you would like to use for your processing take a look at the ShopKeep iPad POS System.


March 9th, 2012 by Jamie Estep

Omni 3740 and 3750 are going away

Filed in: Credit Card Equipment |

The Verifone Omni 3750 and 3740 are on the way out. I’ve received notice from several processors that they will not longer support the 3740 or 3750 after October 31st, 2012. Unlike many phase out’s, most that I have heard from will no longer allow these terminals to process at all. The replacements for the 3740 and 3750 are the Verifone VX510 and the slightly more advanced Verifone VX570. Both of these terminals are available in dial only or dual comm versions which include the ability to process securely over the internet.

If you are using a 3740 or 3750, it would be wise to see if your processor is going to continue support for it. Otherwise, start shopping for a new terminal before they cut yours off completely.


February 29th, 2012 by Jamie Estep

You’ll love Visa’s new FANF fee, thanks Con….s…

Filed in: Industry News, Merchant Accounts | 3 comments

I’ll avoid stating why I think they’re doing this, cough… Durbin… cough, cough…., 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’s business type and the number of location or volume they process.

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’t meet certain processing criteria.

However, all businesses can expect to see the following changes.

Card present (non high-volume MCC’s)
# of locations $ per location per month
1 $2.00
2 $2.00
3 $2.00
4 $2.90
5 $2.90
6 – 10 $2.90
11 – 20 $4.00
21 – 50 $4.00
51 – 100 $6.00
101 – 150 $8.00
151 – 200 $10.00
201 – 250 $14.00
251 – 500 $24.00
501 – 1000 $32.00
1001 – 1500 $40.00
1501 – 2000 $50.00
2001 – 4000 $60.00
> 4000 $65.00
Card not present, Fast food, and Aggregators
Monthly Sales Volume $ per month
< $50 $2.00
$50 – $199 $2.90
$200 – $999 $5.00
$1,000 – $3,999 $7.00
$4,000 – $7,999 $9.00
$8,000 – $39,999 $15.00
$40,000 – $199,999 $45.00
$200,000 – $799,999 $120.00
$800,000 – $1,999,999 $350.00
$2,000,000 – $3,999,999 $700.00
$4,000,000 – $7,999,999 $1,500.00
$8,000,000 – $19,999,999 #3,500.00
$20,000,000 – $39,999,999 $7,000.00
$40,000,000 – $79,999,999 $15,000.00
$80,000,000 – $399,999,999 $30,000.00
> $400,000,000 $40,000.00

For some businesses this may result in reduced fees but it’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.

I hate to say I told you so, but once again the Walmart’s and super retailers got their wish and the rest of the businesses out there end up with a higher cost. It’s unfortunate that organizations like the NRF don’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.


February 10th, 2012 by Jamie Estep

IRS formally makes tax reporting meaningless

Filed in: Merchant Accounts | 1 comment

In the thick of the IRS reporting madness, the IRS has formally made a statement with regard to the new IRS reporting rules.

In a letter to the National Federation of Independent Business, the IRS said Wednesday it would not require retailers and others to explain how and why their business income differs from their credit-card receipts, which Congress now is requiring card companies to report separately to the IRS.

“There will be no reconciliation required” for the 2012 tax year, “nor do we intend to require reconciliation in future years,” said a letter to NFIB from IRS Deputy Commissioner Steven Miller.

Processors have spend millions of dollars and hundreds of thousands of hours trying to meticulously match business information with what the IRS has on file. I’ve strongly opposed the bill since it was first written about 5 years ago. This is an example of a bill that should never have been passed in the first place. It wouldn’t have worked except in all but the most egregious cases of tax evasion and caused an inconceivable burden to processors and normal businesses in the US.

The IRS and US government should issue a formal apology for causing countless time and money to be wasted for just about every US business. My only hope is that this is the first step in completely retracting it.


January 18th, 2012 by Jamie Estep

Zappos Breach – All is well, no credit card data was stolen…

Filed in: Ecommerce, Merchant Accounts | 1 comment

The online retailer Zappos just had a data security breach where they lost 24 Million customer’s personal information records. This loss included names, addresses, email and phone numbers, encrypted passwords, but did not include credit card information.

No doubt that thoughtful security planning prevented the loss of credit card or financially sensitive information. However, it doesn’t really lessen the reality that the repercussions from the Zappos breach could be huge. Does data security go far enough if we accept that personal information is completely acceptable to be lost as long as financial information is not?

With the amount of personal information that was obtained in the Zappos breach, the thieves have a very lucrative marketing or hacking information package.

On the marketing side

Companies pay a lot of money for targeted marketing lists like the one that Zappos inadvertently provided. Let’s see, here’s a list of 24 million people that definitely buy things online, most likely shoes or clothing items, FIRE AWAY…

This information is a telemarketer or direct marketer’s dream, and they can target these known shoppers via phone, mail, and email.

On the hacking side

I can almost guarantee that Zappos customers are going to receive an onslaught of highly engineered spam, viruses, offers, and everything else to their emails. At the same time they are going to start getting physical spam, and scam offers, and probably are going to see telemarketing scams as well. There’s really no limit to how the information can be used for malicious purposes. Scam companies and hacking groups trying to install mallware and spyware are extremely efficient and proficient at developing well planned attacks on unsuspecting users. There are millions of computers called zombie computers because they are being used to send spam and other malicious activities without the knowledge of their owners. Expect some more.

As to the encrypted passwords. Websites typically use 1-way hashing mechanisms for password storage. This means that the password is encrypted, but cannot be decrypted by any reasonable means. The caveat to this is that if the hacker knows how the password was hashed, they can create a huge list of hashes and compare them to find the original. This is a very targeted attack, but with 24 million passwords it’s worth a lot of effort. They will begin finding real password very quickly if they discover the hashing mechanism. Since many users do not use unique passwords between websites, the direct loss from being able to log into user’s bank accounts, or other websites will be significant. I always recommend using a unique password with every site you log into, and use a password manager like roboform.

The reality

The reality of this situation is that Zappos is owned by Amazon.com. I can guarantee that Zappos has some stout security in place, and yet one of the largest, most tech oriented companies on earth, just had a data loss of 24 million records. This tells me that that standards we have in place for protecting data, especially non-sensitive data, are not enough. We should not just be protecting financially sensitive data, but all customer data. Sure there may be no direct cost in replacing bank cards, or obtaining new bank account numbers, stopping checks, or posting chargebacks, but the effect to the customer when you lose their data can be remarkable. We’ve yet to see the actual damages that this breach causes, but with the sheer amount of information out there, there could be substantial damages.


November 17th, 2011 by Jamie Estep

Call your congress-person, oppose the American Firewall

Filed in: Merchant Accounts |

In case you haven’t been paying attention to the US political landscape, there is currently a bill in progress dubbed the great American firewall. It is a thoughtless overreaching nightmare’ish bill that claims to be for preventing copyright infringement.

Please read up and understand the implications of what this bill will do. There has never been a more 1984esque bill to be taken up by both houses of congress. It is absolutely ridiculous that our country would go this far just to help the massive media corporations under the veil that they are doing it for the good of the people. While supportable in concept, this is one of those “the road to hell was paved with good intentions” bills in what it will actually do.

Please contact your congress person and oppose this bill.


July 13th, 2011 by Jamie Estep

IRS reporting, just how bad is it?

Filed in: Industry News, Merchant Accounts | 5 comments

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’re finally past the day of reckoning, let’s revisit how this is exactly going to affect your merchant account and your business.

An Overview

Some time back, the IRS decided that they wanted to see a report of all the money that a merchant processes through their merchant account over the year.

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 “could” get caught. Regardless of the absurdity of requiring the entire country disclose their processing volumes, here we are…

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’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’s fair to say a lot of tax reporting information will not be valid.

So, what if the tax information is not valid?

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, 28% of all of your credit card sales with be held 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.

More fees

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’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’t authorize e-file for your 1099, your processor needs to mail you a physical form.

Exceptions

The exceptions to the filing requirements are:

1. a merchant’s total payment transactions for the year does not exceed $20,000, and
1. the total number of transactions does not exceed 200

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.

Conclusion

It’s unfortunate that the reporting regulation was ever passed. It’s a useless piece of legislation that creates a lot more work for small businesses and it’s unlikely that the reporting will catch any but the worst tax offenders. But, it’s passed and taking effect and there’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.


July 1st, 2011 by Jamie Estep

Payment Industry Changes – Debit Interchange Regulation

Filed in: Industry News, Merchant Accounts |

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 brought monumental changes to the payment processing industry.

Mobile frenzy

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’s arguments, and hopes to be a major player in mobile payments. If the Google Checkout service is any indicator of Google’s success in mobile payments, they simply aren’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.

Debit Interchange Regulation

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’s not entirely clear when and how this will take effect but stay tuned over the next months.

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’s and Amazon.com’s out there. There’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.

Expect major checking account changes

As a result of banks losing roughly 50% of their revenue from debit cards, we should all expect drastic changes 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.

It’s a mute point to argue my position on the interchange regulation at this time. Retailers may be chocking this up as a victory, but don’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.


March 10th, 2011 by Jamie Estep

A Square payment without proper research fails

Filed in: Credit Card Equipment, Fraud, Merchant Accounts | 8 comments

A long time ago I wrote an article about credit card skimming. It remains the most visited page on this blog, I believe, because credit card skimming is one of those concerns that apply to both consumers and to businesses.

About a year ago one of the founders of Twitter and some other talented business persons came up with a mobile payment method called square. Square is a very tiny card reader that attaches to the audio port on a smart phone. It’s truly a clever little device that utilizes an existing port that just about every phone has. Merchant’s can sign up with Square without any fee and just about instantly process. Because of the ease of setup, there’s been some angry customers with money held, but something like this should be expected as the services operates on a similar model to Paypal. Square got some quick funding, and went off to the races faster than any payment related service in history. However, there’s a problem…

Unfortunately, Square also introduced one of the most efficient and low cost methods of creating an advanced credit card skimmer. When you sign up with Square’s processing service, you get the square for FREE. That’s right, for free you can turn your iPhone into a credit card skimming device. Thieves don’t even have to pay the $50 or so for a skimmer anymore, they get one for free. Not only is Square efficient and free, but they’ve already distributed hundreds of thousands of these little skimming nightmares all over the US.

A criminal signs up with Square, obtains the dongle for free and creates a fake Square app on his smartphone. Insert the dongle into the audio jack of a smartphone or iPad, and you’ve got a mobile skimming device that fits in your pocket and that can be used to illegally collect personal and financial data from the magnetic stripe of a payment card. It’s shockingly simple.

There are 2 major problem with the Square hardware.

First, the square device does not encrypt data being transmitted between the reader and the phone. This could easily leave the service open to a targeted attack where other software could read the card information when it is being transmitted between the reader and the phone. This sort of issue may never be a major problem as it would take very specific software or a compromised phone for this flaw to be taken advantage of. However, it still remains a security possibility, one that cannot be overcome without updating the hardware completely.

Second, since the hardware has no encryption or secure link between it and the phone/square service, a programmer could easily write a program that would simply record the card information onto a database or file on the phone. This is the main problem that Verifone and many others are up in arms about. With the large memory cards that are commonly found in phones, a thief could theoretically store millions of card numbers on their phone. Additionally, since just about everyone has a cell phone, it is considerably less conspicuous for a thief to skim cards with a phone than with the dedicated skimmers which look something between a pager or a magnetic card reader you would see attached to a computer.

This morning, VeriFone launched an entire website dedicated towards bringing down square. While VeriFone is a direct and probably the largest competitor of Square with their PayWare Mobile App, they have quickly illustrated not only that the square can be used for skimming, but that there is software that can already be used with the square hardware.

The problem now is that there are tons of these square credit cards readers all over the place, so the damage has already been done. At this point there’s literally nothing that can be done to prevent skimming using square devices. There’s even applications for blackberry and android that already work with the square hardware even though it was designed for the iPhone and iPad. I think that this sort of hardware is a perfect example of what happens when a company pushes software or hardware without putting enough in the research in how to make it secure. There’s more than 1 way to steal a credit card number…

With the amount of focus on PCI and data security of the last 10 years this is a blatant disregard for the most basic best practices, even those established 10 years ago. Twitter may be a whimsical concept, but there’s really nothing amusing about completely botching credit card data security at the expense of consumers and the businesses whom accept those stolen cards…

Update 03-10-2011

So, Jack Dorsey issued a rebuttal to VeriFone‘s website and statements about the Square.

Second, as Dorsey points out, credit card fraud is not new. Every single time you hand over your credit card to someone (whether it is a merchant using Square, or any one of the dozens of other credit card input methods) you are trusting them not to steal it. Criminals steal credit card numbers all the time, both online and offline. But it happens, and when it does, consumers are not liable for fraudulent charges, the credit card companies are.

What’s not fair or accurate is Jack Dorsey’s fundamental lack of understanding of how the credit card industry works! Any merchant knows that if they accept a credit card that was stolen, they are liable for the fraudulent charges. There’s no magical credit card company that’s going to float in and take responsibility for it. The merchant loses when it comes to credit card fraud, plain and simple.

This disregard to merchants all while Square is trying to sell them a processing service is simply insulting. I’m a merchant as well, and this is just disrespectful.

After reading this, I am completely convinced that Jack Dorsey and Square have no business providing a payment service of any type to anyone. Stick to tweeting…


March 10th, 2011 by Jamie Estep

You can’t spend more than $50 on your debit card!

Filed in: Industry News |

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’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.