Quantcast StorefrontBacktalk » Blog Archive » Heartland Filing Contradicts Its Own Statements About Abandoning Retail Customers
advertisement
advertisement

Heartland Filing Contradicts Its Own Statements About Abandoning Retail Customers

Written by Evan Schuman
November 4th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

Proving that there’s never anything so bizarre in payment security circles that some vendor can’t upgrade it to surreal, Heartland Payment Systems and VeriFone this week issued dueling news releases. Each accused the other of either stealing intellectual property or trying to abandon Heartland’s retail customers.

That was bizarre. But when Heartland issued a statement that directly—almost word for word—contradicted its own legal filings, the situation took an Alice In Wonderland twist that makes retail tech worth covering.

The backdrop to this food fight is a pair of lawsuits between the two vendors. VeriFone in September sued Heartland, accusing it of trying to sell a POS terminal that infringes on a patent owned by VeriFone Israel (formerly Lipman Electronic Engineering), a subsidiary of VeriFone Holdings, according to The Nilson Report. VeriFone specifically said that the new Heartland device infringes on a patent covering “an antitamper enclosure for electronic circuitry in a point-of-sale terminal,” Nilson reported.

But Heartland then counter-sued, saying that VeriFone had threatened to cut off hardware, software and support services.

Then on Tuesday (Nov. 3), VeriFone issued a statement aimed at Heartland customers in which it offered to deliver—for free–”complete alternative support to merchants who are currently utilizing VeriFone payment solutions on Heartland Payment Systems‘ network.”

VeriFone’s statement said that it “is taking action to prevent any disruption to merchants after determining that the pending litigation over Heartland’s continual infringement of a VeriFone patent is likely to impact Heartland’s ability to maintain service levels with its customers. VeriFone has informed Heartland that it will terminate its support relationships with Heartland, effective end of day December 31, 2009.”

At the time the release was issued, Heartland was about to hold an investor call, during which CEO Bob Carr would add $35.6 million to its breach costs for the quarter, including “reserves for offers we made to settle certain claims, as well as charges for the expected costs of settlement of certain other claims.”

Hours later on Tuesday, Heartland issued a counter-statement describing the VeriFone offer as “a disingenuous attack” and dismissing suggestions that Heartland couldn’t support its own customers without VeriFone’s help. Heartland also labeled “false” the suggestion that VeriFone could support those Heartland customers.

“Heartland is fully capable–and will continue to be fully capable–of servicing all of its customers,” the statement quoted Carr as saying. “In fact, VeriFone is not able to support our customers. They can’t, because our customers operate on our proprietary payments processing platforms. Heartland is the only entity that can provide full service–including ongoing service of VeriFone terminals–to them. This means our servicing of VeriFone-related issues is not–and will not be–impacted by VeriFone’s false claims and unethical attempts to scare our customers.”

Heartland’s statement would have been a powerful one, had it not been contradicted by Heartland’s own legal filings. In its civil lawsuit against VeriFone, in the area where it’s trying to argue that VeriFone’s threat to cut off support is a big deal and worthy of legal intervention, Heartland addressed the issue.

“VeriFone is critical in serving existing customers and troubleshooting for problems with the POS terminals and credit card processing. Heartland provides troubleshooting and systems integration support for its merchants, which requires assistance from VeriFone,” Heartland’s brief said. “If Heartland were to be cut off from any support, its customers would be forced to reach out directly to VeriFone, which would result in a reduction of service to the customers.”

Heartland did not return a call seeking clarification.

VeriFone did respond to calls to clarify, but it also issued a statement to refute some of the Heartland countercharges. For example, Heartland said that its payment system is proprietary and that VeriFone, therefore, couldn’t support it.

“First, a majority of Heartland merchants do not use Heartland’s proprietary payment application, they instead use VeriFone’s SoftPay,” the VeriFone statement said. “Second, Heartland’s application relies on VeriFone’s platforms, operating systems and libraries. VeriFone will provide operational support, which includes transaction reports, functional issues and operational issues. Merchants will continue to rely on Heartland for reconciliation of payment issues.”

VeriFone said that “Heartland has approximately 240,000 merchants in total and VeriFone systems currently support an estimated 75 percent of Heartland’s restaurant, retail and petroleum customers.”


advertisement

3 Comments | Read Heartland Filing Contradicts Its Own Statements About Abandoning Retail Customers

  1. Alex Says:

    The first reaction that you have is that ‘when it rains it pours’ for Heartland and that they seem to be having a lot of bad luck, but then you think about it a bit more and you have to wonder about decision making…

    It seems like the problems that they are having lately are largely self-inflicted through poor or poorly thought-out decisions.

    I also don’t think it helps things when Bob decides that he’s going to be the one that comes out to discuss the problems, because he seems very focused on blaming anyone and anything for Heartland’s mistakes.

  2. Brian Says:

    I agree with Alex. Heartland has some real risk management issues, which have led to some really poor decisions. Not only did they improperly address PCI compliance by using a checklist approach, rather than a risk-based approach (Note to Heartland: Compliance is not security!); They’ve completely ignored the fact that they have a heavy reliance on a key supplier and they could find themselves out on the street if they alienate them, especially when that supplier is also a competitor.

  3. Tom Anderson Says:

    Bob Carr has developed a personality cult among his employess. However, he is finding that outsiders do not buy into his claims. And yes, I agree with above, all Carr does is play the blame game. I also am learning that Heartland has other internal problems as well. Their employee email system is as porous as a fish net. Their sales force is demoralized and underpaid and their service center is extremely disorganized. I also understand that that Heartland field techs are disatisfied and severly underpaid.

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

What’s The Rush For New PCI Call Center Requirements?

And I have not heard anyone mention the impact on companies who provide quality improvement services. Many merchants hire quality improvement companies to review their audio recordings to provide guidance on how to improve their sales staff’s effectiveness in customer service and sales retention. PCI Council needs to rethink this requirement until there is a widely available commercially viable solution. Read more...
Another ridiculous decision where regulators don't think critically enough about the unintended consequences of their decision. This will be a huge problem for the credit and collections industry. We have to keep all recorded calls for other reasons not related to cc information. We can't purge all of our calls and we don't have the technology to not record part of the conversation. Even if we did, I am not sure we could afford it. Read more...
This "clarification" is causing a lot of panic with large FS clients who now appear to be non-compliant after spending 7 figure sums on their compliance programs. The only alternative to call recording would now appear to be some sort of IVR/push button type interrupt to take card data away from the contact centre. The council is a position to force that sort of process and technology change and this may backfire on them and the vendors that lobbied hard for this clarification. Read more...
PCI council has made a one-sided decision; They should have done a much more in-depth research that could have provided more insight on what regards to the implications of such decision. Read more...

Will Old OS Cause PCI Violation? No, But Marketing Still Says So

This is an interesting issue, because there's more to it than what's apparent on the surface. PA-DSS requires supported and patched operating systems and other software components (e.g., databases, libraries, Java, etc.) per PA-DSS 7.1.b and 8.1, and the option for compensating controls simply isn't there. Merchants can make use of compensating controls for most PCI DSS requirements, but only when legitimate constraints exist and only in ways that meet the intent and rigor of the requirement and go above and beyond the other PCI DSS requirements. Read more...
Why would one automatically upgrade to a "new" OS -- some of the older versions of certain OS-es are more stable and more robust than the crap being peddled today. This is yet another clear example of PCI SSC being out of touch with reality. Rather than requiring a "current" OS, the requirement should be to demonstrate the OS in use is stable and robust, and is adequately hardened against threats. Read more...
There are compensating controls that encrypt the swipe at the driver level as it enter the PC, there are hardware encrypting card swipes so the cardholder data is already encrypted before it comes to the PC -- either of these, especially the second, would remove the OS entirely from a cardholder data risk profile. Read more...
In my opinion, the only thing the vendor did wrong was they didn’t know of that FAQ entry. Even if they did, it changes nothing about the need for merchants to update software that no longer receives updates. Read more...

MasterCard Blinks, Drops Dec. 31 Level 2 PCI Deadline

Reciprocity between MasterCard and Visa was always been a factor in Acquirer merchant level assignments. The brief removal of reciprocity generated a great deal of interest in being able to be classified at a lower level in MasterCard's world. Nevertheless the return of the reciprocity language in the December changes did not effectively create any new Level 2 merchants, but it DID dash the hopes of a lot of them.... :-( Read more...
Let's given them credit??? For being idiotic in the first place? Not on your life! Everyone has just had to scramble and include the costs of the previously announced M/C requirement in their 2010 budgets, and start negotiating with the QSAs for the additional services. All for naught! Read more...
"A bunch of Level 3 and Level 4 merchants just became Level 2s". Is this an accurate statement? MasterCard & Visa have historically included the caveat "or is a Level X in another brand" in their level setting criteria. MasterCard appeared to back way from this in the June pronouncement, and have simply returned to the status quo. Have Acquirers have been tracking and reporting merchants at separate levels by brand? Read more...
I stick by my comment (quoted in the column) about a bunch of L3 and L4 merchants becoming L2s and requiring an onsite. To me, what made MasterCard's original requirement for an onsite assessment for L2s palatable was that they took away their reciprocity provision. That is, they seemed to focus on larger merchants with over a million MasterCard trans/year. With reciprocity in place, a lot of smaller merchants are pulled into the onsite requirement. Rather than causing confusion, I think reciprocity will lead to additional work for processors and acquirers. Read more...

Retailers Sue POS Vendor, Questions Raised Where PCI Duties Stop

I would add a couple more questions: "did the breach involve the use of the default passwords?" (The story doesn't say.) And "were the default passwords used by Computer World to remotely administer the store systems?" "where is the PCI auditor in all this?" Did the restaurant group think they didn't need an audit because Radiant was (mis)representing Aloha as PCI compliant? How is a retailer or even a PCI auditor to know otherwise? A PCI auditor is not necessarily a qualified computer forensic investigator capable of finding the card data on the hard drives. They can only base a decision on information given to them by others. Read more...
There are so many holes in the process it will be difficult to pin blame on just one constituent. It is ridiculous that the technology exists to better secure these transactions (PIN, EMV, etc) yet banks won't use them. Only the banks or government can force this change, and retailers will suffer until then. Read more...
A major issue in this case will be if the restaurants had any support agreements in place with Computer World and if so what those agreements say. In my experience many single unit/small operators choose to skip the support agreements in favor of a "pay as you go" arrangement. In this scenario I can't imagine how the POS VAR can be held responsible for a system they don't own nor exclusively manage. Read more...
There is a big difference in having the POS installation guide say "make sure you set this password because the security of your CHD depends on this" vs. a POS application not storing the CHD in the first place. Traditionally only the merchant was liable for breaches and PCI related fees (fines). Maybe dragging some of the vendors into the liability mud fight will open the eyes of some of these vendors. Read more...

Should Credit Card Transactions Be Free? There May Be A Way

Here in the Netherlands, where the population is notoriously penny-pinching, credit card acceptance is amazingly low. It's both a result of the consumer not wanting to pay interest on everyday purchases as well as merchants not giving up a slice of the action. It is both legal and common to pass the processing fee onto the customer as a surcharge. Now things are moving to leave the credit cards behind: mobile phone payments are becoming more and more common here, and the transaction fees are minimal. Parking and entertainment (movie/concert tickets, nightclubs) have been amongst the first, and it's rapidly gaining momentum because the market has been hungry for the convenience at a price it is willing to pay. Read more...
"Free" is an illusion. Don't charge one person but charge double to someone else. I am very skeptical on anyone who says that advertising will create valid cashflow. Just look at the advertising struggles in a TiVo world. And if you sell your customers data, just be warned that the one group that might have issue with that are you customers (which to me is very important to cashflow. Read more...
Another factor not mentioned here is the impending costs that the processors and issuers are going to incur when someone decides on an end-to-end encryption method, and it then becomes government mandated. I can guarantee that this is a when question and not an if question. The back-end networks are pretty antiquated right now, and it's going to cost billions to replace everything. The cost of tech may be going down, but the cost of replacing millions of servers and hardware, and creating new, proprietary, software is still really expensive. Read more...
Accepting credit cards are not "risk-free" for merchants, contrary to Jim's comments above. Chargebacks are an expense - both in terms of actual transaction reversals and costs associated with managing the process. Chargeback rules and expenses can be everything from a thorny issue to an onerous expense for some merchants, especially for convenience stores that allow customers to pay for gasoline at the pump, or other retailers that allow in-store self-checkout options. Read more...
I've wondered for years why the price of transactions has been so high. Phone companies long ago started offering unlimited calling for flat rates because they understood that in many cases it cost more to report on the transactions (calls) than it did to fulfill them. Read more...
If a home-owner defaults on the mortgage, who is taking the risk? The bank making the loan to the consumer or the person selling the house? It is obviously the bank that takes this risk and is rewarded for that risk through interest rate charges. In my mind, we have mixed together two distinct and unrelated transactions. Read more...
The one big factor not mentioned in this article is who will take over the risk ? Taking credit cards is risk free to merchants and the issuing Banks take the risk if a customer defaults on the payments ! If you had a "interchange free" payment system will the merchants assume the risk ? Also, if there isn't enough profit for the issuing banks they will stop issuing credit cards which will in turn kill our economy. Read more...

The Dangerous Out-Of-Scope PCI Charade

If tokens are ever deemed in-scope, then where does the line stop? I ask this because it would mean that all timestamps, sequential number, random numbers or any other piece of information that may or may not be used to generate a token is within scope -- all data a POS uses and stores, not just payment data. Read more...
Having the ability to do both Tokenization and End to End Encryption (not mere point to point) can have tremendous scope and risk reduction benefits and agility to adapt to change in this fast moving compliance landscape. Being able to have both on tap from a single platform is a solid approach to avoiding the pitfalls. Read more...
But the consumer walks into a particular retail chain, gives their payment card to someone wearing that chain's uniform and the card is swiped. If, six months later, there's a breach and that card was misused, it's the retailer who will in the spotlight. They're the deep pocket and, therefore, the target. If the consumer is angry and wants to cut off business, it will hit the retailer. Therefore, if the retailer is going to end up being blamed no matter what, they have to stay involved. Read more...
True, that someone may be storing a token-to-PAN cross reference. But that would be the bank, not the retailer. If the bank is not sure they can keep their data secure, then there are bigger problems to be addressed than bringing tokens into scope. Read more...
Good general point, Steve, but for the record, not all tokenization is done the same way. Many tokens are associated with lookup lists that allow for them to re-matched to the card data if it's needed, such as for a chargeback. A token doesn't have to be decryptable (is that a word?) for there to be a way to access the original data. Read more...
The out-of-scope argument is very valid but in reference to tokens, the premise of temporarily out-of-scope or abruptly deemed in-scope is flawed. Conway was quoted “anything that could be made unreadable can, in various ways, be made readable again,” this statement is true when talking about encryption technologies (all encryption technologies) but not so with true tokens. True tokens are in no way related to the original data other than as a reference key. Read more...