`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`———————
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`———————
`
`APPLE INC.,
`
`Petitioner,
`
`v.
`
`FINTIV, INC.,
`
`Patent Owner
`
`———————
`
`IPR2022-00976
`U.S. Patent No. 9,892,386
`
`
`
`
`PETITION FOR INTER PARTES REVIEW
`UNDER 35 U.S.C. § 312 AND 37 C.F.R. § 42.104
`
`
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`TABLE OF CONTENTS
`
`I. MANDATORY NOTICES UNDER 37 C.F.R. § 42.8 ....................................... 1
`
`A. Real Party-in-Interest................................................................................. 1
`
`B. Related Matters .......................................................................................... 1
`
`C. Lead and Back-up Counsel and Service Information ............................... 1
`
`II. INTRODUCTION ................................................................................................ 2
`
`III. GROUNDS FOR STANDING ............................................................................ 2
`
`IV. NOTE REGARDING EMPHASIS ...................................................................... 2
`
`V. THE ’386 PATENT ............................................................................................. 3
`
`A. Overview of ’386 Patent ............................................................................ 3
`
`B. Prosecution History ................................................................................... 4
`
`C. Priority Date .............................................................................................. 4
`
`VI. LEVEL OF ORDINARY SKILL IN THE ART ................................................. 4
`
`VII. CLAIM CONSTRUCTION............................................................................... 5
`
`VIII. IDENTIFICATION OF HOW THE CLAIMS ARE UNPATENTABLE ........ 5
`
`A. Statutory Grounds of Challenge and Relief Requested ............................. 5
`
`B. Summary of Grounds ................................................................................ 6
`
`C. Ground 1: Claim 1 would have been obvious over Dill in view of
`Vadhri, Akashika, and Hansen. ................................................................. 8
`
`1. Overview of Dill................................................................................ 8
`
`2. Overview of Vadhri ........................................................................... 9
`
`3. Overview of Akashika .....................................................................10
`
`i
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`4. Overview of Hansen ........................................................................12
`
`5. Claim 1 ............................................................................................14
`
`[1.0] A monetary transaction system for conducting monetary
`transactions between subscribers and other entities, the
`system comprising one or more of:......................................... 14
`
`[1.1.1] an integration tier operable to manage mobile wallet
`sessions,................................................................................... 16
`
`[1.1.2] the integration tier also including a communication
`application programming interface (API) and other
`communication mechanisms to accept messages from
`channels;.................................................................................. 18
`
`[1.2] notification services operable to send notifications through
`different notification channels including one or more of
`short message peer-to-peer, short-message services and
`simple mail transfer protocol emails; ..................................... 25
`
`[1.3] business process services operable to implement business
`workflows, including at least one of executing financial
`transactions, auditing financial transactions, invoking
`third-party services, handling errors, and logging platform
`objects; .................................................................................... 27
`
`[1.4] database services operable to store financial transaction
`details, store customer profiles, and manage money
`containers; ............................................................................... 31
`
`[1.5] a payment handler service operable to use APIs of
`different payment processors including one or more APIs
`of banks, credit and debit cards processors, bill payment
`processors; ............................................................................... 33
`
`[1.6] a rules engine operable to gather financial transaction
`statistics and use the gathered financial transaction
`statistics to enforce constraints including transaction
`constraints; .............................................................................. 40
`
`ii
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`[1.7] a security service operable to perform subscriber
`authentication; ......................................................................... 42
`
`[1.8] at least one entity that is to be involved in the specified
`transaction, the at least one entity having a profile with the
`monetary transaction system: wherein the at least one
`entity is the agent; ................................................................... 45
`
`[1.9.1] wherein the monetary transaction system is implemented
`to deposit funds at an agent branch, ........................................ 48
`
`[1.9.2] the funds being deposited by a subscriber at the agent
`branch using a mobile device configured to run a monetary
`transaction system application, the monetary transaction
`system performing the following steps: .................................. 49
`
`[1.10.1] receiving a communication message from the mobile
`device over one of a plurality of channels connected to the
`monetary transaction system, .................................................. 52
`
`[1.10.2] the communication message being received by an API
`associated with the integration tier of the monetary
`transaction system, .................................................................. 54
`
`[1.10.3] the communication message indicating that the
`subscriber desires to deposit a specified amount of funds
`into the subscriber's account; .................................................. 56
`
`[1.10.4] validating the status of the subscriber's account,
`wherein validating the status of the subscriber's account
`comprises communicating from the integration tier to the
`database services to query attributes of the subscriber's
`account; ................................................................................... 58
`
`[1.10.5] committing a pending transaction through the business
`process services, ...................................................................... 60
`
`[1.10.6] wherein the integration tier communicates a transaction
`commitment request to the business process services; ........... 61
`
`iii
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`[1.10.7] receiving a confirmation from the business process
`services that the pending transaction has been committed; .... 62
`
`[1.10.8] sending, through the notification services, a receipt
`notification to the mobile device; and .................................... 63
`
`[1.10.9] upon receiving a confirmation of commitment from the
`business process services, committing the pending
`transaction to the database services; and ................................ 64
`
`[1.11.1] wherein committing the pending transaction further
`comprises the following steps as orchestrated by the
`business process services: ....................................................... 68
`
`[1.11.2] ensuring, via the database services, that the subscriber
`has an active account; ............................................................. 68
`
`[1.11.3] validating, through communication with the security
`services, one or more of a PIN number and an access
`control list; .............................................................................. 69
`
`[1.11.4] applying with the rules engine, velocity rules; .................. 73
`
`[1.11.5] creating with the database services a new pending
`transaction history record; ...................................................... 78
`
`[1.11.6] holding funds from the agent account balance using the
`payment handler, ..................................................................... 79
`
`[1.11.7] loading the funds to the subscriber account using the
`payment handler; and .............................................................. 81
`
`[1.11.8] updating, using the database services, a pending
`transaction history record to reflect the funds. ....................... 83
`
`D. Grounds 1 and 2: claim 2 would have been obvious over Dill in view
`of Vadhri, Akashika, Hansen, and Liao (Ground 2); claim 3 would
`have been obvious over Dill in view of Vadhri, Akashika, and
`Hansen (Ground 1). .................................................................................84
`
`1. Claims 2 and 3 .................................................................................84
`
`iv
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`a. Limitations in Claims 2 and 3 Identical to Claim 1 ........................84
`
`b. Limitations Unique to Both Claims 2 and 3 ...................................86
`
`[2.1.1]/[3.1.1] an integration tier operable to manage mobile
`wallet sessions and maintain the integrity of financial
`transactions,............................................................................. 86
`
`[2.8]/[3.7] a rules engine operable to gather financial
`transaction statistics and use the gathered financial
`transaction statistics to enforce business constraints
`including transaction constraints; ........................................... 86
`
`[2.11.1]/[3.5.1] a monetary transaction system subscriber that
`has a profile with the monetary transaction system the
`subscriber profile stored in the database of the monetary
`transaction system, .................................................................. 87
`
`[2.11.2]/[3.5.2] wherein the subscriber indicates, via the
`monetary transaction system application, one or more
`specified transactions that are to be performed using the
`monetary transaction system; .................................................. 89
`
`c. Limitations Unique to Claim 3 (Ground 1) .....................................89
`
`[3.10.1] wherein the monetary transaction system is
`implemented to transfer funds using the mobile device
`configured to run a monetary transaction system
`application, including performing the following steps: .......... 89
`
`[3.10.4] the communication message indicating that the
`subscriber desires to transfer a specified amount of funds
`from the subscriber's account to a recipient;........................... 92
`
`d. Limitations Unique to Claim 2 (Ground 2) .....................................95
`
`[2.6] a mobile device configured to run a monetary transaction
`system application; .................................................................. 95
`
`[2.12.1] wherein the monetary transaction system is
`implemented to withdraw funds at an agent branch using
`
`v
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`the mobile device configured to run a monetary
`transaction system application, including performing the
`following steps: ....................................................................... 96
`
`[2.12.4] the communication message indicating that the
`subscriber desires to withdraw a specified amount of funds
`from an account associated with the subscriber, .................. 100
`
`[2.12.5] the communication comprising a secure, perishable
`code; ...................................................................................... 101
`
`[2.12.6] determining that the transaction is valid and in
`progress, ................................................................................ 104
`
`[2.12.7] wherein determining that the transaction is valid
`comprises validating the secure, perishable code and
`communicating from the integration tier to the database
`services to query attributes of the subscriber's account; ....... 105
`
`IX. DISCRETIONARY DENIAL IS INAPPROPRIATE .....................................109
`
`X. CONCLUSION ................................................................................................110
`
`CERTIFICATE OF WORD COUNT ....................................................................111
`
`CERTIFICATE OF SERVICE ..............................................................................112
`
`CLAIMS APPENDIX ............................................................................................113
`
`
`
`
`
`
`
`vi
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`PETITIONER’S EXHIBIT LIST1
`APPL-1001 U.S. Patent No. 9,892,386
`APPL-1002 File History of U.S. Patent No. 9,892,386
`APPL-1003 Declaration of Henry Houh, Ph.D.
`APPL-1004 Curriculum Vitae of Henry Houh, Ph.D.
`APPL-1005 U.S. Patent Publication No. 2009/0265272 to Dill et al. (“Dill”)
`APPL-1006 U.S. Patent Publication No. 2010/013334 to Vadhri (“Vadhri”)
`APPL-1007 U.S. Patent Publication No. 2009/0217047 to Akashika et al.
`(“Akashika”)
`APPL-1008 U.S. Patent Publication No. 2004/0230527 to Hansen et al.
`(“Hansen”)
`APPL-1009 U.S. Patent No. 7,865,141 to Liao et al. (“Liao”)
`APPL-1010 Claims Appendix for U.S. Patent No. 9,892,386
`APPL-1011 Comparison chart for claims 1-3 of U.S. Patent No. 9,892,386
`APPL-1012 G. Winfield Treese et al., “Designing Systems for Internet
`Commerce,” Second Edition, Addison-Wesley, 2003 (“Treese”)
`(excerpt)
`APPL-1013 Original Complaint for Patent Infringement, Fintiv, Inc. v. PayPal
`Holdings, Inc., No. 6:22-cv-00288, ECF. No. 1 (W.D. Tex. March
`17, 2022) (Albright)
`APPL-1014 H. Newton, “Newton’s Telecom Dictionary,” 17th Edition, CMP
`Books, 2001 (excerpt)
`APPL-1015 T. Thai et al., “.Net Framework Essentials,” Third Edition,
`O’Reilly & Associates, Inc., 2003 (excerpt)
`
`
`1 Petitioner’s citations to APPL-1002 use page numbers added per 37 C.F.R.
`
`§ 42.63(d)(2)(ii). Citations to other exhibits use page or paragraph numbers in their
`
`original publications.
`
`vii
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`I. MANDATORY NOTICES UNDER 37 C.F.R. § 42.8
`A. Real Party-in-Interest
`
`Apple Inc. (“Petitioner”) is the real party-in-interest.
`
`B. Related Matters
`
`As of the filing date of this Petition, and to the best knowledge of Petitioner,
`
`U.S. 9,892,386 (“the ’386 patent,” APPL-1001) is involved in the following district
`
`court litigation.
`
`Case
`Fintiv, Inc. v. PayPal Holdings, Inc.
`(Complaint filed March 17, 2022)
`(“PayPal litigation”)
`To the best knowledge of Petitioner, the ’386 patent has not been involved in
`
`Case No.
`No. 6:22-cv-00288
`
`Court
`W.D. Tex.
`
`any proceedings before the Board.
`
`C. Lead and Back-up Counsel and Service Information
`
`Lead Counsel
`Andrew S. Ehmke
`HAYNES AND BOONE, LLP
`2323 Victory Ave. Suite 700
`Dallas, TX 75219
`
`Backup Counsel
`Jonathan R. Bowser
`HAYNES AND BOONE, LLP
`800 17th Street NW, Suite 500
`Washington, DC 20006
`
`
`
`
`
`
`Phone: (214) 651-5116
`Fax: (214) 200-0853
`andy.ehmke.ipr@haynesboone.com
`USPTO Reg. No. 50,271
`
`
`Phone: (202) 654-4503
`Fax: (214) 200-0853
`jon.bowser.ipr@haynesboone.com
`USPTO Reg. No. 54,574
`
`
`
`
`
`1
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`Angela Oliver
`HAYNES AND BOONE, LLP
`800 17th Street NW, Suite 500
`Washington, DC 20006
`
`Eugene Goryunov
`HAYNES AND BOONE, LLP
`2323 Victory Ave. Suite 700
`Dallas, TX 75219
`
`Michael S. Parsons
`HAYNES AND BOONE, LLP
`2323 Victory Ave. Suite 700
`Dallas, TX 75219
`
`
`Phone: (202) 654-4552
`Fax: (214) 200-0853
`angela.oliver.ipr@haynesboone.com
`USPTO Reg. No. 73,271
`
`Phone: (312) 216-1630
`Fax: (214) 200-0853
`eugene.goryunov.ipr@haynesboone.com
`USPTO Reg. No. 61,579
`
`Phone: (972) 739-8611
`Fax: (214) 200-0853
`michael.parsons.ipr@haynesboone.com
`USPTO Reg. No. 58,767
`
`
`Please address all correspondence to lead and back-up counsel. Petitioner
`
`consents to electronic service at the email addresses above and asks Patent Owner
`
`to do the same.
`
`II.
`
`INTRODUCTION
`
`Petitioner requests inter partes review (IPR) and cancellation of claims 1-3
`
`(the “Challenged Claims”) of the ’386 patent.
`
`III. GROUNDS FOR STANDING
`
`Petitioner certifies the ’386 patent is eligible for IPR and Petitioner is not
`
`barred or estopped from requesting an IPR on the grounds herein.
`
`IV. NOTE REGARDING EMPHASIS
`All bold, bold italics, and bold underline has been added. Text in italics
`
`signifies claim language.
`
`2
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`V. THE ’386 PATENT
`A. Overview of ’386 Patent
`
`Figure 2 below shows a monetary transaction system 200 in which a first
`
`subscriber 205 utilizes a mobile device 206 having a mobile wallet application 207
`
`to conduct a transaction with another entity (e.g., another subscriber 222, a retail
`
`store, or agent 223) through a monetary transaction system 210. APPL-1001,
`
`14:27-39, Abstract, 1:37-39.
`
`Subscriber
`
`Subscriber
`
`Agent
`
`APPL-1001, Fig. 2 (annotated)
`
`
`The monetary transaction system 210 accesses profile information 211 about
`
`
`
`the subscriber and uses a rules engine 220 to determine whether the transaction is
`
`3
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`permissible, e.g., based on whether the subscriber has sufficient money in her
`
`account. APPL-1001, 14:40-64.
`
`B. Prosecution History
`
`The ’386 patent was filed as Application No. 15/201,152 (“’152
`
`application,” APPL-1002). The Examiner issued two Office Actions, rejecting the
`
`claims only on the basis of 35 U.S.C. § 101. APPL-1002, 1606-1612, 1366-1371.
`
`The Examiner did not reject the claims on the basis of any prior art.
`
`C. Priority Date
`
`For purposes of the analysis herein, Petitioner assumes a June 3, 2011,
`
`priority date, without conceding that the Challenged Claims are entitled to that
`
`date.
`
`VI. LEVEL OF ORDINARY SKILL IN THE ART
`
`A person of ordinary skill in the art (“POSITA”) in June 2011 would have
`
`had a working knowledge of mobile payment techniques pertinent to the ’386
`
`patent, including software development in the field of mobile payment techniques.
`
`Such POSITA would have had a bachelor’s degree in electrical engineering,
`
`computer science, or equivalent training, and approximately two years of work
`
`experience in software development. Lack of work experience can be remedied by
`
`additional education, and vice versa. APPL-1003, ¶¶21-22.
`
`4
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`VII. CLAIM CONSTRUCTION
`
`Petitioner submits that no claim term requires construction beyond its
`
`ordinary and customary meaning. A POSITA would apply the ordinary and
`
`customary meaning to all terms in the Challenged Claims. APPL-1003, ¶43.
`
`VIII.
`
`IDENTIFICATION OF HOW THE CLAIMS ARE UNPATENTABLE
`
`A. Statutory Grounds of Challenge and Relief Requested2
`
`These references are pertinent to the grounds presented below:
`
`1. U.S. 2009/0265272 (“Dill,” APPL-1005), which published October 3,
`
`2009, and is prior art under §§102(a)-(b).
`
`2. U.S. 2010/0133334 (“Vadhri,” APPL-1006), which published June 3,
`
`2010, and is prior art under §§102(a)-(b).
`
`3. U.S. 2009/0217047 (“Akashika,” APPL-1007), which published August
`
`27, 2009, and is prior art under §§102(a)-(b).
`
`4. U.S. 2004/0230527 (“Hansen,”APPL-1008), which published November
`
`18, 2004, and is prior art under §§102(a)-(b).
`
`5. U.S. 7,865,141 (“Liao,” APPL-1009), which issued January 4, 2011, and is
`
`prior art under §§102(a)-(b).
`
`
`2 The pre-AIA statutory framework applies to the ’386 patent.
`
`5
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`This Petition, supported by the declaration of Dr. Henry Houh (APPL-1003),
`
`requests IPR and cancellation of the Challenged Claims as follows:
`
`Grounds
`#1
`#2
`
`Claim(s)
`1, 3
`2
`
`Basis under 35 U.S.C. § 103
`Dill, Vadhri, Akashika, and Hansen
`Dill, Vadhri, Akashika, Hansen, and
`Liao
`
`B. Summary of Grounds
`
`
`
`Claims 1-3 each recite “[a] monetary transaction system for conducting
`
`monetary transactions between subscribers and other entities.” APPL-1001, 30:54-
`
`55, 32:3-4, 33:34-35. Claims 1-3 differ in the transaction that is conducted:
`
`• Claim 1 recites depositing funds at an agent branch (APPL-1001, 31:22-23);
`
`• Claim 2 recites withdrawing funds at an agent branch (APPL-1001, 32:51-
`
`53); and
`
`• Claim 3 recites transferring funds (APPL-1001, 34:14-15).
`
`As shown in Sections VIII.C-VIII.D below, the monetary transaction system
`
`of claims 1-3 is the predictable combination of well-known features in the art. Dill
`
`teaches a system for making financial transfers in which a subscriber, using a
`
`mobile wallet application, transfers funds through an agent. APPL-1005, Fig. 9,
`
`¶¶100 (“FIG. 9 is a block diagram illustrating another exemplary system for
`
`making financial transfers.”), 101-105, 49-57 (describing system of FIG. 1), Fig. 5,
`
`77 (“FIG. 5 illustrates an exemplary flow for a ‘mobile-to-mobile transaction.’”),
`
`78-81; APPL-1003, ¶¶46-48.
`
`6
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`Dill teaches deposit and transfer transactions because its financial transfer
`
`system performs several different types of services including “delivering funds to a
`
`funds withholding system,” “delivering funds to a bank account of a recipient,”
`
`and “making funds available for pick up at an agent location.” APPL-1005, ¶101;
`
`APPL-1003, ¶49.
`
`Liao shows that it was known for a mobile wallet subscriber to withdraw
`
`funds, as recited in claim 2. APPL-1009, 5:44-55 (user may use “mobile wallet
`
`application…to withdraw money from a bank account.”); APPL-1003, ¶50.
`
`Vadhri shows that it was known to use (1) an application programming
`
`interface (API) in a financial transaction system (APPL-1006, ¶¶52, 50), and (2)
`
`secure, perishable codes (temporary account codes 103/203) in a financial
`
`transaction. APPL-1006, ¶¶17-19, 37, 80; APPL-1003, ¶¶70, 58-60, 252-253.
`
`Akashika shows that it was known to secure financial transactions by using
`
`an access control list. APPL-1007, ¶¶60, 58, 17. Hansen shows that it was known
`
`to utilize velocity limits in authorizing a mobile transaction. APPL-1008, ¶78;
`
`APPL-1003, ¶¶70, 65-66.
`
`All these references are analogous art to the ’386 patent because they are
`
`each (1) in the same field of endeavor (e.g., monetary transaction systems) and (2)
`
`reasonably pertinent to a problem that the ʼ386 patent sought to solve (e.g.,
`
`7
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`monetary transactions between subscribers and other entities). APPL-1003, ¶¶67,
`
`243.
`
`C. Ground 1: Claim 1 would have been obvious over Dill in view of
`Vadhri, Akashika, and Hansen.
`
`1. Overview of Dill
`
`With reference to Figure 9 below, Dill discloses a “system [100] for making
`
`financial transfers.” APPL-1005, ¶100. A money transfer facilitator 140 is coupled
`
`with a financial transfer network 155 to transfer money from a source account 165
`
`in a sender’s financial institution 160 to a destination account 175 in a recipient’s
`
`financial institution 170. APPL-1005, ¶49. A sender 105 transfers money to a
`
`recipient 110 through the money transfer facilitator 140, which may utilize an
`
`agent 135 to facilitate the transfer. APPL-1005, ¶¶50-51, 54 (“[t]he money transfer
`
`facilitator 140 can receive the request to initiate the money transfer
`
`transaction…from the agent 135.”). The transaction may be conducted wirelessly
`
`over a mobile network 115, where the sender 105 and recipient 110 each use a
`
`mobile wallet 125, 130 respectively installed on their mobile devices to interact
`
`with a mobile application 145 of the money transfer facilitator 140. APPL-1005,
`
`¶¶52-54.
`
`8
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`APPL-1005, Fig. 9
`
`2. Overview of Vadhri
`
`
`
`Vadhri is directed to “systems and methods for accessing a value holding
`
`account.” APPL-1006, ¶1. With reference to Figure 5 below, Vadhri teaches a
`
`networked system 502 that manages payments between various applications and
`
`accounts. APPL-1006, ¶¶47-50. Vadhri discloses that an “Application Program
`
`9
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`Interface (API) server 514” provides an interface between (1) application server
`
`518, which hosts marketplace applications 520 and payment applications 522, (2)
`
`client machines 512, 514, and (3) third party servers 530 through the Internet 504.
`
`APPL-1006, ¶¶48-50, 55. Vadhri shows that it was known to use an application
`
`programming interface (API) in a monetary transaction system.
`
`
`
`APPL-1006, Fig. 5 (annotated)
`3. Overview of Akashika
`
`
`
`Akashika is directed to an access control system that promotes secure
`
`communications by protecting sensitive data such as “electronic money or
`
`10
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`important personal information.” APPL-1007, ¶¶7, 9. With reference to Figure 1
`
`below, Akashika discloses a service providing system 1000 in which a client
`
`device 400 communicates with a service providing server 300,3 certificate
`
`authority server 100 and area management server 200 over a network 10. APPL-
`
`1007, ¶¶47-50.
`
`APPL-1007, Fig. 1
`
`
`
`
`3 Akashika’s Figure 1 contains a typographical error. APPL-1007, ¶48 (describing
`
`Figure 1 as including a “certificate authority server 100” and a “service providing
`
`server 300.”).
`
`11
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`As shown in Figure 3 below, the area management server 200 includes an
`
`“access control list generation section 208 [that] generates an access control list”
`
`(ACL) identifying “the scope of…access right[s]” to the client device 400. APPL-
`
`1007, ¶¶60, 58, 17.
`
`
`
`Access Control
`List (ACL)
`
`
`
`APPL-1007, Fig. 3 (annotated)
`4. Overview of Hansen
`
`
`
`With reference to Figure 6A below, Hansen teaches that a payment enabler,
`
`which “perform[s] a money transfer” process 600, checks internal business rules
`
`that include “velocity checks” (step 604). APPL-1008, ¶78. Hansen discloses that
`
`the velocity checks include “a limit on the amount of a single transaction, a limit
`
`12
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`on the aggregate amount for various transactions over a time period, a limit on the
`
`number of transactions during a time period, etc.” Id.
`
`APPL-1008, Fig. 6A (annotated)
`
`
`
`13
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`5. Claim 1
`
`[1.0] A monetary transaction system for conducting monetary transactions
`between subscribers and other entities, the system comprising one or more of:
`
`Dill discloses limitation [1.0]. Dill discloses a “system for making financial
`
`transfers.” APPL-1005, ¶100. Dill’s financial transfer system 100 (“monetary
`
`transaction system”) is depicted in Figure 9 below.4 The system 100 includes a
`
`money transfer facilitator 140 that “affect[s] a transfer from and/or to the [sender’s
`
`and recipient’s] accounts165 and 175 via the financial transfer network 155.”
`
`APPL-1005, ¶49. Dill teaches that the sender 105 and recipient 110 are
`
`“subscribers.” APPL-1005, ¶53 (“[T]he mobile wallet application 121 maintains
`
`mobile wallets 125 and 130 for one or more subscribers, such as the sender 105
`
`and/or recipient 110.”). APPL-1003, ¶¶73-74.
`
`
`
`
`
`
`4 Dill’s system 100 in Figure 9 includes the system 100 in Figure 1 plus interfaces
`
`136-138 and delivery rules 151. APPL-1005, ¶¶100-102.
`
`14
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`Monetary Transaction System
`
`
`Subscriber
`
`
`
`
`Entity
`
`
`Subscriber
`
`
`APPL-1005, Fig. 9 (annotated); APPL-1003, ¶73.
`
`
`
`
`
`
`
`Dill teaches that financial transactions between the subscribers (sender 105,
`
`recipient 110) are conducted with other entities, such as “agent 135 in
`
`communication with the money transfer facilitator 140,” where the “agent 135
`
`provides a channel by which entities can access the services of the money transfer
`
`15
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`facilitator 140.” APPL-1005, ¶51. Dill discloses that “a sender 105 can initiate a
`
`transaction to transfer money to a recipient 110” by “access[ing] the services of the
`
`money transfer facilitator 140.” APPL-1005, ¶51; APPL-1003, ¶75.
`
`Thus, Dill discloses a monetary transaction system for conducting monetary
`
`transactions (system 100) between subscribers (sender 105, recipient 110) and
`
`other entities (e.g., agent 135, financial institutions 160, 170), as recited in [1.0].
`
`APPL-1003, ¶76.
`
`[1.1.1] an integration tier operable to manage mobile wallet sessions,
`
`Dill discloses limitation [1.1.1]. As shown in Figure 9 below, Dill’s money
`
`transfer facilitator 140 includes a transfer options module 145 (“integration tier”)
`
`that sends and receives payment transfer information from one or more interfaces
`
`136-138. The “transfer options module 145 [is] communicatively coupled with the
`
`one or more interfaces 136-138,” and “receive[s] transaction information for a
`
`money transfer transaction from a sender 105 through at least one o[f] the
`
`interfaces 136-138.” APPL-1005, ¶101; APPL-1003, ¶77.
`
`16
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`Integration Tier
`
`
`APPL-1005, Fig. 9 (annotated); APPL-1003, ¶77.
`
`Dill teaches that the transfer options module 145 (“integration tier”)
`
`manages mobile wallet sessions because each transaction corresponds to a mobile
`
`wallet session. The money transfer facilitator 140 “receive[s] transaction
`
`information from a mobile wallet application 121 via a mobile network 115,” and
`
`the transfer options module 145 “select[s] one or more delivery options” based on
`
`the requested transaction. APPL-1005, ¶¶100, 102. The money transfer facilitator
`
`17
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`140 “provide[s] a structured settlement between unrelated entities such as the
`
`sending mobile wallet 125 and receiving mobile wallet 130.” APPL-1005, ¶57.
`
`Each transaction is assigned a unique “transaction identifier,” e.g., by a “mobile
`
`network operator,” and this unique transaction identifier may be “used by the
`
`transfer options module 145 to determine delivery of the transfer.” APPL-1005,
`
`¶105; APPL-1003, ¶78.
`
`Dill’s transfer options module 145 teaches “an integration tier (transfer
`
`options module 145) operable to management mobile wallet sessions,” because the
`
`transfer options module 145 sends and receives transaction details between mobile
`
`wallets 125, 130 within a mobile wallet application 121, and each transaction
`
`corresponds to a mobile wallet session tied to the unique transaction identifier
`
`assigned by a “mobile network operator.” APPL-1003, ¶79.
`
`[1.1.2] the integration tier also including a communication application
`programming interface (API) and other communication mechanisms to accept
`messages from channels;
`
`Limitation [1.1.2] is rendered obvious by Dill and Vadhri. APPL-1003, ¶80.
`
`First, as shown in Figure 9 below, Dill teaches that the transfer options
`
`module 145 (integration tier) includes multiple communication mechanisms to
`
`accept messages from channels. Dill discloses that the “transfer options module
`
`145 [is] communicatively coupled with the one or more interfaces 136-138,” and is
`
`“adapted to receive transaction information for a money transfer transaction from a
`
`18
`
`

`

`Petition for Inter Partes Review of U.S. Patent No. 9,892,386
`
`sender 105 through at least one o[f] the interfaces 136-138.” APPL-1005, ¶101.
`
`The interfaces 136-138 correspond to “communication mechanisms,” because the
`
`transfer options module 145 receives from the interfaces 136-138 “transaction
`
`information,” which corresponds to the claimed “messages.” APPL-1003, ¶81.
`
`Further, as shown in Figure 9, there are communication “channels” between the
`
`transfer options module 145 (“integration tier”) and the interfaces 136-138
`
`(“communication mechanisms”), because the “transfer options module 145 [is]
`
`communicatively coupled with the one or more interfaces 136-138.” APPL-1005,
`
`¶101; APPL-1003, ¶81.
`
`As shown in Figure 9, the communication channel between agent 135 and
`
`the money transfer facilitator 140 corresponds