WO2013/078176
`
`22
`
`PCT/US2012/066013
`
`is sent to clectronic payment system 521. For example, upon purchasing goods 503, item
`
`list 531 is sent to electronic payment system 521 and stored in data warehouse 532.
`
`[0083]
`
`Propensity analysis module 534 can analyze user 507’s purchases, including
`
`item list 531. From the analysis, propensity analysis module 534 can identify items or
`
`categories of items user 507 may be interested in. The items can be items user 507 has
`
`purchased in the past (e.g., an item in goods 503) or items related to items user 507 has
`
`purchases in the past. Propensity analysis module 534 can indicate identified items or
`
`categories of items to advertisement identification module 536. These identified items or
`
`categories are items that the user is likely interested in and, as such, may have a
`
`propensity toward buying these items. The propensity analysis module may use past
`
`purchases, personal preferences, lifestyle or demographic information or other data in the
`
`propensity analysis.
`
`[0084]
`
`Advertisement identification module 536 can then select advertisements from
`
`advertisements 538 that correspond to the identificd items or catcgorics of items. For
`
`example, advertisement
`
`identification module 536 can select advertisement 546 for
`
`presentation at mobile wallet application 511. Advertisement 546 can be an advertisement
`
`for a product madc by a company in packaged goods companics 571. Additionally or
`
`alternatively, the advertisement 546 may be created by the merchant and may advertise
`
`products or services sold by that merchant.
`
`[0085]
`
`Advertising module 533 can send selected advertisements to mobile wallet
`
`application 511. For cxample, advertising module 533 can send advertiscment 546 (c.g.,
`
`related to an item in goods 503)
`
`to mobile wallet application 511.
`
`In general,
`
`advertisements can include interactive content. For example, advertisement 546 includes
`
`content 573. Content 573 can be a video, a link to a company website (e.g., for a company
`
`in packaged goods companics 571), a call to action (such as a questionnairc), or some
`
`other content user 507 can interact with through digital device 508. User 507 can interact
`
`wilh content 573, for example, responding io questions in content 573, Advertisement
`
`response 574 can indicate how user 507 has interacted with content 573.
`
`In one
`
`embodiment, a call to action may be to post an update on Faccbook® or some other
`
`website such as a retail establishment ranking website. If the user makes such a post or
`
`performs some othercall to action, the user may be rewarded with a benefit. That benefit
`
`may berelated to the product about which the user posted on the various websites.
`
`[0086]
`
`Based on advertisement response 574, benefit determination module 576 can
`
`determineif a benefit is to be conferred upon user 507. Benefit determination module 576
`
`10
`
`15
`
`i)wa
`
`APPL-1002
`APPLEINC./ Page 1191 of 1744
`
`APPL-1002
`APPLE INC. / Page 1191 of 1744
`
`

`

`WO2013/078176
`
`23
`
`PCT/US2012/066013
`
`can refer to bencfit rules 578 when making a determination whether or not to confer a
`
`benefit. Thus, when user 507 interacts with advertisement 546 in a specified way (e.g.,
`
`completes a survey, watches a video, etc.), benefit rules 578 can indicate that a company
`
`benefit (e.g., benefit 577)
`
`is to be conferred upon user 507. For example, benefit
`
`determination module 576 can confer benefit 577 on user 507. When user 507 receives an
`
`advertisement for a razor, for instance, and answers a questionnaire on how often they
`
`shave, a razor manufacture can give user 507 a coupon for reduced cost or free razor
`
`blades.
`
`[0087]
`
`When a benefit is to be conferred on a user, the benefit can be stored in the
`
`user’s brand locker. For example, benefit determination module 576 can store benefit 577
`
`in brand locker 572 (part of uscr mobile wallet 524). Benefit 577 can be a coupon, a
`
`reduced cost or free financial service, a voucher, a promotion, a free bill pay, etc.
`
`[0088]
`
`Benefit detcrmination module 576 can also track agercgate statistics, such as,
`
`for example, specified number and/or type of advertisements reccived, for advertisements
`
`presented at native or third party mobile wallet application 511. Benefits can also be
`
`conferred upon users based on the aggregate statistics. For example, benefit determination
`
`module 576 can confer a bencfit upon uscr 507 in response to twenty advertiscments
`
`being presented at mobile wallet application 511. Thus, conferred benefits can be
`
`company-specified benefits or can be electronic payment system-specified benefits.
`
`Electronic payment system 521 can notify a user when a benefit
`
`is conferred. For
`
`example, clectronic payment system 521 can scnd bencfit notification 547 to mobilc
`
`wallet application 511 to indicate benefit 577 being stored in brand locker 572.
`
`[0089]
`
`When user 507 makes subsequent purchases through user mobile wallet 524,
`
`electronic payment system 521 can automatically check brand locker 572 for benefits
`
`related to any purchases items. If benefits for an item are identified, uscr 507 can be
`
`notified through mobile wallet application 511. In some cases, if benefits are identified,
`
`those benefits can be applied automatically when the user purchases that item or service.
`
`Thus, if the benefit is a coupon or a buy one get one free offer, that benefit may be
`
`applicd automatically when the uscr uses his or her mobile wallct application 511 to
`
`purchase that item. Accordingly, embodiments of the invention permit user 507 to self
`
`i)wa
`
`30
`
`monetize digital device 508 through agreeing to participate in opt-in advertising.
`
`[0090]
`
`Although not depicted, various other modules from the architecture of Figures
`
`1 or 2 can also be included electronic payment system 521. The modules expressly
`
`APPL-1002
`APPLEINC./ Page 1192 of 1744
`
`APPL-1002
`APPLE INC. / Page 1192 of 1744
`
`

`

`WO2013/078176
`
`24
`
`PCT/US2012/066013
`
`depicted in Figure 5 can intcropcrate with these othcr modules as appropriate to facilitate
`
`desired functionality.
`
`[0091]
`
`Figures 7-9 will now be described in conjunction with the computer
`
`architecture 600 illustrated in Figure 6. Figure 6 depicts a mobile wallet platform 601 that
`
`may have an architecture as shown in Figure 1. As further depicted in Figure 6, mobile
`
`wallet platform 601 communicates with an agent terminal 602 or a customer 607 to
`
`process transactions using a native or third party mobile wallet 605. Mobile wallet
`
`platform 601 may also communicate with a third party processor 604 to process
`
`transactions using a mobile wallet or third party mobile wallet. Mobile wallet platform
`
`601 may also communicate with a third party mobile wallet platform 603 to process
`
`transactions using a mobile wallet owned or managed by a third party mobile wallet
`
`provider.
`
`[0092]
`
`Mobile wallct platform 601 may also process the mobile wallct transaction or
`
`third party mobile wallct transaction intcmmally, without the usc of third party processors
`
`or third party mobile wallet platforms. In particular, mobile wallet platform 601 may
`
`process transactions using third party mobile wallets in the same or similar mannerthat
`
`transactions arc processcd as
`
`shown in Figures 2-5. Accordingly,
`
`the physical
`
`environment and corresponding computer system architecture 600 shown in Figure 6
`
`allows a cloud-based transaction platform 601 to support multiple third party mobile
`
`wallet providers.
`
`i)wa
`
`30
`
`[0093]
`
`Mobile wallet platform 601 communicates with agent terminal 602, third party
`
`mobile wallet platform 603, third party processor 604, and customer’s mobile phone 619
`
`through a variety of communication channels. For example, the communication between
`
`mobile wallet platform 601 and any one of these entities may be through communication
`
`channels 111, notification channels 112, or third party systems 113, as shown in Figure 1.
`
`Communication between mobile wallet platform 601 and any one of these entities may
`
`also be through processor 121 shownin Figure |.
`
`[0094]
`
`With respect to the entire description of Figure 6, and as explained above, the
`
`term “mobile wallet” cncompasscs not only mobile wallets owned or managed by the
`
`mobile wallet platform, but also third party mobile wallets owned by third party mobile
`
`wallet providers or managed by third party mobile wallet platforms. In contrast, the term
`
`“third party mobile wallet’ refers only to third party mobile wallets owned by third party
`
`mobile wallet providers or managed by third party mobile wallct platforms. Accordingly,
`
`cloud-based transaction platform 601 may manage and process transactions using mobile
`
`APPL-1002
`APPLEINC./ Page 1193 of 1744
`
`APPL-1002
`APPLE INC. / Page 1193 of 1744
`
`

`

`WO 2013/078176
`
`25
`
`PCT/US2012/066013
`
`wallets 605, which may be mobile wallcts owned by cloud-bascd transaction platform
`
`601 or mobile wallets owned by a third party mobile wallet provider.
`
`[0095]
`
`As shown in Figure 6, customer 607 initiates a mobile wallet transaction 608
`
`at agent terminal 602. Agent terminal 602 may be part of an agent network consisting of
`
`one or more agent terminals that communicate with cloud-based transaction platform 601.
`
`Examples of agent
`
`terminals
`
`are
`
`stores
`
`and other
`
`commercial
`
`establishments.
`
`Altematively,
`
`customer 607 may initiate
`
`a mobile wallet
`
`transaction 609 by
`
`communicating with cloud-based transaction platform 601 through a channel selected by
`
`the customer.
`
`[0096]
`
`Mobile wallet transactions 608 and 609 may be one or more of any type of
`
`transaction that can be performed using a mobile wallet, including but not limited to, a
`
`deposit, withdrawal, transfer, purchase, bill payment, topping up of a prepaid mobile
`
`account, or any othertransaction described hercin. Customer 607 mayinitiate transactions
`
`608 and 609 in a varicty of ways. For cxample, customer 607 can initiate a deposit into a
`
`mobile wallet, a withdrawal from a mobile wallet, a bill payment from a mobile wallet,
`
`topping up of a prepaid mobile account using a mobile wallet, a transfer from a mobile
`
`wallct, a remittance transaction, a sclection of health care provider or payment of health
`
`services, a purchase of music, movies, games or other downloadable content, or other
`
`purchases using a mobile wallet.
`
`[0097]
`
`After customer 607 initiates transaction 609 through agent terminal 602, agent
`
`terminal 602 then communicates with cloud-based transaction platform 601 by scnding
`
`transaction data 610 to cloud-based transaction platform 601. Once cloud-based
`
`transaction platform 601 has received the transaction either through transaction data 610
`
`from agent terminal 602 or from transaction 609 initiated by customer 607, cloud-based
`
`i)wa
`
`transaction platform 601 may then process the transaction in a varicty of ways.
`
`[0098]
`
`For example,
`
`cloud-based transaction platform 601 may process
`
`the
`
`transaclion by communicating with third party processor 604 by sending third parly
`
`transaction data 611, which may include someorall of the information in transaction data
`
`610. Third party proccssor can then perform the requested transactional processing and
`
`respond by sending confirmation data 612 to cloud-based transaction platform 601.
`
`Confirmation data 612 can indicate whether the requested mobile wallet transaction was
`
`processed successfully or unsuccessfully.
`
`[0099]
`
`In another example, cloud-based transaction platform 601 may process the
`
`transaction by communicating with third party mobile wallet platform 603 by sending
`
`APPL-1002
`APPLEINC./ Page 1194 of 1744
`
`APPL-1002
`APPLE INC. / Page 1194 of 1744
`
`

`

`WO2013/078176
`
`26
`
`PCT/US2012/066013
`
`third party transaction data 613, which may include someorall of the information in
`
`transaction data 610. Third party mobile wallet platform 603 may have any architecture
`
`which is suitable for processing mobile wallet transactions. Third party mobile wallet
`
`platform 603 may have an architecture that is the same or similar to the architecture
`
`shownin Figure 1.
`
`[00100] Alternatively, third party mobile wallet platform 603 may have a different
`
`architecture.
`
`In addition, any aspects of cloud-based transaction platform 601 or
`
`functionality provided bythat platform may also be present in third party mobile wallet
`
`platform 603. After receiving third party transaction data 613, third party mobile wallet
`
`platform 603 may process the transaction itself or forward the transaction to third party
`
`processor 604 by sending third party transaction data 614.
`
`[00101]
`
`Once processing of the transaction is complete,
`
`third party mobile wallet
`
`platform 603 may respond to cloud-based transaction platform 601 by scnding
`
`confirmation data 615. Confirmation data 615 can indicate whether the requested mobile
`
`wallet transaction was processed successfully or unsuccessfully. In addition, following
`
`the processing performed by third party mobile wallet platform 603 after receiving third
`
`party transaction data 613, the third party mobile wallct platform 603 may provide a
`
`commission or transaction fee 616 to cloud-basedtransaction platform 601.
`
`[00102]
`
`Ina further example, mobile wallet platform 601 may process the transaction
`
`internally within cloud-based transaction platform 601. Specifically, cloud-based
`
`transaction platform 601 may proccss a transaction using a third party mobile wallct
`
`entirely within cloud-based transaction platform 601.
`
`i)wa
`
`30
`
`[00103]
`
`Once processing of the transaction is complete, cloud-based transaction
`
`platform 601 may communicate with agent terminal 602 by sending confirmation data
`
`617 indicating information such as whether the transaction was successful or not. Also
`
`following processing of the transaction, mobile wallet platform may send customer
`
`notification 618 through an appropriate channel such as to the cuslomer’s mobile phone
`
`619. For example, customer notification 618 may be sent using the notification services
`
`102 and notification channels 112 (c.g. SMPP, SMTP, voicc) of Figure 1.
`
`[00104] With reference now to Figures 2, 6 and 7, the cloud-based transaction system
`
`210 receives communication 226 from an agent terminal 223 over a communication
`
`channel connected to the cloud-based transaction platform 210/601 (act 710). The agent
`
`communication indicatcs that a customer 222/205 desires to perform a mobile wallct
`
`transaction using their third party mobile wallet 207. The cloud-based transaction system
`
`APPL-1002
`APPLEINC./ Page 1195 of 1744
`
`APPL-1002
`APPLE INC. / Page 1195 of 1744
`
`

`

`WO 2013/078176
`
`27
`
`PCT/US2012/066013
`
`210 scnds the agent communication to a third party mobile wallet platform 603 (act 720).
`
`The cloud-basedtransaction system 210 then receives communication 611 from the third
`
`party mobile wallet platform confirming processing of the transaction 612 (act 730) and
`
`sends communication 617 to the agent terminal 602 over communication channels 111
`
`connected to the cloud-based transaction platform indicating confirmation of the
`
`processing ofthe transaction (act 740).
`
`[00105]
`
`As mentioned above, multiple different
`
`types of transactions may be
`
`performed using the infrastructure provided by the cloud-based transaction system. The
`
`transactions may be a performed not only by a first customer that uses a first mobile
`
`wallet provider, but also by a second, different customer using a second, different third
`
`party mobile wallet provider. The third party mobile wallet platform may usc a third party
`
`processor to perform (at least parts of) the transaction. The customer may be notified of
`
`confirmation of the processing of the transaction using the third party mobile wallct over
`
`various communication channels connected to the cloud-based transaction platform. In
`
`some cases, each third party mobile wallet provider has their own point of sale (POS)
`
`processing system 230. The third party mobile wallet providers’ POS processing systems
`
`may communicate with cach other using the cloud-bascd transaction platform to process
`
`the transaction.
`
`[00106]
`
`One ofthe transactions made possible by the cloud-based transaction platform
`
`601 is depositing funds into a third party mobile wallet owned by an entity different than
`
`the customer. The cloud-bascd transaction system may reccive a communication 226
`
`from the agent terminal 223 over a communication channel connected to the cloud-based
`
`transaction platform. The agent communication indicates that the customer desires to
`
`deposit a specified amount of funds into their third party mobile wallet 605. The cloud-
`
`based transaction system may then credit the third party mobile wallct with the specified
`
`amount of funds.
`
`[90107] Another transaction provided by the cloud-based transaction platform 601 is
`
`withdrawing funds from a third party mobile wallet owned by an entity different than the
`
`customer. The cloud-based transaction platform receives communication 208 from the
`
`customer 205 indicating that the customer desires to withdraw a specified amount of
`
`funds from the third party mobile wallet. The cloud-based transaction platform 601
`
`retums a secure, perishable withdrawal code to the customer over at least one of the
`
`communication channcls connected to the cloud-based transaction platform.
`
`It also
`
`receives communication from the agent terminal 223 indicating that the withdrawal code
`
`10
`
`15
`
`i)wa
`
`APPL-1002
`APPLEINC./ Page 1196 of 1744
`
`APPL-1002
`APPLE INC. / Page 1196 of 1744
`
`

`

`WO2013/078176
`
`28
`
`PCT/US2012/066013
`
`has been presented to an agent and debits the third party mobile wallet by the specified
`
`amount of funds.
`
`[00108] Another transaction provided by the cloud-based transaction platform 601 is
`
`transferring money from a third party mobile wallet within the cloud-based transaction
`
`platform to a recipient at a second third party mobile wallet provided by a second mobile
`
`wallet provider. In this transaction, the platform 601 receives a customer communication
`
`208 indicating that a customer 205 desires to transfer a specified amount of funds to a
`
`specified recipient using a specified payment method from the third party mobile wallet
`
`606. The cloud-based transaction platform debits the third party mobile wallet by the
`
`specified amount of funds and transfers the specified amount of funds from the cloud-
`
`based transaction platform to the sccond different third party mobile wallet platform for
`
`delivery to the specified recipient. The specified amount of funds is then transferred to the
`
`sccond third party mobile wallet platform.
`
`[00109]
`
`Yct anothcr transaction provided by the cloud-bascd transaction platform 601
`
`is making a purchase from a third party mobile wallet managed by a third party mobile
`
`wallet platform.
`
`In this transaction,
`
`the cloud-based transaction platform receives
`
`communication 208 from the customcr 205 indicating that
`
`the customer desires to
`
`purchase an item for a specified amount of funds using a specified payment method from
`
`the customer’s third party mobile wallet 606. The cloud-based transaction platform
`
`retums a secure, perishable purchase code to the customer, receives communication 226
`
`from the agent terminal 223 indicating that the purchase code has been presented to an
`
`agent, and debits the customer’s third party mobile wallet by the specified amount of
`
`funds.
`
`[00110]
`
`In another embodiment, as shown in Fig. 8, a cloud-based transaction system
`
`i)wa
`
`performsor facilitates a transaction using a third party point of sale (POS) system. The
`
`cloud-based transaction system receives communication 226 from a specified POS system
`
`224 implemented al an agent terminal 223 over a communication channels 111 connected
`
`to the cloud-based transaction platform 210 (act 810). The POS communication indicates
`
`that a customer 205 hasinitiated a mobile wallct transaction using their third party mobile
`
`wallet 207. The cloud-based transaction system sends the POS communication to a
`
`corresponding third party POS transaction processing system 230 that has been
`
`established to process POS transactions from the specified POS system (act $20). The
`
`cloud-based transaction system then receives communication from the third party POS
`
`transaction processing system 230 confirming processing of the transaction (act 830) and
`
`APPL-1002
`APPLEINC./ Page 1197 of 1744
`
`APPL-1002
`APPLE INC. / Page 1197 of 1744
`
`

`

`WO2013/078176
`
`29
`
`PCT/US2012/066013
`
`sends communication to the specificd POS system 224 implemented at the agent terminal
`
`223 indicating confirmation of the processing of the transaction (act 840).
`
`[00111]
`
`In somecases, transaction fees or commissions 616 may be paid by the third
`
`party mobile wallet platform to the cloud-based transaction platform for facilitating the
`
`transaction. One of the transactions allowed by the cloud-based transaction system is
`
`depositing funds into a third party mobile wallet provided by a third party mobile wallet
`
`provider.
`
`In this
`
`transaction,
`
`the cloud-based transaction platform 210 receives
`
`communication 226 from a specified POS system 224 implemented at the agent terminal
`
`223 over a communication channels 111 connected to the cloud-based transaction
`
`platform. The POS communication indicates that the customer 205/222 desires to deposit
`
`a specified amount of funds into the third party mobile wallct 606 provided by the third
`
`party mobile wallet provider. The cloud-based transaction system validates the status of
`
`the third party mobile wallct provided by the third party mobile wallct provider,
`
`determinesif the specified POS system implemented at the agent terminal is authorized to
`
`deposit money, performs a limit check or a velocity check on the third party mobile wallet
`
`provided by the third party mobile wallet provider, credits the third party mobile wallet
`
`provided by the third party mobile wallet provider with the specificd amount of funds,
`
`returns a notification to the specified POS system implemented at the agent terminal
`
`confirming the deposit and notifies the customer that the specified amount of funds were
`
`deposited in the third party mobile wallet provided by the third party mobile wallet
`
`provider over a communication channel connected to the cloud-based transaction
`
`platform 210.
`
`[00112] Another transaction provided by the cloud-based transaction platform 210 is
`
`withdrawing funds from a third party mobile wallet provided by a third party mobile
`
`i)wa
`
`wallet provider. The cloud-based transaction platform 210 reccives communication 208
`
`from a customer 205 indicating that the customer desires to withdraw a specified amount
`
`of funds from the third party mobile wallet 606 provided by the third party mobile wallet
`
`provider. The cloud-based transaction platform 210 validates the status of the third party
`
`mobile wallet provided by the third party mobile wallct provider, determines if the
`
`balance of the third party mobile wallet provided by the third party mobile wallet provider
`
`is sufficient to accommodate the requested withdrawal for the specified amount of funds,
`
`performsa limit check and/or a velocity check on the third party mobile wallet, returns a
`
`secure, perishable withdrawal code to the customer over a communication channel 111
`
`connected to
`
`the
`
`cloud-based
`
`transaction platform,
`
`receives
`
`subsequent POS
`
`APPL-1002
`APPLEINC./ Page 1198 of 1744
`
`APPL-1002
`APPLE INC. / Page 1198 of 1744
`
`

`

`WO2013/078176
`
`30
`
`PCT/US2012/066013
`
`communication 226 indicating that the withdrawal code has becn presented to an agent
`
`(e.g. at agent terminal 223), debits the third party mobile wallet provided by the third
`
`party mobile wallet provider by the specified amount of funds, returns a notification to
`
`the POSsystem at the agent terminal confirming the withdrawal and notifies the customer
`
`205 (e.g. in confirmation 617) that the specified amount of funds were withdrawn from
`
`the third party mobile wallet.
`
`[00113]
`
`In yet another transaction provided by the cloud-based transaction platform,
`
`moneyis transferred using a third party mobile wallet provided by a third party mobile
`
`wallet provider. The
`
`cloud-based transaction platform 210
`
`receives
`
`customer
`
`communication 208 indicating that the customer 205 desires to transfer a specified
`
`amount of funds to a specified recipicnt having a third party mobile wallct 606, where the
`
`transfer uses a specified payment method from the customer’s third party mobile wallet at
`
`the cloud-bascd transaction platform 210. The cloud-based transaction platform validatcs
`
`the status of the specificd payment method, performs a limit check and/or a velocity
`
`check on the specified payment method, performs a check on the specified recipient
`
`having a third party mobile wallet to comply with the office of foreign assets control,
`
`debits the customcr’s mobile wallct at the cloud-based transaction platform by the
`
`specified amount of funds, transfers the specified amount of funds to third party mobile
`
`wallet provider for delivery to the third party mobile wallet of the specified recipient over
`
`a communication channel connected between the cloud-based transaction platform and
`
`the third party mobile wallct provider, and notifics the customer that the specified amount
`
`of funds wastransferred to the specified recipient.
`
`[00114]
`
`In another transaction provided by the cloud-based transaction platform 210, a
`
`purchase is made from a third party mobile wallet provided by a third party mobile wallet
`
`i)wa
`
`provider. In this transaction, the cloud-based transaction system reccives communication
`
`208 from the customer 205 indicating that the customer desires to purchase an item for a
`
`specified amount of funds using a specified payment method [rom the customer’s third
`
`party mobile wallet 606. The cloud-based transaction system returns a secure, perishable
`
`purchase code to the customer, reccives subscquent agent
`
`terminal communication
`
`indicating that the purchase code has been presented to an agent, validates the status of
`
`the specified payment method, determines if the specified payment method can
`
`accommodate a purchase for the specified amount, performs a limit check and/or a
`
`velocity check on the specified payment method, debits the customer’s third party mobile
`
`wallet by the specified amount of funds by sending communication to the third party
`
`APPL-1002
`APPLEINC./ Page 1199 of 1744
`
`APPL-1002
`APPLE INC. / Page 1199 of 1744
`
`

`

`WO2013/078176
`
`31
`
`PCT/US2012/066013
`
`mobile wallct provider, returns a notification to the POS system at the agent terminal
`
`authorizing the purchase and sends a receipt to the customer over at least one of the
`
`plurality of communication channels connected to the cloud-based transaction platform.
`
`[00115]
`
`Figure 9 describes a further embodiment in which a cloud-based transaction
`
`platform facilitates making a purchase from a third party mobile wallet provided by a
`
`third party mobile wallet provider. The cloud-based transaction system 210 receives
`
`communication 208 from a customer 205 over a communication channel connected to the
`
`cloud-based transaction platform (act 910). The customer communication indicating that
`
`a customer desires to purchase an item for a specified amount of funds using a specified
`
`payment method indicated by the customer’s third party mobile wallet 606. The cloud-
`
`based transaction system returns a secure, perishable purchase code to the customer(act
`
`920) and receives communication from an agent terminal 223 over at least one of the
`
`communication channels connected to the cloud-based transaction platform indicating
`
`that the purchase code has been presented to an agent (act 930). The cloud-based
`
`transaction system 210 then debits the customer’s third party mobile wallet 606 by the
`
`specified amountof funds (act 940).
`
`[00116]
`
`Substantially any item may be purchascd using this transaction technique
`
`including items provided directly by the cloud-based transaction system, or items
`
`provided by third party retailers through the cloud-based transaction system. These items
`
`may include health care services, physical, shippable items, music, games, movies or any
`
`other digital or downloadable content.
`
`[00117]
`
`Lmbodiments of the invention can adhere to Know Your Customer (KYC)
`
`rules in the United States by performing Customer Identification Program (CIP) checks as
`
`required by the Bank Secrecy Act and U.S. PATRIOT Act. A minimum amount of
`
`information can be gathered about a customer, such as, for cxamplc, First Name, Last
`
`Name, Date of Birth, Government ID Type, Government ID Number, Address. The CIP
`
`processes are designed to validate customeridentily against government blacklists and
`
`assist in the prevention of money laundering and terrorist financing. A combination of
`
`non-documentary and documentary verification can be uscd to cnsure beyond a
`
`reasonable doubtthe identity of the customer.
`
`[00118]
`
`Non-Documentary Verification can occur through the presentment of the
`
`information that was collected from the user to an external third party, such as, for
`
`example, Lexis Nexis. Documentary Verification can occur
`
`if non-documentary
`
`verification fails, then the user is asked to present an unexpired government ID. Various
`
`10
`
`15
`
`i)wa
`
`APPL-1002
`APPLEINC./ Page 1200 of 1744
`
`APPL-1002
`APPLE INC. / Page 1200 of 1744
`
`

`

`WO2013/078176
`
`32
`
`PCT/US2012/066013
`
`differ forms of identification including Driver’s license, Passport, Alicn identification
`
`(e.g., green card or work visa), and Mexican Consular identification card, can be
`
`accepted,
`
`[00119]
`
`Embodiments of the invention can perform Anti-Money Laundering (AML)
`
`and Combating the Financing of Terrorism (CFT) checks. AML and CFT checks can be
`
`performed using transaction monitoring methods
`
`to flag names and suspicious
`
`transactions for further investigation. The mobile wallet platform can perform AML
`
`and CFT checkson all electronic financial transactions to ensure that electronic funds are
`
`10
`
`15
`
`not being used for money laundering or terrorism. Transaction limits can be placed on
`
`user accounts. The transaction limits are fully configurable for each particular use case,
`
`channel and payment method that allows maximum flexibility to restrict higher risk usc
`
`cases. Velocity checks can also be performed. Velocity Checks ensure that subscribers
`
`arc not abusing the mobile wallct platform within the allowable limits.
`
`[00120]
`
`The present invention may be cmbodiecd in other specific forms without
`
`departing from its spirit or essential characteristics. The described embodiments are to be
`
`considered in all respects only as illustrative and not restrictive. The scope of the
`
`invention is, thercforc, indicated by the appended claims rather than by the forcgoing
`
`description. All changes which come within the meaning and range of equivalency of the
`
`claims are to be embraced within their scope.
`
`APPL-1002
`APPLEINC./ Page 1201 of 1744
`
`APPL-1002
`APPLE INC. / Page 1201 of 1744
`
`

`

`WO2013/078176
`
`33
`
`PCT/US2012/066013
`
`CLAIMS
`
`Whatis claimed:
`
`1.
`
`A cloud-based transaction platform including:
`
`one or more processors;
`
`system memory;
`
`one or more computer-readable storage media having stored thereon computer-
`
`executable instructions that, when executed by the one or more processors, cause the
`
`computing system to perform a method for performing a transaction using a third party
`
`mobile wallet, the method comprising the following:
`
`an act of receiving communication from an agent terminal over one of a
`
`plurality of communication channels connected to the cloud-based transaction
`
`platform, the agent communication indicating that a customerdesires to perform a
`
`mobile wallct transaction using their third party mobile wallct;
`
`an act of scnding the agent communication to a third party mobile wallct
`
`platform;
`
`an act of receiving communication from the third party mobile wallet
`
`platform confirming processing ofthe transaction; and
`
`an act of sending communication to the agent terminal over one of a
`
`plurality of communication channels connected to the cloud-based transaction
`
`platform, the communication indicating confirmation of the processing of the
`
`transaction.
`
`2.
`
`The cloud-based transaction platform of claim 1, wherein a transaction is
`
`performed by a second, different customer using a second, different third party mobile
`
`wallet.
`
`3.
`
`The cloud-based transaction platform of claim 1, wherein the third party
`
`mobile wallet platform comprises a third party processor.
`
`4,
`
`The cloud-based transaction platform of claim 1, wherein the transaction
`
`using a third party mobile wallet comprises one or more of a deposit, a withdrawal, a
`
`transfer, a purchase,a bill payment, or topping up of a prepaid mobile account.
`
`5.
`
`The cloud-based transaction platform of claim 1, further