Innovate1 v. First Bridge Merchant Solutions, LLC

• Court: District Court, C.D. California
• Decided: March 14, 2022
• Docket: 2:20-cv-07681
• Status: Unknown

Opinion

Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 1 of 14 Page ID #:1354

6 UNITED STATES DISTRICT COURT 7 CENTRAL DISTRICT OF CALIFORNIA 8

9 INNOVATE1 SERVICES INC, et al., Case No. 2:20-cv-07681-SB (AGRx) 10 11 Plaintiffs/Counter- Defendants, FINDINGS OF FACT AND 12 CONCLUSIONS OF LAW 13 vs.

14 FIRST BRIDGE MERCHANT 15 SOLUTIONS, LLC, et al.,

16 Defendants/Counter- 17 Claimants.

21 This case involves a dispute between an online visa and passport application 22 processor, Plaintiff and Counter-Defendant Innovate Services Inc. (Innovate1), and its 23 former payment processor, Defendant and Counter-Claimant First Bridge Merchant 24 Solutions, LLC (FBMS). Innovate1 and its owner and president, Anthony 25 Nwachukwu, have brought claims for breach of contract, breach of fiduciary duty, 26 fraud, and conversion. FBMS has brought counterclaims for breach of contract, fraud, 27 and unfair business practices. The Court held a bench trial in this case. After 28

1 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 2 of 14 Page ID #:1355

1 evaluating the evidence at trial and weighing credibility, the Court issues the findings 2 of fact and conclusions of law as set forth below. 3 4 PLAINTIFFS’ COMPLAINT 5 1. Innovate1 provides online visa and passport application processing 6 services, and Nwachukwu is the owner and president of Innovate1. FMBS provides 7 services as a payment processor for merchants like Innovate1. 8 2. In 2014, Innovate1 contracted with Newworks Limited to provide visa 9 and passport application processing services for the Government of Nigeria. 10 Newworks Limited appointed and authorized a subsidiary, Newworks Inc., to accept 11 the funds on its behalf. Nwachukwu is a 40% owner of Newworks Limited and 12 accepted appointment on behalf of Newworks Inc. Ex. 21. 13 3. For a company like Innovate1 to accept credit card payments online, it 14 must use a payment processor. From 2011 to 2015, Marc Geolina and Ryan Rainey 15 provided payment processor services to Innovate1 and its predecessor, SW Global 16 LLC, through their company GrayPay. In 2016, Geolina and Rainey approached 17 Innovate1 and proposed a contract for payment processing services with their separate 18 entity, FBMS. 19 4. On December 15, 2016, Innovate1 and FBMS entered into a merchant 20 agreement (Agreement). Ex. 32. Under the Agreement, FBMS agreed to provide 21 payment processing services for Innovate1’s online visa and passport applications and 22 open a reserve deposit account on Innovate1’s behalf. FBMS would be entitled to a 23 “discount rate” (or commission) of 5% (which FBMS could increase up to 12% at its 24 discretion) of the total payments transacted, plus various other fees. After deducting 25 the fees to which it was entitled, FBMS was required to settle the funds owed to 26 Innovate1 on a weekly basis. FBMS was also authorized to retain in the reserve 27 account 10% of the total payments received as security for liabilities on a rolling six- 28 month basis.

2 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 3 of 14 Page ID #:1356

1 5. FBMS opened an account at a Bulgarian bank named Transact EU for 2 purposes of processing the transactions for Innovate1. FBMS also set up an 3 application processing interface (API), a software intermediary program that allowed 4 the Innovate1, FBMS, and bank computers to communicate with each other. The 5 record of each transaction made by Innovate1 and its customers (including the date, 6 time, and amount of the transaction) was recorded and saved in real time through the 7 API gateway on the parties’ respective server/database. 8 6. Payment processing under the Agreement occurred for approximately 15 9 months, starting in December 2016. During this period, however, issues arose with 10 FBMS’s reporting on the transactions, including the failure to consistently provide 11 weekly reports. Out of the 64 weeks of transacting business, FBMS provided only 48 12 weekly summaries. Ex. 261, at 4–5. And when reviewing records of the individual 13 transactions, Innovate1 noticed that the weekly summaries did not accurately report 14 the number of transactions and dollar amounts. Ex. 40. Nwachukwu raised questions 15 about, among other things, FBMS’s withholding of excessive reserve amounts and its 16 failure to provide weekly accountings, to settle the accounts on a weekly basis, and to 17 disburse any payments for several weeks. 18 7. On December 27, 2017, Nwachukwu again raised these issues 19 concerning FBMS’s performance and demanded that certain changes be made if 20 Innovate1 were to continue doing business with FBMS. Ex. 196. Nwachukwu also 21 raised issues about “shortfalls in deposits” from January 2017 to December 2017. Id. 22 Over the next several weeks, Nwachukwu continued to inquire about obtaining these 23 funds. 24 8. On March 8, 2018, Innovate1 stopped processing payments through 25 FBMS and began using another processor because of the outstanding issues. Ex. 236. 26 No funds have been distributed to Innovate1 pursuant to the Agreement since 27 February 22, 2018. 28 9. During trial, both parties conceded that Innovate1’s case largely involves

3 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 4 of 14 Page ID #:1357

1 an accounting dispute that turns on a disagreement between the parties’ principal 2 experts. At a high level, the disagreement centers around the total amount of money 3 received from the transactions processed by FBMS, the total amount of money 4 retained by FBMS, and the total amount of money paid to Innovate1. A major 5 difference in the experts’ conclusions turns on the different data upon which they 6 relied in making their calculations. 7 10. Plaintiffs’ expert, Frank Gramlich, based his calculations on an Excel 8 spreadsheet that contained the API gateway records of all transactions and payments 9 processed through FBMS. Ex. 262. Gramlich calculated Innovate1’s damages by 10 applying the rates actually charged by FBMS as shown in its summary reports to the 11 actual sales amounts shown in the spreadsheet. For each week in which FBMS 12 produced a weekly summary but did not include every transaction from the relevant 13 period, Gramlich accepted the rate and fee structure applied by FBMS in the 14 corresponding weekly summary. To recreate summaries for the 16 missing weeks, 15 Gramlich “assumed” that the rate and fee structure did not change within the relevant 16 period and accepted FBMS’s rates and fees as stated in the weekly summaries 17 preceding and following the gap. Ex. 261.1 Gramlich concluded that: 18 (1) $873,275.79 in funds from the transactions were not deposited into the Transact 19 EU account; (2) FBMS took excess fees, commissions, and rolling reserve deposits of 20 $1,987,368.75 from the funds deposited into the Transact EU account; and (3) FBMS 21 failed to release $982,478.50 from the reserve account. Accordingly, Gramlich 22 calculates a total loss of $3,843,123.04. Id. 23 11. FBMS recognized in its closing argument that neither party has provided 24 the Court with perfect source data to determine the amount of money owed to 25 Innovate1, but it objects to the admission of the spreadsheet relied upon by Gramlich. 26

27 1 FBMS does not challenge Mr. Gramlich’s extrapolated calculation of the various 28 rates and fees.

4 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 5 of 14 Page ID #:1358

1 FBMS argues that the spreadsheet was created by a third-party entity that serves as 2 Innovate1’s “IT/back office personnel,” Jan. 24 Nwachukwu Decl. ¶ 24, and therefore 3 is hearsay that does not fall within the business records exception, Fed. R. Evid. 4 803(6). The spreadsheet contains a list of all payment transactions that were 5 processed through the API gateway; those transactions are “automatically computer- 6 generated” in real time “without human input or review” and are not considered 7 hearsay. United States v. Gonzales, 615 F. App’x 405 (9th Cir. 2015); see also United 8 States v. Lizarraga-Tirado, 789 F.3d 1107, 1110 (9th Cir. 2015) (“[M]achine 9 statements aren’t hearsay.”). The records in the spreadsheet thus fall outside the 10 purview of Rule 801. 11 12. Even if the records were hearsay, however, the spreadsheet that contains 12 them falls within the scope of the business records exception. Nwachukwu explained 13 the process by which the spreadsheet was created. Each successful payment 14 transaction was recorded by the API and saved on Innovate1’s database in the cloud. 15 Nwachukwu had access to Innovate1’s cloud database, which was maintained by 16 Innovate1’s IT company, Zetasoft. Both Nwachukwu and Zetasoft could generate 17 reports from the information stored on the database. Nwachukwu instructed Zetasoft 18 to provide him with all of the applications processed by FBMS. Zetasoft downloaded 19 all of the transactions processed by FBMS in the order in which they occurred, from 20 first to last. The spreadsheet is the result of that download of information—that is, it 21 was not separately prepared but merely downloaded from the cloud database. FBMS 22 takes issue with the fact that the transactions were presented to the Court in the form 23 of a spreadsheet that was prepared by a third party for purposes of litigation. But 24 “transferring these records into spreadsheets for purposes of litigation [does not] 25 eliminate[] the business records exception” because “business records in one form 26 may be presented in another for trial.” United States v. Channon, 881 F.3d 806, 811 27 (10th Cir. 2018) (holding that a database of computer-generated records presented in 28 the form of a spreadsheet prepared by a third party for purposes of litigation fell

5 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 6 of 14 Page ID #:1359

1 within the business records exception). The Excel spreadsheet is merely the form in 2 which Innovate1 presented the underlying transactions to the Court for trial and is 3 therefore admissible. 4 13. FBMS makes additional arguments challenging the reliability of the 5 spreadsheet. It claims that: (1) the spreadsheet contains fewer data points than the 6 raw data; (2) the spreadsheet did not contain a column that identified FBMS as the 7 processor for each transaction; and (3) the spreadsheet included a column that 8 identified transactions from countries other than the three processed by FBMS (the 9 United States, Canada, and Germany). But the trustworthiness of the record goes to 10 its weight, not admissibility. United States v. Parris, 69 F. App’x 863, 863 (9th Cir. 11 2003); see also United States v. Scholl, 166 F.3d 964, 978 (9th Cir. 1999) (upholding 12 the admissibility of records that were “merely estimates, and crude ones at that”). 13 And Nwachukwu provided an explanation that the Court finds credible and sufficient 14 to address the reliability issues raised by FBMS. The spreadsheet was extremely 15 voluminous even with a smaller number of data points; other than the fact that no 16 column identifies FBMS as the processor, FBMS does not point to any data point 17 from the raw data that was crucially left out of the spreadsheet. And even without a 18 separate column identifying FBMS as the processor, there are reliable indicia that 19 FBMS was the sole processor of every transaction included in the spreadsheet. First, 20 Innovate1’s payment processors “are each assigned specific geographical locations,” 21 and no more than one processor is ever assigned to the same country. Jan. 24 22 Nwachukwu Decl. ¶ 14. FBMS is the only payment processor that handles 23 applications from the United States, Canada, and Germany.2 Second, Innovate1 uses 24 25

26 2 The country information in the spreadsheet reflects the home address or citizenship 27 of the applicant, not the embassy location—e.g., an Indian citizen may have his or her application processed by the embassy in the United States—and thus the API from 28 which the spreadsheet’s transactions are derived contains “only transactions in the

6 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 7 of 14 Page ID #:1360

1 a distinct API for each payment processor, thus only FBMS was using the API from 2 which the spreadsheet data originated.3 3 14. By contrast, FBMS’s expert Rodrigo Macias relied on the weekly 4 summaries. The Court does not find that these weekly summaries reflect an accurate 5 record of the total business conducted under the Agreement. Among other things, the 6 Court is not persuaded by FBMS’s explanation that the gaps in the weekly 7 summaries—including eight consecutive weeks—represent periods with no 8 transactions at all. The Court does not find this to be credible and finds that the 9 weekly summaries are an unreliable measure of the transactions that occurred during 10 the parties’ relationship under the Agreement. 11 15. In contrast, the Court finds reliable the transaction and payment 12 information reflected in the spreadsheet, which derives from the transactions and 13 payments processed by FBMS for Innovate1 through the API gateway. Although 14 Innovate1 had access to this information at the time the transactions occurred, its 15 failure to notice the extent of the missing funds can be explained by its oversight (and 16 even ineptitude, which came across at times during trial) and does not cause the Court 17 to reject the spreadsheet data as unreliable. Accordingly, the Court relies on the 18 spreadsheet to resolve this accounting dispute and credits the accounting performed by 19 Gramlich. 20 16. Even if the Court disregarded the spreadsheet and relied on Macias’s 21 damages calculations, however, the Court would still find this calculation to include 22

23 geographic area covered by FBMS and only transactions processed by FBMS.” Id. 24 ¶¶ 14, 16. 25 3 Nwachukwu also explained that each payment processor is assigned a different 26 sequence of numbers that are used to identify each transaction completed by the processor. FBMS’s sequence identification begins the transaction identification 27 number of every transaction it processes, and each transaction appears in increasing 28 sequential order, with no duplicate numbers appearing.

7 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 8 of 14 Page ID #:1361

1 over $1 million in damages. Macias calculated that $591,912.25 was owed to 2 Innovate1, but he assumed that FBMS transferred $583,932.42 to Innovate1 from its 3 Wells Fargo bank account. Ex. 301. Macias testified that he had been unable to 4 verify this transfer and that, if it were found that those payments were in fact not made 5 by FBMS, he would add $583,932.42 to the total amount of damages. There is no 6 reliable evidence that this transfer occurred; and the Court finds that FBMS never paid 7 the $583,932.42 to Innovate1. Accordingly, even if the Court adopted Mr. Macias’s 8 calculations, the total loss would be $1,175,844.67. 9 17. The Court finds that (1) Innovate1 and FBMS had a valid and 10 enforceable Agreement; (2) Innovate1 performed as required by the Agreement; 11 (3) FBMS breached the Agreement by failing to pay the money owed under the 12 Agreement; and (4) caused Innovate1 damages in the amounts set forth by Gramlich. 13 18. The Court further finds that FBMS breached its fiduciary duty. FBMS 14 maintained the reserve account for Innovate1’s benefit and acted as its trustee but 15 failed to safeguard Innovate1’s funds in the account and misappropriated the funds by 16 failing to return the monies owed from the reserve account. 17 19. The Court similarly finds that Plaintiffs have proven their claim for 18 conversion because (1) Innovate1 was entitled to funds in the reserve account, 19 (2) FBMS took possession of those funds and deprived Innovate1 of their possession, 20 which (3) caused damages to Innovate1. Fong v. E. W. Bank, 19 Cal. App. 5th 224, 21 231 (2018) (stating the elements for conversion). 22 20. Finally, the Court finds that Plaintiffs have not proven their fraud claims 23 by a preponderance of the evidence. See The Grubb Co. v. Dep’t of Real Est., 194 24 Cal. App. 4th 1494, 1503 (2011) (stating the applicable standard of proof). In their 25 Fourth Amended Complaint, Plaintiffs alleged that FBMS represented it had a 26 relationship with a domestic bank at which it would open an account for Innovate1, 27 28

8 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 9 of 14 Page ID #:1362

1 which was false because FBMS opened an account overseas.4 Fourth Amended 2 Complaint, Dkt. No. 79, ¶¶ 63–66. The Court finds there is not sufficient evidence 3 that FBMS intended to misrepresent the identity of the bank that maintained the 4 reserve account. Further, Innovate1 failed to prove that it reasonably and 5 detrimentally relied on any negligent or intentional misrepresentation about the 6 identity of the bank. Bank statements show that Transact EU transferred funds to an 7 account in Mauritius maintained by Newworks Inc. as early as January 2017, Ex. 35, 8 and there is no evidence that Plaintiffs could not identify Transact EU as the bank that 9 made these transfers into Newworks’s account. Accordingly, Plaintiffs failed to prove 10 their fraud claims. 11 21. FBMS’s affirmative defenses are without merit. FBMS’s performance 12 under the Agreement is not excused due to Innovate1’s breach because the Court does 13 not find that Innovate1 breached the Agreement (or caused any damage that would 14 justify allowing FBMS to retain the money owed to FBMS). See discussion ¶¶ 2–3 15 infra (FBMS’s Counterclaims). Similarly, the Court does not find that FBMS is 16 entitled to equitable relief under the unclean hands doctrine because it has not proved 17 that Innovate1 engaged in misconduct by concealing its relationship with Newworks. 18 Indeed, FBMS knew about Newworks’s involvement as early as January 2017. Id. 19 FBMS also raises an affirmative defense of “no causation,” arguing that Innovate1 is 20 21 4 The additional alleged misrepresentations in the Fourth Amended Complaint relate 22 to Geolina and Rainey, and the Court previously dismissed the fraud claims against them. Dkt. No. 94. The Court relies on the allegations in the Fourth Amended 23 Complaint because Plaintiffs did not request that the Court conform the pleading to 24 proof (and the Court declines to do so, sua sponte, without giving FBMS an opportunity to respond). Although the unsigned joint proposed pretrial conference 25 order notes that it “shall supersede the pleadings,” it does not specify a factual basis 26 for Plaintiffs’ fraud claims. Dkt. No. 122-1, at 12. Plaintiffs merely identify the elements of their fraud claims and include a vague description of the evidence they 27 will rely on. The Court does not find this to be a sufficient basis to reform Plaintiffs’ 28 fraud claims as pleaded in the Fourth Amended Complaint.

9 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 10 of 14 Page ID #:1363

1 not the real party in interest with respect to the monies owed, and thus cannot recover 2 them as damages. But whether Innovate1 has separate contractual obligations with 3 Newworks Inc. and Newworks Limited does not deprive it of a right to claim the 4 monies owed under its contract with FBMS. FBMS owes the monies to Innovate1 5 under the parties’ Agreement regardless of whether Innovate1 may, in turn, owe an 6 outstanding amount under separate contracts with nonparties. Finally, Innovate1’s 7 damages are not uncertain because the Court finds the spreadsheet upon which 8 Gramlich relies admissible and reliable. 9 22. In summary, the Court finds that FBMS breached its Agreement with 10 Innovate1 (Count 1), breached its fiduciary duty (Count III), and are liable for 11 conversion (Count VII).5 FBMS therefore owes Innovate1 $3,843,123.04 in damages. 12 The Court does not find that FBMS made intentional and negligent misrepresentations 13 about the identity of the international bank (Counts IV and V). 14 FBMS’S COUNTERCLAIMS 15 1. In its counterclaims, FBMS claims that Innovate1 breached the 16 Agreement, committed fraud, and engaged in unfair business practices by presenting 17 Newworks Limited’s transactions as its own. 18 2. The Agreement contains a provision whereby Innovate1 represented that 19 “no third party has any claim on the funds deposited into [the reserve account].” Ex. 20 32 ¶ 12. The Court is not persuaded that Innovate1’s separate contractual obligations 21 to Newworks Limited and Newworks Inc. created a prohibited third-party claim to the 22 funds in the reserve account—at least not as contemplated by the contracting parties. 23 FBMS clearly knew about Newworks’s involvement as early as January 2017—only 24 25

26 5 Counts II and VI of Plaintiffs’ Fourth Amended Complaint, as well as all claims 27 against Geolina and Rainey, were dismissed on May 31, 2021, pursuant to the Court’s 28 order granting in part Defendants’ motion to dismiss. Dkt. No. 94.

10 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 11 of 14 Page ID #:1364

1 weeks after entering into the Agreement—and treated Newworks as its client. FBMS 2 sent Innovate1 a letter to be given to Newworks Inc.’s bank representing that 3 “Newworks Inc./Innovate1 Services” was its client, and that FBMS “processes 4 payments for their company utilizing FBMS’s payment services.” Ex. 41. At trial, 5 FBMS argued that even if it knew about Newworks, Inc., it did not have knowledge of 6 Newworks Limited. The Court finds that FBMS knew that it was processing 7 payments for Innovate1 on behalf of another company, and that it did not matter to it 8 whether that company was Newworks Limited or its subsidiary Newworks Inc. 9 3. Even if the Court did find that Innovate1 breached the Agreement, 10 committed fraud, or engaged in unfair business practices by representing third-party 11 transactions as its own, FBMS has not demonstrated that Innovate1 caused the 12 claimed damages. 13 4. On October 5, 2017, Geolina received an email from Paysafe Acquiring 14 that raised concerns about transaction laundering through FBMS’s account with 15 Transact EU. Ex. 328. The email does not identify any business other than FBMS. 16 However, FBMS contends that the email refers to concerns that specifically involved 17 Innovate1. Geolina testified that, after receiving this email, he had subsequent 18 conversations with someone at Paysafe or Transact EU about their concerns that 19 Innovate1 was engaged in transaction laundering. 20 5. On February 9, 2018, Geolina received an email from Transact EU 21 requesting information from FBMS and asking questions about the services provided 22 by Newworks Inc. and the relationship between Newworks Inc. and FBMS. Ex. 228. 23 Geolina did not inform Innovate1 about the request. Nor did Geolina reply to the 24 email or otherwise respond in writing; he testified that he responded by telephone but 25 has no record of the conversation and does not know with whom he spoke. 26 6. On March 1, 2018, Geolina contacted Innovate1 for information 27 concerning Newworks Inc., and Nwachukwu provided the requested information. Ex. 28 235. They exchanged a series of emails over the next several days. Geolina testified

11 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 12 of 14 Page ID #:1365

1 that he informed Nwachukwu in a telephone communication in the midst of these 2 email exchanges that FBMS’s “banking partner could no longer support wires 3 internationally for Innovate1” because the bank needed to identify the “ultimate 4 beneficiary” of the funds in the account. Geolina Decl. ¶ 43. Innovate1 subsequently 5 provided FBMS with Newworks Limited’s agreements with Socketworks Limited, 6 Ex. 237, and Newworks Inc., Ex. 239, which FBMS provided to Transact EU. 7 7. On March 29, 2018, Transact EU terminated its agreement with FBMS 8 “due to non-compliance.” Ex. 244. It cited a provision in the agreement (Article 5) 9 that allowed Transact EU to terminate its contract with FBMS for fraud, dishonesty, 10 misrepresentation, excessive chargebacks, or information deemed “unsatisfactory.” 11 Id.; Ex. 29. The letter makes no reference to Innovate1, Newworks Inc., or Newworks 12 Limited. The termination prevented FBMS from accessing the funds held in the 13 reserve account or the API data. FBMS was also placed on a “terminated merchant 14 file list with visa and mastercard associations and black listed [sic] with all banks in 15 the industry.” Geolina Decl. ¶ 45. FBMS has been inoperative since being placed on 16 the blacklist. Id. ¶ 49. 17 8. The Court does not find Geolina’s testimony about his communications 18 with Paysafe and Transact EU credible. FBMS did not introduce any additional 19 written documentation that would support his explanations, and Geolina 20 unconvincingly testified that he preferred to communicate by telephone because he 21 believed written communications could be misinterpreted. And despite the apparent 22 threat to its account, FBMS continued to process transactions for Innovate1 for several 23 more months after Paysafe first contacted FBMS, without taking any action or 24 bringing either the emails or any concerns about transaction laundering to Innovate1’s 25 attention. In short, the Court finds Geolina’s testimony to be self-serving and 26 27 28

12 Case 2:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 13 of 14 Page ID #:1366

1 unreliable (here and elsewhere).6 2 9. Moreover, Geolina admitted at trial that Paysafe and Transact EU’s 3 concerns of transaction laundering applied to accounts FBMS managed for other 4 clients whose funds also have not been released. The Court finds that FBMS failed to 5 demonstrate that Paysafe’s transaction laundering concerns were attributable solely to 6 Innovate1, and that Transact EU would not have terminated its relationship with 7 FBMS but for the concern about Innovate1. Accordingly, FBMS has failed to 8 demonstrate that Innovate1 caused the damages that purportedly resulted from the loss 9 of its banking relationship. 10 10. Even if FBMS could establish that Innovate1 partially or wholly caused 11 the termination of the banking relationship and resulting damage to its business, the 12 Court nevertheless would find that FBMS failed to reliably prove damages. FBMS 13 initially and implausibly contended that it was damaged in the amount of 14 $16,805,052.50 based on its lost revenue between April 2018 and December 2021. 15 Ex. 309 at 5. In his expert report, Macias calculated his estimate of gross revenue by 16 extrapolating from FBMS’s 2016, 2017, and 2018 tax returns. Ex. 309B. At trial, 17 however, Macias testified that since proffering his expert report, he had calculated net 18 profits as a more accurate measure of damages. By examining FBMS’s tax returns, 19 Macias determined that the average profit margin per year was between seven and 20 twelve percent. Applying that margin to the $16,805,052.50 in gross revenue, Macias 21 determined that FBMS lost profits in the amount of $1.6 million. 22 11. The Court finds this damages theory unsupported and speculative. First, 23 if Innovate1 was not solely responsible for Transact EU’s termination of its contract 24 with FBMS (as FBMS had the same issue with other clients), FBMS’s damages 25

26 6 The Court generally found the evidence presented by Plaintiffs, including the 27 testimony, to be more credible and reliable than that presented by the defense, and the 28 findings of fact and conclusions of law reflecting that finding.

13 Case #:20-cv-07681-SB-AGR Document 162 Filed 03/14/22 Page 14o0f14 Page ID #:1367

1 ||theory does not provide a way for the Court to measure damages caused specifically 2 || by Innovatel (or otherwise provide a legal basis to impose joint and several liability). 3 ||Second, the damage theory presupposes a continued revenue stream and profit margin 4 || extrapolated from three prior years of FBMS’s tax returns, which Macias did not 5 ||adequately explain and is not supported by the evidence. 6 12. Inshort, the Court finds that FBMS failed to establish that Innovatel 7 |\|breached the Agreement (Count I), committed fraud (Count IT), or engaged in unfair 8 || business practices (Count III) that resulted in damage to FBMS as claimed. 10 DISPOSITION 1] The Court will enter a final judgment separately. 12 13 4 Dated: March 14, 2022

is Ors. 16 Stanley Blumenfeld, Jr. 7 United States District Judge 18 19 20 21 22 23 24 25 26 27 28