Payment Logistics Limited v. Lighthouse Network, LLC

District Court, S.D. California·Decided November 30, 2020·No. 3:18-cv-00786·Unknown

Opinion

1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 SOUTHERN DISTRICT OF CALIFORNIA 10 11 PAYMENT LOGISTICS LIMITED, Case No.: 3:18-cv-00786-L-AGS

12 Plaintiff, ORDER GRANTING DEFENDANTS’ 13 v. MOTION TO DISMISS [doc. no. 104] AND DENYING PLAINTIFF’S 14 LIGHTHOUSE NETWORK, LLC et al., MOTION TO FILE A SUR-REPLY 15 Defendants. [doc. no. 114] 16 17 Pending before the Court is Defendants’ motion to dismiss Plaintiff’s second 18 amended complaint. Plaintiff opposed the motion and Defendants replied. To the extent 19 Defendants raised new arguments in their reply, the arguments were not considered in 20 this order. See Zamani v. Carnes, 491 F.3d 990, 997 (9th Cir. 2007) ("The district court 21 need not consider arguments raised for the first time in a reply brief."). Accordingly, 22 Plaintiff’s motion to file a sur-reply (doc. no. 114) is denied as moot. The Court decides 23 the motions on the briefs without oral argument. See Civ. L. R. 7.1 (d.1). For the reasons 24 stated below, Defendants’ motion to dismiss is granted. 25 I. BACKGROUND 26 Plaintiff Payment Logistics Limited (“PLL”) alleges antitrust violations in the 27 payment processing industry for mid-to-large table-service restaurants. Between 2017 28 and 2019, through horizontal and vertical acquisitions, Defendant Lighthouse Network, 1 LLC (“Lighthouse”) acquired some of Plaintiff’s competitors and vertically integrated its 2 services. Plaintiff claims Defendants’ mergers and acquisitions substantially lessen 3 competition. 4 Restaurants1 utilize the following products and services to process customers’ card 5 payments: (1) point-of-sale (“POS”) systems, which are comprised of hardware, 6 software, and external support services that enable merchants to manage restaurant 7 operations and process payments; (2) merchant account services, which enable merchants 8 to connect to a network of credit and debit card companies for authorization and 9 settlement of electronic payment transactions; and (3) direct processors and/or payment 10 interfaces, which transmit payment data from POS systems to merchant account service 11 networks. (Second Am. Compl., doc. no. 117 (“SAC”),2 at 6-7).3 12 Restaurant owners purchase POS systems, which serve as the “brain” of the 13 restaurant operations, managing everything from seating and reservations, patrons’ 14 orders, assisting the kitchen to prepare orders so that the patrons at the same table 15 uniformly receive their courses at the appropriate time, inventory tracking, recording 16 employee time, financial and productivity oversight, as well as payment processing. 17 (SAC ¶¶ 37, 38.) The POS system represents a significant investment in time, money 18 and business disruption for the restaurant, and is therefore rarely switched more than 19 every five to seven years. (Id. ¶¶ 38, 73.) POS dealers assist restaurants in selecting the 20 POS system to fit their needs. (Id. at 7.) If the need arises, rather than changing the 21 22

23 24 1 The relevant segment of the restaurant industry is mid-to-large table-service restaurants. All references to restaurants relate to this segment. 25 2 The first and second amended complaints, as well as the parties’ motion to dismiss 26 briefing were filed under seal pursuant to leave of Court. Redacted public versions were 27 separately filed at docs. no. 59, 98, 115 (Plaintiff’s opposition).

28 1 entire POS system, a restaurant is more likely to upgrade its software, including the 2 payment interface and/or merchant account service. (Id. ¶ 38.) 3 Once a restaurant installs a POS system, it may be limited to the payment 4 interface(s) and/or merchant account service provider(s) already integrated in the system 5 or that can quickly become integrated. (SAC ¶ 74.) Software developers who create 6 POS systems dictate which payment interfaces are capable of integration with their POS 7 system software. (Id.) A POS system may offer multiple payment interfaces, allowing a 8 restaurant owner a choice of payment interfaces, and consequently also a choice of 9 merchant account service providers. (Id. ¶ 77.) 10 Since approximately 2014, the industry has been undergoing “significant 11 consolidation,” resulting in alliances or acquisitions vertically integrating POS systems, 12 payment interfaces, and merchant account service providers. (SAC ¶ 79; see also First 13 Am. Compl., doc. no. 88, ¶ 60.) Such networks are considered “closed.” (SAC ¶ 79.) 14 This means that the POS system may be compatible only with a specific payment 15 interface or interfaces, and the payment interface may be aligned with a specific merchant 16 account service provider. (Id. at 5; see also id. ¶¶ 3, 64, 78.) In contrast, payment 17 interfaces that are compatible with multiple POS systems or merchant account networks 18 are considered “neutral” or “independent.” (Id. at 5; see also id. ¶¶ 3, 64.) Prior to 19 consolidation, many POS systems offered multiple payment interfaces, each providing 20 restaurant owners with a choice of payment interfaces and merchant account service 21 providers. (Id. ¶ 77.) With consolidation, many POS systems became “closed.” (See id. 22 ¶ 80.) 23 Whether a payment interface is closed or neutral makes a difference. (SAC ¶ 64.) 24 Neutral or independent payment interfaces charge restaurants the same data transmission 25 fee regardless of the merchant account service provider, while closed interfaces charge 26 more for merchant account services outside the closed network. (Id. at 5.) 27 Plaintiff provides independent payment interfaces and merchant account services 28 in the relevant restaurant segment. Prior to the mergers and acquisitions that form the 1 basis for this action, Lighthouse owned Harbortouch, a POS system, and provided 2 merchant account services. (SAC ¶¶ 5-6.) In the summer and fall of 2017, Lighthouse 3 acquired three POS systems (Restaurant Manager, Future POS, and POSitouch). (Id. ¶¶ 4 5, 80, 81.) After the acquisition, it “restricte[ed] POS Dealers’ promotion of non- 5 Lighthouse-affiliated Payment Interfaces, such as PLL.” (Id. ¶ 80.) 6 In January 2018, Lighthouse acquired Defendant Shift4 Corporation (“Shift4 7 Corp.”), a payment interface company. (Id. ¶ 6.) Lighthouse created Defendant Shift 4 8 Payments, LLC (“Shift4”), a new company which consolidated the three levels of the 9 payment processing industry: POS systems, payment interfaces, and merchant account 10 services. (Id.) 11 Prior to the acquisition, Shift4 Corp. was an independent payment interface 12 compatible with multiple merchant account service providers. (SAC ¶¶ 6, 22, 64.) As 13 part of the merger, Lighthouse planned to eliminate Shift4 neutrality to increase 14 transaction fees. (Id. ¶ 6.) In February 1, 2018, Defendants started to steer the 15 restaurants using Defendant-owned POS systems to Shift4 for payment processing. 16 (SAC ¶¶ 90-91.) They sought to accomplish this by charging restaurants higher fees for 17 processing payments outside the Shift4 network. (Id. ¶¶ 10, 90-91.) 18 In 2018, Shift4 negotiated strategic partnerships with two independent software 19 vendors who provided software for POS systems Maitre’D and Micros. (SAC ¶ 6.) 20 In September 2019, Defendants acquired Defendant Merchant Link, LLC 21 (“Merchant Link”), one of the largest payment interfaces in the relevant restaurant 22 segment. (SAC ¶ 11.) With this acquisition, Defendants increased their share of the 23 payment interface market for POS systems in the relevant restaurant segment to 47%. 24 (Id. ¶¶ 11, 86.) Before the acquisition, Merchant Link was an independent payment 25 interface. (Id. at 4; see also id. ¶ 84.) Post-acquisition, Defendants started “attempting to 26 coerce” Merchant Link users to migrate to the Shift4 interface. (Id. ¶ 11.) 27 The majority of Merchant Link clients in the relevant market use Micros, one of 28 the largest POS systems.

Free access — add to your briefcase to read the full text and ask questions with AI

Payment Logistics Limited v. Lighthouse Network, LLC, (S.D. Cal. 2020).

Payment Logistics Limited v. Lighthouse Network, LLC (Payment Logistics Limited v. Lighthouse Network, LLC) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Foman v. Davis
371 U.S. 178 (Supreme Court, 1962)
Atlantic Richfield Co. v. USA Petroleum Co.
495 U.S. 328 (Supreme Court, 1990)
Watters v. Wachovia Bank, N. A.
550 U.S. 1 (Supreme Court, 2007)
Vera v. McHugh
622 F.3d 17 (First Circuit, 2010)
United States v. Shinderman
515 F.3d 5 (First Circuit, 2008)
Robert S. Robertson v. Dean Witter Reynolds, Inc.
749 F.2d 530 (Ninth Circuit, 1984)
Rafael Navarro v. Sherman Block
250 F.3d 729 (Ninth Circuit, 2001)
Zucco Partners, LLC v. Digimarc Corp.
552 F.3d 981 (Ninth Circuit, 2009)
Lien Huynh v. Chase Manhattan Bank
465 F.3d 992 (Ninth Circuit, 2006)
Zamani v. Carnes
491 F.3d 990 (Ninth Circuit, 2007)
Lee v. City of Los Angeles
250 F.3d 668 (Ninth Circuit, 2001)
Ebner v. Fresh, Inc.
838 F.3d 958 (Ninth Circuit, 2016)