Advanced Software Design Corp. v. Federal Reserve Bank

583 F.3d 1371, 92 U.S.P.Q. 2d (BNA) 1489, 2009 U.S. App. LEXIS 21464, 2009 WL 3110804
CourtCourt of Appeals for the Federal Circuit
DecidedSeptember 30, 2009
Docket2008-1152
StatusPublished
Cited by35 cases

This text of 583 F.3d 1371 (Advanced Software Design Corp. v. Federal Reserve Bank) 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
Advanced Software Design Corp. v. Federal Reserve Bank, 583 F.3d 1371, 92 U.S.P.Q. 2d (BNA) 1489, 2009 U.S. App. LEXIS 21464, 2009 WL 3110804 (Fed. Cir. 2009).

Opinion

NEWMAN, Circuit Judge.

Plaintiffs Advanced Software Design Corporation and its founder, Calin A. Sandra, (collectively “Advanced Software”) appeal the summary judgment of the United States District Court for the Eastern District of Missouri, Catherine D. Perry, J., dismissing certain counts of their patent infringement suit on the ground that the acts relevant to this appeal were “by or for the United States” and thus could only be pursued in the Court of Federal Claims under 28 U.S.C. § 1498(a). 1 Final judgment was entered pursuant to Federal Rule of Civil Procedure 54(b). Because the allegedly infringing activity was for the *1373 United States and with its authorization and consent, the dismissal of the relevant counts is affirmed.

BACKGROUND

Advanced Software brought this suit against Fiserv, Inc. and three regional Federal Reserve Banks, charging them with infringement of three patents owned by Advanced Software relating to a method for detecting fraudulent bank checks. The patents are U.S. Patent Nos. 6,792,-110; 6,549,624; and 6,233,340 (“the Sandru patents”). Issues of the scope, validity, and infringement of these patents were not reached by the district court, and are not before us on this appeal.

The technology charged with infringement is called “seal encoding” technology, whereby certain check identifying data such as the check number, payee, date, and amount payable are encoded, using appropriate software, in a “seal” on the face of the check when the check is printed. Using software programmed with the encryption system, a bank at which the check is processed after its deposit can decode the seal and compare this decoded information to the information that appears on the check. Any discrepancy will alert the bank to a possible altered or counterfeited check. Because the procedure involves both encoding, which takes place when the checks are issued, and decoding and verification, the technology depends upon participation by both the check issuer and the bank that processes the check after its deposit. As concerns the involvement of the United States, the assertions of infringement arise from use of this system with checks of the United States Treasury.

Before the Treasury adopted the seal encoding system, when a United States check was deposited at a bank of first deposit, it would be transferred to the Reserve Bank of which that bank was a member, and paid from Treasury funds held by that Reserve Bank. The check would then be forwarded to the Treasury, and its Financial Management Service (FMS) would conduct a reconciliation process to identify fraudulent checks. FMS would verify information on the check and, if a discrepancy appeared, FMS would investigate further. The Treasury has up to sixty days to identify an altered or counterfeit check, and receives a refund of any funds that had been transferred to pay a fraudulent check, if identified within this period. Meanwhile the perpetrator will have received the funds from the bank of first deposit, and the system is such that the member bank or the Reserve Bank generally bears the loss. See generally Indorsement and Payment of Checks Drawn on the United States Treasury, 69 Fed.Reg. 17,272, 17,273 (April 1, 2004) (explaining amendments to 31 C.F.R. Part 240 relating to the 60-day period for FMS investigation and reconciliation). Now, with the seal encoding technology, the detection system can detect fraudulent checks promptly at the Reserve Bank, notifying the bank of first deposit to freeze the funds before they are withdrawn by the perpetrator. 2

The seal encoding technology reached the Treasury by way of employees of Reserve Banks who learned of the technology, which was developed by a British company and acquired by Fiserv, Inc. A pilot project based on Treasury checks was conducted by Fiserv and the Philadelphia Reserve Bank, under a contract entered be *1374 tween them in July 2001. The United States was not a party to this contract, although the Treasury participated in the pilot program by printing checks with encoded seals. In reviewing a draft of the contract between the Reserve Bank and Fiserv, the Treasury requested that the following draft recital be modified:

WHEREAS, the Reserve Bank, acting on behalf of the Financial Management Services (“FMS”), a bureau in the Department of the Treasury (“Treasury”), desires to evaluate the use of certain seal encoding technology.

(Draft contract appended to email from Blake Prichard of the Philadelphia Reserve Bank, to Fiserv, July 26, 2001, at J.A. 278). Treasury requested rewording, as reflected in an email from Mr. Prichard that quoted the following passage from an earlier message .from an unnamed Treasury official:

First paragraph under Background: “acting on behalf of the FMS” ... since it is a joint project, I wonder if it should be “in conjunction with” or similar wording. My concern is that Procurement has concerns when they think the Fed is simply doing a procurement for us, as opposed to doing a procurement simply as an element of a project they are doing -for or with us.

(Email from Blake Prichard to Fiserv, July 31, 2001, at J.A. 284). Accordingly, “on behalf of’ was changed to “in conjunction with” in the final contract. The significance of this change was debated in the district court, for the Reserve Banks pressed the defense that they could not be sued for patent infringement because their activity was for the United States. In turn, Advanced Software pointed to deposition testimony of a Treasury official stating that the Treasury does not view the Reserve Banks as its contractors in connection with arrangements between the Banks and other entities. The official explained:

When we instruct the Federal Reserve to do something on our behalf and they choose to do a procurement, it is their contract. We will often have conversation with them about what the contract will include, what the contractor will do compared to what the Federal Reserve will do, but the contract is between the Federal Reserve Bank and the vendor. • We don’t sign off on those contracts. We don’t consider them our contractors.

(Dep. of Judith Tillman, Deputy Commissioner of FMS, at J.A. 507, undated in Appendix.)

After the pilot program was successfully completed, further contracts were entered between the Reserve Banks and Fiserv, on terms that included Fiserv’s agreement to indemnify the Banks for any patent infringement.

On motion of the defendants, the district court dismissed the infringement claims that were based on U.S. Treasury checks, ruling that the alleged acts of infringement were “for the United States” and could be litigated only in the Court of Federal Claims pursuant to 28 U.S.C. § 1498(a). The statute is as follows:

28 U.S.C.

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

Related

May v. United States
Federal Claims, 2026
MAIMON v. United States
Federal Claims, 2025
Bozeman Financial LLC v. Federal Reserve Bank
955 F.3d 971 (Federal Circuit, 2020)
Zaccari v. United States
Federal Claims, 2019
Saint-Gobain Ceramics & Plastics, Inc. v. Ii-Vi Inc.
369 F. Supp. 3d 963 (C.D. California, 2019)
Golden v. United States
Federal Claims, 2018
Robinson v. United States
Federal Claims, 2017
Silver Buckle Mines, Inc. v. United States
132 Fed. Cl. 77 (Federal Claims, 2017)
American Innotek, Inc. v. United States
126 Fed. Cl. 468 (Federal Claims, 2016)
Astornet Technologies Inc. v. Bae Systems, Inc.
802 F.3d 1271 (Federal Circuit, 2015)
Crye Precision LLC v. Bennettsville Printing
124 F. Supp. 3d 231 (E.D. New York, 2015)
St. Bernard Parish Government v. United States
121 Fed. Cl. 747 (Federal Claims, 2015)
Sheridan v. United States
120 Fed. Cl. 127 (Federal Claims, 2015)
Iris Corporation v. Japan Airlines Corporation
769 F.3d 1359 (Federal Circuit, 2014)
Canvs Corporation v. United States
118 Fed. Cl. 587 (Federal Claims, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
583 F.3d 1371, 92 U.S.P.Q. 2d (BNA) 1489, 2009 U.S. App. LEXIS 21464, 2009 WL 3110804, Counsel Stack Legal Research, https://law.counselstack.com/opinion/advanced-software-design-corp-v-federal-reserve-bank-cafc-2009.