USOO9147 184B2
`
`(12) United States Patent
`Dickelman
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 9,147,184 B2
`Sep. 29, 2015
`
`(54) CONTROL SYSTEM ARRANGEMENTS AND
`METHODS FOR DISPARATE NETWORK
`SYSTEMS
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`(75) Inventor: Mark Dickelman, Inverness, IL (US)
`(73) Assignee: U.S. Bank National Association,
`Cincinnati, OH (US)
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 1259 days.
`Appl. No.: 12/323,127
`
`(*) Notice:
`
`(21)
`(22)
`(65)
`
`(60)
`
`(51)
`
`(52)
`
`5,465,206 A 11, 1995 Hilt et al.
`5,596,642 A
`1/1997 Davis et al.
`5,596,643 A
`1/1997 Davis et al.
`5,649,117 A
`7/1997 Landry
`5,649,118 A
`7/1997 Carlisle et al.
`5,650,604 A
`7/1997 Marcous et al.
`5,717,989 A
`2f1998 ToZZoli et al.
`6,070,150 A
`5/2000 Remington et al.
`6,292,789 B1
`9, 2001 Schutzer
`6,298,335 B1 10/2001 Bernstein
`6,529, 187 B1
`3/2003 Dickelman
`6,847,953 B2 *
`1/2005 Kuo ................................ 705/75
`7,092,913 B2
`8/2006 Cannon, Jr.
`7,174,302 B2
`2/2007 Patricelli et al.
`7,280,981 B2 10/2007 Huang et al.
`7.464,859 B1 12/2008 Hawkins
`7.584,151 B2
`9, 2009 Wells et al.
`7,590,557 B2
`9, 2009 Harrison et al.
`7.627,523 B1
`12/2009 Symonds et al.
`(Continued)
`Primary Examiner — Matthew Gart
`Assistant Examiner — Reva R Danzig
`(74) Attorney, Agent, or Firm — Crawford Maunu PLLC
`(57)
`ABSTRACT
`Electronic transaction data sets are processed for a multitude
`of disparate transactions using a plurality of autonomous
`payment networks. A Software-programmed computer type
`system receives and processes point-of-sale transaction data
`to select one of the payment networks associated with a
`participant ID (e.g., for a buyer or seller) in the transaction
`data. The system includes a plurality of network-specific
`interface modules, each associated with a specific payment
`network for interfacing therewith. For point-of-sale transac
`tion data, the interface module corresponding to the selected
`payment network communicates payment data to the selected
`payment network to effect electronic payment for the point
`of-sale transaction data.
`
`20 Claims, 6 Drawing Sheets
`
`
`
`30
`
`Filed:
`
`Nov. 25, 2008
`
`Prior Publication Data
`US 2009/O144166A1
`Jun. 4, 2009
`
`Related U.S. Application Data
`Provisional application No. 60/991,379, filed on Nov.
`30, 2007.
`
`(2012.01)
`(2006.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`
`Int. C.
`G06O20/20
`G06G L/14
`G06O20/10
`G06O40/00
`G06O 30/02
`G06O 10/10
`G06O 10/06
`G06O 30/04
`G06O 30/06
`U.S. C.
`CPC ................ G06O20/20 (2013.01); G06O20/10
`(2013.01); G06O20/202 (2013.01); G06Q
`40/00 (2013.01)
`
`(58) Field of Classification Search
`USPC ................................... 705/39, 64, 40, 1.1, 21
`See application file for complete search history.
`
`-304
`
`306
`
`Wirtual Wallet (including
`selection of buyer network and
`account)
`
`Buyer Profiles
`
`-310
`
`Routing System
`
`-314
`
`Source andistination Acxults
`-316
`
`Selected Eestimationistworki
`Asout
`
`8elected SirteNetwork!
`Account
`
`Nsick
`
`
`
`A
`
`Purchase
`information and
`Selectec
`NetworkAccount
`
`
`
`324
`
`Seller Network.Account
`Selection
`
`-320
`'-
`W
`
`WI
`
`seller Profiles
`
`322
`
`APPL-1019 / IPR2022-00976 / Page 1 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`US 9,147,184 B2
`Page 2
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`2/2010 Robbins, Jr. et al.
`7,661,586 B2
`2/2010 Dirnberger et al.
`7,664,690 B2
`3/2010 Patricelli et al.
`7,680,679 B1
`7.693,783 B2 * 4/2010 Balasubramanian et al. .. 705/38
`T.702,530 B2
`4/2010 Pearson
`7.702.553 B1
`4/2010 Dickelman
`7.702,577 B1
`4/2010 Dickelman
`77 (1621 B2
`5 2010 Huanget al.
`2001/0014878 A1
`8, 2001 Mitra et al.
`2002fOOO2495 A1
`1/2002 Ullman
`2002/011 1886 A1
`8/2002 Chenevich et al.
`2002/011 1915 A1
`8, 2002 Clemens et al.
`2002/011 1916 A1* 8, 2002 Coronna et al. ................ TO5/64
`2002fO145051 A1 10, 2002 Charrin
`2002/0184147 A1 12/2002 Boulger
`2003/0004867 A1* 1/2003 Kight et al. ..................... 705/39
`2003/OOO9382 A1* 1/2003 D'Arbeloff et al. ............ 705/17
`2003, OO61147 A1
`3/2003 Fluhr et al.
`2003, OO61157 A1
`3, 2003 Hirka et al.
`
`2/2004 Roskind
`2004.0024.703 A1
`2/2004 Holm-Blagget al.
`2004/0030657 A1
`3/2004 Huang et al.
`2004/0044621 A1
`4, 2004 Metal.
`2004/0080691 A1
`52004 Baker et al.
`2004/0093302 AI
`3/2005 Dickelman et al.
`2005/0060579 A1
`4/2005 Courtion et al.
`2005/OO77350 A1
`2005/0222961 A1 10, 2005 Stab et al.
`2005/0267840 Al 12/2005 Holm-Blagget al.
`2006/008990.6 A1
`4/2006 Rowley
`2006/01 16957 A1
`6/2006 May et al.
`2006/0178986 A1* 8, 2006 Giordano et al. ............... TO5/40
`2007/0O3.8577 A1
`2/2007 Werner et al.
`2007/0282743 A1 12/2007 Lovelett et al.
`2008/0046358 A1
`2/2008 Holm-Blagget al.
`2008/009 1596 A1* 4/2008 Labaton .......................... TO5/40
`2008/0103985 A1
`5/2008 Huang et al.
`2008/0275748 A1 11/2008 John
`2008/0306838 A1 12/2008 Fleet et al.
`2008/0307034 A1 12/2008 Fleet et al.
`2009 OO3O848 A1
`1/2009 Wendel
`
`* cited by examiner
`
`APPL-1019 / IPR2022-00976 / Page 2 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`U.S. Patent
`
`Sep. 29, 2015
`
`Sheet 1 of 6
`
`US 9,147,184 B2
`
`60I
`
`
`
`3.In?deo uo?oesuel L Jelles-le-Ang
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`VI "OIH
`
`OLI — ^
`
`he
`
`as a on up us
`
`is
`
`(~~-----------
`
`__----------
`
`JOSS0001)|
`
`APPL-1019 / IPR2022-00976 / Page 3 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`U.S. Patent
`
`Sep. 29, 2015
`
`Sheet 2 of 6
`
`US 9,147,184 B2
`
`
`
`E]eqal“OLAauaaresuoOBSUBIal84ng
`
`Qunowry)
`
`Lor901sor
`
`60T801
`
`
`
`tor—4
`
`
`
`Jrolcory
`
`J31/9S-9ANg
`
`
`
`
`
`SOBHSzU|JOYSSuonoesuelsf<
`
`andes
`
`
`
`
`
`
`
`10;~3/9S
`
`
`
`
`
`
`
`
`
`J0p9/8Si:=S8TWayshgjunooayJ21}9¢gwiayshgjunasayJaAngi
`
`
`
`
`
`sjunogoysa3S
`
`aiqeaissey
`
`
`
`yunosoy13]/3S
`
`}Wayshg
`
`
`
`
`
`S}UNODDYJ8|]8S
`
`aIQeAasay
`
`
`
`yUNOIIYJBIeS
`
`Zwayskgs
`
`
`
`
`
`2IGeAIS0aySyunoDoyyunosoy—_—_——_—_——|_—
`
`git—*
`
`
`
`luay}shgwajskg
`
`_A€ITai?Au
`
`
`
`
`
`~BulpioH
`
`
`
`induywdu|
`
`ZweyshsS
`
`
`
`qunoooyJeAng
`
`
`
`pagaspspes
`
`
`
`
`Burodaysakng
`
`lusjueYyayy
`
`
`
`BurpiodosyJoAng
`
`LUSHUBYooyy
`
`
`
`sjunoaoyJayag
`
`aiqeajoay
`
`
`
`qunoasy19/185
`
`Nwlajshg
`
`
`
`
`
`Wa]SA8JORUODJEIOUBU|
`
`
`
`junosaysehng
`
`Nwayshs
`
`
`JaAng
`
`Burpiodey
`
`LUSIUEYOS|\]
`
`
`
`(‘ype‘uoHEeNaeosey‘uoIOe}eppnely‘ypne)
`
`
`
`
`
`
`
`APPL-1019 / IPR2022-00976 / Page 4 of 19
`APPLEINC. v. FINTIV, INC.
`
`
`
`SoByeyU]JaAng
`
`
`
`
`
`qunugoyJelng
`
`|Wwiayshg
`
`
`
`APPL-1019 / IPR2022-00976 / Page 4 of 19
`APPLE INC. v. FINTIV, INC.
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Sep. 29, 2015
`
`Sheet 3 of 6
`
`US 9,147,184 B2
`
`205
`
`/ Buyer/Seller
`
`Interface
`
`-202 \r
`N.
`--> A
`(Account ID."
`Buyer/Seller
`- /
`interface
`
`
`
`
`
`
`
`Population System
`
`Payment Routing
`
`Seller or Buyer
`
`
`
`
`
`O O
`
`Seller or Buyer
`Network
`
`APPL-1019 / IPR2022-00976 / Page 5 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`U.S. Patent
`
`Sep. 29, 2015
`
`Sheet 4 of 6
`
`US 9,147,184 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`9 °5) ILI
`
`APPL-1019 / IPR2022-00976 / Page 6 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`U.S. Patent
`
`Sep. 29, 2015
`
`Sheet 5 of 6
`
`US 9,147,184 B2
`
`
`
`
`
`rirJOyUSp]
`
`ost?
`
`
`
`
`
`
`
`
`
`yekng
`
`
`
`
`
`YWOMISNa]}eedsiqSIPaqyeiedsiqjo4oyQuep]
`‘AS
`
`
`.@Sf]S101x9]-4jaAng
`JoyajeSslwals,
`uo|pesuelysauquapyJeyuepy
`
`
`1218SjafngJeAng
`
`eedaPiJefng
`uonsesuel}sekng
`eedaindeg
`
`
`
`
`
`
`
`
`
`YOMISNSIBUIS
`
`uonoesuely
`
`Pye
`
`abus
`
`OMaN
`
`SoeLayu|
`
`
`
`Jeng
`
`Jeyquap;
`
`andes
`
`eee
`
`aaAng
`
`J9yUSpE
`
`
`
`pO
`
`
`
`
`
`
`Suynoy
`
`uolsisoq.
`
`ainjdes
`
`Jalyue|
`
`veun
`
`
`
`
`
`
`Jafng
`ALSOP)
`
`
`
`
`APPL-1019 / IPR2022-00976 / Page 7 of 19
`APPLEINC. v. FINTIV, INC.
`
`APPL-1019 / IPR2022-00976 / Page 7 of 19
`APPLE INC. v. FINTIV, INC.
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Sep. 29, 2015
`
`Sheet 6 of 6
`
`US 9,147,184 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`APPL-1019 / IPR2022-00976 / Page 8 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`US 9,147,184 B2
`
`1.
`CONTROL SYSTEMARRANGEMENTS AND
`METHODS FOR DISPARATE NETWORK
`SYSTEMS
`
`RELATED PATENT DOCUMENTS
`
`This patent document claims the benefit, under 35 U.S.C.
`S119(e), of U.S. Provisional Patent Application Ser. No.
`60/991,379, entitled “Control System Arrangements and
`Methods for Disparate Network Systems' to Dickelman,
`Mark and filed on Nov.30, 2007, which is fully incorporated
`herein by reference as describing and illustrating Subject mat
`ter (in part(s) or in its entirety) that can be practiced with the
`subject matter disclosed herein.
`
`10
`
`15
`
`FIELD OF THE INVENTION
`
`This invention relates generally to computer-automated
`devices, systems and methods, and as an example, to systems
`and methods for automated computer systems and networks
`implemented as may be foundina control center of a financial
`institution.
`
`BACKGROUND
`
`Computer systems and networks that process data in con
`trol centers for financial institutions have struggled to keep up
`with the ever increasingly complex and expanding variety of
`electronic transaction and accounting data, particularly as
`more and more transactions are carried out using electronic
`payment, which is often a credit-based payment. Electronic
`data used in effecting payment relates and leads up to imple
`mentations of payment systems and associated payment net
`works, which generally employ proprietary-type processing
`functions and require relatively complex interactivity with
`electronic systems operated by entities for which payment is
`processed (e.g., merchant point-of-sale (POS) devices).
`These systems have often been susceptible to issues of com
`patibility and complex negotiations required for any integra
`tion and cross-network use.
`Generally, associated payment networks involve two pri
`mary components. The first component is a seller or merchant
`access network (e.g., Elavon R.) that provides connection to
`the POS devices (e.g., directly or via merchant internal net
`works) and identification of the type of payment account
`(e.g., Visa R or VoyagerR). A second component includes
`payment processing networks that process payment instruc
`tions based on established agreements by parties participating
`in the processing of payment. Generally, these payment pro
`cessing networks are one of two different categories, propri
`etary networks (e.g., Voyager(R) or association networks.
`Examples of association networks include the networks pro
`vided by VISAR) and MASTERCARDR) and/or the particular
`acquiring/issuing banks. For a particular transaction, the
`operator of the association network controls the flow of funds
`for the transaction. Often, this includes a fee that is passed on
`to the seller, Such as a percentage of the transaction. The
`participating sellers have an agreement with the network
`(e.g., VISA or MASTERCARD), but do not have a transac
`tional relationship between one another with respect to the
`association network transactions.
`These types of transactions have generally been imple
`mented by sellers having an existing relationship with a par
`ticular bank, and often involve the use of a transaction card or
`corresponding account involving one or more of a credit or
`debit type of account structure. When a purchase is made, the
`seller sends transaction information to the bank, which is
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`Sometimes referred to as the acquiring bank. The acquiring
`bank can forward payment information to another bank that
`issued the buyer's account (e.g., a credit card issuer), which is
`often referred to as an issuing bank. In many instances, pay
`ment processing networks assign interchange fees for these
`types of transactions. These fees are paid between the parties
`based on the type of transaction, authentication and location,
`and may be passed on to the seller.
`An example proprietary network involves a merchant-pro
`vided in-store credit or debit account (e.g., an account pro
`vided by Target Corporation for use in purchasing goods from
`a store operated thereby). A seller or a seller-contracted third
`party facilitates the settlement, authorization and/or other
`functions associated with transactions involving the in-store
`account. In some instances, sellers form bilateral agreements
`with other sellers to allow use of a network by multiple sellers
`and/or to coordinate the use of multiple networks between
`multiple sellers. For instance, two department stores may
`forman agreement to allow the use of a common proprietary
`network card/account at either store, or they may allow use of
`two different proprietary network cards/accounts (i.e., one
`from each store) at either store.
`A few networks are operated to allow a single (multi
`purpose) card (e.g., a physical transaction card with data
`thereon, or a corresponding account) to provide access to
`more than one related credit and/or debit type of account. The
`card interfaces with a network that would otherwise support
`one or more of the accounts, and a user of the card (card
`holder) can designate a desired one of the accounts to use.
`However, the buyer must still carry the multi-purpose card for
`use and can only use the multi-purpose card at locations that
`Support that particular card, and the transactions are generally
`processed using the selected account and its related propri
`etary-type of payment network.
`In this complex and ever expanding background of various
`payment networks, consumers have an increasing number of
`accounts from which they can access funds for purchases
`(e.g., credit, debit, insurance, health-savings accounts, money
`markets, investment and retirement). These accounts can vary
`with respect to their respective fees, tax implications, interest
`rates, limitations on withdraw amounts and a number of other
`properties. Often the consumer is forced to spend consider
`able time and effort to manage such accounts and associated
`transactions. For example, considerable time and effort can
`be expended in determining how to best apply specific trans
`actions and/or purchased items to the various accounts. In
`Some instances, the actual implementation of such a determi
`nation can be just as difficult.
`Another challenge to the implementation and management
`of transaction processing systems and, to some degree, mer
`chant-specific types of accounts relates to the lack of Volume
`of buyers (and/or sellers) that may be associated with the
`systems and accounts. For instance, relatively small mer
`chants may find it difficult to promote and operate a transac
`tion account and related system where the Volume of users is
`relatively low.
`The above and other matters remain challenging to the
`implementation, operation and Sustained growth of card and
`related types of accounts, and the electronic transactions and
`interactions related to the same.
`
`SUMMARY
`
`The present invention is exemplified in a number of
`embodiments, implementations and applications, some of
`which are summarized below.
`
`APPL-1019 / IPR2022-00976 / Page 9 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`US 9,147,184 B2
`
`3
`According to an example embodiment, a computer circuit
`arrangement facilitates electronic payment between disparate
`autonomous payment networks respectively having network
`specific payment processing protocols. The circuit arrange
`ment includes a point-of-sale interface circuit, a plurality of 5
`payment network interface modules, and a control processor
`circuit. The point-of-sale interface circuit receives, for each
`transaction, electronic point-of-sale transaction data from a
`remote point-of-sale device. Each of the plurality of payment
`network interface modules electronically communicates with
`an associated payment network using protocols specific to the
`associated payment network to which communications are
`sent. The control processor circuit carries out the following,
`for each transaction and point-of-sale transaction data
`received therefor. The point-of-sale transaction data is used to
`identify participant ID data for at least one participant in the
`transaction. Business rules data electronically associated
`with the participant ID data is retrieved and used to select one
`of the payment network interface modules to process elec
`tronic payment for the transaction. The selected payment
`network interface module is controlled to electronically com
`municate payment data for the transaction data to the mod
`ules associated payment network, using protocols specific to
`the associated payment network, to facilitate payment for the
`transaction.
`According to another example embodiment, a software
`programmed circuit arrangement is configured for use in a
`system that facilitates payment between users of the system,
`the users including sellers providing goods or services to
`buyers paying for the goods or services, the payment being
`provided between disparate, autonomous payment networks
`of the buyers and sellers. The circuit arrangement includes an
`input to receive, for a particular transaction, transaction data
`from at least one of a routing network for a point-of-sale
`device at which transaction data is input, a buyer payment
`network and a seller payment network that is disparate from
`the buyer payment network. The circuit arrangement also
`includes a control processor to perform one of auditing, fee
`calculation and fraud monitoring of the transaction for trans
`action data received from at least one of the disparate pay
`ment networks.
`Another example embodiment is directed to a processor
`readable storage medium having stored thereon instructions
`45
`for performing the aforesaid steps to facilitate electronic pay
`ment between disparate autonomous payment networks
`respectively having network-specific payment processing
`protocols.
`The above summary is not intended to describe each illus
`trated embodiment or every implementation of the present
`invention.
`
`4
`FIG. 3 shows a data flow diagram for network selection,
`according to an example embodiment of the present inven
`tion;
`FIG. 4 shows an electronic buyer-seller interface system,
`according to another example embodiment of the present
`invention; and
`FIG. 5 shows another buyer-seller interface system,
`according to another example embodiment of the present
`invention.
`While the invention is amenable to various modifications
`and alternative forms, specifics thereof have been shown by
`way of example in the drawings and will be described in
`detail. It should be understood, however, that the intention is
`not to limit the invention to the particular embodiments
`described. On the contrary, the intention is to cover all modi
`fications, equivalents, and alternatives falling within the spirit
`and scope of the invention.
`
`DETAILED DESCRIPTION
`
`The present invention is believed to be applicable to a
`variety of different types of transaction processing systems
`and related integrated communications, management control,
`and has been found to be particularly useful for applications
`involving disparate, autonomous payment networks. While
`the present invention is not necessarily limited to Such
`approaches, various aspects of the invention may be appreci
`ated through a discussion of various examples using these and
`other contexts.
`A number of different embodiments of the present inven
`tion are directed to one or more of the components and meth
`ods described, in this document, in connection with disparate
`payment systems. A discussion of the overall system func
`tionality can be useful in understanding the individual com
`ponents and methods.
`Consistent with an example embodiment of the present
`invention, an approach to processing payment involves con
`trolling interactions between disparate, autonomous payment
`processing networks to process different payment aspects for
`a common set of transaction data received for a particular
`transaction. For instance, when a merchant (i.e., seller) trans
`mits point-of-sale purchase data including a transaction
`amount and buyer's account data (e.g., obtained from a
`credit-type or debit-type card or related account number asso
`ciated therewith), an integrated processor receives the point
`of-sale data and coordinates electronic funds transfers with
`two or more of the autonomous networks. In this context, a
`single card or account can be used as a manner in which to
`access a plurality of payment networks, and payment for a
`common transaction can be effected using disparate, autono
`mous networks that, absent the integrated processor, would
`not otherwise be capable of communicating with one another.
`In many aspects, such an approach involves interacting with
`payment networks configured and operated for operating
`independently, to respectively provide payment to a merchant
`and effect settlement from a buyer, with these functions now
`carried out via the integrated processor.
`These payment processing approaches are amenable to use
`in processing payment using a multitude of different payment
`approaches and scenarios involving one or more accounts and
`participating networks for buyers, merchants or other trans
`action participants. For example, some embodiments are
`directed to providing payment from a buyer using a first
`payment processing network (e.g., a Elavon R and/or VISAR)
`network as described above) to obtain account information
`for the buyer, and providing settlement to a merchant using a
`different account (and its related payment network) for the
`
`10
`
`15
`
`25
`
`30
`
`35
`
`40
`
`50
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The invention may be more completely understood in con
`sideration of the detailed description of various embodiments
`of the invention that follows in connection with the accom
`panying drawings, in which:
`FIG. 1A shows a system for implementing a transaction
`using disparate seller and buyer networks, according to an
`example embodiment of the present invention;
`FIG. 1B shows a system for implementing a transaction
`using disparate seller and buyer networks, according to
`another example embodiment of the present invention;
`FIG. 2 shows a block diagram for a system, according to
`another example embodiment of the present invention;
`
`55
`
`60
`
`65
`
`APPL-1019 / IPR2022-00976 / Page 10 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`5
`buyer. Other embodiments are directed to using different
`accounts and related payment networks for effecting payment
`and for providing settlement for the buyer. Other embodi
`ments are directed to using different accounts and related
`payment networks for collecting an initial pre-payment (e.g.,
`an immediate payment from a third party) for collecting Sub
`sequent payment from the buyer and, where appropriate, for
`providing settlement for the pre-payment. Still other embodi
`ments are directed to providing payment from a buyer using
`an account for the buyer and its related payment processing
`network, and providing electronic funds from the payment to
`a merchant account that uses a different payment network.
`Other combinations of networks are also used in connection
`with various embodiments.
`As should be appreciated, the central/integrated processor
`can thus coordinate interactions between a multitude of dif
`ferent accounts and different payment networks, and can do
`so using a single account for a particular transaction partici
`pant in order to access other accounts for the participant. For
`instance in transaction involving the sale of goods or services
`from a seller to a buyer, a payment network can be selected for
`the buyer that is disparate from the payment network used by
`seller by using a standardized card or a proprietary network,
`or other buyer identification sufficient upon which to autho
`rize payment. This can be useful for allowing a buyer to use a
`standardized card and a seller having only access to (or pre
`ferring the use of) a proprietary network. Payment authoriza
`tion may involve an audit, which may include comparing data
`from one or more of a buyer-based audit, seller-based auditor
`an audit based upon a third party operating the central/inte
`grated processor. The results of the audit can be provided to
`the selected networks and used, for example as indication that
`the transaction can go forward (e.g., validation regarding the
`transaction amount and Source).
`Payment accounts and related networks are selected using
`one or more of a variety of approaches. In some embodi
`ments, user profiles with any appropriate rules are stored and
`used to identify and select an available account for effecting
`payment for a transaction. These profiles (and rules) can be
`stored for buyers and, as appropriate, sellers. In some appli
`cations, an account and related payment network is selected
`automatically using profiles and related rules. In other
`instances, user input is obtained in order to select a payment
`account, to allow a buyer and/or seller to directly select and
`control the use of a particular payment account. In all of these
`instances, parties to a particular transaction need not have
`direct knowledge of account and related payment network for
`other parties to the transaction, and further do not need to
`participate in any agreement with a payment network used by
`anotherparty. In addition, Such approaches may be carried out
`using a processor (e.g., a computer) that uses profiles, rules
`and transaction information to selecting, routing and other
`wise implementing associated accounts and related payment
`networks.
`While not necessarily limited thereto, various embodi
`ments are directed to the implementation of processor
`arrangements and systems, consistent with discussion herein,
`at financial institutions such as banking institutions that are
`well Suited for making use of network and account access. For
`instance, banking institutions have many existing interfaces
`to payment networks, and many payment networks are linked
`to accounts held at a banking institution. The payment net
`works operate by transferring money to and from these
`accounts, thereby completing transactions. Other payment
`networks use local banking institutions as intermediaries to
`transfer funds. The use of a bank can beneficial for a number
`of reasons including, but not limited to, secured transactions,
`
`10
`
`15
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 9,147,184 B2
`
`6
`federal insurance and relative stability; however, disparate
`payment networks do not have automated mechanisms to
`transfer funds therebetween.
`Aspects of the present invention, when implemented by a
`banking institution, can provide automated access between
`Such networks. In some instances, the transactions can be
`implemented with the transaction details being transparent to
`the payment networks and/or the individual participants. For
`example, an individual participant could identify a desired
`payment network to use without requiring that a front-end
`payment network (e.g., the payment network associated with
`the POS transaction) have a pre-existing bilateral agreement
`with a desired payment network. A specific example of Such
`an instance involves a buyer's use of a credit card to imple
`ment a POS transaction. Consistent with one implementation
`of the present invention, credit card transaction data is
`received by a banking institution, which can use a payment
`routing network to select a payment network, other than a
`payment network associated with the credit card, to complete
`the transaction. Accordingly, the aspects of the present inven
`tion can be particularly useful for providing a centralized
`routing system that operates using existing autonomous and
`disparate payment networks. Moreover, these approaches
`may be carried out using an identification of a user, be that
`based upon a particular payment account (e.g., a credit card)
`or based upon another form of identification (e.g., a mobile
`phone account or a state-issued identification card (e.g., driv
`er's license), where payment is carried out using a wholly
`different payment account. That is, once a buyer is identified
`into the system, using one or more of a multitude of identifi
`cation approaches, payment accounts and networks can be
`selected and implemented independent from any manner in
`which that buyer is identified. Seller accounts and networks
`can be similarly selected.
`Turning now to the figures, FIG. 1A shows a system 100 for
`processing transactions using disparate payment processing
`networks, according to various example embodiments of the
`present invention. The system 100 can be operated in accor
`dance with one or more of the above-discussed electronic
`payment and transaction processing systems and approaches,
`as well as those discussed in connection with the figures and
`those claimed. In these contexts, disparate buyer and seller
`networks may involve networks operating on different
`accounts that are not recognized or otherwise accessible by
`other respective buyer and/or seller networks that operate
`with the system 100, and can be respectively used in process
`ing electronic payment for a transaction using two or more of
`the disparate networks.
`When electronic transaction information is received (e.g.,
`from a merchant's point-of-sale device), the system 100 iden
`tifies the buyer in the transaction and determines whether
`payment for a transaction is appropriate using a set of rules
`embodied and processed in a financial control system 116.
`For instance, when a buyer wishes to purchase goods and
`services from a seller (merchant), the buyer can provide
`account information Such as a credit card number to a the
`seller either physically (i.e., at a store) or electronically when
`purchasing over the Internet. This information is captured
`together with sufficient information to identify transaction
`aspects (e.g., an amount), and is provided to the system 100,
`which uses the information to approve and otherwise process
`the payment for the transaction in accordance with the buy
`er's account rules.
`A buyer/seller transaction capture interface 109 captures
`data for transactions between buyers and sellers using, for
`example, a network-based interface (e.g., operating over the
`Internet) and/or a merchant/seller point-of-sale device that
`
`APPL-1019 / IPR2022-00976 / Page 11 of 19
`APPLE INC. v. FINTIV, INC.
`
`

`

`US 9,147,184 B2
`
`7
`captures account information from a buyer (e.g., using an
`identification card, credit card or debit card). Where a point
`of-sale device is used to interact with a buyer, the interaction
`may simply involve allowing the buyer's card to be Swiped, or
`involve a more complex acquisition of other inputs or selec
`tions from the buyer. Numerous other interfaces can also be
`implemented in accordance with these embodiments, with
`Some of these interfaces and related approaches discussed in
`further detail herein.
`The data captured by the interface 109 varies depending
`upon the application, and generally includes data pertinent to
`effecting payment for a transaction, such as identification for
`a buyer and a seller (and/or their respective accounts), as well
`as a transaction amount for payment. Where appropriate,
`other transaction data such as time-stamps, transaction type
`(e.g., Internet purchase, storefront purchase, utility payments
`or gasoline purchases), a type of goods or services sold, or
`security information is also captured. Exemplary types of
`security information that may be provided with the transac
`tion data include personal pin numbers, biometric data, pass
`words, social security numbers and interactive authentication
`data received via an external communication device Such as
`via email or a cellular phone.
`An account selection processor 150 uses the captured data
`together with profiles and business rules to select buyer and
`seller account/payment systems and input the selections to
`system selection processors 112 and 113, via inputs 114 and
`115. The system selection processors 112 and 113 respond to
`the inputs by respectively selecting buyer and seller account
`processors 160 and 170, which each respectively interact with
`an autonomous payment network. The buyer and seller
`account processors 160 and 170 respectively interact with
`payment networks for the particular account for which trans
`actions are processed to process payment from a buyer and
`provide funds to a seller, less any associated transaction fees.
`Fee calculation and/or collection may involve, for example,
`applying standard network fees (e.g., credit card basis points,
`cost-per-use fee, interest and/or float costs), System imple
`menter cost and associated fees, and fees corresponding to
`write-offs (e.g., due to disputes and underwriting).
`Each of the account selection, system selection and buyer/
`seller account p