Mobile wallet account provisioning systems and methods

Description

BACKGROUND

The present disclosure relates generally to the field of systems that use mobile devices to transfer funds. More specifically, the present disclosure relates to systems and methods for enabling individuals to use their electronic devices to transfer funds, purchase products and services.

Payments for products and services are often completed using credit cards, debit cards, checks, or cash. At the same time, most people carry some type of mobile handheld electronic device, such as a cellular phone, smart phone, mobile handheld wireless e-mail device, personal digital assistant, portable gaming devices, and so on. Most of these devices tend to have a wireless Internet connection. A person may wish to make payments to merchants or other individuals using these mobile devices. Likewise, a person may wish to transfer funds to other individuals using their mobile devices. Enhanced systems and methods of facilitating such transactions would be desirable.

SUMMARY

According to one example embodiment, a computer system receives an indication from a user that the user wishes to perform a mobile wallet transaction to transfer funds to a recipient using a mobile device. The transaction is authenticated by the computer system. The authentication includes receiving login credentials manually entered by the user and determining that the login credentials match stored login credentials for the user. The authentication further includes determining that the mobile device has a device token stored thereon that matches a device token stored in a database of the computer system. The device token uniquely identifies the mobile device in the computer system. The authentication further includes determining that the mobile device has a customer token stored thereon that matches the customer token stored in the database. The customer token uniquely identifying the customer in the computer system. The computer system transmits the funds to the recipient responsive to the authenticating step.

According to another example embodiment, a financial institution computer system creates a new financial account for a user. The financial institution computer system activates the new account as a source of funds for a mobile wallet. The user does not need to take any action outside of the mobile wallet to have the account activated as a source of funds for the mobile wallet.

According to another example embodiment, a computer system receives an indication from a user that the user wishes to create a mobile wallet. The computer system accesses a database to retrieve a list of one or more accounts held by the user at a financial institution. The computer system generates a screen display to present to the user via a mobile device, the screen display showing the list of accounts held by the user. The computer system receives a user selection of at least one of the accounts. In response to the user selection, the at least one account is provisioned to the mobile wallet.

According to another example embodiment, a financial institution computer system receives online banking login credentials from a mobile device at an online banking website of a financial institution to initiate a mobile online banking session for a user. During the online banking session, the computer system presents the user with a link to have a mobile wallet circuit placed on the mobile device. The computer system places the mobile wallet circuit on the mobile device responsive to a user selection of the link, including transmitting a mobile wallet application to the mobile device and causing installation of the mobile wallet application to occur on the mobile device.

BRIEF DESCRIPTION OF THE FIGURES

The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the disclosure will become apparent from the description, the drawings, and the claims, in which:

FIG. 1 is a block diagram of a computer-implemented payment processing system, according to an example embodiment.

FIG. 2 illustrates a payment process that may be implemented by the system in FIG. 1 according to an example embodiment.

FIG. 3 illustrates a user registration process and a token generation process during registration, according to an example embodiment.

FIGS. 3A-3F illustrate display screens that may be displayed to the user during the process of FIG. 3.

FIG. 4 illustrates a payment code generation process for an authenticated mobile wallet session, according to an example embodiment.

FIGS. 4A-4D illustrate display screens that may be displayed to the user during the process of FIG. 4.

FIG. 5 illustrates a Track 1 format for a generated QR code that may be created in the token generation process, according to an example embodiment.

FIG. 6 illustrates a Track 2 format for a generated QR code that may be created in the token generation process, according to an example embodiment.

FIG. 7 illustrates a tokenized primary account number (TPAN) format within the QR code of FIGS. 5-6, according to an example embodiment.

FIG. 8 illustrates a Track 2 format for a code generated, according to an example embodiment.

FIG. 9 illustrates a process that may be implemented by the system in FIG. 1 according to an example embodiment.

FIG. 10 illustrates a payment process that may be implemented by the system in FIG. 1 according to an example embodiment.

DETAILED DESCRIPTION

Before turning to the figures which illustrate example embodiments, it should be understood that the application is not limited to the details or methodology set forth in the following description or illustrated in the figures. It should also be understood that the phraseology and terminology employed herein is for the purpose of description only and should not be regarded as limiting.

Referring generally to the figures, systems and methods for providing token generation and validation features for a payment processing system are described. More particularly, the present disclosure relates to the use of codes with tokens for validation during payment processing. The codes may be transmitted, e.g., using optical image methods (e.g., QR code), NFC, wireless, Bluetooth, low energy Bluetooth, RFID, hypersonic, Wi-Fi, cellular 3G, 4G, GSM, LiFi, etc. The systems and methods described herein may be implemented for users having a mobile wallet implemented on a mobile device. The mobile wallet allows the user access to accounts via the mobile device to provide payments to merchants or other users. The systems and methods described herein allow for integration between a mobile wallet server and a merchant for processing a payment.

In an embodiment of the present disclosure, a code representing a substitute card number may be generated and formatted for use as part of a validation system. When a user registers for a mobile wallet account, a customer token may be generated for the user and a device token may be generated for the device used by the user. The customer token and device token may be used to verify further transactions between the user and the mobile banking system or mobile wallet account.

When the user logs into his or her mobile wallet and wishes to make a payment using funds in the user's accounts, the customer token and device token are sent or provided to a server system. A substitute card number (tokenized) including a trace ID number as described below may be provided to the user by a mobile wallet computer system. The mobile wallet computer system and a point of sale (POS) device, e.g., at the store location at which the payment is to be submitted, use the substitute credit card number to authenticate the transaction. The substitute card number may be formatted to include a portion of an actual card number held by the user, e.g., so that the last four digits appearing on a receipt provided to the user match those of the user's actual card number, even though a substitute card number was provided to the merchant to process the payment.

In various embodiments, the substitute card number (tokenized) including a trace ID number as described below may be converted back into the actual credit card number by a mobile wallet computer system. For example, the merchant point of sale device may provide the substitute card number to an acquirer processor computer system, which in turn may provide the substitute card number to the mobile wallet computer system. In response, and after authenticating the transaction, the mobile wallet computer system may return the actual card number to the acquirer processor computer system. The acquirer processor may then provide the actual card number to a payment network, which in turn may provide the card number to a source account (credit card issuer) computer system for payment processing.

In other embodiments, rather than providing the substitute card number to the mobile wallet computer system, the acquirer processor computer system may provide the substitute card number to a payment network computer system. In turn, the payment network computer system may provide the substitute card number to the mobile wallet computer system, which, after authenticating the transaction, may then return the actual card number to the payment network computer system. The payment network computer system may then provide the actual card number to a source account computer system for payment processing.

Referring to FIG. 1, a computer-implemented payment processing system 100 is shown, according to an example embodiment. The payment processing system 100 may be used to set up and utilize a mobile wallet. The user may be a business entity and/or an individual consumer that has one or more source accounts with a financial institution. The source accounts may include business or consumer demand deposit, credit card, debit card accounts, lines of credit, and so on. The mobile wallet account may be created for the user to transmit funds from a source account to pay for goods or services to a merchant. Additionally, funds can be transferred from the source account to another person.

The payment processing system 100 may include, among other systems, a mobile device 110, a mobile wallet bank computer system 120, a source account bank computer system 130, a merchant computer system 140, an acquirer/processor computer system 145 and a payment system 150. The various systems may communicate through a network 160, which may include one or more of the Internet, cellular network, Wi-Fi, Wi-Max, a proprietary banking network, or any other type of wired or wireless network. In some embodiments, the mobile wallet bank computer system 120 and source account bank computer system 130 may be owned by the same entity. In other embodiments, the mobile wallet bank computer system 120 and source account bank computer system 130 may be owned by a different entity.

The mobile wallet bank computer system 120, the source account bank computer system 130, the acquirer/processor computer system 145 and the payment system 150 may each include a computer system (e.g., one or more servers each with one or more processing circuits), each including a processor and memory. The processors may be implemented as application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components. The memory may be one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described herein. The memory may be or include non-transient volatile memory, non-volatile memory, non-transitory computer storage media. The memory may include data base components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described herein. The memory may be communicably connected to the processor and include computer code or instructions for executing one or more processes described herein.

The mobile wallet account may be established in a variety of ways, for example, through an online banking area of a website of the banking institution that operates the mobile wallet bank computer system 120.

The mobile device 110 may be used by an individual user (e.g., a business owner or employee, a consumer, etc.) to create and interact with a mobile wallet account. The mobile device 110 may, for example be, a cellular phone, smart phone, mobile handheld wireless e-mail device, personal digital assistant, portable gaming device, or other suitable device. The mobile device 110 includes a network interface logic 112, a display device 114, an input device 115, and a mobile wallet client application 116. The network interface logic 112 may include, for example, program logic that connects the mobile device 110 to the network 160. For example, the mobile device 110 may receive and display screens including account information, transaction instructions, and so on. In one embodiment, a screen may be used to request a username and password information from the user, to prompt the user to provide information regarding the amount of a payment and which merchant or individual (e.g., name, address, phone number or e-mail, a selection of a recipient by the user from his/her memory or from the mobile device 110, etc.) is to receive the payment. Such screens are presented to the user via the display device 114. The input device 115 may be used to permit the user to initiate account access and to facilitate receiving requested information from the user. The input device 115 may include, for example, a keypad or keyboard, a touchscreen, a microphone, or any other device that allows the user to access the payment processing system 100. As will be appreciated, in addition to or instead of the mobile device 110, users may also be provided with the ability to access the payment processing system 100 using another type of computer (e.g., a desktop or laptop computer executing browser software) to perform the operations described herein as being performed by the mobile device 110.

The mobile wallet client application 116 or mobile wallet circuit may include program logic executable by mobile device 110 to implement at least some of the functions described herein. In order to make the mobile wallet circuit 116, the mobile wallet bank computer system 120 may provide a software application and make the software application available to be placed on the mobile device 110. For example, the mobile wallet bank computer system 120 may make the software application available to be downloaded (e.g., via the online banking website of the mobile wallet bank, via an app store, or in another manner). Responsive to a user selection of an appropriate link, the mobile wallet application may be transmitted to the mobile device and may cause itself to be installed on the mobile device 110. Installation of the software application creates the mobile wallet circuit on the mobile device 110. Specifically, after installation, the thus-modified mobile device 110 includes the mobile wallet circuit (embodied as a processor and instructions stored in non-transitory memory that are executed by the processor).

As will be appreciated, the level of functionality that resides on the mobile device 110 as opposed to the mobile wallet bank computer system 120 may vary depending on the implementation. The client application 116 may provide an interface that is configured to receive and display mobile web pages received from the mobile wallet bank computer system 120 (e.g., web pages prompting the user to provide information to create an account, web pages displaying account balance information and past transactions, and so on). Upon initiation of a transaction, the client application 116 may request data from the mobile wallet computer system 120 to generate a unique code/token. The unique code/token may then be transmitted by the mobile device 110 to the merchant computer system 140 as part of a transaction to facilitate authentication of the transaction. In other embodiments, the mobile wallet bank computer system 120 may implement the code/token generator.

The mobile wallet client application 116 is used in connection with merchant computer system 140 located at a brick and mortar store location. Additionally, the mobile wallet application 116 may also be used in connection with online merchant transactions. In another embodiment, merchants may be provided with the ability to have a mobile storefront and profile within the mobile wallet client application 116. For example, merchants may be provided with the ability to display marketing material, provide information, and promote products or discounts. Merchants may also be provided with the ability to sell items directly through their mobile storefront for the account holder to purchase from within the mobile wallet client application 116.

The mobile wallet client application 116 may offer a user to choose any one of the accounts for transferring funds to the merchant for goods or services. An account holder may select a default account that is used to make payments. The account holder may use account selection logic to select the account the account holder wants to use to pay the merchant or other recipient.

The mobile wallet bank computer system 120 includes code/token generator 118, account processing logic 122, an accounts database 124, network interface logic 126, transaction verification logic 127, and an account directory 128. In one embodiment, the mobile wallet bank computer system 120 is operated by a first banking entity that maintains and handles transaction processing for mobile wallet accounts. The mobile wallet accounts may be created via interaction of the mobile wallet application 116 with the mobile wallet bank computer system 120. The user may or may not have conventional bank accounts with the banking entity that maintains the mobile wallet bank computer system 120. If the user does not have bank accounts with the entity that maintains the mobile wallet bank computer system 120, then accounts associated with another banking entity may also be used. Again, in such an embodiment, the flow of funds into and out of the mobile wallet accounts may also be processed by the first banking entity using the mobile wallet bank computer system 120.

The mobile wallet bank computer system 120 is configured to store information regarding mobile wallet accounts. By way of example, information for a specific mobile wallet account 125 is shown as being stored in the accounts database 124. As will be appreciated, the accounts database 124 may also store information regarding many other mobile wallet accounts (not shown). As will also be appreciated, the extent to which transaction details are tracked and maintained in account processing logic 122 and stored in a storage database provided by the mobile wallet bank computer system 120 may vary in differing embodiments. The account database 124 may store details regarding credit card accounts. In particular, the account database 124 may store each financial transaction that occurred. Each financial transaction may include the amount of the transaction and the merchant.

The code generator 118 may receive a request from an account holder to initiate a transaction. In response, the code generator 118 may generate a code that may be transmitted by the mobile device 110 to the merchant computer system 140. As will be appreciated, any suitable method may be used to transmit the code. In various embodiments, the code may be transmitted using optical image methods (e.g., QR code), NFC, wireless, Bluetooth, low energy Bluetooth, RFID, hypersonic, Wi-Fi, cellular 3G, 4G, GSM, LiFi, etc. For purposes of providing an example, it is sometimes assumed in the discussion of FIGS. 1-11 that an optical method is used (e.g., QR code). In various embodiments, the code may be generated without the account holder providing the merchant's name or amount of transaction. The code generator 118 can be configured to generate a code that incorporates at least one of a date, time, trace ID, unique transaction identifier, and geographic location of the mobile device. In other embodiments, the code generator 118 may generate a tokenized numerical code that is in the Track 1 and Track 2 formats as specified by the ISO 8583 specification.

The code may incorporate at least a portion of an account number for a source account that is associated with the mobile wallet account. The incorporated user account number indicates the payment method to be associated with the transaction (e.g., which of the user's credit cards will be used for the transaction). The code may be generated such that a combination of random digits and a portion of a payment card number are included in the code, e.g., so that the last four digits appearing on a receipt provided to the user match those of the user's actual card number, even though a substitute card number was provided to the merchant. The various fields of such a code, and the format of such a code, are described in greater detail in FIGS. 5-8.

The mobile wallet account 125 holds funds that are transmitted to a recipient 140 upon receiving instructions from the user through the mobile device 110. As described below, funds flow into and out of the mobile wallet account 125 through the payment system 150. The mobile wallet account logic 120 is connected to the payment system 150 through the network 160. The network interface logic 126 may include, for example, program logic that connects the mobile wallet bank computer system 120 to the network 160.

The mobile wallet bank computer system 120 further includes transaction verification logic 127. The transaction verification logic 127 may receive a transaction amount from the merchant computer system 140. In some embodiments, the transaction verification logic 127 may generate a message to send to the mobile device 110 for verifying the transaction amount. Upon receiving the verification message, the account holder via the mobile device 110 may approve or deny the transaction amount for the mobile wallet bank computer system 120.

The source account computer system 130 includes account processing logic 132, an accounts database 134, and network interface logic 136. In an example embodiment, as previously indicated, during registration process for the mobile wallet account 125, the user may be prompted to identify a source account 135, that is, a source of funds for the mobile wallet account. The source account 135 may be an existing demand deposit account or a credit card account held by the user with the same financial institution or another financial institution. When the mobile wallet account 125 is created, the user is prompted to provide bank account information (e.g., routing number and/or account number) for the source account 135 that is used as a source of funds for the mobile wallet account 125. Thus, the financial institution that provides the mobile wallet account 125 for the user and the financial institution that typically provides banking services to the user may be two different financial institutions. In such situations, a second banking entity that maintains and handles transaction processing for source accounts may operate the source account computer system 130. In other situations, the computer systems 120 and 130 may be considered as being integrated in a single payment processing system (e.g., if the two financial institutions are the same). As will be appreciated, in a situation where the mobile wallet computing system 120 has many users, some users may have all their mobile wallet source accounts at the same bank that operates the mobile wallet computer system 120, some users may have all their mobile wallet source accounts at a bank other than the same bank that operates the mobile wallet computer system 120, and some users may have some of their mobile wallet source accounts at the same bank that operates the mobile wallet computer system 120 and other of their mobile wallet source accounts at a bank other than the bank that operates the mobile wallet computer system 120.

The merchant computer system 140 may be used at a point of sale location to conduct transactions with the account holder. For example, the merchant computer system 140 may include a point of sale computer system such as a cash register system connected to a central server system operated by the merchant. As another example, the merchant computer system 140 may include a mobile computing device (e.g., smart phone, tablet PC, etc.) operated by a store clerk as the clerk moves throughout the store. Again, the mobile computing device in such an embodiment may connect to a central server system operated by the merchant.

The merchant computer system 140 includes network interface logic 142, a code scanner 144, location indicator logic 146, fund requesting logic 148, and fund receiving logic 149. In one embodiment, the network interface logic 142 is configured to allow the merchant computer system 140 to communicate with the network 140. The network interface logic 142 sends and receives data from the mobile device 110 and the mobile wallet bank computer system 120.

The code scanner 144 may be configured to scan codes, such as but not limited to, optically scanned or non-optically scanned codes. In the embodiment of the present disclosure, the code scanner 204 scans one or more types of codes. After receiving the code, the scanner 144 determines the information that was incorporated into the code by the mobile device 110 or the mobile wallet bank computer system 120 that generated the code, as described below.

The location indicator logic 146 provides an indication of the geographic location of the code scanner 144. In one embodiment, the location indicator logic 146 may be programmed with the known address of the merchant location as the location of the code scanner, such that the location of the merchant can be compared with the location of the mobile device 110 as part of authenticating a transaction.

The fund requesting logic 148 communicates a fund request via the network interface logic 142 to the acquirer/processor computer system 145. In some embodiments, the fund requesting logic 148 may send the tokenized card number (that includes an issuer identification number (T N), trace ID (generated numbers), checksum helper digit, last 4 digits of the actual card number) received from the user to the acquirer/processor computer system 145. In response to receiving a tokenized card number, the acquirer processor computer system 145 sends the tokenized card number to the mobile wallet bank computer system 120, which in turn sends the actual card number and a trace ID (embedded within the issuer discretionary field) to the acquirer processor computer system 145. The fund receiving logic 149 determines when payment has been received by the merchant computer system 140 and allocates the payment accordingly.

The merchant computer system 140 may further connect to or integrate with other hardware. For example, in one embodiment, the merchant computer system 140 may connect to a card reader for reading credit cards, debit cards, stored value cards, and so on. As another example, the merchant computer system 140 may be configured to prompt the user to provide a random security code. The random security code may be generated by the mobile device 110, by a separate security dongle, or in another manner. The security code may be provided to the merchant computer system 140 directly by the mobile device, may be keyed into the merchant computer system 140 (e.g., by a store clerk), or may be received in another manner.

The acquirer processor computer system 145 includes a computer system that transmits and receives messages from the mobile wallet bank computer system 120, the merchant computer system 140, or the payment system 150. In various embodiments, the acquirer processor computer system 145 may receive the tokenized card information and route the received information to the mobile wallet bank computer system 120. In other embodiments, the acquirer processor computer system 145 may receive the actual card information from the mobile wallet bank computer system 120 with the trace ID embedded within the issuer discretionary field in track 2 format. In some embodiments, the acquirer processor computer system 145 may transmit the actual card information with the trace ID to the payment system 150. In various embodiments, the acquirer processor computer system 145 may process the payment in the mobile wallet system described herein.

In other embodiments, and as previously noted, the acquirer processor computer system 145 may instead route the tokenized card information with the trace ID number to payment system 150. In turn, the payment system 150 may provide the substitute card number to the mobile wallet computer system 120, which, after authenticating the transaction, may then return the actual card number to the payment system 150. The payment system 150 may then provide the actual card number to a source account computer system 130 for payment processing.

The payment system 150 may comprise at least one card network 152. In some embodiments, the payment system comprises multiple card networks 152, such as Visa®, MasterCard®, American Express®, Discover®, Diners Club®, etc. In such an embodiment, the appropriate card network 152 may be determined based on the first digit of the actual account number (i.e., “4” corresponding to Visa®, “5” corresponding to Mastercard®, “6” corresponding to Discover®, and so on). The acquirer processor computer system 145 may therefore route the transaction to the appropriate card network 152 based on the first digit of the substitute credit card number. The card network 152 may then route the substitute card number to the mobile wallet computer system 145 based on the issuer identification number (IIN). For example, the card network 152 may identify the credit card number provided by the acquirer processor computer system 145 as being a substitute credit card number and not an actual credit card number based on the TIN. In one embodiment, this identification occurs based on the TIN being a card network-owned TIN that has been licensed to the mobile wallet bank and that has been designated by the mobile wallet bank and the card network for use in mobile wallet transactions. In such an arrangement, the acquirer processor computer system 145 processes the transaction like any other credit card transaction, and it is not necessary for the acquirer processor computer system 145 to be aware that the transaction is a mobile wallet transaction. Given the relatively limited number of card networks (e.g., Visa®, MasterCard®, American Express®, Discover®, Diners Club®, etc.), and given the much larger number of acquirer/processors, such an arrangement has the technical benefit of reducing modifications to existing computer systems to implement the features described herein. In other embodiments, this identification is made based on an indication from the merchant computer system 140 and/or the acquirer processor computer system 145 that the transaction is a mobile wallet transaction. Based on the TIN, the card network 152 may transmit the substitute card number to the mobile wallet computer system in turn receive the actual card number, expiration date, and authentication code (e.g., cvv, etc.) from the mobile wallet bank computer system 120.

The payment processing system 100 may further include additional bank computer systems that may allow the mobile wallet platform of the present disclosure to be accessed by consumers and merchants that bank at various different banking institutions. The additional bank computer systems may provide the services described herein through multiple banks, allowing for broader adoption of the mobile wallet platform.

FIG. 2 illustrates a process 200 that may be implemented by the system in FIG. 1. When a user wishes to make a payment at a merchant, for example, the user may access the mobile wallet client application 116 by entering a PIN or other login credentials and then selecting a “pay now” or similar button. For example, the user may be located at a merchant location and may wish to pay for a good or service. As another example, the user may be located away from the merchant location or be engaged in an online transaction.

At step 201, the mobile device 110 requests access to funds in the mobile wallet via the mobile wallet bank computer system 120 to pay for a good or service. The mobile device 110 may provide a PIN, a customer ID, and a device ID to the mobile wallet bank computer system 120. The user may be identified and authenticated based on a match of these three data elements with information stored in the mobile wallet bank computer system 120. Further, the user's mobile wallet account information may be located/determined.

Next, at step 202, the mobile wallet bank computer system 120 may generate a tokenized credit card number as described in greater detail below. The tokenized credit card number may include a few generated numbers and a few numbers from the actual credit card number. In one embodiment, the tokenized credit number starts with an issuer identification number (IIN) that corresponds to the mobile wallet bank computer system 120, ends with the last four digits of the actual credit card account number of the credit card that is being used in the transaction, and further includes intervening digits including a trace ID and a checksum helper digit. The trace ID is described in further detail below and allows for enhanced authentication during the payment process. The may permit checksum verification of the tokenized credit card number. Various checksum algorithms may be used to verify that the tokenized credit card number is a valid credit card number.

The tokenized credit card number may be transmitted to the mobile device 110 in the form of a code. For example, the data may be encoded in accordance with the track 1 and/or track 2 formats used in the magnetic stripes of credit cards. In some embodiments, the code is formatted in Track 2 format. In either case, the primary account number field may contain the tokenized credit card number and the issuer discretionary field may contain the payment token. In yet other embodiments, another format is used.

At step 203, the tokenized credit card number is transmitted to the mobile device 110. If the mobile wallet bank computer system 120 and the source account computer system 130 are different computer systems (e.g., if the user is using a credit card that is provided by a different bank than the bank the operates the mobile wallet computer system 120), then the trace ID may also be sent to the source account computer system 130 at step 203.

At step 205, the mobile device 110 may display or otherwise transmit the tokenized credit card number to merchant computer system 140 (e.g., using a QR code, NFC, wireless, Bluetooth, low energy Bluetooth, RFID, hypersonic, Wi-Fi, cellular 3G, 4G, GSM, LiFi, or other method). At step 207, after receiving the tokenized card number, the merchant computer system 140 sends the transaction to an acquirer processor computer system 145 for processing.

Next, at step 209, the acquirer processor computer system 145 sends the tokenized card number to the mobile wallet bank computer system 120. After receiving the request from the acquirer processor computer system 145, the mobile wallet bank computer system 120 may determine the actual card number and send the actual card number back to the acquirer processor at step 211. In one embodiment, the determination of the actual card number may occur by searching for the account information associated with the payment token and/or trace ID within the tokenized card number. Additionally, the trace ID from the tokenized card number may be sent with the actual card number at step 211. At this point, the issuer discretionary field is no longer need for the payment token, hence, the trace ID may be sent to the acquirer processor computer system 145 in the issuer discretionary field.

At step 212, the acquirer processor computer system 145 sends the actual card number and the trace ID to the payment system 150 for processing a payment. The payment system 150 sends the actual card number with the trace ID and the transaction amount to the source account bank computer system 130 at step 213. The source account bank computer 130 may retrieve the trace ID that was received from the mobile wallet bank computer system 120 by searching for the actual card number that was received from the payment system 150. The source account bank computer 130 may compare the trace ID that was received/stored at step 203 with the trace ID that was received from the payment system 150 at step 213. Assuming there is a match, the source account bank computer 130 may issue an approval for the transaction. After verifying the actual card number and the trace ID in the issuer discretionary field, the source account bank computer system 130 may send an approval to the payment system 150 at step 215. The approval message may be sent from the payment system 150, to acquirer processor computer system 145, to the point of sale system 140, in steps 217 and 219. Upon receiving the approval message the point of sale system 140 may generate a receipt for the user. In some embodiments, the receipt may be sent to the mobile device 110 electronically. In other embodiments, the receipt may be printed physically at the point of sale location. The receipt may include the last four digits of the actual credit card account number of the credit card that was used in the transaction.

The use of the payment token and trace ID as described herein allows for two levels of authentication. The payment token is generated by the mobile wallet computer system at step 202. The payment token is then transmitted to the mobile device 110, then to the merchant computer system 140, then to the acquirer processor computer system 145, and eventually back to the mobile wallet computer system 120 where it is matched with the original payment token generated at step 202. Similarly, the Trace ID is also generated by the mobile wallet computer system at step 202, and then transmitted to the mobile device 110, then to the merchant computer system 140, then to the acquirer processor computer system 145, and eventually back to the mobile wallet computer system 120 where it is matched with the Trace ID generated at step 202. In the case of the Trace ID, however, the Trace ID is then further transmitted back to the acquirer processor computer system 145, then to the payment system 150, and then to the source account computer system 130 where it is matched with the Trace ID generated at step 202. Accordingly, the trace ID used in conjunction with the tokenized credit card number allows both the mobile wallet bank computer system 140 and the source account bank computer system 130 to authenticate the transaction. Using the trace ID in the above described manner may permit the source account bank computer system 130 and the mobile wallet bank computer system 120 to verify the trace ID at least twice prior to approving a transaction and transferring funds. Further, and as described in greater detail below, the trace ID may be used by the source account computer system 130 to determine whether the credit card transaction was a mobile wallet transaction (e.g., as opposed to an in-person card-present transaction involving use of the user's physical credit card, as opposed to an online transaction, and so on). Hence, the source account bank computer system 130 may provide a different customer experience to the mobile wallet user. The source account bank computer system 130 may also determine risk differently for transactions that use a mobile wallet.

In some embodiments, instead of embedding the trace ID in a tokenized credit card account number at step 202, the actual credit card number is transmitted to the mobile device 110 and the merchant computer system 140. In such an embodiment, the trace ID may be included in the issuer discretionary field at step 202, and the payment token may be communicated in another manner or another payment matching mechanism may be used. The trace ID may be stored in the issuer discretionary field and may travel though the payment processing system, until it is verified by the source account bank computer system 130. After being verified by the source account bank computer system 130, the transaction may be approved and the funds may be transferred from the source account bank computer system to the acquirer processor computer system 145. In other embodiments, the same financial institution may own the source account bank computer system 130 and the mobile wallet bank computer system 120.

Referring now to FIG. 3 and FIGS. 3A-3F, FIG. 3 is a flow chart of a process 300 detailing a user registration process and a token generation process during registration, according to an example embodiment. FIGS. 3A-3F are screens that may be displayed to the user during the process 300 of FIG. 3 according to an example embodiment. Process 300 may be executed by a mobile device 110 and a mobile wallet bank computer system 120 that is configured to create and manage a mobile wallet account. Process 300 may be executed for a user who wishes to start a mobile wallet account 125 for a source account 135. In the example of FIG. 3, it is assumed that the user has an account at the bank that operates the mobile wallet computer system 140. As will be appreciated, a similar process may be used for users that have accounts only at other banks.

As previously indicated in connection with FIG. 1, a user may perform the registration via an online banking website of the mobile wallet bank. For example, as shown in FIG. 3A, a user may select a button 301 for an online banking application on the mobile device 110.

After the button 301 is selected, the user may be presented with a screen as shown in FIG. 3B. Process 300 includes receiving user authentication information into the mobile wallet bank computer system 120 using existing financial institution credentials (step 302). Existing credentials may include, for example, a username and password combination or card information (card number, account number, expiration date, CVV) for an online banking website of the bank that operates the mobile wallet computer system 120. For example, in FIG. 3B, the credentials are entered in fields 303 and 305, respectively, of a login screen to the online banking website. In one embodiment, the credentials may match keyboard-entered credentials that are used to access the source account via online banking. In other embodiments, the credentials may match other types of authentication credentials that are used to access online banking (e.g., facial recognition on a captured image or video of the user on a camera of the mobile device, voice or speech recognition captured by an input device of the mobile device, fingerprint authentication, etc.). After providing online banking login credentials as shown in FIG. 3B, the user may be taken to a top-level online banking screen as shown in FIG. 3C. The screen shown in FIG. 3C shows an overview of accounts and account balances held by the user.

Process 300 further includes initiating a registration process for a mobile wallet account with the user (step 304). Step 304 includes receiving a user indication to create a new mobile wallet account. In some embodiments, the user may be presented with a menu option on his or her mobile device to create a new mobile wallet account, among other options. For example, in the top-level screen shown in FIG. 3C, a button 327 is provided that allows the user to receive additional information about the mobile wallet application. After selecting the button 327 in FIG. 3C, the user may be taken to a mobile wallet introductory screen as shown in FIG. 3D. In the screen shown in FIG. 3D, the user is provided with an option to tour the mobile wallet application and with an option to initiate the mobile wallet registration. Upon selecting button 329, the mobile wallet registration process is initiated. After selecting the button 329 in FIG. 3D, the user may be taken to a first screen for the mobile wallet registration as shown in FIG. 3E.

Process 300 further includes receiving user account information (step 306). Receiving the user account information may include prompting the user to provide mobile wallet login credentials, e.g., a PIN number associated with a debit card or credit card held by the user at the bank. For example, in FIG. 3E, the user enters a PIN number in field 331. The user may also be prompted to identify the source account(s) the user wishes to associate with the mobile wallet account. For example, the user may enter information about accounts held at other banks that may serve as source accounts. In other embodiments, the user may be presented with various fields on the mobile device that allow the user to select one or more source accounts held by the user, to enter account information (e.g., an account number) in one or more fields, or otherwise. For example, as shown in FIG. 3F, the user may be presented with a list 333 of accounts the user has with a particular source account bank computer system, and may choose one or more accounts to view account information and to select the account for use with the mobile wallet account. Thus, the mobile wallet may auto-provision the existing accounts of the user to the mobile wallet, without the user having to manually enter the 16-digit credit card account number or other account information (e.g., in the case of other types of financial accounts). The user may further provide information to create a user profile including other information as warranted. In some embodiments, the mobile wallet computer system 120 may establish a connection with the computer systems 130 of other financial institutions, such that the accounts held by the user at the other financial institutions may be auto-provisioned to the mobile wallet as well. In both cases, the user may be provided with information about current account balances regarding the accounts.

Process 300 further includes generating a customer token and device token (step 308), and sending the customer token and device token to the mobile device of the user (step 310). The customer token and device token may be tokens that identify the user and the associated mobile device to the mobile wallet bank computer system in the future. The tokens are encrypted by the mobile wallet bank computer system and provided to the mobile device. The mobile device stores the tokens for future use. In one example embodiment, each time the user accesses the mobile wallet system with a new mobile device 110, the mobile device is assigned its own device token. A device and customer token are stored on each device in order to bind the device to the user (one device can only have one wallet user, but one user can have multiple devices). Once a mobile device for mobile wallet account is registered, the user only needs to enter their existing PIN to access their mobile wallet from the registered device (which PIN may be typically eight characters or less and consist only of numbers). The full login credentials associated with online banking are not needed (which often consist of a combination of lower case letters, upper case letters, numbers, and special characters (e.g., punctuation marks)). Instead, possession by the user of the registered device provides an additional level of authentication that avoids the need for full login credentials. Additionally, it may be noted that the level of functionality available the user through the mobile wallet may be less than the level of functionality available to the user through the full online banking website, thereby providing further risk mitigation.

Process 300 further includes receiving a default payment method from the user (step 312) and completing the registration (step 314). Step 314 may include a user accepting terms and conditions associated with use of the mobile wallet account. The default payment method may indicate how a user wishes to normally pay for a particular transaction. For example, the user may provide options relating to how to manage overdrafts, whether the total payment should be provided in one or more payments, or otherwise. Process 300 may include storing the default payment method (step 316) in the profile database of the mobile wallet bank computer system 120 (or another database of the mobile wallet bank computer system). The default payment method may be recalled by the mobile wallet bank computer system 120 during a future payment process.

Process 300 may also include generating and sending an offline code token to the source account bank computer system. The offline code may be used by the payment processing system, and more particularly the source account bank computer system, to execute a payment for the user when the mobile device is offline, or for other account management purposes. In some embodiments, the mobile device may store one or more offline codes to provide to the merchant. The mobile device 110 may not contact the mobile wallet bank computer system 120 and may provide the code to the merchant computer system 140.

As will be appreciated, the arrangement of FIG. 3 facilitates keeping the list of source accounts that is up to date and accurate to the user. For example, each time a transaction is to be performed, the mobile wallet computer system 120 may access a list of accounts held by the user at the mobile wallet bank. In some cases, an account that was previously active may no longer be active. For example, a user may have reported a physical credit card associated with a credit card account as having been lost or stolen. Prior to presenting a list of available source accounts to the user in the context of a particular transaction, the mobile wallet computer system 120 may determine that a previously-provisioned source account is no longer available as a source of funds. Hence, when the mobile wallet computer system 120 generates a screen display to present to the user via a mobile device showing the list of accounts held by the user at the financial institution, the previously-provisioned source account that is no longer available as a source of funds may be excluded from the list. When the list of available source accounts is presented to the user, the user may select a new source account for the transaction. For example, if the credit card account was the user's default payment method, the user may select a new default payment method (e.g., an existing demand deposit account).

Additionally, the arrangement may also permit new accounts to be activated and added to the mobile wallet, e.g., a new card account, a new savings account, a new line of credit, and so on. In the case of a new card account, the new card account may, for example, be a new credit card account, a new demand deposit account with a debit card, or an existing demand deposit account with a new debit card.

For example, in the case of a lost or stolen credit card, the bank may create a new credit card account in replacement of the credit card account for which the physical credit card was reported as having been lost or stolen. When the mobile wallet computer system 120 accesses the list of accounts held by the user, the mobile wallet computer system 120 may identify the new credit card account as being an account that has not yet been provisioned to the mobile wallet. When the screen display is generated showing the list of accounts held by the user, the list may then include the new credit card account, which may be selected by the user for provisioning to the mobile wallet. Again, the new credit card account may be provisioned to the mobile wallet without any manual entry by the user of account information regarding the new credit card account (other than the selection of the new credit card account by the user, indicating that the user wishes to add the new credit card account to the mobile wallet).

In the case of a new credit card account, the bank may issue a new credit card account immediately upon learning of the lost or stolen credit card associated with the previous credit card account. Typically, the bank may then mail the user a new physical/plastic credit card. Upon receiving the new physical credit card, the user may then activate the new credit card, e.g., by calling a credit card activation phone number printed on a sticker that has been placed on the card.

In some embodiments, the user may be provided with the option of activating the new credit card account through the mobile wallet. For example, the bank may perform a first activation of the new credit card account for purposes of transactions implemented via a mobile wallet. Such an activation may be performed via the mobile wallet itself (i.e., the user does not need to take any action outside of the mobile wallet to have the new credit card account activated). For example, the user may be prompted with a message indicating that the credit card account has not yet been activated, and querying whether the user wishes to do so no (e.g., “Click ‘Yes’ to activate your new credit card for your mobile wallet”). For security purposes, the first activation does not activate the credit card for non-mobile wallet transactions involving use of the plastic credit card. Rather, the bank may also perform a second activation of the new credit card account for purposes of transactions implemented via a physical credit card associated with the new credit card account. Hence, the plastic credit card is not useable for credit card transactions until the second activation occurs. Such an arrangement ensures that the user is in possession of the physical credit card before the physical credit card is activated for purposes of transactions implemented via the physical credit card (e.g., a card-present transaction at a bricks and mortar merchant).

As will be appreciated, it may often take several days or more for a new physical credit card to be produced and delivered to the user after the user reports a previous credit card as having been lost or stolen. In the arrangement described herein, the credit card account may be activated for mobile wallet transactions much earlier, before the credit card is activated for the non-mobile wallet transactions involving use of the plastic credit card. For example, the credit card account may be activated one or more days before the user receives the plastic credit card, or even within one day of the bank receiving the report from the user that the plastic credit card has been lost or stolen. In some embodiments, the new credit card account may be activated for the mobile wallet within one hour or less of receiving the report from the user that the plastic credit card has been lost or stolen.

In other embodiments, when a credit card is reported as lost or stolen, the mobile wallet computer system 120 may permit the user to continue using the credit card number associated with the plastic credit card for mobile wallet transactions, but prevent the plastic credit card from being used for card-based transactions. When a physical credit card is lost or stolen, the physical credit card has been compromised. However, for purposes of the mobile wallet bank computer system 120, the account number is simply an account identifier. So long as the mobile wallet has not been compromised, the mobile wallet computer system 120 can ensure the integrity of the transaction based on the fact that the user is in possession of the mobile device 110, particularly in situations where at a point of sale a tokenized card number is used, anyway (e.g., as described above in connection with FIG. 2).

Referring now to FIG. 4 and FIGS. 4A-4D, FIG. 4 is a flow chart of a process 400 detailing a payment code generation process for an authenticated mobile wallet session, according to an example embodiment. FIGS. 4A-4D are screens that may be displayed to the user during the process 400 of FIG. 4 according to an example embodiment. Process 400 may be executed for a user requesting to execute a payment (e.g., transaction) with a merchant or other recipient 140. Process 400 may be executed by a mobile wallet bank computer system 120 configured to manage the user mobile wallet account.

FIG. 4A shows a mobile banking screen that may be displayed to the user after the mobile wallet application has been installed on the mobile device 110. Similar to FIG. 3B, the user is prompted in FIG. 4A to provide full online banking login credentials (fields 323 and 325). By providing such credentials in fields 323 and 325, the user may be provided with the full functionality of the online banking website. However, in FIG. 4A, the user is also provided with a second option, namely to provide mobile wallet login credentials (via selecting button 425). Hence, in FIG. 4A, the user is presented with two possible authentication paths, a first authentication path that prompts the user to provide online banking login credentials to gain access to online banking, and a second authentication path that prompts the user to provide mobile wallet login credentials to gain access to the mobile wallet. If the user selects the second authentication path, the user is delivered to the more payment-focused functionality of the mobile wallet.

Process 400 includes receiving a PIN from the user (step 402) to authenticate the user (FIG. 4B). At step 402 the mobile wallet client application 116 prompts the user for a PIN that was used during the registration steps in process 300. Hence, as previously indicated, the user may be authenticated based on the user's mobile wallet banking credentials (e.g., 4 digit PIN), rather than being prompted to provide the user's usual online banking authentication credentials (username and password).

In an alternative embodiment, a user may log into a mobile banking session with a source account bank computer system, or the user may directly access the mobile wallet bank computer system. Process 400 further includes allowing the user access to his or her mobile wallet account (step 404). For example, the user may access his or her mobile wallet account through his or her account at the source account bank computer system, or may log into his or her mobile wallet account at the mobile wallet bank computer system by providing a PIN or other identifier to the mobile wallet bank computer system.

Process 400 further includes validating the user based on the customer token and device token (step 406). When the user logs in to access his or her mobile wallet account, the customer token and device token stored on the mobile device (stored during step 310 of process 300) are provided to the mobile wallet bank computer system. The mobile wallet bank computer system validates the user and/or the mobile device for use with the mobile wallet account. Step 406 may further include validating the user based on the PIN or other identifier also provided to the mobile wallet bank computer system. For example, in order to be validated, the customer token, the device token, and the PIN may all need to match (i.e., be associated with each other in the mobile wallet computer system 120). As previously indicated, each user may have one customer token and one PIN which together are associated with multiple device tokens (such that the user can access the mobile wallet account from multiple devices).

Process 400 further includes generating a new device token (step 408), and sending the new device token to the mobile device of the user (step 410). Hence, in some embodiments, the device token may change each time the user uses the device. The device token may be a token that will identify the user and the associated mobile device to the mobile wallet bank computer system in the future. More particularly, the device token may identify a current session of the user. In other words, the token may be used to identify a particular function that the user may perform during the session, such as initiating a purchase. The token is encrypted by the mobile wallet bank computer system and provided to the mobile device. The mobile device stores the device token for future use.

Process 400 further includes receiving an indication that the user wishes to execute a payment or other transaction (step 412). Upon the indication, the mobile wallet bank computer system generates a code (e.g., a QR code) based on the user's default payment method (step 414) (FIG. 4C). The QR code is generated including a combination of random digits and account information of the user. For example, the QR code may include the last four digits of a debit card or credit card number of an account associated with the user and the request. The account information may be used to identify a source account for the transaction at a later step in the transaction. The mobile wallet bank computer system 120 may use token information (e.g., customer token and device token information) from the mobile device to identify the mobile wallet account and associated source account to use in code generation. The code may provide credit card data or tokenized credit card data in Track 1 or Track 2 format, as described below with reference to FIGS. 5-7. The generated code is then provided as part of a payment token to the mobile device and/or to the merchant or other recipient of the payment or funds (step 416) (FIG. 4D).

Referring to FIGS. 5-6, codes that may be sent during operation of the system 100 are shown. As previously indicated, information embedded in the codes may be embedded in a Track 1 format and Track 2. The code may be sent optically as a code or in another manner. As will be appreciated, the code formats shown in FIGS. 5-6 are example code formats that may be used with the systems and methods described herein. In other embodiments, other formats may be used.

The Track 1 format in FIG. 5 is shown to include 76 digits and the Track 2 format in FIG. 6 is shown to include 38 digits. Each format may generally include a format code (digit 1), tokenized primary account number 501 (digits 2-20), a field separator (digit 21), an expiration date 505 (digits 35-38 in Track 1, digits 22-25 in Track 2), a service code (digits 39-41 or 26-28), and a payment token 507 (digits 42-76 or 29-38). Each track may additionally or alternatively include other fields representing different data to be embedded in the code. In one embodiment (the Track 1 format), the credit card data may include a customer name or other customer identifier (e.g., in digits 22-33 of the Track 1 format).

In various embodiments of the present disclosure, account information associated with the user's mobile wallet account may be represented in the code using digits 2 through 20 of the Track 1 or Track 2 format. This is shown in FIGS. 5-6 as the tokenized primary account number (TPAN). Referring also to FIG. 8, the TPAN format is shown in greater detail.

As shown in FIG. 7, the first six digits of the TPAN may represent an issuer identification number (IIN) that is used to route the TPAN to the appropriate mobile wallet bank computer system 120. The IIN is a predetermined number issued to each bank for financial institution for routing fund transfer requests. In the present configuration, an TIN that is associated with the bank that operates the mobile wallet computer system 120 may be used.

Digits 7 through 15 of the TPAN may represent a Trace ID, and digits 16 through 19 may represent account information (e.g., the last four digits of an actual account number, or other account information). First generating random numbers for digits 7 through 14 may create the Trace ID. The Trace ID may be used for verifying and approving a user initiated transaction. Once those digits are determined, then digit 15 may be calculated. Digit 15 is calculated such that digit 19 may be used as the checksum digit of the tokenized card number or the code. In other words, even though digit 19 is fixed (as part of the actual card number of the account), digit 19 may be used as the checksum digit, because digit 15 is calculated in such a way to allow the code to pass the error detection process. Digits 1-19 from FIG. 7 map to digits 2-20 in FIGS. 5 and 6. For example, digits 2-20 of FIGS. 5 and 6 may include the IIN, Trace ID, pseudo check digit, last 4 digits of the card number as shown in FIG. 7.

The checksum digit is used for error detection purposes (e.g., to detect errors in manually inputted data that is included in the code). For example, the checksum digit is used to help detect single digit errors, errors where digits are transposed, twin errors, etc. The checksum digit may then be used in one of several algorithms for checking for errors in the code. It should be appreciated that one of any type of checksum algorithm may be used with the embodiment described herein.

In other embodiments, a digit other than digit 15 may be used as the calculated digit. For example, any eight of the nine digits between digit 7 and 15 may be randomized, and the remaining digit may be used as the “checksum helper” digit (e.g., the digit calculated to make digit 19 the checksum digit).

Referring also to FIG. 8, actual card number is sent in Track 2 format that may be generated at step 810 is shown in greater detail. As compared to the QR code of FIGS. 5-7, the trace ID is moved to digits 26-33, and the actual account number may be provided as digits 2 through 17. In other words, a subset of the original token generated by the mobile wallet bank computer system is moved into a discretionary field of the new generated token. The code is shown to generally include the trace ID and account number, along with an expiration date field (e.g., with the same digits as determined in an earlier process of creating the original token) and a service code field. The code may optionally include any other type of information.

In various embodiments, using the trace ID may allow the financial institution to identify mobile wallet transactions. Upon identifying the mobile wallet transactions, the financial institution may segment the mobile wallet transactions for risk, customer service, security, and card not present transactions. In other embodiments, the transactions that were performed using mobile wallet bank computer system 120 each use a trace identification number and the user may be charged a different fee for such transactions. In various embodiments, when a user of a mobile wallet account loses their credit card or debit card and the financial institution issues the user a new credit card or debit card, the mobile wallet may be able to auto provision the newly issued cards. Auto provisioning may allow the user to use the mobile wallet account prior to receiving and/or activating the credit or debit card. In other embodiments, in the case of mobile wallet fraud, the mobile wallet account of the user may be reset.

A credit card may be used to pay for a transaction at a point of sale location using the physical credit card, known as a credit card present transaction. A credit card may be used when a credit card is not physically located at a merchant location, such as but not limited to, an online merchant transaction where the credit card information is entered in an online transaction. A financial institution may rank the risk of fraud for each type of transaction. In some embodiments, the financial institution may assign a higher risk rating to a credit card that is not present at the merchant location than a credit card present transaction. In various embodiments, a mobile wallet that performs a transaction at a merchant location may be considered more secure than a physical credit card because the mobile wallet does not provide the merchant the actual credit card number and the mobile wallet does not have the actual credit card number. Accordingly, the financial institution may determine that a transaction was a mobile wallet transaction based on the trace ID and rate the transaction to be more secure or fraud resistant than card present transaction. The financial institution may create a new risk rating that is of a lower risk for mobile wallet transactions. In some embodiments, the transactions that are performed using a mobile wallet may be charged different fee because of the risk rating. In various embodiments, due to the reduction of risk the mobile wallet transactions may be charged a lower fee than card present or card not present transactions.

FIG. 9 illustrates a process 900 that may be implemented by the system in FIG. 1. In various embodiments, process 900 may be used when an account holder reports their physical card lost or stolen via telephone, Internet, mobile device, etc. In some embodiments, process 900 may allow the account holder to perform one or more transactions using the mobile wallet stored on a mobile device, even after the physical card has been lost or stolen. Some advantages of process 900 may include the account retaining the use of the account even after the loss of a physical card. Additional advantages may include the account holder being able to activate the newly issued replacement card by using the mobile wallet functionality.

At step 903, the financial institution computer system may receive a message from the user that the physical card is lost or stolen. In various embodiments, the account holder may contact the financial institution computer system using various communication methods, such as but not limited to, telephone, Internet, and mobile device. Upon receiving the message from the account holder that the physical card is lost or stolen, the financial institution computer system may ask the account holder whether the mobile wallet account has also been compromised. After receiving input from the account holder that the mobile wallet account holder has not been compromised, the financial institution computer system may deactivate the physical card account, at step 905. In some embodiments, the financial institution computer system may assign the uncompromised mobile wallet account to a temporary account to allow the account holder to conduct transactions using the mobile wallet.

In various embodiments, the financial institution computer system may receive a request for a transaction from a merchant, at step 907. At step 909, the financial institution computer system determines whether the transaction is being performed by a mobile wallet or whether the transaction is being performed by the physical card information. Since the mobile wallet transaction is performed using at least a trace ID, the financial institution computer system may differentiate between the mobile wallet transaction and the physical card information transaction.

Upon determining that the transaction request is not from a mobile wallet or is using the actual card information, the financial institution computer system may deny the transaction request, at step 911. The financial institution computer system would be able to avoid any fraudulent transactions using the actual card information by denying the transaction request that did not originate from a mobile wallet associated with the account.

When the financial institution computer system determines that the transaction request originated from a mobile wallet account, the financial institution may determine whether a new replacement card number has been issued to the account holder at step 913. If a new replacement card number has not been issued, the financial institution may approve the transaction at step 915 based on the determination that the transaction is a mobile wallet transaction and based on the fact that the mobile wallet account has not been compromised. In some embodiments, the transaction may be approved using the temporary card number discussed above.

In various embodiments, when the financial institution has issued a new card, but account holder has not activated the physical card because the account holder has not received the card or other reasons, the financial institution may update its records with respect to the mobile wallet. For example, at step 917, the financial institution computer system may update its records to associate the new card number with the mobile wallet account of the previous card number at step 917. After step 917, the financial institution may send an approval for the transaction request at step 919. In other embodiments, the mobile wallet client application on the mobile device 110 may prompt the user to activate the card prior to the user having received the physical card. In other embodiments, even after receiving the card the account holder may wish to activate the card via the mobile wallet application. Activating the card by the account holder, may update the financial institution settings to associate the new card number with the mobile wallet account number.

FIG. 10 illustrates a payment process that may be implemented by the system in FIG. 1 according to an example embodiment. Except as otherwise described below, the payment process of FIG. 10 is the same as the payment process of FIG. 2. Hence, the above discussion with respect to FIG. 2 applies to FIG. 10 as well, except as otherwise described below.

In the embodiment of FIG. 10, rather than providing the substitute card number to the mobile wallet computer system 120 (as in FIG. 2), the acquirer processor computer system 145 provides the substitute card number to a card network computer system 152. Hence, a tokenized card number may be generated and ultimately delivered to the acquirer processor computer system 145 at steps 1001, 1003, 1005, 1007 in the manner described above in connection with steps 201, 203, 205, 207.

Next, at step 1009, the acquirer processor computer system 145 sends the tokenized card number to the card network computer system 152. Next, at step 1011, the card network computer system 152 sends the tokenized card number to the mobile wallet bank computer system 120. After receiving the request from the card network computer system 152, the mobile wallet bank computer system 120 may determine the actual card number and send the actual card number back to the acquirer processor at step 1012. In one embodiment, the determination of the actual card number may occur by searching for the account information associated with the payment token and/or trace ID within the tokenized card number. Additionally, the trace ID from the tokenized card number may be sent with the actual card number at step 1012, similar to step 211. Again, at this point, the issuer discretionary field is no longer needed for the payment token, hence, the trace ID may be sent to the acquirer processor computer system 145 in the issuer discretionary field.

At step 1013, the card network computer system 152 sends the actual card number and the trace ID to the source account computer system 130 for processing a payment. The source account bank computer 130 may retrieve the trace ID that was received from the mobile wallet bank computer system 120 by searching for the actual card number that was received from the payment system 150. The source account bank computer 130 may compare the trace ID that was received/stored at step 1003 with the trace ID that was received from the payment system 150 at step 1013. Assuming there is a match, the source account bank computer 130 may issue an approval for the transaction. After verifying the actual card number and the trace ID in the issuer discretionary field, the source account bank computer system 130 may send an approval to the payment system 150 at step 1015. Steps 1017, 1019, and 1021 may be performed in the same manner as discussed above in connection with steps 217, 219, and 221.

As discussed above in connection with FIG. 2, the use of the payment token and trace ID as described herein allows for two levels of authentication. The payment token is generated by the mobile wallet computer system at step 1002. The payment token is then transmitted to the mobile device 110, then to the merchant computer system 140, then to the acquirer processor computer system 145, then to the card network computer system 152, and eventually back to the mobile wallet computer system 120 where it is matched with the original payment token generated at step 1002. Similarly, the Trace ID is also generated by the mobile wallet computer system at step 1002, and then transmitted to the mobile device 110, then to the merchant computer system 140, then to the acquirer processor computer system 145, then to the card network computer system 152, and eventually back to the mobile wallet computer system 120 where it is matched with the Trace ID generated at step 1002. In the case of the Trace ID, however, the Trace ID is then further transmitted back to the payment system 150, and then to the source account computer system 130 where it is matched with the Trace ID generated at step 1002. Accordingly, the trace ID used in conjunction with the tokenized credit card number allows both the mobile wallet bank computer system 140 and the source account bank computer system 130 to authenticate the transaction. Using the trace ID in the above described manner may permit the source account bank computer system 130 and the mobile wallet bank computer system 120 to verify the trace ID at least twice prior to approving a transaction and transferring funds. Further, as previously discussed, the trace ID may be used by the source account computer system 130 to determine whether the credit card transaction was a mobile wallet transaction (e.g., as opposed to an in-person card-present transaction involving use of the user's physical credit card, as opposed to an online transaction, and so on). In other embodiments, the mobile wallet computer system 120 generates a tokenized card number, but does not embed a trace ID in the tokenized card number.

In some embodiments, instead of embedding the trace ID in a tokenized credit card account number at step 1002, the actual credit card number is transmitted to the mobile device 110 and the merchant computer system 140. In such an embodiment, the trace ID may be included in the issuer discretionary field at step 1002, and the payment token may be communicated in another manner or another payment matching mechanism may be used. The trace ID may be stored in the issuer discretionary field and may travel though the payment processing system, until it is verified by the source account bank computer system 130. After being verified by the source account bank computer system 130, the transaction may be approved and the funds may be transferred from the source account bank computer system to the acquirer processor computer system 145. In other embodiments, the same financial institution may own the source account bank computer system 130 and the mobile wallet bank computer system 120. Hence, as previously described in connection with the discussion of FIG. 2, the tokenized card account number and trace ID features may each be used alone or in combination with each other.

The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions. Software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features specific to particular implementations. Certain features described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated in a single software product or packaged into multiple software products embodied on tangible media.

Thus, particular implementations of the subject matter have been described. Other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.

The claims should not be read as limited to the described order or elements unless stated to that effect. It should be understood that various changes in form and detail may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims. All implementations that come within the spirit and scope of the following claims and equivalents thereto are claimed.

Claims

1. A computer-implemented method, comprising: providing, by a computer system operated by a first institution, a mobile wallet on a mobile device of a user;generating, by the computer system, a customer token regarding the user;generating, by the computer system, a device token regarding the mobile device;encrypting and sending, by the computer system to the mobile device, the customer token regarding the user and the device token regarding the mobile device;receiving, by the computer system, a user credential associated with a second institution;accessing, by the computer system based on the received user credential associated with the second institution, information regarding an account of the user at the second institution;automatically provisioning, by the computer system, the account of the user at the second institution to the mobile wallet;providing, by the computer system, tokenized account information associated with the provisioned account to the mobile wallet;receiving, by the computer system, an input of a login credential associated with the first institution from the mobile device;receiving, by the computer system, an indication of an initiation of a mobile wallet transaction;validating and identifying, by the computer system, the user based on the received login credential and the customer token stored on the mobile device responsive to receiving the indication of the initiation of the mobile wallet transaction;validating, by the computer system, the mobile wallet of the mobile device based on the device token stored on the mobile device responsive to receiving the indication of the initiation of the mobile wallet transaction; andtransferring, by the computer system, funds from the provisioned account to a recipient as part of the mobile wallet transaction responsive to validating the user and the mobile wallet.
2. The method of claim 1, wherein the account of the user at the second institution comprises at least one of a credit card account or a demand deposit account, and wherein transferring, by the computer system, funds from the provisioned account to the recipient includes transferring funds from the at least one of the credit card account or the demand deposit account to the recipient.
3. The method of claim 1, further comprising: generating, by the computer system, a screen display regarding the provisioned account; andtransmitting, by the computer system, the screen display to the mobile device of the user.
4. The method of claim 3, wherein generating, by the computer system, the screen display includes showing a current account balance for the provisioned account.
5. The method of claim 1, wherein the first institution and the second institution are different.
6. The method of claim 1, wherein the funds are transferred from the provisioned account of the user at the second institution based on the login credential associated with the first institution.
7. The method of claim 1, wherein the login credential associated with the first institution is different than the login credential associated with the second institution.
8. The method of claim 1, further comprising: by the computer system, a tokenized card number identifying the account of the user associated with the second institution within a primary account number field of a code, the code in track 1 or track 2 format;identifying, by the computer system, the account of the user associated with the second institution based on the embedded tokenized card number; andsending, by the computer system, the code to the mobile device.
9. A computer system operated by a first institution, the computer system comprising: one or more processors; anda non-transitory machine-readable media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: providing a mobile wallet on a mobile device of a user;generating a customer token regarding the user;generating a device token regarding the mobile device;encrypting and sending to the mobile device the customer token regarding the user and the device token regarding the mobile device;receiving a user credential associated with a second institution;accessing information regarding an account of the user at the second institution;automatically provisioning the account of the user at the second institution to the mobile wallet;providing tokenized account information associated with the provisioned account to the mobile wallet;receiving an indication of an initiation of a mobile wallet transaction from the mobile device;validating and identifying the user based on the received customer token stored on the mobile device responsive to receiving the indication of the initiation of the mobile wallet transaction;validating the mobile wallet of the mobile device based on the device token stored on the mobile device responsive to receiving the indication of the initiation of the mobile wallet transaction; andtransferring funds from the provisioned account to a recipient as part of the mobile wallet transaction responsive to validating the user and the mobile wallet.
10. The computer system of claim 9, wherein the account of the user at the second institution comprises at least one of a demand deposit account or a credit card account, and wherein transferring funds from the provisioned account to the recipient includes transferring funds from the at least one of the demand deposit account or the credit card account to the recipient.
11. The computer system of claim 9, wherein the operations further comprise: generating a screen display regarding the provisioned account; andtransmitting the screen display to the mobile device of the user.
12. The computer system of claim 11, wherein generating the screen display includes showing a current account balance for the provisioned account.
13. The computer system of claim 9, wherein the first institution and the second institution are different.
14. The computer system of claim 9, wherein receiving the indication of the initiation of the mobile wallet transaction includes receiving an input of a login credential associated with the first institution from the mobile device, wherein the funds are transferred from the provisioned account of the user at the second institution based on the login credential associated with the first institution.
15. The computer system of claim 14, wherein the login credential associated with the first institution is different than the user credential associated with the second institution.
16. The computer system of claim 9, wherein the operations further comprise: embedding a tokenized card number within a primary account number field of a code, the code being in track 1 or track 2 format;identifying the account based on the embedded tokenized card number; andsending the code to the mobile device.
17. A mobile device, comprising: a display device;a processor coupled to the display device and a computer readable medium, the computer readable medium having instructions stored thereon that, when executed by the processor, cause the processor to: receive a customer token regarding a user associated with the mobile device;receive a device token regarding the mobile device;receive, via the display device, a selection of an account of the user associated with an institution to provision to a mobile wallet;receive tokenized account information associated with the selected account;provide the customer token and the device token to a mobile wallet computer system; andreceive a request for a mobile wallet transaction, the request comprising an indication to transfer funds from the selected account to a recipient.
18. The mobile device of claim 17, wherein the customer token and the device token are stored on the mobile device, wherein the customer device token validates the user and the device token validates the mobile device.
19. The mobile device of claim 17, wherein the instructions, when executed by the processor, further cause the processor to: provide, via the display device, a message indicating an amount of funds to be transferred from the selected account to the recipient as part of the mobile wallet transaction.
20. The mobile device of claim 17, wherein the instructions, when executed by the processor, further cause the processor to: provide, via the display device based on a transferring of funds from the selected account to the recipient, a confirmation message indicating completion of the mobile wallet transaction.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 14/501,880, filed on Sep. 30, 2014, titled “Mobile Wallet Account Provisioning Systems and Methods,” which is a continuation-in-part application of U.S. application Ser. No. 14/266,580, filed Apr. 30, 2014, titled “Mobile Wallet Using Tokenized Card Systems and Methods,” both of which are incorporated by reference herein in their entireties.

US Referenced Citations (576)

Number	Name	Date	Kind
5412192	Hoss	May 1995	A
5778067	Jones et al.	Jul 1998	A
6016484	Williams et al.	Jan 2000	A
6018724	Arent	Jan 2000	A
6353811	Weissman	Mar 2002	B1
6615194	Deutsch et al.	Sep 2003	B1
6865547	Brake et al.	Mar 2005	B1
6873974	Schutzer	Mar 2005	B1
7287695	Wankmueller	Oct 2007	B2
7395243	Zielke et al.	Jul 2008	B1
7398919	Cooper	Jul 2008	B2
7765481	Dixon et al.	Jul 2010	B2
7774274	Jones et al.	Aug 2010	B2
7822206	Birk et al.	Oct 2010	B2
7827057	Walker et al.	Nov 2010	B1
7909243	Merkow et al.	Mar 2011	B2
7930225	Wahlberg et al.	Apr 2011	B2
7945776	Atzmony et al.	May 2011	B1
7958049	Jamison et al.	Jun 2011	B2
7970669	Santos	Jun 2011	B1
8019365	Fisher	Sep 2011	B2
8078140	Baker et al.	Dec 2011	B2
8126806	Dimartino et al.	Feb 2012	B1
8160959	Rackley et al.	Apr 2012	B2
8215560	Granucci et al.	Jul 2012	B2
8280788	Perlman	Oct 2012	B2
8332290	Venturo et al.	Dec 2012	B1
8401904	Simakov et al.	Mar 2013	B1
8433657	Dinan	Apr 2013	B2
8452257	Granucci et al.	May 2013	B2
8467766	Rackley et al.	Jun 2013	B2
8468587	Blinn et al.	Jun 2013	B2
8489067	Rackley, III et al.	Jul 2013	B2
8504699	Vaughan et al.	Aug 2013	B2
8533123	Hart	Sep 2013	B2
8538845	Liberty	Sep 2013	B2
8548908	Friedman	Oct 2013	B2
8548926	Balistierri et al.	Oct 2013	B2
8555361	Nakhjiri et al.	Oct 2013	B2
8566237	Forzley	Oct 2013	B2
8566239	Arthur et al.	Oct 2013	B2
8571953	Gopalakrishnan et al.	Oct 2013	B2
8577803	Chatterjee et al.	Nov 2013	B2
8589290	Baskerville	Nov 2013	B2
8615468	Varadarajan	Dec 2013	B2
8626632	Dolan et al.	Jan 2014	B1
8627424	O'Malley et al.	Jan 2014	B1
8635131	Saunders	Jan 2014	B1
8639621	Ellis et al.	Jan 2014	B1
8645971	Carlson et al.	Feb 2014	B2
8676704	Ledbetter et al.	Mar 2014	B2
8682802	Kannanari	Mar 2014	B1
8700729	Dua	Apr 2014	B2
8706628	Phillips	Apr 2014	B2
8725576	Fisher	May 2014	B2
8725577	Fisher	May 2014	B2
8732080	Karim	May 2014	B2
8744966	Amacker et al.	Jun 2014	B1
8750901	Gupta et al.	Jun 2014	B1
8762265	Kessler et al.	Jun 2014	B2
8762270	Evans et al.	Jun 2014	B1
8768830	Jorgensen et al.	Jul 2014	B1
8768834	Zacarias et al.	Jul 2014	B2
8774781	Speiser et al.	Jul 2014	B1
8781955	Schamer et al.	Jul 2014	B2
8831677	Villa-Real	Sep 2014	B2
8838501	Priebatsch	Sep 2014	B1
8843125	Kwon et al.	Sep 2014	B2
8843417	Hammad	Sep 2014	B2
8880432	Collins, Jr.	Nov 2014	B2
8924246	Chen et al.	Dec 2014	B1
8925805	Grigg et al.	Jan 2015	B2
8930271	Ellis et al.	Jan 2015	B1
8972297	Kay et al.	Mar 2015	B2
8977251	Grigg et al.	Mar 2015	B2
8989712	Wentker et al.	Mar 2015	B2
9020836	Fisher et al.	Apr 2015	B2
9026460	Grigg et al.	May 2015	B2
9027109	Wolberg-Stok et al.	May 2015	B2
9031880	Bishop et al.	May 2015	B2
9037509	Ellis et al.	May 2015	B1
9043240	Langus et al.	May 2015	B2
9043605	Machani	May 2015	B1
9098190	Zhou et al.	Aug 2015	B2
9111266	Kessler et al.	Aug 2015	B2
9117242	Ellis et al.	Aug 2015	B1
9177307	Ross et al.	Nov 2015	B2
9195984	Spector et al.	Nov 2015	B1
9208488	Liberty	Dec 2015	B2
9208528	Chelst et al.	Dec 2015	B2
9218624	Moghadam	Dec 2015	B2
9256876	Vasant Akole et al.	Feb 2016	B2
9286606	Diamond	Mar 2016	B2
9317849	Pitroda et al.	Apr 2016	B2
9324068	Soundararajan	Apr 2016	B2
9361616	Zhou et al.	Jun 2016	B2
9424572	Bondesen et al.	Aug 2016	B2
9473491	Johansson et al.	Oct 2016	B1
9652770	Kurani et al.	May 2017	B1
9659312	Ellis et al.	May 2017	B1
9691058	Epler et al.	Jun 2017	B2
9704157	Ellis et al.	Jul 2017	B1
9741051	Carpenter et al.	Aug 2017	B2
9785934	Davis et al.	Oct 2017	B2
9805363	Rudnick et al.	Oct 2017	B1
9928518	Vippagunta et al.	Mar 2018	B1
9972047	Elliott et al.	May 2018	B1
10019740	Simantov et al.	Jul 2018	B2
10115112	Fordyce, III	Oct 2018	B2
10121129	Kalgi	Nov 2018	B2
10140615	Carpenter et al.	Nov 2018	B2
10169812	Bajgier et al.	Jan 2019	B1
10223710	Purves et al.	Mar 2019	B2
10235668	Ellis et al.	Mar 2019	B1
10242368	Poole	Mar 2019	B1
10380583	Ellis et al.	Aug 2019	B1
10380596	Butler et al.	Aug 2019	B1
10395247	Gilliam et al.	Aug 2019	B2
10402897	Czyzewski et al.	Sep 2019	B1
10445739	Sahni et al.	Oct 2019	B1
10467615	Omojola et al.	Nov 2019	B1
10515356	Cronic et al.	Dec 2019	B2
10565558	Fredericks et al.	Feb 2020	B2
10586236	Pourfallah et al.	Mar 2020	B2
10600128	Graham et al.	Mar 2020	B2
10817950	Iqbal et al.	Oct 2020	B1
10853787	Mango	Dec 2020	B1
10887301	Vera et al.	Jan 2021	B1
10997592	Kurani	May 2021	B1
11042882	Ledford et al.	Jun 2021	B2
11068866	Hecht et al.	Jul 2021	B1
11144902	Gaddam et al.	Oct 2021	B2
11151546	Mossoba et al.	Oct 2021	B2
11210715	Lindsey et al.	Dec 2021	B2
11228660	Rapaka et al.	Jan 2022	B2
11288660	Kurani	Mar 2022	B1
11295294	Kurani	Apr 2022	B1
11334579	Quade et al.	May 2022	B1
11416766	Chao et al.	Aug 2022	B2
11422393	Stray et al.	Aug 2022	B2
11436581	Walker et al.	Sep 2022	B1
20020032602	Lanzillo et al.	Mar 2002	A1
20020052852	Bozeman	May 2002	A1
20020062249	Iannacci	May 2002	A1
20020198829	Ludwig et al.	Dec 2002	A1
20030028481	Flitcroft et al.	Feb 2003	A1
20030040964	Lacek	Feb 2003	A1
20030055785	Lahiri	Mar 2003	A1
20030056096	Albert et al.	Mar 2003	A1
20040088349	Beck et al.	May 2004	A1
20040230535	Binder et al.	Nov 2004	A1
20040236632	Maritzen et al.	Nov 2004	A1
20040254848	Golan et al.	Dec 2004	A1
20040260646	Berardi et al.	Dec 2004	A1
20050021401	Postrel	Jan 2005	A1
20050043997	Sahota et al.	Feb 2005	A1
20050077350	Courtion et al.	Apr 2005	A1
20050086492	Nicodemus et al.	Apr 2005	A1
20050125317	Winkelman et al.	Jun 2005	A1
20050125668	Botz	Jun 2005	A1
20050133590	Rettenmyer et al.	Jun 2005	A1
20050138377	First et al.	Jun 2005	A1
20050184145	Law et al.	Aug 2005	A1
20050235363	Hibbard et al.	Oct 2005	A1
20060129502	Pastusiak et al.	Jun 2006	A1
20060229985	Lalwani et al.	Oct 2006	A1
20060235795	Johnson et al.	Oct 2006	A1
20060253335	Keena et al.	Nov 2006	A1
20070125840	Law	Jun 2007	A1
20070168354	Ramer et al.	Jul 2007	A1
20070170243	Desany et al.	Jul 2007	A1
20070174873	Griggs	Jul 2007	A1
20070198432	Pitroda	Aug 2007	A1
20070199061	Byres et al.	Aug 2007	A1
20070244811	Tumminaro	Oct 2007	A1
20070250923	M'Raihi	Oct 2007	A1
20080005006	Tritt et al.	Jan 2008	A1
20080006685	Rackley, III et al.	Jan 2008	A1
20080033878	Krikorian et al.	Feb 2008	A1
20080040265	Rackley, III et al.	Feb 2008	A1
20080127317	Nakhjiri	May 2008	A1
20080203152	Hammad et al.	Aug 2008	A1
20080208742	Arthur et al.	Aug 2008	A1
20080242274	Swanburg et al.	Oct 2008	A1
20080243701	Von Mueller	Oct 2008	A1
20080294556	Anderson	Nov 2008	A1
20080319887	Pizzi et al.	Dec 2008	A1
20090027191	Farah et al.	Jan 2009	A1
20090043695	Hickey	Feb 2009	A1
20090048971	Hathaway et al.	Feb 2009	A1
20090076950	Chang et al.	Mar 2009	A1
20090106558	Delgrosso et al.	Apr 2009	A1
20090157531	Bui	Jun 2009	A1
20090177563	Bernstein et al.	Jul 2009	A1
20090192873	Marble	Jul 2009	A1
20090228384	Melik-Aslanian et al.	Sep 2009	A1
20090228966	Parfene et al.	Sep 2009	A1
20090271287	Halpern	Oct 2009	A1
20090319409	Omidyar	Dec 2009	A1
20090319427	Gardner et al.	Dec 2009	A1
20090327010	Vadhri	Dec 2009	A1
20090327151	Carlson et al.	Dec 2009	A1
20100057553	Ameiss et al.	Mar 2010	A1
20100082481	Lin et al.	Apr 2010	A1
20100114724	Ghosh et al.	May 2010	A1
20100114731	Kingston et al.	May 2010	A1
20100114733	Collas et al.	May 2010	A1
20100125495	Smith et al.	May 2010	A1
20100125510	Smith et al.	May 2010	A1
20100131415	Sartipi	May 2010	A1
20100191602	Mikkelsen et al.	Jul 2010	A1
20100205077	Hammad	Aug 2010	A1
20100274655	Postrel	Oct 2010	A1
20100280896	Postrel	Nov 2010	A1
20100325048	Carlson et al.	Dec 2010	A1
20100332386	Vancini et al.	Dec 2010	A1
20110055080	Ahlers et al.	Mar 2011	A1
20110071914	Beasley et al.	Mar 2011	A1
20110106601	Perlman et al.	May 2011	A1
20110106674	Perlman	May 2011	A1
20110137797	Stals et al.	Jun 2011	A1
20110145149	Valdes et al.	Jun 2011	A1
20110153397	Wagenheim	Jun 2011	A1
20110153498	Makhotin et al.	Jun 2011	A1
20110154466	Harper et al.	Jun 2011	A1
20110191160	Blackhurst et al.	Aug 2011	A1
20110196782	Allen et al.	Aug 2011	A1
20110251892	Laracey	Oct 2011	A1
20110270665	Kim et al.	Nov 2011	A1
20110270748	Graham et al.	Nov 2011	A1
20110270749	Bennett et al.	Nov 2011	A1
20110276489	Larkin	Nov 2011	A1
20110289004	Prakash et al.	Nov 2011	A1
20110295748	Woodriffe	Dec 2011	A1
20110295749	Scalisi	Dec 2011	A1
20110302084	Melik-Aslanian et al.	Dec 2011	A1
20110313918	Lawson et al.	Dec 2011	A1
20120011063	Killian et al.	Jan 2012	A1
20120018511	Hammad	Jan 2012	A1
20120022944	Volpi	Jan 2012	A1
20120078735	Bauer et al.	Mar 2012	A1
20120078751	MacPhail et al.	Mar 2012	A1
20120084210	Farahmand	Apr 2012	A1
20120110634	Jakobsson	May 2012	A1
20120130731	Canetto	May 2012	A1
20120130887	Meckling	May 2012	A1
20120143705	Bhattacharya et al.	Jun 2012	A1
20120150669	Langley et al.	Jun 2012	A1
20120150687	Hart	Jun 2012	A1
20120158589	Katzin et al.	Jun 2012	A1
20120185317	Wong	Jul 2012	A1
20120185387	Doyle	Jul 2012	A1
20120192254	Garcia Perez et al.	Jul 2012	A1
20120196586	Grigg et al.	Aug 2012	A1
20120197793	Grigg et al.	Aug 2012	A1
20120197794	Grigg et al.	Aug 2012	A1
20120209749	Hammad et al.	Aug 2012	A1
20120233005	White	Sep 2012	A1
20120239417	Pourfallah et al.	Sep 2012	A1
20120253852	Pourfallah et al.	Oct 2012	A1
20120253913	Richard	Oct 2012	A1
20120254021	Wohied et al.	Oct 2012	A1
20120271705	Postrel	Oct 2012	A1
20120271712	Katzin et al.	Oct 2012	A1
20120284130	Lewis et al.	Nov 2012	A1
20120284195	McMillen et al.	Nov 2012	A1
20120290376	Dryer et al.	Nov 2012	A1
20120296720	Pirillo	Nov 2012	A1
20120301774	Jiang et al.	Nov 2012	A1
20120303425	Katzin et al.	Nov 2012	A1
20120310774	Chassin	Dec 2012	A1
20120323717	Kirsch	Dec 2012	A1
20120323762	Kapur et al.	Dec 2012	A1
20120330837	Persaud et al.	Dec 2012	A1
20130006848	Kuttuva	Jan 2013	A1
20130013499	Kalgi	Jan 2013	A1
20130013509	Perlman et al.	Jan 2013	A1
20130018777	Klein	Jan 2013	A1
20130018786	Sher	Jan 2013	A1
20130018791	Mendicino et al.	Jan 2013	A1
20130018792	Casey et al.	Jan 2013	A1
20130024364	Shrivastava et al.	Jan 2013	A1
20130030941	Meredith et al.	Jan 2013	A1
20130042261	Tavormina et al.	Feb 2013	A1
20130046697	Schibuk	Feb 2013	A1
20130054336	Graylin	Feb 2013	A1
20130054454	Purves et al.	Feb 2013	A1
20130060679	Oskolkov et al.	Mar 2013	A1
20130060689	Oskolkov et al.	Mar 2013	A1
20130060696	Martin et al.	Mar 2013	A1
20130060708	Oskolkov et al.	Mar 2013	A1
20130065555	Baker et al.	Mar 2013	A1
20130073365	McCarthy	Mar 2013	A1
20130073459	Zacarias et al.	Mar 2013	A1
20130074168	Hao et al.	Mar 2013	A1
20130080241	Fisher	Mar 2013	A1
20130080323	Scipioni	Mar 2013	A1
20130110628	Yeo et al.	May 2013	A1
20130110658	Lyman et al.	May 2013	A1
20130132854	Raleigh et al.	May 2013	A1
20130143089	Teshima et al.	Jun 2013	A1
20130144663	Qawami et al.	Jun 2013	A1
20130144702	Tabor et al.	Jun 2013	A1
20130151400	Makhotin et al.	Jun 2013	A1
20130166332	Hammad	Jun 2013	A1
20130168450	Von Mueller et al.	Jul 2013	A1
20130173456	Grigg et al.	Jul 2013	A1
20130173474	Ranganathan et al.	Jul 2013	A1
20130179336	Lyons et al.	Jul 2013	A1
20130179352	Dwyre et al.	Jul 2013	A1
20130185167	Mestre et al.	Jul 2013	A1
20130191227	Pasa et al.	Jul 2013	A1
20130191277	O'Leary et al.	Jul 2013	A1
20130191278	O'Leary et al.	Jul 2013	A1
20130200999	Spodak et al.	Aug 2013	A1
20130204785	Monk et al.	Aug 2013	A1
20130226720	Ahluwalia et al.	Aug 2013	A1
20130226751	Friedholm et al.	Aug 2013	A1
20130226799	Raj	Aug 2013	A1
20130232032	Chaturvedi et al.	Sep 2013	A1
20130238455	Laracey	Sep 2013	A1
20130246258	Dessert	Sep 2013	A1
20130246260	Barten et al.	Sep 2013	A1
20130246261	Purves et al.	Sep 2013	A1
20130246265	Al-Sahli	Sep 2013	A1
20130254028	Salci	Sep 2013	A1
20130254102	Royyuru	Sep 2013	A1
20130254114	Smith	Sep 2013	A1
20130254115	Pasa et al.	Sep 2013	A1
20130260734	Jain et al.	Oct 2013	A1
20130262309	Gadotti	Oct 2013	A1
20130262316	Hruska	Oct 2013	A1
20130262317	Collinge et al.	Oct 2013	A1
20130275250	Rodell et al.	Oct 2013	A1
20130282588	Hruska	Oct 2013	A1
20130290121	Simakov et al.	Oct 2013	A1
20130290169	Bathula et al.	Oct 2013	A1
20130290176	Tirumalashetty	Oct 2013	A1
20130297425	Wallaja	Nov 2013	A1
20130297486	Colborn	Nov 2013	A1
20130297513	Kirillin et al.	Nov 2013	A1
20130304559	Stone et al.	Nov 2013	A1
20130304642	Campos	Nov 2013	A1
20130317928	Laracey	Nov 2013	A1
20130317984	O'Leary et al.	Nov 2013	A1
20130332344	Weber	Dec 2013	A1
20130332353	Aidasani et al.	Dec 2013	A1
20130346302	Purves et al.	Dec 2013	A1
20140006129	Heath	Jan 2014	A1
20140006194	Xie et al.	Jan 2014	A1
20140006276	Grigg et al.	Jan 2014	A1
20140006277	Rao	Jan 2014	A1
20140012750	Kuhn et al.	Jan 2014	A1
20140019352	Shrivastava	Jan 2014	A1
20140019360	Yang	Jan 2014	A1
20140038546	Neal et al.	Feb 2014	A1
20140040139	Brudnicki et al.	Feb 2014	A1
20140052617	Chawla et al.	Feb 2014	A1
20140058855	Hussein et al.	Feb 2014	A1
20140058936	Ren et al.	Feb 2014	A1
20140058938	McClung, III	Feb 2014	A1
20140067677	Ali et al.	Mar 2014	A1
20140074581	Johnson et al.	Mar 2014	A1
20140074637	Hammad	Mar 2014	A1
20140074655	Lim et al.	Mar 2014	A1
20140074724	Gordon et al.	Mar 2014	A1
20140081783	Paranjape et al.	Mar 2014	A1
20140081854	Sanchez et al.	Mar 2014	A1
20140089171	Gandhi	Mar 2014	A1
20140089195	Ward et al.	Mar 2014	A1
20140096215	Hessler	Apr 2014	A1
20140100975	Van	Apr 2014	A1
20140101034	Tanner et al.	Apr 2014	A1
20140101048	Gardiner et al.	Apr 2014	A1
20140108254	Lee	Apr 2014	A1
20140108263	Ortiz et al.	Apr 2014	A1
20140109200	Tootill et al.	Apr 2014	A1
20140114856	Jung et al.	Apr 2014	A1
20140118704	Duelli et al.	May 2014	A1
20140122310	Torrens et al.	May 2014	A1
20140122563	Singh et al.	May 2014	A1
20140129357	Goodwin	May 2014	A1
20140129433	Rosenberger	May 2014	A1
20140129442	Hanson et al.	May 2014	A1
20140136352	Ramakrishna et al.	May 2014	A1
20140143089	Campos et al.	May 2014	A1
20140180849	Kimberg et al.	Jun 2014	A1
20140188586	Carpenter et al.	Jul 2014	A1
20140188704	Grossman et al.	Jul 2014	A1
20140188718	Grossman et al.	Jul 2014	A1
20140188719	Poornachandran et al.	Jul 2014	A1
20140201086	Gadotti et al.	Jul 2014	A1
20140207680	Rephlo	Jul 2014	A1
20140210321	Dixon	Jul 2014	A1
20140214640	Mallikarjunan et al.	Jul 2014	A1
20140222670	Concannon	Aug 2014	A1
20140236792	Pant et al.	Aug 2014	A1
20140244506	Gramling	Aug 2014	A1
20140249948	Graylin et al.	Sep 2014	A1
20140250003	Levchin et al.	Sep 2014	A1
20140258135	Park et al.	Sep 2014	A1
20140279097	Alshobaki et al.	Sep 2014	A1
20140279459	Weiss et al.	Sep 2014	A1
20140279469	Mendes	Sep 2014	A1
20140279489	Russell et al.	Sep 2014	A1
20140279559	Smith et al.	Sep 2014	A1
20140279566	Verma et al.	Sep 2014	A1
20140282068	Levkovitz et al.	Sep 2014	A1
20140297435	Wong	Oct 2014	A1
20140297520	Levchin et al.	Oct 2014	A1
20140297524	Ravindranath et al.	Oct 2014	A1
20140304095	Fisher	Oct 2014	A1
20140304187	Menn	Oct 2014	A1
20140310173	Caldwell	Oct 2014	A1
20140310182	Cummins	Oct 2014	A1
20140337175	Katzin et al.	Nov 2014	A1
20140337621	Nakhimov	Nov 2014	A1
20140344153	Raj et al.	Nov 2014	A1
20140347265	Aimone et al.	Nov 2014	A1
20140351072	Wieler et al.	Nov 2014	A1
20140351126	Priebatsch	Nov 2014	A1
20140351130	Cheek et al.	Nov 2014	A1
20140365322	Phillips	Dec 2014	A1
20140365363	Knudsen et al.	Dec 2014	A1
20140376576	Jespersen et al.	Dec 2014	A1
20140379576	Marx et al.	Dec 2014	A1
20150019944	Kalgi	Jan 2015	A1
20150026049	Theurer et al.	Jan 2015	A1
20150032626	Dill et al.	Jan 2015	A1
20150032627	Dill et al.	Jan 2015	A1
20150035643	Kursun	Feb 2015	A1
20150039462	Shastry et al.	Feb 2015	A1
20150046241	Salmon et al.	Feb 2015	A1
20150046339	Wong et al.	Feb 2015	A1
20150066790	Desanti	Mar 2015	A1
20150074774	Nema et al.	Mar 2015	A1
20150088633	Salmon et al.	Mar 2015	A1
20150089568	Sprague et al.	Mar 2015	A1
20150095075	Breuer et al.	Apr 2015	A1
20150095219	Hurley	Apr 2015	A1
20150100442	Van Heerden et al.	Apr 2015	A1
20150100495	Salama et al.	Apr 2015	A1
20150112781	Clark et al.	Apr 2015	A1
20150120472	Aabye et al.	Apr 2015	A1
20150121063	Maller et al.	Apr 2015	A1
20150134514	Chan et al.	May 2015	A1
20150134540	Law et al.	May 2015	A1
20150137938	Slaby et al.	May 2015	A1
20150140960	Powell et al.	May 2015	A1
20150154588	Purves et al.	Jun 2015	A1
20150178693	Solis	Jun 2015	A1
20150178725	Poetsch	Jun 2015	A1
20150186855	Bennett et al.	Jul 2015	A1
20150186872	Sobol et al.	Jul 2015	A1
20150186875	Zhang et al.	Jul 2015	A1
20150186886	Schwalb et al.	Jul 2015	A1
20150186952	Brown et al.	Jul 2015	A1
20150187021	Moring et al.	Jul 2015	A1
20150193745	Handwerger et al.	Jul 2015	A1
20150193869	Del Vecchio et al.	Jul 2015	A1
20150213435	Douglas et al.	Jul 2015	A1
20150220914	Purves et al.	Aug 2015	A1
20150229622	Grigg et al.	Aug 2015	A1
20150237026	Kumar	Aug 2015	A1
20150242987	Lee et al.	Aug 2015	A1
20150254660	Allison et al.	Sep 2015	A1
20150254698	Bondesen et al.	Sep 2015	A1
20150254699	Bondesen et al.	Sep 2015	A1
20150278799	Palanisamy	Oct 2015	A1
20150278816	Fleishman et al.	Oct 2015	A1
20150287015	Kaplinger et al.	Oct 2015	A1
20150287037	Salmon et al.	Oct 2015	A1
20150319158	Kumnick	Nov 2015	A1
20150324768	Filter et al.	Nov 2015	A1
20150332252	Shahrokhi et al.	Nov 2015	A1
20150333964	Wang et al.	Nov 2015	A1
20150339662	Huang et al.	Nov 2015	A1
20150339663	Lopreiato et al.	Nov 2015	A1
20150339671	Krietzman et al.	Nov 2015	A1
20150348029	Van Os et al.	Dec 2015	A1
20150363810	Kim et al.	Dec 2015	A1
20150371212	Giordano et al.	Dec 2015	A1
20150371234	Huang et al.	Dec 2015	A1
20150371326	Montesano et al.	Dec 2015	A1
20160004876	Bye et al.	Jan 2016	A1
20160012465	Sharp	Jan 2016	A1
20160026999	Kurian	Jan 2016	A1
20160042341	Griffin et al.	Feb 2016	A1
20160042344	Thimmana et al.	Feb 2016	A1
20160048828	Lee	Feb 2016	A1
20160048929	Parento et al.	Feb 2016	A1
20160054336	Anderberg et al.	Feb 2016	A1
20160063496	Royyuru et al.	Mar 2016	A1
20160065370	Le Saint et al.	Mar 2016	A1
20160071071	Lazay	Mar 2016	A1
20160071074	Baird	Mar 2016	A1
20160071096	Rosca	Mar 2016	A1
20160071097	Lazay	Mar 2016	A1
20160071099	Lazay	Mar 2016	A1
20160071109	Lazay	Mar 2016	A1
20160071110	Lazay	Mar 2016	A1
20160086170	Hurt et al.	Mar 2016	A1
20160086179	Barbier	Mar 2016	A1
20160092696	Guglani et al.	Mar 2016	A1
20160092866	Liberty et al.	Mar 2016	A1
20160092868	Salama et al.	Mar 2016	A1
20160092874	O'Regan et al.	Mar 2016	A1
20160125396	Brickell et al.	May 2016	A1
20160125409	Meredith et al.	May 2016	A1
20160125417	Huang et al.	May 2016	A1
20160132875	Blanco et al.	May 2016	A1
20160132884	Fridman et al.	May 2016	A1
20160140555	Scipioni	May 2016	A1
20160140561	Cowan	May 2016	A1
20160162882	McClung, III	Jun 2016	A1
20160162889	Badenhorst	Jun 2016	A1
20160180305	Dresser et al.	Jun 2016	A1
20160269416	Camenisch et al.	Sep 2016	A1
20160283925	Lavu et al.	Sep 2016	A1
20160342962	Brown et al.	Nov 2016	A1
20160342992	Lee	Nov 2016	A1
20160343043	Hicks et al.	Nov 2016	A1
20160379215	Clerkin	Dec 2016	A1
20170017958	Scott et al.	Jan 2017	A1
20170061402	Mobin et al.	Mar 2017	A1
20170061406	Adams et al.	Mar 2017	A1
20170061438	Patel	Mar 2017	A1
20170164139	Deselaers et al.	Jun 2017	A1
20170178110	Swanson et al.	Jun 2017	A1
20170185989	Bozovich, Jr.	Jun 2017	A1
20170193468	Chougule et al.	Jul 2017	A1
20170228715	Gurunathan	Aug 2017	A1
20170236118	Laracey	Aug 2017	A1
20170337542	Kim et al.	Nov 2017	A1
20170357969	Huang et al.	Dec 2017	A1
20170364914	Howard	Dec 2017	A1
20180007052	Quentin	Jan 2018	A1
20180012203	Hall	Jan 2018	A1
20180032981	Shanmugam et al.	Feb 2018	A1
20180047016	Sarin	Feb 2018	A1
20180068308	Gupta et al.	Mar 2018	A1
20180082283	Sharma	Mar 2018	A1
20180096428	Gorenstein	Apr 2018	A1
20180157336	Harris et al.	Jun 2018	A1
20180219863	Tran	Aug 2018	A1
20180285836	Enobakhare	Oct 2018	A1
20180322488	Arana et al.	Nov 2018	A1
20180324204	McClory et al.	Nov 2018	A1
20180365675	Sivaraman	Dec 2018	A1
20180374076	Wheeler	Dec 2018	A1
20190108505	Perlman	Apr 2019	A1
20190122222	Uechi	Apr 2019	A1
20190220908	Wilkes	Jul 2019	A1
20190236577	Schmid et al.	Aug 2019	A1
20190280863	Meyer et al.	Sep 2019	A1
20190304029	Murray et al.	Oct 2019	A1
20190385250	Bhattacharjee et al.	Dec 2019	A1
20200005277	Prabhu et al.	Jan 2020	A1
20200028753	Powar et al.	Jan 2020	A1
20200034813	Calinog et al.	Jan 2020	A1
20200051117	Mitchell	Feb 2020	A1
20200097957	Driggs et al.	Mar 2020	A1
20200151706	Mossoba et al.	May 2020	A1
20200175496	Finke et al.	Jun 2020	A1
20200219060	Fredericks et al.	Jul 2020	A1
20200279305	Mossoba et al.	Sep 2020	A1
20210056552	Murray	Feb 2021	A1
20210110392	Lacoss-Arnold et al.	Apr 2021	A1
20210158333	Cohen et al.	May 2021	A1
20210166260	Ho et al.	Jun 2021	A1
20210358754	Masuoka et al.	Nov 2021	A1
20210398179	Kolaja et al.	Dec 2021	A1
20220027873	Pathuri et al.	Jan 2022	A1
20220101609	Hu et al.	Mar 2022	A1
20220147967	Clark	May 2022	A1
20220210209	Vanbuskirk et al.	Jun 2022	A1

Foreign Referenced Citations (22)

Number	Date	Country
2002-312554	Oct 2002	JP
20090014076	Feb 2009	KR
WO-2011100529	Aug 2011	WO
WO-2011113121	Sep 2011	WO
WO-2012139003	Oct 2012	WO
WO-2013079793	Jun 2013	WO
WO-2014012138	Jan 2014	WO
WO-2014111888	Jul 2014	WO
WO-2014134180	Sep 2014	WO
WO-2014207615	Dec 2014	WO
WO-2014210321	Dec 2014	WO
WO-2015016780	Feb 2015	WO
WO-2015023172	Feb 2015	WO
WO-2015054697	Apr 2015	WO
WO-2016009198	Jan 2016	WO
WO-2016053975	Apr 2016	WO
WO-2016097879	Jun 2016	WO
WO-2016153977	Sep 2016	WO
WO-2016172107	Oct 2016	WO
WO-2016196054	Dec 2016	WO
WO-2017106309	Jun 2017	WO
WO-2018005798	Jan 2018	WO

Non-Patent Literature Citations (41)

Entry
“Cashcloud Mobile eWallet”, FinTech Forum Exchange, Jul. 1, 2016. 4 pages.
“Cashcloud mobile eWallet”, Popote Payments, www.popotepayments.com, 2016. 6 pages.
A Smart Card Alliance Payments Council White Paper; Publication date: Sep. 2011; Publication No. PC-11002; 191 Clarksville Rd. Princeton Junction, NJ 08550 www.smartcardalliance.org (Year: 2011).
EMV, “Payment Tokenisation Specification Technical Framework”, 2014 EMVCO, LLC. 84 pages.
How to Control Children's Spending on Debit Cards \| Money \| by Jill Paperworth, May 10, 2009, https:www.theguardian.com/money/2009/mar/.../children-debit-cards-online-spend . . . (Year: 2009).
Kyrillidis, Mayes, Markantonakis; Card-present Transactions on the Internet Using the Smart CardWeb Server; 2013, IEEE; 12th (Year: 2013).
Lehdonvirta et al., UbiPay: Minimizing Transaction Costs with Smart Mobile Payments, Proceedings of the 6th International Conference on Mobile Technology, Application & Systems, ACM, Jan. 2009, retrieved from the Internet at http://www.researchgate.net/profile/Tatsuo_Nakajima/publication/220982951_UbiPay_minimizing_transaction_costs_with_smart_mobile_payments/links/548e9dad0cf225bf66a607bb.pdf on Oct. 30, 2015, 8 pages.
N. C. Kiran and G. N. Kumar, “Reliable OSPM schema for secure transaction using mobile agent in micropayment system,” 2013 Fourth International Conference on Computing, Communications and Networking Technologies (ICCCNT), 2013, pp. 1-6, doi: 10.1109/ICCCNT.2013,6726503. (Year: 2013).
P. De, K. Dey, V. Mankarand S. Mukherjea, “Towards an interoperable mobile wallet service,” 2013 10th International Conference and Expo on Emerging Technologies fora Smarter World (CEWIT), 2013, pp. 1-6, doi: 1109/CEWIT.2013.6713767. (Year: 2013).
Ron White, How Computers Work, Oct. 15, 2003, Que, 7th Edition, p. 4. (Year: 2003).
Smart Card Alliance, “The Mobile Payments and NFC Landscape: A U.S. Perspective,” Sep. 2011. 53 pages.
The University of Alaska staff, Managing Finance Reports with Vista Plus, Aug. 2008, The University of Alaska, web, 2-20 (Year: 2008).
W. Adi, A. Al-Qayedi, A. A. Zarooni and A. Mabrouk, “Secured multi-identity mobile infrastructure and offline mobile-assisted micro-payment application,” 2004 IEEE Wireless Communications and Networking Conference (IEEE Cat. No. 04TH8733), 2004, pp. 879-882 vol. 2, doi: 10.1109/WCNC.2004.1311302. (Year: 2004).
White, Ron, “How Computers Work”, Que Publishing, 7th Ed, Oct. 15, 2003, p. 4. 23 pages.
Yang, Ming-Hour. “Security enhanced EMV-based mobile payment protocol.” TheScientificWorldJournal vol. 2014 (2014): 864571. Doi: 10.115/2014/864571 (Year: 2014).
Hany Herb, Hassan Farahat, and Mohamed Ezz, SecureSMSPay: Secure SMS Mobile Payment Model, 2008, 2008 2nd International Conference on Anti-counterfeiting, Security and Identification (pp. 11-17) (Year:2008).
J. Gao, V. Kulkarni, H. Ranavat, L. Chang and H. Mei, “A 2D Barcode-Based Mobile Payment System,” 2009 Third International Conference on Multimedia and Ubiquitous Engineering, 2009, pp. 320-329, doi: 10.1109/MU E.2009.62. (Year: 2009).
Kyrillidis; Mayes; Markantonakis, Card-present Transactions on the Internet Using the Smart CardWeb Server, 2013, IEEE, 12th, p. 616 (Year: 2013).
Latterell, Kayla, “How Do Gift Cards Work?,” https://www.cardsource.com/news/how-do-gift-cards-work, pp. 1-6.
“Messages in the SCT interbank space—pacs.008 and pacs.002”, Nov. 1, 2017, Paiementor, pp. 1-3 (Year: 2017).
“Wang et al. Mobile payment security, threats, and challenges, Mar. 24, 2016, IEEE Xplore, Entire document” (Year: 2016).
Alipay, Alipay Documentation Red Packet QR Code Introduction, printed on Sep. 30, 2019 at Internet address https://intl.alipay.com/doc/redpacket/scrzsv, 2 pages.
Alipay, Trust Makes It Simple, printed on Sep. 30, 2019 from Internet address https://intl.alipay.com/, 3 pages.
Authors et al.: Disclosed anonymously, Notifying a User When a Bill is Due Using a Notification On the User's Mobile Device, Oct. 18, 2013 IP.com PAD, entire document (Year: 2013).
Authors et al.: Tianliang Lei ; Title: Investigation of Cross-Social Network User Identification; Date of Conference: Apr. 21-22, 2022. (Year: 2022).
Authors: Saygin Baksi et al.; Title: Optimal primary-secondary user pairing and power allocation in cognitive cooperative multiple access channels; Date Added to IEEE Xplore: Apr. 10, 2014 (Year: 2014).
Bravo, Bravo Pay, CrunchBase, printed on Sep. 30, 2019 from Internet address https://www.crunchbase.com/organization/bravo#section-overview, 9 pages.
Bravo, Tip or Pay Your Tour Guide Without Sharing Personal Info, printed on Sep. 30, 2019 from Internet address https://trybravo.com, 4 pages.
Bravo, Trybravo's Competitors, Revenue, No. of Employees, Funding and Acquisitions, printed from Internet address https://www.owler.com/company/trybravo on Sep. 30, 2019, 2 pages.
DipJar, printed on Sep. 30, 2019 from Internet address https://www.dipjar.com/, 10 pages.
LevelUp, Restaurant Customers Expect Seamless Digital Experiences, printed on Sep. 30, 2019 from Internet address https://www.thelevelup.com/, 4 pages.
Message in the SCT interbank space—pacs.008 and pacs.002, Nov. 1, 2017, Paiementor, pp. 1-3 (Year: 2017).
Square, Inc., Grow Your Business Your Way With Square Tools, printed on Sep. 30, 2019 from Internet address https://squareup.com/us/en, 8 pages.
TSIP, Introducing Helping Heart—A Contactless Payment Jacket to Help the Homeless, dated Jul. 4, 2017, printed on Sep. 30, 2019 from Internet address https://www.tsip.co.uk/blog/2019/2/19/introducing-helping-heart-a-contactless-payment-jacket-to-help-the-homeless, 4 pages.
Uber, How Uber Works, printed on Sep. 30, 2019 from Internet address https://www.uber.com/us/en/about/how-does-uber-work/, 6 pages.
Wazeopedia, Main Page, printed on Sep. 30, 2019 from Internet address https://wazeopedia.waze.com/wiki/USA/Main_Page, 3 pages.
“Authors et al., Secure Authorization Token, Sep. 18, 2013, IP.com PAD, entire document” (Year: 2013).
1. Authors: Saygin Baksi et al.; Title: Optimal primary-secondary user pairing and power allocation in cognitive cooperative multiple access channels; Date Added to IEEE Xplore: Apr. 10, 2014 (Year: 2014).
2. Authors et al.: Tianliang Lei ; Title: Investigation of Cross-Social Network User Identification; Date of Conference: Apr. 21-22, 2022 . (Year: 2022).
Urien, P., et al., “A breakthrough for prepaid payment: End to end token exchange and management using secure SSL channels created by EAP-TLS smart cards”, 2011 International Conference on Collaboration Technologies and Systems (CTS), 2011. (Year: 2011).
P2P-Paid: A Peer-to-Peer Wireless Payment System by Gao et al (Year: 2005).

Continuations (1)

	Number	Date	Country
Parent	14501880	Sep 2014	US
Child	17713071		US

Continuation in Parts (1)

	Number	Date	Country
Parent	14266580	Apr 2014	US
Child	14501880		US

Mobile wallet account provisioning systems and methods

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract