MiCamp Solutions LLC v. PayStream LLC

CourtDistrict Court, D. Arizona
DecidedJanuary 30, 2024
Docket2:23-cv-01842
StatusUnknown

This text of MiCamp Solutions LLC v. PayStream LLC (MiCamp Solutions LLC v. PayStream LLC) is published on Counsel Stack Legal Research, covering District Court, D. Arizona primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
MiCamp Solutions LLC v. PayStream LLC, (D. Ariz. 2024).

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

9 MiCamp Solutions LLC, No. CV-23-01842-PHX-ROS

10 Plaintiff, ORDER

11 v.

12 PayStream LLC, et al.,

13 Defendants. 14 15 Plaintiff MiCamp Solutions LLC believes its former employees, Defendants Jeremy 16 Fried and Robert McDonald, engaged in misconduct during and after their employment. 17 MiCamp also alleges it entered into a contract with PayStream LLC, a company associated 18 with Defendant Fried, but PayStream subsequently breached that contract. The complaint 19 contains no specific facts regarding the events underlying MiCamp’s claims. Instead, the 20 complaint provides basic background information and then recites the elements of each 21 claim. The lack of supporting factual allegations requires the complaint be dismissed. 22 BACKGROUND 23 MiCamp “is in the business of promoting credit and debit card processing services 24 for merchants.” (Doc. 15-1 at 2). The complaint does not provide any additional 25 explanation of MiCamp’s business but it appears MiCamp locate merchants who wish to 26 obtain payment processing services from larger entities, such as Wells Fargo. As of some 27 unidentified date, Fried was the Chief Technology Officer for MiCamp while McDonald 28 was the Director of Software Engineering. In those positions, both Fried and McDonald 1 had access “to sensitive and highly confidential business and technology information.” 2 (Doc. 15 at 3-4). 3 On an unidentified date, Fried left his employment with MiCamp. Upon leaving, 4 Fried retained some of MiCamp’s confidential information. The complaint does not 5 identify what information Fried retained. As for McDonald, he remained at MiCamp after 6 Fried left. On an unidentified date while McDonald was still working for MiCamp, Fried 7 “solicited McDonald to provide work for” a separate company. (Doc. 15 at 5). McDonald 8 accepted and “utilized MiCamp’s time and resources to provide services” to that company. 9 (Doc. 15 at 5). On an unidentified date, McDonald left MiCamp’s employment. 10 McDonald allegedly retained MiCamp’s confidential information but, as with Fried, the 11 complaint does not identify what information was retained. 12 On March 21, 2021, MiCamp and an entity known as PayStream LLC entered into 13 a written agreement. The agreement stated PayStream would locate merchants “interested 14 in procuring” payment processing services from MiCamp. (Doc. 15-1 at 2). The 15 agreement promised MiCamp would pay PayStream based on the number of merchants 16 PayStream located. As part of the contract PayStream agreed it would not “call on, solicit, 17 take away, or attempt to call on, solicit, or take away any of the merchants [or] customers” 18 of MiCamp. (Doc. 15-1 at 6). According to MiCamp, the agreement was binding on 19 PayStream as well as Fried because “Fried was the alter ego of Paystream.” The complaint 20 does not allege any facts supporting this alter ego relationship. (Doc. 15 at 6). 21 In May 2021, MiCamp and PayStream entered into a second written agreement 22 “related to the licensing of certain source code and/or software” owned by a nonparty. 23 (Doc. 15 at 8). The complaint alleges PayStream “fraudulently misrepresented material 24 terms of that agreement” to MiCamp, including the purchase price. (Doc. 15 at 8). No 25 details are given regarding these misrepresentations. Moreover, there is no explanation 26 how PayStream was able to misrepresent the terms of an agreement that MiCamp itself 27 signed. Most importantly, the complaint does not assert any claims related to this second 28 written agreement and why it is referenced in the complaint is a mystery. 1 Based on these limited facts, MiCamp alleges claims for breach of fiduciary duty 2 against Fried and McDonald. The complaint bases these claims on unidentified actions 3 taken while Fried and McDonald worked for MiCamp. MiCamp also alleges a claim for 4 tortious interference against Fried based on Fried’s contact with McDonald while 5 McDonald still worked for MiCamp. Finally, MiCamp alleges claims for breach of 6 contract and breach of the covenant of good faith and fair dealing against PayStream and 7 Fried. The contract-based claims are based on PayStream and Fried allegedly violating the 8 written agreement requiring PayStream locate merchants for MiCamp. The complaint 9 alleges the written agreement was breached in numerous ways but, as with all the other 10 claims, there are no factual allegations identifying the particular actions of PayStream and 11 Fried that breached the agreement. McDonald answered the complaint while PayStream 12 and Fried filed a joint motion to dismiss. 13 ANALYSIS 14 Resolving the motion to dismiss requires the Court accept all of MiCamp’s factual 15 allegations as true and construe them in the light most favorable to MiCamp. While 16 “detailed factual allegations” are not required, “labels and conclusions” together with “a 17 formulaic recitation of the elements of a cause of action will not do.” Bell Atl. Corp. v. 18 Twombly, 550 U.S. 544, 555 (2007). To avoid dismissal, MiCamp’s complaint needed to 19 contain “more than an unadorned, the-defendant-unlawfully-harmed-me accusation.” 20 Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009). The present complaint does not satisfy these 21 requirements as there are so few factual allegations it is impossible to know why, exactly, 22 MiCamp is suing PayStream and Fried. 23 I. Tortious Interference 24 MiCamp asserts a tortious interference claim against Fried. To state such a claim, 25 MiCamp was required to allege facts showing five elements: “the existence of a valid 26 contractual relationship or business expectancy,” Fried knew of “the relationship or 27 expectancy,” Fried’s actions induced or caused “a breach or termination of the relationship 28 or expectancy,” MiCamp suffered damage as a result, and Fried’s interference was 1 “improper as to motive or means.” Neonatology Assocs., Ltd. v. Phoenix Perinatal Assocs. 2 Inc., 164 P.3d 691, 693 (Ariz. Ct. App. 2007). The final element requiring the interference 3 be “improper” is crucial and Arizona courts use a seven-factor test to differentiate between 4 proper and improper interference. Id. 5 MiCamp bases its tortious interference claim on allegations Fried knew McDonald 6 was MiCamp’s employee when Fried “solicit[ed] McDonald to perform services for” a 7 nonparty. (Doc. 15 at 12). As best as the Court can tell, MiCamp believes it constituted 8 tortious interference for Fried to offer McDonald alternative employment while McDonald 9 was still employed by MiCamp. Even assuming Fried’s action satisfied the first four 10 elements of tortious interference, there are no allegations showing Fried’s actions were 11 “improper as to motive or means.” Neonatology Assocs., 164 P.3d at 693. Absent 12 additional facts, such as the presence of an agreement prohibiting such actions by 13 McDonald or Fried, the act of soliciting McDonald to work elsewhere does not qualify as 14 tortious interference. See Bar J Bar Cattle Co. v. Pace, 763 P.2d 545, 549 (Ariz. Ct. App. 15 1988) (recognizing action motivated by “legitimate competitive reason” undercuts tortious 16 interference claim). The tortious interference claim must be dismissed. 17 II. Breach of Contract 18 MiCamp asserts a breach of contract claim against Fried and PayStream based on 19 the contract where PayStream promised to locate merchants “interested in procuring” 20 payment processing services from MiCamp. (Doc. 15-1 at 2).

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

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Silverton v. Department Of The Treasury
644 F.2d 1341 (Ninth Circuit, 1981)
Bar J Bar Cattle Co., Inc. v. Pace
763 P.2d 545 (Court of Appeals of Arizona, 1988)
Neonatology Associates, Ltd. v. Phoenix Perinatal Associates Inc.
164 P.3d 691 (Court of Appeals of Arizona, 2007)
Bike Fashion Corp. v. Kramer
46 P.3d 431 (Court of Appeals of Arizona, 2002)

Cite This Page — Counsel Stack

Bluebook (online)
MiCamp Solutions LLC v. PayStream LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/micamp-solutions-llc-v-paystream-llc-azd-2024.