Cumis Ins. Society, Inc. v. Merrick Bank Corp.

680 F. Supp. 2d 1077, 2010 U.S. Dist. LEXIS 5453, 2010 WL 148207
CourtDistrict Court, D. Arizona
DecidedJanuary 11, 2010
Docket4:06-cv-00515
StatusPublished
Cited by1 cases

This text of 680 F. Supp. 2d 1077 (Cumis Ins. Society, Inc. v. Merrick Bank Corp.) 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
Cumis Ins. Society, Inc. v. Merrick Bank Corp., 680 F. Supp. 2d 1077, 2010 U.S. Dist. LEXIS 5453, 2010 WL 148207 (D. Ariz. 2010).

Opinion

ORDER

CINDY K. JORGENSON, District Judge.

Pending before the Court is Defendant Merrick Bank Corp.’s Motion for Partial Summary Judgment [Doc. # 137]. A response and a reply have been filed. The parties presented oral argument to the Court on November 2, 2009.

I. Factual and Procedural Background 1 The Second Amended Complaint (“SAC”), Doc. # 73, alleges that Cumis Insurance Society, Inc. (“Cumis”) is an insurer that provides coverage to credit unions. This dispute involves a data secu *1080 rity breach involving, among others, Merrick Bank Corporation (“Merrick”), Merrick’s agent CardSystems Solutions, Inc. (“CardSystems” or “CSSI”), Sawis, Inc., and Sawis Communications Corporation (Sawis Defendants will be collectively referred to as “Sawis”).

Merrick acted as an issuing bank, an acquiring bank, and a sponsoring bank in the Visa system. As an issuing bank, Merrick issued Visa credit and debit cards to customers. As an acquiring bank, Merrick contracted with merchants to make payments to merchants as part of the credit card transaction process. The hundreds of thousands of merchants that want to be able to accept Visa and/or MasterCard cards customarily do so through independent sales organizations (“ISOs”), which aggregate many merchants and which contract with acquirers such as Merrick and processors such as CardSystems. As a sponsoring bank, Merrick acted as a sponsor for third — party transaction processors such as CardSystems-which are not members of the Visa/MasterCard card associations (“Associations”) and need to be sponsored in order to have access to the Visa/MasterCard systems. Absent such sponsorship by an Association member, a processor cannot function as a processor, or in any other capacity, with respect to Association card transactions.

As a sponsoring bank, Merrick has stated that:

All aspects of the Visa and MasterCard card transaction processes are conducted according to rules and regulations imposed by the Associations. By contractual agreements, both Merrick and CSSI are subject to these rules.
Under each Association’s broad rules on indemnification, a member bank that sponsors a processor such as CSSI is responsible for the processor’s proper performance under the Association rules and undertakes full financial responsibility, irrespective of fault, for all losses or costs incurred by the Association or its members that are attributable to acts or omissions of the sponsored processor. The Association rules also provide for the imposition of penalties or fines on a member for violations of the Association rules by a sponsored third-party processor — whose acts and/or omissions are imputed to the sponsoring member. In addition, in the Visa system, to designate a processor such as CSSI as a sponsored entity, a member must file a signed registration document in which the member explicitly indemnifies Visa for all losses resulting by the sponsored entity’s acts or omissions.

PSOF, ¶ 5.

On or about August 2005, Visa announced that an Optional Alternative Compliance Process (“OACP”) to resolve claims by issuing banks for reimbursement of their counterfeit fraud losses resulting from the CardSystems security breach was available. Merrick asserts that participation in the Visa OACP was limited to account numbers identified in the specified Visa Compromised Account Management System (“CAMS”) alerts. 2 Merrick also asserts that smaller credit unions were not given the opportunity to participate in the OACP, except through a BIN sponsor. 3 Instead of issuing banks processing their claims through the standard compliance *1081 process, the issuing banks could select the alternative process in which reimbursement to issuing banks would be for a claim amount calculated by Visa. In calculating each issuing banks’ claim amount in the OACP, Visa only considered counterfeit fraud losses reported by issuing banks through August 31, 2005. In the OACP, Visa notified the issuing banks of the amount they were entitled to recover through the OACP — there were no negotiations between Visa and the issuing banks concerning that amount. Additionally, there were no negotiations between Visa and the issuing banks concerning the terms of the Issuer Certification and Release of Liability (“Issuer Certification”) an issuing bank was required to execute before receiving payment for its losses. Merrick asserts that the Issuer Certification includes the following:

By signing this form and receiving payment from the Acquirer in the amount determined by Visa to be compensable under this claim as specified on the Issuer Claim Statement, our center hereby releases Visa and the Acquirers who appoint CardSystems Solutions Incorporate as their processors from all magnetic-stripe counterfeit claims, losses, damages and liabilities attributable to this data compromise event.

DSOF, Ex. D. 4 Without waiving its objections to this assertion, Cumis asserts that the Issuer Certification also includes the following:

Our Center certifies that no chargeback rights exist or have been successfully exercised on any of the disputed transactions for which we are seeking reimbursement through this claim.
Our Center certifies that we have not sought and will not seek compensation for any transactions included in this claim through compliance rights in respect of this or any other magnetic stripe data compromise incident.

Id.

The claim amount Visa determined each issuing bank was entitled to receive in the OACP was based upon a calculation created by Visa. This claim amount was always less than the amount of the issuing bank’s actual counterfeit losses reported before the August 31, 2005 deadline. If an issuing bank agreed to accept the claim amount calculated by Visa and could support their claims, the issuing banks were required to execute an Issuer Certification. Merrick asserts that the recovery received by issuers participating in the Visa OACP was funded by acquiring banks that sponsored CardSystems; as the majority of the transactions processed by CardSystems were for Merrick, Merrick’s pro rata allocation of liability was 70.0706%. 5 Merrick also asserts that, with respect to the claims currently asserted by Cumis on behalf of its insureds for Visa related damages, at a minimum, 92 of these credit unions participated in the Visa OACP, and the claims asserted on their behalf by Cumis against Merrick, based on currently available information, totals approximately $3,229,852.12. 6

*1082 Shaughnessy states, inter alia, in his declaration:

...

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
680 F. Supp. 2d 1077, 2010 U.S. Dist. LEXIS 5453, 2010 WL 148207, Counsel Stack Legal Research, https://law.counselstack.com/opinion/cumis-ins-society-inc-v-merrick-bank-corp-azd-2010.