{"id":3995,"date":"2019-02-26T06:16:15","date_gmt":"2019-02-26T12:16:15","guid":{"rendered":"https:\/\/reformingretail.com\/?p=3995"},"modified":"2019-02-26T06:16:23","modified_gmt":"2019-02-26T12:16:23","slug":"from-the-front-line-payments-companies-still-cant-sell-pos","status":"publish","type":"post","link":"https:\/\/reformingretail.com\/index.php\/2019\/02\/26\/from-the-front-line-payments-companies-still-cant-sell-pos\/","title":{"rendered":"From the Front Line: Payments Companies Still Can’t Sell POS"},"content":{"rendered":"\n

It should be no secret that payments is encroaching on POS\u2019s territory<\/a>. From white labeling and reselling POS solutions, to buying POS companies outright, banks and their acquiring channels view POS as a tourniquet for their payment churn woes. By that we mean that payments processing is a massively commoditized game of price matching: everyone runs around offering the same solution and he with the lowest rate wins the deal. As such churn is very high and a POS is much harder to replace when it\u2019s bundled with payments (as the POS has operational implications when it\u2019s yanked out).
<\/p>\n\n\n\n

Yet the cultures of the two organizations are drastically different and it becomes apparent when looking at two qualities.
<\/p>\n\n\n\n

\"\"
andertoons.com<\/figcaption><\/figure>\n\n\n\n

First is product. All processing is virtually the same. No matter the type or size of merchant, the offering is very similar. Sure there are different card types and risks, but generally that has a lot of carry over to any merchant you can conceive. So the payments service you’d sell to a mall kiosk operator is the same you\u2019d sell to a $500M retail chain. POS, on the other hand, couldn\u2019t be more different. Feature complexity is tied directly to operations and businesses operate differently. That\u2019s partially why there are so many POS companies out there<\/a> – multiple niches and segments are hard for even well-funded incumbents to serve adequately. Because there\u2019s such a large product difference, processors have immense difficulty appropriately and ethically<\/em> selling POS.
<\/p>\n\n\n\n

Second is support. Many would argue that support in payments is merely lip service – that payments is as close to set-it-and-forget-it as one will get and thusly payments companies don\u2019t emphasize their support operations. POS is a much more critical tool for business success, is more complex, and has traditionally come with 24\/7 support models, including on-site expertise should a business be willing to pay. Payments companies are not set up this way. In fact we\u2019ve noted on multiple occasions <\/a>that POS companies too often receive the first support call as the merchant has learned their payments provider defines “support” much differently than they do. So somewhat related to product differences, payments companies are not built for the level of support needed to successfully manage POS (though there are tools helping them get there<\/a>).
<\/p>\n\n\n\n

To heap even more skepticism on the notion that payments companies will successfully sell and support POS in the near term we turn to some anecdotes from the field. Our sources requested that they remain anonymous as they are often installation and support service providers for processor-bundled POS systems. More specifically, they accept installation work from a national network of POS and general retail technology installation dispatchers. A lot of their work comes from Toast, who is so concentrated on sales that they can\u2019t keep up with their installation backlog, and Upserve, who has no field installers at all.
<\/p>\n\n\n\n

When a job is advertised for either Toast or Upserve, we take it. We do so because we have a really good feel for how that install is going to go; that\u2019s because these POS companies require site surveys ahead of time. For instance, Toast does their own site surveys and provides us with the details, and Upserve will dispatch us to do a site survey before committing to anything greater. In this way we understand all of the X factors we’ll encounter before we get too far down the road.
<\/p><\/blockquote>\n\n\n\n

This is a stark contrast from the work they get from banks and processors.
<\/p>\n\n\n\n

When we receive an advertisement (it’s an alert that a job is available, similar to how Uber and Lyft drivers receive requests) and the customer is Elavon, many of us think twice. If it’s Elavon, it’s likely going to be an NCR Silver job or one from Talech. In the case of either POS we\u2019ve literally never seen a site survey done. Talech site surveys are nearly always \u2018done\u2019 by the bank rep. Bank reps don’t understand very much about networking, routers, cabling, or wifi. They get it wrong every time.
<\/p><\/blockquote>\n\n\n\n

We have some inklings for why this occurs, but let\u2019s turn to some specific anecdotes from one of our sources.
<\/p>\n\n\n\n

I know of about a dozen bank POS installs that have been done in my area. All of them have gone poorly with the exception of a handful that only had one or two terminals. On the last Talech installation, the bank rep had sold the merchant two Cradlepoint MBR routers which could only be located near the customer’s Comcast gateway. The site didn’t have strong enough wireless signal to reach the service area. The bank rep also sold the merchant kitchen printers and cash drawers they simply didn’t need. On top of all of that, the merchant was sold iPad Pro’s without the proper stands and all of the iPads shipped with Verizon 4G\/LTE service. This is totally unnecessary if the merchant got a 4G\/LTE modem to serve as the failover.
<\/p><\/blockquote>\n\n\n\n

These experienced field technicians also find the same problem with processor support that merchants find. \u201cWhen something goes wrong we reach out to the bank to figure what hardware has been installed, why it\u2019s been installed, and then perform a gap-analysis to see what\u2019s missing. When we\u2019ve dialed the Clover support line, as an example, we get a prompt for a merchant ID. We pump this in and then the phone rolls over to some ISO rep’s cellphone, which is invariably on a golf course. It never fails.\u201d
<\/p>\n\n\n\n

If this reads as a joke it shouldn\u2019t: these are merchants whose livelihoods are on the line, and payments processors are not handling them properly. Why does this happen?
<\/p>\n\n\n\n

Payments culture.<\/strong>
<\/p>\n\n\n\n

Payments reps are given quotas. They\u2019re not incentivized to successfully sell or support a POS, only to hit their payments numbers. So is it surprising that the rep will do anything to sell the system and attach their processing, even if there\u2019s no fit? This of course creates a cascade of downstream problems.
<\/p>\n\n\n\n

  1. The processor is on the hook to deliver a POS that might not even physically work in-store. There\u2019s a juggling act of hardware and installation services that follow, increasing the processor\u2019s costs<\/li>
  2. The customer acquisition cost (CAC) skyrockets as resources are levied to appease the merchant – all in an effort to keep the payments business, mind you, not because it\u2019s the right thing to do<\/li>
  3. Merchants learn to hate POS because they\u2019ve had a terrible first experience, and this makes sales cycles shittier for everyone across the industry<\/li><\/ol>\n\n\n\n

    Payments companies would make more money if they were more transparent. If street reps had visibility into POS sale and support costs, they might not put their employer on the hook all the time. If quotas were were tied to the length of time merchants kept their POS systems, we\u2019d probably see some drastic changes in culture too.
    <\/p>\n\n\n\n

    Alas, transparency and payments are two words that hardly ever go together. When viewed in the context of the undeniable future of software and data, payments is still the tail wagging the dog.
    <\/p>\n