(12) United States Patent
`Liberty et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 9,189,785 B2
`Nov. 17, 2015
`
`US009 189785B2
`
`(54) DEBITNETWORK ROUTING SELECTION
`USING ASCANNABLE CODE
`
`(71) Applicants: Michael A. Liberty, Windermere, FL
`(US); Steve Bacastow, Cumming, GA
`(US)
`(72) Inventors: Michael A. Liberty, Windermere, FL
`(US); Steve Bacastow, Cumming, GA
`(US)
`(73) Assignee: Mozido, Inc., Austin, TX (US)
`(*) Notice:
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`(21) Appl. No.: 13/974,375
`(22) Filed:
`Aug. 23, 2013
`
`(65)
`
`Prior Publication Data
`US 2014/OO54369 A1
`Feb. 27, 2014
`
`Related U.S. Application Data
`(60) Provisional application No. 61/704,337, filed on Sep.
`21, 2012, provisional application No. 61/693,055,
`filed on Aug. 24, 2012.
`(51) Int. Cl.
`G06K 19/00
`G06K 5/00
`G06O40/00
`G06O20/26
`G06O20/32
`(52) U.S. Cl.
`CPC ............ G06O20/26 (2013.01); G06O20/3274
`(2013.01)
`
`(2006.01)
`(2006.01)
`(2012.01)
`(2012.01)
`(2012.01)
`
`(58) Field of Classification Search
`CPC ..... G06Q 40/00: G06Q 20/26: G06Q 20/227;
`G06Q 20/354; G06Q 30/06; G06Q 30/02:
`G06Q 20/12: G06Q 20/204: G06Q 20/20;
`G06Q 20/36; G06Q 30/0601; G06Q 20/387:
`
`G06Q 30/0641; G06Q 20/351; G06Q 20/40:
`GO6K 197083
`See application file for complete search history.
`References Cited
`
`(56)
`
`U.S. PATENT DOCUMENTS
`
`2/2013 Laracey
`8,380,177 B2
`8,639,621 B1* 1/2014 Ellis et al. ....................... TO5/41
`2005/0027648 A1
`2/2005 Knowles et al.
`2005, 0125343 A1* 6/2005 Mendelovich ......... G06Q 20/04
`705/39
`
`(Continued)
`
`FOREIGN PATENT DOCUMENTS
`
`WO
`WO
`
`11, 2012
`2012.158133
`6, 2014
`2014O93943
`OTHER PUBLICATIONS
`
`International Search Report and Written Opinion of PCT/US 13/
`75199 dated Apr. 29, 2014.
`(Continued)
`Primary Examiner — Thien T Mai
`(74) Attorney, Agent, or Firm — Workman Nydegger
`(57)
`ABSTRACT
`Embodiments are directed to selecting a debit network using
`a quick response (QR) code and to processing a payment
`using a debit network selected according to information
`embedded in a QR code. In one scenario, a mobile computer
`system receives input indicating that a user has initiated a
`payment for various items sold by a provider of goods or
`services. The mobile computer system determines that the
`user or the provider has specified a preference indicating
`which debit network is to be used to process the payment. The
`mobile computer system then generates a QR code with the
`debit network selection and portions of the user's debit
`account information embedded in the QR code, and sends the
`generated QR code to a payment processing system. The
`payment processing system may be cloud-based, or may be
`run locally at the provider's point of sale.
`21 Claims, 5 Drawing Sheets
`
`200-
`\
`
`User
`205
`
`Mobile Computer System 20
`
`
`
`2f
`
`211
`
`212
`
`23
`
`214
`
`Mobile Wallet Application
`
`User Demographic
`information
`
`User Payment Preferences
`
`User Purchasing History
`
`Retailer's Debit
`Network Preferences
`
`Determining Module
`
`QR Code Generating Module
`
`
`
`24
`7
`Retailer's Debit
`Nstworks Preferences
`
`Retail location 225
`226
`
`Point Of Sale
`
`22
`Checkout Register
`
`W
`
`228
`
`Retaillems
`
`- - - - - - - - - -
`
`230
`
`Ex.1001
`APPLE INC. / Page 1 of 14
`
`

`

`US 9,189,785 B2
`Page 2
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`2006/0208065 A1
`
`9, 2006 Mendelovich ......... G06Q 20/04
`235,380
`
`3/2007 Arseneau et al.
`2007/0058041 A1
`4/2007 Vaughn et al.
`2007/0088624 A1
`6, 2007 Walker et al.
`2007. O13001.6 A1
`7/2008 Deibert et al.
`2008/O1723.17 A1
`9/2008 Higgins et al.
`2008/0222048 A1
`3988:
`A. 858 E.
`2010/005 1685 A1* 3/2010 Royyuru et al. .............. 235,379
`2010/028283.6 A1 1 1/2010 Kempfet al.
`2012fOO78673 A1
`3/2012 Koke et al.
`2012/0085829 A1
`4/2012 Ziegler
`
`2012/0209749 A1* 8, 2012 Hammad et al. ............. 705/27.1
`2012fO267432 A1 10, 2012 Kuttuva
`2012/0290421 A1 1 1/2012 Qawami et al.
`2013/022861.6 A1* 9, 2013 Bhosle et al. ................. 235,375
`2014/0058834 A1
`2/2014 Liberty et al.
`2014/0172531 A1
`6/2014 Liberty et al.
`
`OTHER PUBLICATIONS
`
`International Search Report for PCT/US 11/00855 dated Nov. 9,
`2011.
`Gao et al. "A 2-D Barcode-Based Mobile Payment System.” In. MUE
`'09 Third International Conference on Multimedia and Ubiquitous
`Engineering, 2009, pp. 320-329.
`* cited by examiner
`
`Ex.1001
`APPLE INC. / Page 2 of 14
`
`

`

`U.S. Patent
`U.S. Patent
`
`Nov. 17, 2015
`
`Sheet 1 of 5
`
`US 9,189,785 B2
`US 9,189,785 B2
`
`
`
`S}eM SOW
`
`ELLswaysAyedpe
`
`(IGeqAIPAD)Md
`quawAeg
`
`dndo| ewiniy
`
`(Alesi4 9 Jaq)
`quawced |IId
`
`(waysAg Buyig)
`ONAW / ON
`
`(leA yedAouoy)
`JOqUaa
`
`(Jeye/duooueg)
`
`(don 8 Sad)
`JOSS890/d ‘XJ
`
`(nM 8 IDW)
`SsoUenIWIAY
`
`
`
`Ja|pueyjuuswAed
`
`GOL
`
`
`
`BuueaBGuea|9OLL
`
`euibuy
`
`JOSSaI0Id
`
`
`
`LebaueN
`
`
`
`
`
`EQ}.suojeuuogaaimeg
`
`
`
`(yoieg)(ongqa)
`
`
`
`
`
`asnoyasnoy_
`
`Aueqyoelg aINjoayyouy
`
`JeUOOUNWOE}4
`
`
`
`
`
`——Bulyojeyy
`
`60Lauibuysainy
`Zhpsuoneouon
`ZOLsania
`UOHEDYHON
`bOl
`
`
`rolS801AI9S8899014SSSUISNG
`
`LLLhI
`
`saoueguonezZWOYINY
`
`LO|29ULuonesBayu
`
`SOLjpeseqeieg90OLsaoiaagAqunaag
`
`JeuleyoD
`AQuol|
`
`s1alqo
`[Old
`
`AJOSH XL
`AJOJSIH XL
`
`wo
`Auedwo5
`wo
`uossed
`
`LOL
`
`Ex.1001
`APPLEINC./ Page 3 of 14
`
`Ex.1001
`APPLE INC. / Page 3 of 14
`
`

`

`U.S. Patent
`
`Nov. 17, 2015
`
`Sheet 2 of 5
`
`US 9,189,785 B2
`
`LeeLL|
`
`
`
`
`
`
`
`uoleo07|Ie}ay199SJele}oyp02922ddSODUAIBJAgSYIOMONUO!JEOI|AAyYJSI|EAA[1QO/\\fGez
`
`
`
`
`
`
`
`
`
`
`
`
`
`uojoesuel|}igequoljoesuel|jigeqainpow-Buluiwwajaq
`
`
`
`
`
`
`
`
`
`JONSON(1e}5“B'2)yYJONjaN
`
`c‘9
`
`
`
`
`
`ainpoywBuyjesauayapo9YH
`
`
`
`SWS}[IP}Oy
`
`alesJOJulod
`
`
`
`Cca1ydesbowagJasn
`
` ,Ja\sifiayinoyoaG0¢
`
`
`
`
`
`
`ReednopeyoUOULUOJU|Jasn
`
`
`
`
`
`SEOUala}el4JUBWARYJaf)
`
`
`
`
`
`AsojsiqBuiseyoungJas)
`
`
`
`{g8qSJaIIejoY
`
`
`
`SOOUIOJAI4OMJON
`
`Ex.1001
`APPLEINC./ Page 4 of 14
`
`
`
`
`
`10zwashsJejndwo4siqoyy
`
`Ex.1001
`APPLE INC. / Page 4 of 14
`
`
`
`

`

`U.S. Patent
`
`Nov. 17, 2015
`
`Sheet 3 of 5
`
`US 9,189,785 B2
`
`300
`
`
`
`Receive input indicating That User Has
`Initiated A Payment
`
`Determine That User And/Or Provider HaS
`Specified Debit Network Preference
`
`Generate QR COde With Embedded Debit NetWOrk
`Selection User Debit ACCOUnt Information
`
`Send Generated QR Code To Payment
`Processing System
`
`310
`
`320
`
`330
`
`340
`
`FIG. 3
`
`Ex.1001
`APPLE INC. / Page 5 of 14
`
`

`

`U.S. Patent
`
`Nov. 17, 2015
`
`Sheet 4 of 5
`
`US 9,189,785 B2
`
`
`
`Receive QR COde With Embedded
`Payment Information
`
`Determine Which Debit NetWOrk To Use TO
`Process Payment
`
`Send Payment Amount And User's Debit ACCount
`Information To Determined Debit Network
`
`Receive indication That Payment Was
`Processed By Determined Debit Network
`
`410
`
`420
`
`430
`
`440
`
`FIG. 4
`
`Ex.1001
`APPLE INC. / Page 6 of 14
`
`

`

`U.S. Patent
`
`Nov. 17, 2015
`
`Sheet 5 of 5
`
`US 9,189,785 B2
`
`
`
`QR Code 501
`
`Embedded Information
`
`502
`
`User's Preferred Debit
`NetWOrk
`
`Provider's Preferred
`Debit NetWOrk
`
`Total Payment
`AmOUnt
`
`GOOds Or Services
`Being Purchased
`
`USer's Debit
`ACCOUnt Information
`
`USer's Purchase
`History
`
`Rewards
`
`Selected NetWOrk
`
`FIG. 5
`
`Ex.1001
`APPLE INC. / Page 7 of 14
`
`

`

`US 9,189,785 B2
`
`1.
`DEBITNETWORK ROUTING SELECTION
`USING ASCANNABLE CODE
`
`CROSS REFERENCE TO RELATED
`APPLICATIONS
`
`This application claims priority to and the benefit of U.S.
`Provisional Application Ser. No. 61/704,337, entitled “Debit
`Network Routing Selection Using a QR Code, filed on Sep.
`21, 2012. This application also claims priority to and the
`benefit of U.S. Provisional Application Ser. No. 61/693,055,
`entitled “Debit Network Routing Selection Using a QR
`Code', filed on Aug. 24, 2012. Both of these applications are
`incorporated by reference herein in their entirety.
`
`10
`
`15
`
`2
`This Summary is provided to introduce a selection of con
`cepts in a simplified form that are further described below in
`the Detailed Description. This Summary is not intended to
`identify key features or essential features of the claimed sub
`5 ject matter, nor is it intended to be used as an aid in determin
`ing the scope of the claimed Subject matter.
`Additional features and advantages will be set forth in the
`description which follows, and in part will be apparent to one
`of ordinary skill in the art from the description, or may be
`learned by the practice of the teachings herein. Features and
`advantages of embodiments described herein may be realized
`and obtained by means of the instruments and combinations
`particularly pointed out in the appended claims. Features of
`the embodiments described herein will become more fully
`apparent from the following description and appended
`claims.
`
`BACKGROUND
`
`Computers have become highly integrated in the work
`force, in the home, in mobile devices, and many other places.
`Computers can process massive amounts of information
`quickly and efficiently. Software applications designed to run
`on computer systems allow users to perform a wide variety of
`functions including business applications, Schoolwork, enter
`tainment and more. Software applications are often designed
`to perform specific tasks, such as word processor applications
`for drafting documents, or email programs for sending,
`receiving and organizing email.
`Today's Smartphones use Software applications to perform
`a wide variety of functionality. In some cases, this function
`ality may include the ability to pay for items using a mobile
`payment system. Such a mobile payment system may allow
`users to pay for items at a store or over the internet using their
`phone.
`
`BRIEF SUMMARY
`
`25
`
`30
`
`35
`
`40
`
`Embodiments described herein are directed to selecting a
`debit network using a quick response (QR) code and to pro
`cessing a payment using a debit network selected according to
`information embedded in a QR code. In one embodiment, a
`mobile computer system receives input indicating that a user
`has initiated a payment for various items sold by a provider of
`goods or services. The mobile computer system determines
`that the user or the provider has specified a preference indi
`cating which debit network is to be used to process the pay
`45
`ment. The mobile computer system then generates a QR code
`with the debit network selection and portions of the user's
`debit account information embedded in the QR code, and
`sends the generated QR code to a payment processing system.
`The payment processing system may be cloud-based, or may
`be run locally at the provider's point of sale.
`In another embodiment, a computer system processes a
`payment using a debit network selected according to infor
`mation embedded in a QR code. The computer system
`receives a QR code that includes portions of embedded pay
`ment information. The embedded payment information
`includes at least the following: a total payment amount that is
`to be paid by a user, debit account information for the user,
`and an indication of which debit network is to be used to
`process the payment. The computer system determines which
`debit network is to be used to process the payment based on
`the indication provided in the embedded payment informa
`tion in the received QR code, sends the payment amount and
`the user's debit account information to the determined debit
`network and, after the payment has been processed, receives
`an indication that the payment was processed by the deter
`mined debit network.
`
`50
`
`55
`
`60
`
`65
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`To further clarify the above and other features of the
`embodiments described herein, a more particular description
`will be rendered by reference to the appended drawings. It is
`appreciated that these drawings depict only examples of the
`embodiments described herein and are therefore not to be
`considered limiting of its scope. The embodiments will be
`described and explained with additional specificity and detail
`through the use of the accompanying drawings in which:
`FIG. 1 illustrates a computer platform architecture for pro
`viding mobile wallet and payment processing services.
`FIG. 2 illustrates an embodiment in which a debit network
`is selected for performing a debit transaction.
`FIG. 3 illustrates a flowchart of an example method for
`selecting a debit network using a QR code.
`FIG. 4 illustrates a flowchart of an example method for
`processing a payment using a debit network selected accord
`ing to information embedded in a QR code.
`FIG. 5 illustrates a QR code with multiple portions of
`embedded information.
`
`DETAILED DESCRIPTION
`
`Embodiments described herein are directed to selecting a
`debit network using a quick response (QR) code and to pro
`cessing a payment using a debit network selected according to
`information embedded in a QR code. In one embodiment, a
`mobile computer system receives input indicating that a user
`has initiated a payment for various items sold by a provider of
`goods or services. The mobile computer system determines
`that the user or the provider has specified a preference indi
`cating which debit network is to be used to process the pay
`ment. The mobile computer system then generates a QR code
`with the debit network selection and portions of the user's
`debit account information embedded in the QR code, and
`sends the generated QR code to a payment processing system.
`The payment processing system may be cloud-based, or may
`be run locally at the provider's point of sale.
`In another embodiment, a computer system processes a
`payment using a debit network selected according to infor
`mation embedded in a QR code. The computer system
`receives a QR code that includes portions of embedded pay
`ment information. The embedded payment information
`includes at least the following: a total payment amount that is
`to be paid by a user, debit account information for the user,
`and an indication of which debit network is to be used to
`process the payment. The computer system determines which
`debit network is to be used to process the payment based on
`the indication provided in the embedded payment informa
`
`Ex.1001
`APPLE INC. / Page 8 of 14
`
`

`

`US 9,189,785 B2
`
`10
`
`15
`
`3
`tion in the received QR code, sends the payment amount and
`the user's debit account information to the determined debit
`network and, after the payment has been processed, receives
`an indication that the payment was processed by the deter
`mined debit network.
`The following discussion now refers to a number of meth
`ods and method acts that may be performed. It should be
`noted, that although the method acts may be discussed in a
`certain order or illustrated in a flow chart as occurring in a
`particular order, no particular ordering is necessarily required
`unless specifically stated, or required because an act is depen
`dent on another act being completed prior to the act being
`performed.
`Embodiments of the present invention may comprise or
`utilize a special-purpose or general-purpose computer system
`that includes computer hardware. Such as, for example, one or
`more processors and system memory, as discussed in greater
`detail below. Embodiments within the scope of the present
`invention also include physical and other computer-readable
`media for carrying or storing computer-executable instruc
`tions and/or data structures. Such computer-readable media
`can be any available media that can be accessed by a general
`purpose or special-purpose computer system. Computer
`readable media that store computer-executable instructions
`25
`and/or data structures are computer storage media. Com
`puter-readable media that carry computer-executable instruc
`tions and/or data structures are transmission media. Thus, by
`way of example, and not limitation, embodiments of the
`invention can comprise at least two distinctly different kinds
`of computer-readable media: computer storage media and
`transmission media.
`Computer storage media are physical storage media that
`store computer-executable instructions and/or data struc
`tures. Physical storage media include computer hardware,
`such as RAM, ROM, EEPROM, solid state drives (“SSDs),
`flash memory, phase-change memory (PCM), optical disk
`storage, magnetic disk storage or other magnetic storage
`devices, or any otherhardware storage device(s) which can be
`used to store program code in the form of computer-execut
`able instructions or data structures, which can be accessed
`and executed by a general-purpose or special-purpose com
`puter system to implement the functionality disclosed herein.
`Transmission media can include a network and/or data
`links which can be used to carry program code in the form of
`45
`computer-executable instructions or data structures, and
`which can be accessed by a general-purpose or special-pur
`pose computer system. A "network” is defined as one or more
`data links that enable the transport of electronic data between
`computer systems and/or modules and/or other electronic
`devices. When information is transferred or provided over a
`network or another communications connection (eitherhard
`wired, wireless, or a combination of hardwired or wireless) to
`a computer system, the computer system may view the con
`nection as transmission media. Combinations of the above
`should also be included within the scope of computer-read
`able media.
`Further, upon reaching various computer system compo
`nents, program code in the form of computer-executable
`instructions or data structures can be transferred automati
`cally from transmission media to computer storage media (or
`Vice versa). For example, computer-executable instructions
`or data structures received over a network or data link can be
`buffered in RAM within a network interface module (e.g., a
`“NIC), and then eventually transferred to computer system
`RAM and/or to less volatile computer storage media at a
`computer system. Thus, it should be understood that com
`
`55
`
`4
`puter storage media can be included in computer system
`components that also (or even primarily) utilize transmission
`media.
`Computer-executable instructions comprise, for example,
`instructions and data which, when executed at one or more
`processors, cause a general-purpose computer system, spe
`cial-purpose computer system, or special-purpose processing
`device to perform a certain function or group of functions.
`Computer-executable instructions may be, for example, bina
`ries, intermediate format instructions such as assembly lan
`guage, or even Source code.
`Those skilled in the art will appreciate that the invention
`may be practiced in network computing environments with
`many types of computer system configurations, including,
`personal computers, desktop computers, laptop computers,
`message processors, hand-held devices, multi-processor sys
`tems, microprocessor-based or programmable consumer
`electronics, network PCs, minicomputers, mainframe com
`puters, mobile telephones, PDAs, tablets, pagers, routers,
`Switches, and the like. The invention may also be practiced in
`distributed system environments where local and remote
`computer systems, which are linked (either by hardwired data
`links, wireless data links, or by a combination of hardwired
`and wireless data links) through a network, both perform
`tasks. As such, in a distributed system environment, a com
`puter system may include a plurality of constituent computer
`systems. In a distributed system environment, program mod
`ules may be located in both local and remote memory storage
`devices.
`In this description and the following claims, "cloud com
`puting is defined as a model for enabling on-demand net
`work access to a shared pool of configurable computing
`resources (e.g., networks, servers, storage, applications, and
`services). The definition of "cloud computing is not limited
`to any of the other numerous advantages that can be obtained
`from Such a model when properly deployed.
`For instance, cloud computing is currently employed in the
`marketplace so as to offer ubiquitous and convenient on
`demand access to the shared pool of configurable computing
`resources. Furthermore, the shared pool of configurable com
`puting resources can be rapidly provisioned via virtualization
`and released with low management effort or service provider
`interaction, and then scaled accordingly.
`A cloud computing model can be composed of various
`characteristics such as on-demand self-service, broad net
`work access, resource pooling, rapid elasticity, measured Ser
`vice, and so forth. A cloud computing model may also come
`in the form of various service models such as, for example,
`Software as a Service (“SaaS), Platform as a Service
`(“PaaS), and Infrastructure as a Service (IaaS). The cloud
`computing model may also be deployed using different
`deployment models such as private cloud, community cloud,
`public cloud, hybrid cloud, and so forth. In this description
`and in the claims, a "cloud computing environment is an
`environment in which cloud computing is employed.
`Additionally or alternatively, the functionally described
`herein can be performed, at least in part, by one or more
`hardware logic components. For example, and without limi
`tation, illustrative types of hardware logic components that
`can be used include Field-programmable Gate Arrays (FP
`GAs). Program-specific Integrated Circuits (ASICs), Pro
`gram-specific Standard Products (ASSPs), System-on-a-chip
`systems (SOCs), Complex Programmable Logic Devices
`(CPLDs), and other types of programmable hardware.
`Still further, system architectures described herein can
`include a plurality of independent components that each con
`tribute to the functionality of the system as a whole. This
`
`30
`
`35
`
`40
`
`50
`
`60
`
`65
`
`Ex.1001
`APPLE INC. / Page 9 of 14
`
`

`

`5
`modularity allows for increased flexibility when approaching
`issues of platform scalability and, to this end, provides a
`variety of advantages. System complexity and growth can be
`managed more easily through the use of Smaller-scale parts
`with limited functional scope. Platform fault tolerance is
`enhanced through the use of these loosely coupled modules.
`Individual components can be grown incrementally as busi
`ness needs dictate. Modular development also translates to
`decreased time to market for new functionality. New func
`tionality can be added or subtracted without impacting the
`core system.
`FIG. 1 illustrates an example system architecture for a
`mobile wallet platform. Integration tier 101 is configured to
`manage mobile wallet sessions and maintain integrity of
`financial transactions. Integration tier 101 can also include a
`15
`communication (e.g., Web services) API and/or other com
`munication mechanisms to accept messages from channels
`111. Other mechanisms include, but are not limited to: Inter
`national Standards Organization (“ISO) 8583 for Point of
`Sale (“POS) and Automated Teller Machines (ATM)
`devices and Advanced Message Queuing Protocol (AMOP)
`for queue based interfaces. Each of channels 111 can be
`integrated to one or more mechanisms for sending messages
`to integration tier 101. Notification services 102 is configured
`to send various notifications through different notification
`channels 112, such as, for example, Short Message Peer-to
`Peer (“SSMP) for Short Messaging Service (“SMS) and
`Simple Mail Transfer Protocol (“SMTP) for emails. Notifi
`cation services 102 can be configured through a web services
`API.
`Service connectors 103 are a set of connectors configure to
`connect to 3rd party systems 113. Each connector can be a
`separate module intended to integrate an external service to
`the system architecture. Business process services 104 are
`configured to implement business workflows, including
`executing financial transactions, auditing financial transac
`tions, invoking third-party services, handling errors, and log
`ging platform objects. Payment handler 105 is configured to
`wrap APIs of different payment processors, such as, for
`example, banking accounts, credit/debit cards or processor
`121. Payment handler 105 exposes a common API to facilitate
`interactions with many different kinds of payment proces
`SOS.
`Security services 106 are configured to perform subscriber
`authentication. Authorization services 107 are configured to
`perform client authorization, Such as, for example, using a
`database-based Access Control List (ACL) table.
`Database 108 is configured to manage customer accounts
`(e.g., storing customer accounts and properties), manage
`company accounts (e.g., storing company accounts and prop
`erties), manage transaction histories (e.g., storing financial
`transaction details), store customer profiles, storing dictionar
`ies used by the mobile wallet platform, such as, for example,
`countries, currencies, etc., and managing money containers.
`Rules engine 109 is configured to gather financial transaction
`statistics and uses the statistics to provide transaction prop
`erties, such as, for example, fees and bonuses. Rules engine
`109 is also configured to enforce business constraints, such
`as, for example, transactions and platform license constraints.
`Name matching engine 110 is configured to match differ
`ent objects according to specified configuration rules. Match
`ing engine 110 can be used to find similarities between
`names, addresses, etc. Transaction processor 121 is config
`ured to manage financial accounts and transactions. The
`transaction processor 121 can be used to hold, load, withdraw
`and deposit funds to mobile wallet accounts. Transaction
`processor 121 can also be used as a common interface to a
`
`65
`
`40
`
`45
`
`50
`
`55
`
`60
`
`US 9,189,785 B2
`
`10
`
`25
`
`30
`
`35
`
`6
`third party processor System. When used as a common inter
`face, financial operations may be delegated to the external
`processor. A Clearing House Subsystem of transaction pro
`cessor 121 can be used to exchange the financial information
`with a bank.
`Components of a mobile wallet platform can be connected
`to one another over (or be part of) a system bus and/or a
`network. Networks can include a Local Area Network
`(“LAN”), a Wide Area Network (“WAN”), and even the Inter
`net. Accordingly, components of the mobile wallet platform
`can be “in the cloud'. As such, mobile wallet platform com
`ponents as well as any other connected computer systems and
`their components, can create message related data and
`exchange message related data (e.g., Internet Protocol (“IP)
`datagrams and other higher layer protocols that utilize IP
`datagrams, such as, Transmission Control Protocol (“TCP),
`Hypertext Transfer Protocol (“HTTP), Simple Mail Transfer
`Protocol (“SMTP), etc.) over the system bus and/or network.
`The components depicted in FIG. 1 can interoperate to
`provide a number of financial and other services including but
`not limited to enrolling a customer for a mobile wallet, adding
`a stored value account (either hosted by a mobile wallet
`platform or a third party), adding a bank or credit union
`account to a mobile wallet, adding a debit or credit card
`account to a mobile wallet, depositing funds in a mobile
`wallet, withdrawing funds from a mobile wallet, paying bills
`from a mobile wallet, topping up a prepaid mobile account
`through a mobile wallet, transferring funds through a mobile
`wallet (nationally or internationally), making in-store pur
`chases using a mobile wallet, and various other tasks as
`described herein below.
`The telephone, smartphone, tablet or other computing sys
`tem that interacts with the mobile payment system typically
`includes a camera, image sensor, image scanner or other
`hardware that allows a user to scan or capture an image. For
`instance, as shown in environment 200 of FIG. 2, computer
`system 201 may include a camera 202. The computer system
`201 may include a telephone, smartphone, tablet or other type
`of mobile computing system. The user of the phone 201 (i.e.
`user/customer 205) may thus point the camera 202 or other
`hardware at an object Such as a can of Soup and either take a
`picture of the object, or allow software to scan the image
`using the camera. Software on the phone or tablet 201 then
`performs a local search or consults a database (e.g. over the
`internet) to retrieve information related to that item or product
`including coupons or price discounts.
`In addition to receiving product information and discounts,
`the user 205 may also use their phone 201 or other device to
`pay for the items they wish to buy. In one embodiment, a
`customer may be at a retail location 225 shopping for various
`items 228. Once the customer 205 has finished shopping, he
`or she proceeds to the checkout area. The checkout area
`includes a point of sale 226 with a checkout register 227 that
`typically accepts cash, debit or credit cards as payment. The
`checkout register 227 may also be configured to allow users to
`pay using a mobile wallet. Accordingly, the customer may use
`a mobile wallet application 210 on a smartphone (e.g. 201),
`tablet or other computer system to pay for the items.
`When paying for the items 228, the determining module
`215 of user's digital device 201 may determine that the user
`205 is attempting to use their mobile wallet application 210 to
`pay for the items. The mobile wallet application may use
`various types of information to determine which debit net
`work (e.g. 230A or 230B) is to be used to process the payment
`transaction. As will be understood by one skilled in the art,
`various different debit networks exist for processing debit
`transactions (e.g. Star or Nice). These debit networks conduct
`
`Ex.1001
`APPLE INC. / Page 10 of 14
`
`

`

`7
`the transactions between the retailer's bank and the custom
`er's bank that allow the user to pay for items using a debit card
`linked to their own checking (or other type of) account. These
`debit networks typically charge different fee amounts for
`each transaction, and typically receive at least a portion of that
`fee as income. Debit networks are thus incentivized to process
`an increased number of transactions and provide debit trans
`action services for a lower price than their competitors. Simi
`larly, retailers are incentivized to select debit networks that
`process debit transactions for a lower amount. Allowing the
`user and/or the retailer to specify a certain debit network for
`processing debit transactions may lead to an increased num
`ber of users for a given network, and may lead to reduced
`transaction fees for retailers.
`As will further be understood by one skilled in the art, debit
`transactions may be transactions that are processed by tradi
`tional Electronic Funds Transfer (EFT) debit networks (e.g.
`Star, NYCE, PULSE, etc.), but they may alternatively be
`transactions that are processed via direct automated clearing
`house (ACH) debits. In such cases, the debit transactions
`would be sent to an Originating Depository Financial Insti
`tution (ODFI). A user may need to provide additional infor
`mation about their bank (in addition to their debit account
`information) that would allow the ACH transaction to be
`routed through the ODFI, as opposed to using the traditional
`debit networks. As such, it will be understood that when
`describing debit transactions herein, the debit transactions
`may be processed by either a traditional debit network, or via
`an ACH debit that uses an ODFI to process the transaction.
`In some cases, the decision as to which debit network to use
`for a given transaction will be based on either the customer's
`demographic information, the customer's payment prefer
`ences or the customer's purchasing history. For example, the
`user 205 may provide demographic information 211 to the
`mobile wallet application 210 indicating their age or age
`range, income or income range, general housing location (e.g.
`area code) or other similar information. This information may
`be used, at least in Some cases, to provide targeted advertise
`ments, promotions or coupons to the user via the mobile
`wallet. The user's demographic information 211 may provide
`indications or other clues that the user may prefer one debit
`network over another (e.g. for cost reasons, convenience rea
`Sons, or because the user is receiving a discount or reward 231
`from a particular debit network). Accordingly, this informa
`tion may be used by determining module 215 when determin
`ing which debit network to use for a given transaction.
`Similarly, user payment preferences 212 and/or user pur
`chasing history 213 for user 205 may be used to determine
`which debit network to use for a debit transaction. For
`example, if the user has indicated in their payment prefer
`ences which debit network to use, that information may be
`provided to the determining module 215. Moreover, if the
`user's purchasing history indicates that a