throbber
Covered Business Method Review
`United States Patent No. 7,840,486
`
`
`
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`––––––––––
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`––––––––––
`
`MASTERCARD INTERNATIONAL INCORPORATED
`Petitioner
`
`v.
`
`JOHN D’AGOSTINO
`Patent Owner
`
`––––––––––
`
`
`Patent No. 7,840,486
`Application No. 11/252,009
`Filed: October 17, 2005
`Issued: November 23, 2010
`Title: System and Method for Performing Secure Credit Card Transactions
`
`––––––––––
`
`PETITION FOR COVERED BUSINESS METHOD PATENT REVIEW
`UNDER 35 U.S.C. § 321, 37 C.F.R. § 42.304
`
`
`
`
`- i -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`
`
` TABLE OF CONTENTS
`
`LIST OF EXHIBITS……………………………………………………………....iv
`
`I.
`
`II.
`
`INTRODUCTION........................................................................................1
`
`PETITIONER HAS STANDING ................................................................2
`
`A.
`
`B.
`
`The ‘486 Patent is a Covered Business Method Patent ...............................2
`
`Petitioner is a Real Party in Interest Sued for Infringement........................5
`
`
`
`
`
`
`III.
`
`C. Related Matters ............................................................................................5
`
`OVERVIEW OF SPECIFIC GROUNDS FOR WHICH IT IS MORE
`LIKELY THAN NOT THAT THE CHALLENGED CLAIMS (1-30) OF
`THE ‘486 PATENT ARE UNPATENTABLE............................................6
`
`IV.
`
`BACKGROUND INFORMATION FOR THE ‘486 PATENT ..................7
`
`A. Overview of the ‘486 Patent ........................................................................7
`
`B.
`
`The ‘486 Patent Prosecution History ...........................................................7
`
`
`
`
`
`C.
`
`
`V.
`
`The ‘988 Patent Ex Parte Reexamination File History .............................10
`
`DETAILED EXPLANATION OF REASONS FOR RELIEF SHOWING
`IT IS MORE LIKELY THAN NOT THAT THE CHALLENGED
`CLAIMS ARE UNPATENTABLE...........................................................12
`
`A.
`
`The Challenged Claims are Invalid under §§ 102 and/or 103 ...................12
`
`1. Claim Construction.................................................................................13
`
`2. Ground 1: Claims 1-15 and 22-30 are Anticipated Under 35 U.S.C. §
`102 by Cohen ..........................................................................................15
`
`3. Ground 2: Claims 16-21 are Obvious Under 35 U.S.C. § 103 by Cohen
`in View of Musmanno ............................................................................37
`
`- ii -
`
`
`
`
`
`
`
`
`
`
`
`

`

`4. Ground 3: Claims 1-15 and 22-30 are Anticipated Under 35 U.S.C. §
`102 by Flitcroft .......................................................................................45
`
`Covered Business Method Review
`United States Patent No. 7,840,486
`
`
`5. Ground 4: Claims 16-21 are Obvious Under 35 U.S.C. § 103 by Flitcroft
`in View of Musmanno ............................................................................69
`
`CONCLUSION ..........................................................................................79
`
`
`
`
`VI.
`
`
`
`- iii -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`
`
`PETITIONER’S LIST OF EXHIBITS
`
`Exhibit 1001 – U.S. Patent No. 7,840,486
`
`Exhibit 1002 – File History for U.S. Patent No. 7,840,486
`
`Exhibit 1003 – File History for U.S. Reexamination No. 90/012,517
`
`Exhibit 1004 – U.S. Patent No. 6,422,462 (“Cohen”)
`
`Exhibit 1005 – U.S. Patent No. 6,636,833 (“Flitcroft”)
`
`Exhibit 1006 – U.S. Patent No. 5,826,243 (“Musmanno”)
`
`Exhibit 1007 – Complaint in D’Agostino v. MasterCard, Inc. et al. (13-cv-0738)
`
`Exhibit 1008 – Declaration of Jack D. Grimes, Ph.D.
`
`Exhibit 1009 – Excerpts from Random House Webster’s Unabridged Dictionary,
`
`Second Edition
`
`Exhibit 1010 – U.S. Patent No. 6,064,987 (“Walker”)
`
`Exhibit 1011 – U.S. Patent No. 5,283,829 (“Anderson”)
`
`Exhibit 1012 – ISO 8583 Financial Transaction Card Originated Messages –
`
`Interchange Message Specifications (1992) (“ISO 8583”)
`
`Exhibit 1013 – File History for U.S. Patent No. 8,036,988
`
`
`
`
`
`
`
`- iv -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`Pursuant to 35 U.S.C. § 321 and 37 C.F.R. § 42.304, MasterCard
`
`International Incorporated (“Petitioner” and real party in interest), hereby petitions
`
`for review under the transitional program for covered business method patents of
`
`claims 1-30 (all claims) of U.S. Pat. No. 7,840,486 (“the ‘486 Patent”), issued to
`
`John D’Agostino (“D’Agostino”). Petitioner hereby asserts it is more likely than
`
`not that at least one of the challenged claims is unpatentable and respectfully
`
`requests review of, and judgment against, Claims 1-30 as unpatentable under §§
`
`102 and/or 103.
`
`I.
`
`INTRODUCTION
`
`The ‘486 Patent attempts to claim the use of a transaction code – in lieu of a
`
`credit card number – for making secure transactions that are limited to a single
`
`merchant. This was a practice that was common in the credit card industry before
`
`the priority date of the ‘486 Patent. During prosecution, the ‘486 Patent issued
`
`only after the Applicant attempted to distinguish the claims over the prior art on
`
`the basis of the following limitation:
`
`defining a payment category including at least limiting purchases to a
`single merchant for at least one transaction, said single merchant
`limitation being included in said payment category prior to any
`particular merchant being identified as said single merchant
`
`However, this limitation does not in fact distinguish the claims of the ‘486
`
`patent from the prior art. The prior art already disclosed the use of credit card
`
`
`
`- 1 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`transaction codes that were limited to a single transaction, which inherently limits
`
`the card to use at a single merchant – because once the card is first used at any
`
`merchant, it cannot be used again. Therefore, the Applicant had claimed in the
`
`‘486 Patent nothing more than a feature that was inherently disclosed in the prior
`
`art. Accordingly, and as explained in detail below, the prior art invalidates the
`
`‘486 Patent.
`
`II.
`
`PETITIONER HAS STANDING
`
`A.
`
`The ‘486 Patent is a Covered Business Method Patent
`
`The ‘486 Patent is a “covered business method patent” under § 18(d)(1) of
`
`the Leahy-Smith America Invents Act, Pub. L. 112-29 (“AIA”) and § 42.301.
`
`More specifically, the term “covered business method patent” means “a patent that
`
`claims a method or corresponding apparatus for performing data processing or
`
`other operations used in the practice, administration, or management of a financial
`
`product or service, except that the term does not include patents for technological
`
`inventions.” See AIA § 18(d)(1); 37 C.F.R. § 42.301(a); see also 77 Fed. Reg.
`
`48733, 48735 (Aug. 14, 2012). The legislative history explains that the definition
`
`of covered business method patent was drafted to encompass patents “claiming
`
`activities that are financial in nature, incidental to a financial activity or
`
`complementary to a financial activity.” See 77 Fed. Reg. 48735 (Aug. 14, 2012).
`
`
`
`
`
`Here, the ‘486 Patent claims a method for data processing and other
`
`- 2 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`operations used in the practice, administration, and management of a financial
`
`product and service, and more particularly to a method for performing secure credit
`
`card purchases. The claimed method involves the creation and use of a transaction
`
`code wherein a customer does not need to reveal their credit card number to a
`
`merchant in order to make a purchase. Thus, the ‘486 Patent claims an activity that
`
`is entirely financial in nature, and involves the operations of a financial product
`
`and service, consequently qualifying it as a “covered business method patent.”
`
`Moreover, the ‘486 patent is not directed to a “technological invention.” A
`
`“technological invention” claims “subject matter as a whole [that] recites a
`
`technological feature that is novel and unobvious over the prior art; and solves a
`
`technical problem using a technical solution.” § 42.301(b).1 This is not the case
`
`here. The ‘486 Patent’s claims are directed to performing ordinary credit card
`
`transactions using conventional security techniques, i.e., the use of a transaction
`
`1 See, e.g., 77 Fed. Reg. 48,756, 48,764 (Aug. 14, 2012) (“Mere recitation of
`
`known technologies, such as computer hardware, communication or computer
`
`networks, software, memory, computer-readable storage medium, . . . display
`
`devices or databases, or . . . an ATM or point of sale device,” or reciting “use of
`
`known prior art technology to accomplish a process or method, even if that process
`
`or method is novel and non-obvious” will “not typically render a patent a
`
`technological invention.”).
`
`
`
`- 3 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`code. See Exh. 1001 at Abstract. The claimed method does not contain any novel
`
`and unobvious technological feature: it merely claims the creation of a transaction
`
`code and the communication of the transaction code to the account holder and
`
`merchant to facilitate the secure credit card transaction. See Exh. 1001 at 4:3-24.
`
`In fact, this basic use of a transaction code to facilitate secure credit card
`
`transactions was well-known in the industry before the filing date of the ‘486
`
`Patent, see, e.g., U.S. Patent No. 6,422,462 to Cohen; U.S. Patent No. 6,636,833 to
`
`Flitcroft et al. The claims of the ‘486 Patent recite no particular hardware,
`
`arrangement of hardware, or software to implement the system. See CBM2012-
`
`00001, Decision Instituting CBM Review, Paper No. 36, at 27 (January 9, 2013)
`
`(holding that the claims were not directed to a technological invention because “no
`
`specific, unconventional software, computer equipment, tools or processing
`
`capabilities are required” by the claims). In addition, the subject matter as a whole
`
`solves no “technical problem,” and instead is directed to a method of carrying out a
`
`financial transaction.
`
`In addition, the ‘486 Patent is classified into Class 705. As the legislative
`
`history of the AIA reveals, this classification raises a presumption that the ‘486
`
`Patent is a covered business method patent. 157 Cong. Rec. S1368, S1379 (daily
`
`ed. March 8, 2011)(Statement of Sen. Kyl). Finally, as noted below, the ‘486
`
`Patent has been asserted against MasterCard’s inControl offering, which is a
`
`
`
`- 4 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`financial service. See Exh. 1007, Complaint at ¶ 19-22. This alone should suffice
`
`to make the patent eligible for covered business method review. 157 Cong. Rec.
`
`S1364, S1365 (daily ed. March 8, 2011)(daily ed. Statement of Sen. Schumer)(“if a
`
`patent holder alleges that a financial product or service infringes its patent, that
`
`patent shall be deemed to cover a financial product or service”); see also 157
`
`Cong. Rec. S5432 (daily ed. Sept. 8, 2011).
`
`Accordingly, the ‘486 Patent qualifies for covered business method review.
`
`B.
`
`Petitioner is a Real Party in Interest Sued for Infringement
`
`The ‘486 Patent was asserted against Petitioner in Case No. 1:13-cv-00738,
`
`John D’Agostino v. MasterCard, Inc. et al, pending in the U.S. District Court for
`
`the District of Delaware. See Exh. 1007, Complaint.
`
`C. Related Matters
`
`As noted above, Case No. 1:13-cv-00738 is currently pending in the U.S.
`
`District Court for the District of Delaware. Petitioner is also filing, concurrent
`
`with this Petition, an additional Petition seeking review of the related U.S. Patent
`
`Number 8,036,988 (the “‘988 Patent”), which claims priority to the ‘486 patent as
`
`a continuation.
`
`In addition, there is a pending reexamination for the ‘988 Patent in
`
`Reexamination No. 90/0123,517, filed September 12, 2012, in the United States
`
`Patent and Trademark Office. See Exh. 1003 – File History for Reexamination No.
`
`
`
`- 5 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`
`90/012,517.
`
`III. OVERVIEW OF SPECIFIC GROUNDS FOR WHICH IT IS MORE
`LIKELY THAN NOT THAT THE CHALLENGED CLAIMS (1-30)
`OF THE ‘486 PATENT ARE UNPATENTABLE
`
`Pursuant to § 42.208 (and § 42.300), Petitioner asserts that every one of the
`
`challenged claims 1-30 of the ‘486 Patent is unpatentable as invalid under §§ 102
`
`and/or 103. The accompanying Exhibit List lists all prior art references relied
`
`upon in the Petition for the asserted grounds of invalidity under §§ 102 and/or 103.
`
`Petitioner specifically requests cancellation of the challenged claims on the
`
`following statutory grounds:
`
`− GROUND 1. Claims 1-15 and 22-30 are Unpatentable under 35 USC § 102 as
`
`Anticipated by Cohen
`
`− GROUND 2. Claims 16-21 are Unpatentable under 35 USC § 103 as Obvious
`
`over Cohen in view of Musmanno
`
`− GROUND 3. Claims 1-15 and 22-30 are Unpatentable under 35 USC § 102 as
`
`Anticipated by Flitcroft
`
`− GROUND 4. Claims 16-21 are Unpatentable under 35 USC § 103 as Obvious
`
`over Flitcroft in view of Musmanno
`
`Section V lists each ground upon which it is more likely than not that the
`
`challenged claims are unpatentable as anticipated under §§ 102 and/or 103, and
`
`renders a detailed explanation therefor. Grounds 3 and 4 are being presented in the
`
`
`
`- 6 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`event the Board does not accept Petitioner’s construction of “generating [a/said]
`
`transaction code” and adopts a broader, albeit in Petitioner’s view a faulty,
`
`alternative construction, both discussed below.
`
`IV. BACKGROUND INFORMATION FOR THE ‘486 PATENT
`A. Overview of the ‘486 Patent
`
`The ‘486 Patent is directed to a secure method for performing credit card
`
`purchases, wherein a customer submits a transaction code, rather than an entire
`
`credit card number to a merchant when making a purchase. Generally, the
`
`customer contacts an authorizing entity, such as a credit card company or issuing
`
`bank, and requests a transaction code. The transaction code can be limited to
`
`purchases within a payment category, such as limiting the code to be used with a
`
`single merchant and other limitations, such as restricting the use to a particular
`
`period of time. The customer can then use the transaction code to make a purchase
`
`at a merchant or online.
`
`B.
`
`The ‘486 Patent Prosecution History
`
`On October 17, 2005, the Applicant filed U.S. Patent Application No.
`
`11/252,009 which ultimately issued as the ‘486 Patent. The claims of the ‘486
`
`Patent issued after only two rejections citing the same prior art references during
`
`prosecution. The Examiner rejected the claims in a non-final office action under §
`
`103(a) as unpatentable over U.S. Patent No. 6,000,832 (“Franklin”) in view of U.S.
`
`
`
`- 7 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`Patent Publication No. 2001/0011249 (“Yanagihara”) in further view of U.S.
`
`Patent No. 5,500,513 (“Langhans”). See Exh. 1002, ‘486 Patent File History,
`
`6/10/09 Office Action at 7.
`
`In response to the non-final office action, the Applicant argued that
`
`independent claim 1 “recites, inter alia, defining a payment category including at
`
`least limiting purchases to a single merchant for at least one transaction, said single
`
`merchant limitation being included in said payment category prior to any particular
`
`merchant being identified as said single merchant.” See Exh. 1002, ‘486 Patent
`
`File History, 12/10/09 Response to Office Action at 23 (emphasis in original). The
`
`Applicant argued that the cited prior art “fails to teach or suggest the claimed
`
`feature of the single merchant limitation being included in said payment category
`
`prior to any particular merchant being identified as said single merchant.” Id. at 25
`
`(emphasis added). The Applicant provided similar arguments for the other
`
`pending independent claims. Id. at 25-28.
`
`The Examiner subsequently rejected the claims in a final office action again
`
`under § 103(a) as unpatentable over Franklin in view of Yanagihara in further view
`
`of Langhans. See Exh. 1002, ‘486 Patent File History, 3/29/10 Final Office Action
`
`at 5.
`
`In response to the final office action, the Applicant again argued that the
`
`cited prior art did not teach “a single merchant limitation being included in a
`
`
`
`- 8 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`payment category prior to any particular merchant being identified as said single
`
`merchant.” See Exh. 1002, ‘486 Patent File History, 7/26/10 Response to Final
`
`Office Action at 19 (emphasis in original). The Applicant provided similar
`
`arguments for the other pending independent claims. Id. at 21-22.
`
`After an examiner interview, the Examiner allowed the pending claims
`
`noting that he found the Applicant’s arguments persuasive. More specifically, the
`
`Examiner stated in the reasons for allowance the “uniquely patentable feature” of:
`
`defining a payment category including at least limiting purchases to a
`single merchant for at least one transaction, said single merchant
`limitation being included in said payment category prior to any
`particular merchant being identified as said single merchant
`
`See Exh. 1002, ‘486 Patent File History, 9/1/10 Notice of Allowance at 11. The
`
`application subsequently issued as the ‘486 Patent on November 23, 2010.
`
`
`
`Prior to issuance, the Applicant filed a continuation application, U.S. Patent
`
`Application No. 12/902,399, which ultimately issued as U.S. Pat. No. 8,036,988
`
`(“the ‘988 Patent”). During prosecution of the ‘988 Patent, the same Examiner
`
`rejected the pending claims of the ‘988 Patent in view of the ‘486 Patent,
`
`concluding that the claims of the ‘988 Patent were not patentably distinct from
`
`those of the ‘486 Patent. See Exh. 1013, ‘988 Patent File History, 1/14/11 Office
`
`Action at 2-3. The Applicant did not contest that ground for rejection. Instead, to
`
`
`
`- 9 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`overcome that rejection, the Applicant disclaimed the ability to enforce the ‘988
`
`Patent beyond the term of the ’486 Patent – conceding that the claims of the ‘486
`
`Patent and those of the ‘988 Patent are not patentably distinct from each other. See
`
`Exh. 1013, ‘988 Patent File History, 3/21/11 Terminal Disclaimer.
`
`C.
`
`The ‘988 Patent Ex Parte Reexamination File History
`
`On September 12, 2012, the Petitioner filed a Request for Ex Parte
`
`Reexamination of the related ‘988 Patent, and after an initial decision denying the
`
`request, on January 7, 2013, the Petitioner filed a Petition for Review under 37
`
`C.F.R. § 1.181. On June 7, 2013, the Director of the Central Reexamination Unit
`
`granted the Petition for Review and granted the Request for Ex Parte
`
`Reexamination of the ‘988 Patent. In the decision granting the petition, the
`
`Director stated: “in Cohen one can limit the transaction only to a particular type of
`
`merchant, such as computer stores” and further noted that the “card can be limited
`
`to use at certain types of stores, such as clothing stores.” See Exh. 1003, ‘988
`
`Patent Reexamination History, 6/7/13 CRU Decision, at 5. “At the same time,
`
`limiting to ‘clothing stores’ does not identify any one particular merchant.” Id.
`
`The director concluded that “[a]ccordingly, it would appear that Cohen does
`
`include ‘defining a payment category to include at least limiting a number of
`
`transactions to one or more merchants, said one or more merchants limitation being
`
`included in said payment category prior to any particular merchant being identified
`
`
`
`- 10 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`as one of said one or more merchants’ as claimed.” Id. This element is almost
`
`exactly the same as the “uniquely patentable feature” of the ‘486 Patent as
`
`identified by the Examiner during prosecution of the ‘486 Patent. The principal
`
`difference is that the ‘486 Patent claims a payment category that is limited to “a
`
`single merchant”, where as the limitation addressed in the ‘988 Patent is a payment
`
`category that is limited to “one or more merchants.”
`
`To further explain the reasoning for why Cohen discloses this element, the
`
`Director noted that:
`
`Cohen does not necessarily limit transactions to any specific merchant
`or particular store – if Cohen provides a limit of ‘clothing stores’ then
`there is necessarily a limit on number of stores, as not all stores are
`clothing stores. At the same time there is no limit or specific
`identification of any specific store. Cohen therefore limits a number of
`transactions to one or more merchants, those of a specific industry,
`while not identifying [any] particular merchant. Limiting by industry
`does not necessarily identify a particular merchant. Id. at 6.2
`
`As the Director reasoned in his decision, a particular type of store could include
`
`
`2 In the Office Action subsequently issued in the Ex Parte Reexamination, the
`
`Examiner agreed with the Director, rejecting all the claims of the ‘988 Patent. See
`
`Exh. 1003, ‘988 Patent Reexamination History, 9/11/13 Office Action, at 4-5, 13-
`
`14, and 18-19.
`
`
`
`- 11 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`one or more merchants, but it undoubtedly could also be “a single merchant.” Id.
`
`at 7 (granting reexamination for all claims of the ‘988 patent, including claim 21
`
`which claims a payment category that is limited to “a single merchant”).3
`
`Therefore, the Director found that Cohen inherently discloses the exact limitation
`
`that the Applicant relied on to distinguish the claims of the ‘486 Patent from the
`
`prior art.
`
`V. DETAILED EXPLANATION OF REASONS FOR RELIEF
`SHOWING IT IS MORE LIKELY THAN NOT THAT THE
`CHALLENGED CLAIMS ARE UNPATENTABLE
`
`Pursuant to §§ 42.22 and 42.304(b), a full statement of the reasons for the
`
`relief requested, with a detailed explanation of the evidence, including material
`
`facts, and the governing law, rules and precedent is provided below.
`
`A.
`
`The Challenged Claims are Invalid under §§ 102 and/or 103
`
`The following discussion details, in Sections V.A.2-V.A.5, each ground for
`
`which it is more likely than not that each challenged claim is invalid based on the
`
`prior art identified above as either anticipated under § 102 or obvious under § 103
`
`(or a combination, where applicable). Section V.A.1 lists and explains the bases for
`
`Petitioner’s relevant claim constructions for the challenged claims.
`
`3 This conclusion is consistent with the Applicant’s own admission that the claims
`
`of the ‘486 Patent and the ‘988 Patent are not patentably distinct from each other.
`
`See Exh. 1013, ‘988 Patent File History, 3/21/11 Terminal Disclaimer.
`
`
`
`- 12 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`
`1.
`
`Claim Construction
`
`Pursuant to § 42.300(b), and solely for purposes of this review, Petitioner
`
`construes the claim language such that claim terms are given their broadest
`
`reasonable interpretation. For terms not specifically listed and construed below,
`
`and in the absence, to date, of detailed arguments from D’Agostino indicating a
`
`need for construction or a disagreement regarding the meaning of the vast majority
`
`of terms, Petitioner interprets them for purposes of this review in accordance with
`
`their plain and ordinary meaning under the required broadest reasonable
`
`interpretation. Because this standard is different from the standard used in U.S.
`
`District Court litigation, see In re Am. Acad. of Sci. Tech Ctr., 367 F.3d 1359,
`
`1364, 1369 (Fed. Cir. 2004); see also MPEP § 2111, Petitioner expressly reserves
`
`the right to argue in litigation a different claim construction for any term in the
`
`‘486 Patent as appropriate to that proceeding.
`
`• “generating [a/said] transaction code”: For review purposes, this term
`
`means “creating a code usable as a substitute for a credit card number in a purchase
`
`transaction, the number pre-coded to be indicative of a specific credit card
`
`account.” (Exh. 1001, ‘486 Patent at Abstract; 3:43-48; 6:19-38; 6:63-7:1; see Exh.
`
`1008, Grimes Dec. at ¶ 20).4
`
`4 In the event the Board does not accept Petitioner’s construction of “generating
`
`[a/said] transaction code,” but concludes instead that this term means “creating a
`
`
`
`- 13 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`• “defining a payment category”: For review purposes, this term means
`
`“specifying the type of limitation (or limitations) that are available to be applied to
`
`a transaction code in order to limit its use.” (Exh. 1001, ‘486 Patent at 2:67-3:3;
`
`3:48-4:2; 4:20-24; 7:2-8; 7:56-8:43; see Exh. 1008, Grimes Dec. at ¶ 21).
`
`• “particular merchant”: For review purposes, this term means “a
`
`specific merchant with whom a customer can engage in the purchase transaction.”
`
`(Exh. 1001, ‘486 Patent at 3:67-4:2; 4:8-13; 4:44-49; see Exh. 1008, Grimes Dec.
`
`at ¶ 22).
`
`• “verifying that said defined purchase parameters are within said
`
`designated payment category”: For review purposes,
`
`this
`
`term means
`
`“ascertaining that any limitation associated with the designated payment category
`
`is satisfied.” (Exh. 1001, ‘486 Patent at 4:8-13; 7:8-24; see Exh. 1008, Grimes Dec.
`
`at ¶ 23).
`
`• “promotional material”: For review purposes, this term means “any
`
`information about the product that facilitates the purchase transaction.” (Exh. 1001,
`
`
`code usable as a substitute for a credit card number in a purchase transaction”
`
`(without the clause “the number pre-coded to be indicative of a specific credit card
`
`account”) (“Alternative Construction”) then Petitioner presents Grounds 3 and 4
`
`below.
`
`
`
`- 14 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`‘486 Patent at 3:7-12; 5:36-48; 7:25-38; see Exh. 1008, Grimes Dec. at ¶ 24).
`
`2. Ground 1: Claims 1-15 and 22-30 are Anticipated Under 35
`U.S.C. § 102 by Cohen
`(i) Overview of Cohen
`
`U.S. Patent No. 6,422,462 to Cohen (Exh. 1004, “Cohen”) claims priority to
`
`U.S. Provisional Application No. 60/079,8845, which was filed on March 30, 1998.
`
`Accordingly, Cohen is prior art under at least 35 U.S.C. § 102(e), and thus
`
`Petitioner contends satisfies AIA § 18(a)(1)(C).6 Cohen teaches customized,
`
`limited use card numbers for use in purchase transactions over a credit card
`
`network. Cohen at 2:32-43.
`
`Cohen discloses an account holder contacting their credit card company,
`
`verifying their identity, and then being provided with a transaction code number to
`
`be used for a single or limited range of transactions. Id. at 3:41-48; 13:8-14. The
`
`
`5 U.S. Provisional Application No. 60/079,884 supports the subject matter relied
`
`upon in Cohen in compliance with 35 U.S.C. 112, first paragraph.
`
`6 This Board has previously instituted a Covered Business Method Patent Review
`
`on the basis of prior art under 35 U.S.C. § 102(e). See CBM 2013-00008, Decision
`
`Instituting CBM Review, Paper No. 20, at 20-21, 35 (June 24, 2013) (holding that
`
`the CBM petition was granted on the basis of prior art that included U.S. Pat. No.
`
`5,940,812 to Tengel, a 102(e) prior art reference).
`
`
`
`- 15 -
`
`

`

`Covered Business Method Review
`United States Patent No. 7,840,486
`account holder can indicate in advance the limitations applicable to the transaction
`
`code number. Id. at 3:49-52. Once the account holder has received the number,
`
`they can communicate the number to a merchant like it was a regular credit card
`
`number, which the merchant can use to obtain authorization for the purchase
`
`transaction with the credit card company. Id. at 5:35-39. The credit card company
`
`can authorize the use of the customized number, or deny it if it is used for anything
`
`other than the single or customized use indicated by the account holder. Id. at
`
`5:44-49.
`
`Examples of the customized uses for which a disposable or customized
`
`number can be indicated may include a time limit, Id. at 6:7, specific merchant or
`
`industry, Id. at 8:2-14, a specific merchant or merchants, Id. at 8:33-34, purchase
`
`amount, Id. at 8:44, etc. These various customized uses can also be used in
`
`combination, such as a customized number to be used on specific dates, for
`
`specific amounts, etc. and those limits are recorded by the credit card company and
`
`associated with the customized number for verification when payment transactions
`
`occurs, Id. at 10:24-35.
`
`(ii)
`
`Independent Claim 1
`
`Claim
`1. A method of
`performing secure
`credit card purchases,
`said method
`comprising:
`
`Cohen
`Cohen discloses “provid[ing] improved credit cards
`and methods for credit card transactions ... provid[ing]
`methods and apparatus for secure transmission of
`credit card information.” (Cohen at 1:48-62) (emphasis
`added).
`
`
`
`- 16 -
`
`

`

`a) contacting a custodial
`authorizing entity
`having custodial
`responsibility of
`account parameters of a
`customer's account that
`is used to make credit
`card purchases;
`b) supplying said
`custodial authorizing
`entity with at least
`account identification
`data of said customer's
`account;
`c) defining a payment
`category including at
`least limiting purchases
`to a single merchant for
`at least one transaction,
`
`said single merchant
`limitation being
`included in said
`payment category prior
`to any particular
`merchant being
`identified as said single
`merchant;
`
`Covered Business Method Review
`United States Patent No. 7,840,486
`Cohen discloses that a user can contact a custodial
`authorizing entity: “[A] user dials into her credit card
`company....” (Cohen at 3:42-44).
`
`Cohen discloses that a user can provide the custodial
`authorizing entity with her account identification data:
`“[A] user dials into her credit card company…and after
`providing the ordinary credit card number and
`verification data….” (Cohen at 3:42-45).
`
`Cohen discloses a use of various payment categories:
`“The card can also be customized for only particular
`uses or groups of uses.” (Cohen at 7:66-67).
`Cohen discloses a payment category limiting
`transactions to a single merchant: “The card could
`even [be] customized for use in a particular store
`itself...” (Cohen at 8:25-34).
`“[I]n one embodiment…[t]hese credit cards or credit
`card numbers are generated for a one time, single
`transaction basis, after which they are disposed of, or
`thrown away. The numbers can be used…to effect a
`single transaction.” (Cohen at 2:35-43) (emphasis
`added). See Exh. 1008, Grimes Dec. at ¶ 31.
`Cohen discloses that the transaction code is limited to
`a single transaction with one merchant: “in one
`embodiment…[t]hese credit cards or credit card
`numbers are generated for a one time, single
`transaction basis” and then “[a]fter a one time use of
`the credit card number, the number is deactivated.”
`(Cohen at 2:35-43). The merchant for the one-time use
`credit card is not identified until the credit card is used
`for the single transaction. Therefore, the credit card is
`limited to a single transaction with one merchant
`before the merchant is identified at the time the credit
`card is used. See Exh. 1008, Grimes Dec. at ¶ 32.
`
`
`
`- 17 -
`
`

`

`d) designating said
`payment category
`thereby designating at
`least that a transaction
`code generated in
`accordance with said
`payment category can
`be used by only one
`merchant;
`
`e) generating a
`transaction code by a
`processing computer of
`said custodial
`authorizing entity,
`
`said transaction code
`reflecting at least the
`limits of said designated
`
`Covered Business Method Review
`United States Patent No. 7,840,486
`Cohen discloses a user designating the payment
`category by specifying the type(s) of limitation to
`apply: “a user can indicate in advance of
`purchase...what the single use or the customized credit
`card number is to be used for.” (Cohen at 3:49-52).
`Cohen discloses that the transaction code could be
`limited to a single merchant: “The card could even [be]
`customized for use in a particular store itself...”
`(Cohen

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket