Net MoneyIN, Inc. v. VeriSign, Inc.

545 F.3d 1359, 88 U.S.P.Q. 2d (BNA) 1751, 2008 U.S. App. LEXIS 21827, 2008 WL 4614511
CourtCourt of Appeals for the Federal Circuit
DecidedOctober 20, 2008
Docket2007-1565
StatusPublished
Cited by170 cases

This text of 545 F.3d 1359 (Net MoneyIN, Inc. v. VeriSign, Inc.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359, 88 U.S.P.Q. 2d (BNA) 1751, 2008 U.S. App. LEXIS 21827, 2008 WL 4614511 (Fed. Cir. 2008).

Opinion

LINN, Circuit Judge.

Net MoneyIN, Inc. (“NMI”) appeals from a final judgment of the United States District Court for the District of Arizona, which held the asserted claims of U.S. Patents No. 5,822,737 (“the '737 patent”) and No. 5,963,917 (“the '917 patent”) invalid. NMI also appeals from the district court’s denial of its motion for leave to amend its complaint to assert a claim for inducement of infringement. Because the district court correctly found claims 1, 13, and 14 of the '737 patent and claim 1 of the '917 patent, which contain limitations in means-plus-function format, invalid under 35 U.S.C. § 112 ¶2 as lacking corresponding structure, we affirm that portion of the judgment. Because the district court did not abuse its discretion in denying NMI’s motion to amend, we also affirm that ruling. Because the district court applied an incorrect standard of law in finding claim 23 of the '737 patent invalid as anticipated under 35 U.S.C. § 102(a), however, we reverse the grant of summary judgment of anticipation. Thus, we affirm-in-part, reverse-in-part, and remand for proceedings consistent with this opinion.

I. BACKGROUND

This case involves systems for processing credit card transactions over the Internet and for addressing security concerns not present in direct retail transactions. In the early days of Internet commerce, merchants recognized that one key to the *1363 success of Internet sales would be the ability to provide customers with assurances of security in the processing of financial transactions over the Internet using credit cards, bank accounts; and other means of electronic payment. Responding to that need, the industry investigated encryption techniques and architectures to protect sensitive data. One such effort is reflected in a 1995 working document entitled “Internet Keyed Payments Protocol” (“the iKP reference”), published by the Internet Engineering Task Force and IBM. That document sets forth standards on “how payments may be accomplished efficiently, reliably[,] and securely.” J.A. at 1375. The iKP reference explains that its goal was “to enable Internet-based secure electronic payments while utilizing the existing financial infrastructure for payment authorization and clearance. The intent is to avoid completely, or at least minimize, changes to the existing financial infrastructure outside the Internet.” Id. To that end, the iKP reference suggests two standard models, or protocols. 1

In the first protocol, (1) the customer selects one or more items to purchase from the merchant’s website; (2) the customer sends credit card information to the merchant; (3) the merchant sends the credit card information and amount of the purchase to the merchant’s bank; (4) the merchant’s bank seeks authorization for the purchase from the issuing bank over the existing banking network; and (5) the merchant’s bank notifies the merchant (but not the customer) of transaction approval. See id. at 1381 (flow diagram); Appellant’s Br. at 7.

In the second protocol, (1) the customer selects one or more items to purchase on the merchant’s website; (2) the customer sends an authorization request, along with its credit card information and the amount of the purchase, to the merchant’s bank; (3) the merchant’s bank seeks authorization from the issuing bank over the existing banking network; (4) the merchant’s bank notifies the customer of transaction approval; and (5) the customer sends the authorization response to the merchant. See J.A. at 1342, 1394; Appellant’s Br. at 8-9.

Unsatisfied with the early approaches taken by others, Mark Ogram, an inventor and patent attorney, set out to create a new payment model to remedy what he perceived as two deficiencies in the prior art protocols: “the fact that the customer had to send confidential information over the Internet to an unknown merchant; and the fact -that credit card issuers imposed onerous financial requirements on merchants.” Appellant’s Br. at 10. Ogram’s idea was to add a fifth entity, a “payment processing” or “financial processing” entity, to supplement the conventional model with four entities: the customer, merchant, merchant’s bank, and issuing bank. According to Ogram, the new financial processing entity would: “(1) receive credit card account information and an amount to be charged from the customer when the customer placed the order; (2) seek authorization from the card issuer over the existing banking network; and (3) notify both the customer and the merchant of authorization.” Id.

On February 5, 1996, Ogram filed a patent application directed to a payment model utilizing a financial processing entity. He formed NMI shortly thereafter to *1364 implement the model as a business for processing credit card transactions over the Internet. Ogram’s patent application resulted in the '737 and '917 patents, both of which are assigned to NMI. Claim 1 of the '737 patent is illustrative of the invention claimed:

1. A financial transaction system comprising:
a) a first bank computer containing financial data therein, said financial data including customer account numbers and available credit data, said first bank computer including means for generating an authorization indicia in response to queries containing a customer account number and amount;
b) a merchant computer containing promotional data;
c) a customer computer being linked with said merchant computer and receiving said promotional data; and,
d) a financial processing computer remote from said merchant computer and having means for:
1) receiving customer account data and amount data from said customer computer,
2) querying said first bank computer with said customer account data and said amount data,
3) receiving an authorization indicia from said first bank computer,
4) communicating a self-generated transaction indicia to said customer computer, and,
5) communicating the self-generated transaction indicia to said merchant computer.

According to their abstracts, the '737 and '917 patents relate to “[a]n automated payment system particularly suited for purchases over a distributed computer network such as the Internet.”

In 2001, NMI filed suit for infringement of the '737 and '917 patents against a number of parties alleged to compete in the Internet credit card processing field, including VeriSign, Inc. and eProcessing-Network (collectively, “VeriSign”). Following a claim construction hearing, the district court construed a number of terms in dispute. Net MoneyIN, Inc. v. VeriSign, Inc., No. 01-CV-441, 2005 WL 5960650 (D.Ariz. Oct. 19, 2005) (“Claim Construction Decision”).

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

Related

Vivint v. Alarm.com
D. Utah, 2020
Victaulic Company v. Iancu
Federal Circuit, 2018
Microsoft Corporation v. Biscotti, Inc.
878 F.3d 1052 (Federal Circuit, 2017)
In Re: Chudik
851 F.3d 1365 (Federal Circuit, 2017)
Enfish, LLC v. Microsoft Corporation
822 F.3d 1327 (Federal Circuit, 2016)
Summit 6, LLC v. Samsung Electronics Co., Ltd.
802 F.3d 1283 (Federal Circuit, 2015)
Trustees of Columbia University v. Illumina, Inc.
620 F. App'x 916 (Federal Circuit, 2015)
Richard Williamson v. Citrix Online, LLC
792 F.3d 1339 (Federal Circuit, 2015)
Acme Scale Company, Inc. v. Lts Scale Company, LLC
615 F. App'x 673 (Federal Circuit, 2015)
Kennametal, Inc. v. Ingersoll Cutting Tool Company
780 F.3d 1376 (Federal Circuit, 2015)
Virnetx, Inc. v. Cisco Systems, Inc.
767 F.3d 1308 (Federal Circuit, 2014)
Augme Technologies, Inc. v. Yahoo! Inc.
755 F.3d 1326 (Federal Circuit, 2014)
Allergan, Inc. v. Apotex Inc.
754 F.3d 952 (Federal Circuit, 2014)
Canvs Corporation v. United States
116 Fed. Cl. 294 (Federal Claims, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
545 F.3d 1359, 88 U.S.P.Q. 2d (BNA) 1751, 2008 U.S. App. LEXIS 21827, 2008 WL 4614511, Counsel Stack Legal Research, https://law.counselstack.com/opinion/net-moneyin-inc-v-verisign-inc-cafc-2008.