A mobile payment system and method are described that facilitates the secure and real time user authentication and activation of a mobile payment account for a user portable electronic device over a communications network.
|
10. A portable electronic device comprising:
a contactless data communication interface;
a wallet application module for contactless payment at an electronic point of sale via the contactless data communication interface, the wallet application module configured to:
transmit a request to create a mobile payment account at mobile payment account management system, the request including data identifying the portable electronic device and an associated user;
receive and store data identifying the created mobile payment account in a secure memory, wherein the mobile payment account has a one-time activation servicing state that is: a first inactive state of the mobile payment account indicating that the associated user must be verified by the account management system, a second inactive state of the mobile payment account indicating that the mobile wallet application must be configured for user access security, and an active state of the mobile payment account indicating that the user is verified and user access security is configured;
prompt the user to initiate an identity verification process with the mobile payment account management system;
transmit user input for identity verification by the mobile account management system;
receive data from the mobile payment account management system indicating that the activation servicing state of the mobile payment account is set to the second inactive state, and in response, prompt the user to configure user access security; and
transmit data indicating that the mobile wallet application is configured for user access security to the mobile payment account management system, whereby the wallet application module is enabled for contactless payment for future transactions with multiple merchants using the activated mobile payment account.
1. A mobile payment account management system for providing a mobile payment account associated with a portable electronic device to enable contactless payment at an electronic point of sale using a wallet application module on the portable electronic device, the system comprising one or more processors configured to:
receive a request from the wallet application module on the portable electronic device, to create a mobile payment account, the request including data identifying the portable electronic device and an associated user;
create a mobile payment account associated with the portable electronic device based on data received in the request, wherein the created mobile payment account includes data identifying a one-time activation servicing state of the mobile payment account as:
a first inactive state of the mobile payment account indicating that the associated user must be verified by the account management system,
a second inactive state of the mobile payment account indicating that the mobile wallet application must be configured for user access security, and then
an active state of the mobile payment account indicating that the user is verified and user access security is configured;
transmit data identifying the created mobile payment account to the wallet application module on the portable electronic device, wherein the activation servicing state of the mobile payment account is initially set to the first inactive state;
receive, from the portable electronic device, a user validation response, verifying the identity of the associated user based on the received validation response, and in response, set the activation servicing state of the mobile payment account to the second inactive state; and
receive data indicating that user access security has been configured for the mobile wallet application, and in response set the activation servicing state of the mobile payment account to the active state, whereby the wallet application module is enabled for contactless payment for future transactions with multiple merchants using the activated mobile payment account.
2. The system of
3. The system of
4. The system of
5. The system of
6. The system of
7. The system of
8. The system of
transmitting the data included in the received request to create a mobile payment account to a payment account issuer;
receiving embossing data from the payment account issuer relating to an established payment account; and
creating mobile payment account data including data from the received embossing data and data identifying the associated portable electronic device.
9. The system of
11. The portable electronic device of
|
This invention relates to a mobile payment account system, and more particularly to activating a mobile payment account on a mobile device to enable contactless payment at an electronic point of sale.
Mobile payment account systems are generally known, in which portable electronic devices are configured to provide payment from an electronic wallet. Typically, these portable electronic devices are configured to enable a contactless communication with a merchant Point Of Sale (POS) terminal to carry out a payment transaction, for example using near field communication (NFC) technology.
Such conventional mobile payment systems typically involve a complicated process for provisioning a mobile payment account on the portable electronic device. Customers expect a certain degree of security and peace of mind that their sensitive identification and account details are protected from theft, and therefore known account provisioning systems involve a time consuming activation process which often requires the customer to, for example, post in a copy of documents to verify their identity, telephone the account issuer to provide verbal confirmation of their identity, or login to a website to complete a lengthy authentication process. This results in significant delays between a customer requesting a new mobile payment account and the time when the mobile account is actually provisioned and ready for use to carry out payment transactions.
What is desired is a more efficient account provisioning system and method which enables substantially real time activation of a new mobile payment account and which facilitates expedient security measures to prevent fraudulent use and identity theft.
In one aspect of the present invention, a mobile payment account activation system and method are provided for facilitating the automated activation of a mobile payment account stored on a portable electronic device, comprising an account activation unit for automatically authenticating a user associated with the mobile payment account by transmitting validation data to the portable electronic device and for activating the provisioned mobile payment account after the user has been authenticated based on the transmitted validation data.
In another aspect, the present invention provides a mobile payment account activation system for facilitating the automated activation of a mobile payment account stored on a portable electronic device, comprising an account activation unit for automatically authenticating a user associated with the mobile payment account by transmitting validation data to the portable electronic device and for activating the provisioned mobile payment account after the user has been authenticated based on the validation data.
In yet another aspect, a mobile device for use in a mobile payment system is provided, comprising a communication network interface, a secure memory for storing data associated with at least one inactive mobile payment account data, and an account activation module operable to receive validation data from the account provisioning system to facilitate automatic authentication of the user and automatically activation of the mobile payment account.
Preferably, the validation data does not facilitate payment from the activated mobile payment account. Preferably, the validation data used in the automated activation process comprises one or more identification and validation questions that are answered by the user via the portable electronic device to authenticate the user's identity. According to another aspect, enhanced out of band questions may be presented to the user via the portable electronic device depending for example on predetermined levels of security.
In another aspect of the invention, a mobile payment account activation system and method are provided for facilitating the automatic activation of a mobile payment account in a mobile payment system, the mobile payment account activation system arranged to store a plurality of mobile payment accounts associated with a user and comprising an account activation unit for receiving a user selection of an inactive mobile payment account and automatically activating the selected mobile payment account after the user has been authenticated.
In another aspect, there is provided a computer program arranged to carry out the above methods when executed by a computer or system.
There now follows, by way of example only, a detailed description of embodiments of the present invention, with references to the figures identified below.
Overview
A specific embodiment of the invention will now be described for a process involving a mobile payment system activating the mobile payment account for use on a user mobile device at a merchant's electronic point of sale terminal. In this embodiment, the process includes steps for securely provisioning the mobile payment account for a user but as those skilled in the art will appreciate, the activation process may be a separate process operating on mobile payment account data pre-provisioned on the mobile device.
Referring to
As shown in
The mobile device 3 also includes a payment account wallet application module 8 storing processing instructions used to control the operation of the mobile device 3, for example to i) request creation of a new mobile payment account, ii) handle a secure mobile payment account activation process, and/or iii) process a transaction with a merchant via the electronic POS terminal 5 to effectively transfer funds from the mobile payment account on the mobile device 3 to the merchant. As those skilled in the art will appreciate, the payment account wallet application module 8 may be provided as one or more software components of an operating system running on the mobile device 3 or as one or more separate software applications installed on the mobile device 3. Such software applications may be configured to run as background applications on the mobile device 3 that monitor for and activate upon receipt of appropriate messages or events, or may be launched by the user, so as to carry out the above operations. Alternatively, the payment account wallet application module 8 may be stored in the secure memory 4, and may for example be loaded into a virtual machine of the mobile device 3 to provide the functionality of the present embodiment.
Before the user can use the mobile device 3 to carry out transactions with a merchant electronic POS terminal 5, a new mobile payment account may be provisioned for the user, for example in response to a user requesting a new mobile payment account via the mobile device 3. Payment account data 6 may be created by the account activation system 7 for a new mobile payment account, and the account activation system 7 may be arranged to immediately transmits the payment account data 6 to the mobile device 3 for storage in the secure memory 4 of the mobile device 3. As those skilled in the art will appreciate, this is just one way in which an inactive mobile payment account can be provisioned on the mobile device 3 and any other method of delivery is envisaged. A notification message may be displayed by the mobile device 3 to alert the user that the mobile payment account is ready but requires authentication via the mobile payment account module 8 before the mobile payment account can be activated.
A secure activation process is then carried out between the mobile device 3 and the account activation system 7 to authenticate the identity of the user trying to activate the new mobile payment account. Once the authentication is successful, the account activation system 7 activates the mobile payment account. The activated mobile payment account data stored in the secure memory 4 of the mobile device 3 can then be used to carry out transactions with a merchant electronic POS terminal 5 via the contactless communication link 9, whereby a requested amount of funds can be transferred from the mobile payment account stored in the mobile device 3 to the merchant's bank 12.
Account Activation System
The account activation system 7 in the mobile payment system 1 will now be described in more detail with reference to
As shown in
If creation of a new mobile payment account is required, the middleware server 16 may initiate a provisioning process by sending an instant provisioning request to the account creation server 17 via a secure network communication link, such as a web services communication link. As is known in present payment account systems, the account creation server 17 establishes an account at a payment account issuer 10 in response to receiving an instant provisioning request. This process typically involves passing account details from the instant provisioning request to the payment account issuer 10, or any other known card payment account processing platform (pre-paid, credit deposit), to establish a new account at the payment account issuer 10. Once the new account has been established by the payment account issuer 10, the account creation server 17 may receive an embossing data file from the payment account issuer 10 which would typically be used to create a physical plastic payment card for the user. The account creation server 17 may create the mobile payment account data 6 including data from the embossing data file received from the payment account issuer 10 as well as additional data pertaining to the mobile device 3 and to the mobile user requesting the new account which will be used in the mobile account activation process. The mobile payment account data 6 may then be passed to the TSM server 18 via the middleware 16, which may perform logical data preparation of the received mobile payment account data 6 by forming appropriate commands to be written to the secure memory 4 of the mobile device 3. As those skilled in the art will appreciate, the precise form of the data may depend on the particular implementation of the secure memory 4 of the mobile device 3 and/or the payment association scheme program for facilitating payment. The TSM server 18 may also perform encryption of the mobile payment account data 6, for example of the sensitive payment account information in the mobile payment account data 6 such as the payment keys. The TSM server 18 may then passes the encrypted payment account data 6 of the provisioned inactive mobile payment account to the mobile device 3 via the communications server 13 and the cellular telephone network 11.
As will be described below, the middleware server 16 also handles authentication of the mobile user through validation messages communicated between the mobile device 3 and the middleware server 16 via the communications server 13. The middleware server 16 stores validation data pertaining to the mobile user requesting the new account until the mobile payment account has been activated. Alternatively or additionally, the validation data may be stored and provided by the payment account issuer 10 or by a third party system (not shown). The validation data may be in the form of identification and validation (ID&V) questions and answers, based on ID&V information associated with the mobile payment account which is stored on the middleware server 16 or payment account issuer 10, and/or based on additional ID&V information provided by a third party. The ID&V information may include publicly available information that only the user would know to be the answers, and therefore the ID&V information does not need to be transmitted over the air nor made available through the account authentication application on the mobile device 3. After the middleware server 16 and the payment account issuer 10 authenticate the mobile user, the mobile payment account is then activated by the middleware server 16 and the payment account issuer 10 to enable payments to be made from the mobile payment account.
The communications server 13 also includes a separate TSM unit 15 for securely routing the payment account data 6 created by account activation system 7 to the mobile device 3. In particular, the TSM unit 15 in the communications server 13 does not access any of the sensitive data stored in the encrypted payment account data 6 that is routed to the mobile device 3 via the cellular telephone network interface 14.
Mobile Device
As mentioned above, the mobile device 3 includes a secure memory 4. The mobile device 3 is operable to receive the payment account data 6 and activation request messages from and send validation messages to the account activation system 7 via a cellular telephone network interface 33 and the cellular telephone network 11, and to store the received payment account data 6 in the secure memory 4. The mobile device 3 is also operable to receive transaction authorization request messages from and send authorization messages to the merchant's POS terminal 5 via a contactless communications link interface 37 and the contactless communications link 9.
The mobile device 3 also includes a payment account wallet application module 8 as mentioned above, which stores processing instructions used to control the operation of the mobile device 3 to perform the various mobile payment account processes, as will be described in detail below. As schematically illustrated in
Also schematically illustrated in the exemplary embodiment of
The mobile device 3 may also include one or more other third party application modules 44 stored in the secure memory 4, for example an application module related to third party loyalty scheme. The secure memory 4 may also stores a UICC applet 45 which is an application to manage and hold the mobile network operator's functionality and secure information, such as a network key and GSM PIN.
Account Activation Process
A brief description has been given above of the components forming part of the mobile payment system 1 of this embodiment. A more detailed description of the operation of these components in this embodiment will now be given for an example computer-implemented mobile payment account provisioning process in a situation where a user wishes to request a new mobile payment account via the mobile device 3, with reference to the flow diagram of
As shown in
As part of the account provisioning process if necessary, at step S3-5, the middleware server 16 may send an instant mobile account provisioning request (which includes the data identifying the mobile device 3 and the user details) to the account creation server 17. At step S3-7, the account creation server 17 may extract the user details from the received instant mobile account provisioning request and sends the extracted user details to the payment account issuer 10 to establish a new account at the payment account issuer 10. At step S3-9, the account creation server may receive an embossing data file for the new account from the payment account issuer 10 after the new account has been established at the payment account issuer 10. At step S3-11, the account creation server 17 may then create mobile payment account data 6 for a new mobile payment account based on the received embossing data file. The new mobile payment account data 6 includes the data identifying the mobile device 3 received in the instant mobile account provisioning request.
At step S3-13, the account creation server 17 may then send the mobile payment account data 6 for the new provisioned mobile payment account to the TSM server 18 via the middleware server 16. At step S3-15, the TSM server 18 may prepare the mobile payment account data 6 for transmission to and storage on the mobile device 3. This may involve logical data preparation of the mobile payment account data 6 by forming appropriate commands to be written to the secure memory 4 of the mobile device 3. At step S3-17, the TSM server 18 may also perform encryption of the sensitive payment account information in the mobile payment account data 6 such as the payment keys, if necessary. This encryption may be performed based on known software and/or hardware functionality of the mobile device 3. At step S3-19, the TSM server 18 may send the encrypted payment account data 6 to the mobile device 3 via the communications server 13 and the cellular telephone network 11, and at step S3-21, the mobile device 3 may store the received payment account data 6 of the mobile payment account in the secure memory 4.
As the provisioned mobile payment account is not activated at this stage, at step S3-23, the mobile device 3 displays an indication to notify the user that a mobile payment account has been provisioned and is ready for activation. At step S3-25, the middleware server 16 carries out a user authentication and account activation process as will be described below, to activate the mobile payment account stored on the mobile device 3 ready for use by the transaction authorization sub-module 45, as well as to update the activation state of the mobile payment account at the account activation system 7 and/or the payment account issuer 10.
Account Activation Process
An example of a process flow of the mobile payment system 1 for handling a user authorization and mobile account activation process between the account activation system 7 and the mobile device 3 will now be described with reference to the flow diagram of
Additionally, those skilled in the art will appreciate that the level of security can be controlled and determined based on a risk profile for the mobile user. For example, a user that is requesting a mobile payment account for the first time may be classified as a high risk user and accordingly may be presented with a plurality of ID&V questions, for example three questions using validation information sourced from a third party to verify the user's identity with a higher level of confidence. Such ID&V questions may for example be of the form “Where did you live in 1994?”, where the questions may be generated based on ID&V information obtainable from public records but where the user is the only person likely to know the answers. As mentioned above, the ID&V information itself need not be transmitted by the account activation system 7 over the cellular telephone network 11, and the ID&V questions and answers are never transmitted together in the same message, thus reducing the risk of identity theft and fraud.
A user may, on the other hand, be classified as a low risk user for example if that user is requesting an additional mobile payment account and therefore would already be registered on the account activation system 7 and the payment account issuer 10, or for example may have a mobile device and/or software that facilitates a more secure communication link with the account activation system 7. For a low risk user, a less complicated authentication process could be used, for example involving a single ID&V question based on user details previously provided to the account activation system 7.
Therefore, at step S4-9, the middleware server 16 determines if another ID&V question is to be transmitted to the mobile device 3, and if so, steps S4-5 and S4-7 are repeated for the additional ID&V question.
The use of ID&V questions and validation of received answers advantageously provides an additional measure of security against identification theft on top of the secured communication channels that are in place, particularly because the present invention allows for real-time activation of a mobile payment account directly from a user's mobile device 3. For example, account creation may be requested immediately after the user has purchased the mobile phone or at any later time where the user may be in a public environment and at risk of a fraudster observing as the user enters his or her identification details into the mobile device 3. More devious methods for theft of input identification details may involve hacking or eavesdropping of the secured communication channels between the mobile device 3 and the account activation system 7. The automated user authentication steps of the account activation process advantageously reduce the risk of identity theft because a fraudster is prevented from unauthorized usage of a mobile payment account merely from any stolen answers to ID&V questions as the data that is transmitted (which may be sensitive data such as the user's social security number or date of birth) does not facilitate actual payment from an activated mobile payment account which is typically enabled by user entry of a correct PIN. The present invention further advantageously provides for this secure implementation while at the same time minimizing the delay in activating a provisioned mobile payment account so that a user can effectively activate a provisioned mobile payment account in real time.
When the middleware server 16 determines at step S4-9 that no further ID&V questions are required and the identity of the mobile user has been automatically authenticated by validation of each the received user responses as compared to the stored validation data, the middleware server 16 may then wait for confirmation from the mobile device 3 that the user has agreed to the mobile payment account terms and conditions, at step S4-11. As shown in
After the middleware server 16 has received confirmation at step S4-11 as necessary, then at step S4-13, the TSM server 18 systematically generates an unblock command which is sent back to the mobile device 3, via for example the TSM unit 15 of the communications server 13. In response to receiving the unblock command, the middleware server 16 changes the state of the mobile payment account to “Issuer PIN Unblocked” at step S4-15. Then, at step S4-17, the mobile device 3 prompts for and receives a PIN input by the user for the mobile payment account, and additionally, may also prompt for and receive a user input secret word for the mobile payment account. As shown in
Summary and Advantages
A description of the components of a mobile payment account activation system embodying the present invention has been given. A detailed description has also been given of the functional operation of each component during an account provisioning and account activation process in the mobile payment system.
A number of advantages are achieved with the account activation system described above. As mentioned above, the account activation system can advantageously activate a new mobile payment account for a mobile user in real time, as the computer-implemented user authentication and activation processes are automated by the account activation system so that a mobile user can efficiently and securely activate an inactive mobile payment account provisioned on a mobile device, without requiring manual intervention to provide additional verification in order to complete the activation process, such as a preset pass code by way of a telephone call, or in person in store or in branch, or logging on to a website of an account issuer or bank through a web browser, or delivery of any authentication or verification documents between the user and the account issuer or bank by mail or post. The present invention thereby facilitates real time provisioning and activation of the mobile payment account ready to be used to carry out transactions at a merchant POS.
The account activation system can also be configured to adjust a level of security relating to the user authentication and activation process depending for example on a determined risk of the mobile user. Therefore, a lower risk mobile user may have the additional convenience of a simplified activation process, whereas an unfamiliar or higher risk mobile user will have a more complicated activation process, thereby reducing the chances of fraudulent account activation and identity theft.
The above described account activation system also has the advantage that the merchant POS terminal and the secure payment account issuers operate in a conventional manner. The system can therefore be easily incorporated into existing contactless mobile payment systems.
Computer Systems
The computer servers of the account activation system described herein may be implemented by computer systems such as computer system 1000 as shown in
Computer system 1000 includes one or more processors, such as processor 1004. Processor 1004 may be any type of processor, including but not limited to a special purpose or a general-purpose digital signal processor. Processor 1004 is connected to a communication infrastructure 1006 (for example, a bus or network). Various software implementations are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the art how to implement the invention using other computer systems and/or computer architectures.
Computer system 1000 also includes a main memory 1008, preferably random access memory (RAM), and may also include a secondary memory 610. Secondary memory 1010 may include, for example, a hard disk drive 1012 and/or a removable storage drive 1014, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. Removable storage drive 1014 reads from and/or writes to a removable storage unit 1018 in a well-known manner. Removable storage unit 1018 represents a floppy disk, magnetic tape, optical disk, etc., which is read by and written to by removable storage drive 1014. As will be appreciated, removable storage unit 618 includes a computer usable storage medium having stored therein computer software and/or data.
In alternative implementations, secondary memory 1010 may include other similar means for allowing computer programs or other instructions to be loaded into computer system 1000. Such means may include, for example, a removable storage unit 1022 and an interface 1020. Examples of such means may include a removable memory chip (such as an EPROM, or PROM, or flash memory) and associated socket, and other removable storage units 1022 and interfaces 1020 which allow software and data to be transferred from removable storage unit 1022 to computer system 1000. Alternatively, the program may be executed and/or the data accessed from the removable storage unit 1022, using the processor 1004 of the computer system 1000.
Computer system 1000 may also include a communication interface 1024. Communication interface 1024 allows software and data to be transferred between computer system 1000 and external devices. Examples of communication interface 1024 may include a modem, a network interface (such as an Ethernet card), a communication port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communication interface 1024 are in the form of signals 1028, which may be electronic, electromagnetic, optical, or other signals capable of being received by communication interface 1024. These signals 1028 are provided to communication interface 1024 via a communication path 1026. Communication path 1026 carries signals 1028 and may be implemented using wire or cable, fiber optics, a phone line, a wireless link, a cellular phone link, a radio frequency link, or any other suitable communication channel. For instance, communication path 1026 may be implemented using a combination of channels.
The terms “computer program medium” and “computer usable medium” are used generally to refer to media such as removable storage drive 1014, a hard disk installed in hard disk drive 1012, and signals 1028. These computer program products are means for providing software to computer system 1000. However, these terms may also include signals (such as electrical, optical or electromagnetic signals) that embody the computer program disclosed herein.
Computer programs (also called computer control logic) are stored in main memory 1008 and/or secondary memory 1010. Computer programs may also be received via communication interface 1024. Such computer programs, when executed, enable computer system 1000 to implement embodiments of the present invention as discussed herein. Accordingly, such computer programs represent controllers of computer system 1000. Where the embodiment is implemented using software, the software may be stored in a computer program product and loaded into computer system 1000 using removable storage drive 1014, hard disk drive 1012, or communication interface 1024, to provide some examples.
Alternative embodiments may be implemented as control logic in hardware, firmware, or software or any combination thereof.
It will be understood that embodiments of the present invention are described herein by way of example only, and that various changes and modifications may be made without departing from the scope of the invention.
For example, in the embodiment described above, the mobile payment account is provisioned on a mobile handset which communicates with the account activation system via a cellular telephone network. As those skilled in the art will appreciate, instead of a mobile handset, other portable electronic devices configured for contactless payment with a merchant electronic POS and having suitable input and display means, may be adapted to carry out the functionality of real time provisioning and/or activation as described in the above embodiment. Additionally, those skilled in the art will appreciate that the portable electronic device may be configured to communicate with the account activation system via any other form of communication channel, such as a wired or wireless network connection, a Bluetooth connection, or the like. Alternatively, the mobile payment account data may be provisioned on the portable electronic device by means of data transfer for example via any suitable data communication path or by way of a computer readable medium.
In the embodiment described above, the mobile device is provisioned with a mobile payment account by the account activation system through secure transfer of data representing the mobile payment account, which data including data defining an amount of pre-paid funds transferred from the user's payment account issuer and/or data identifying a user's account at a payment account issuer from which funds can be transferred to a merchant bank to complete a transaction. As those skilled in the art will appreciate, the mobile device may instead or additionally be securely provisioned with data representing one or more other types of accounts, such as an insurance account, a loyalty and rewards scheme membership or the like, and the account activation system may be configured to conduct a secure data transfer to the mobile device of data representing such an account, for example including the account or membership number or any other type of secure reference number.
Alternative embodiments may be envisaged, which nevertheless fall within the scope of the following claims.
Bauer, John, McMillen, Glenn Curtiss, Schuetz, Christine Ann, Lloyd, Garry, Crozier, Eric
Patent | Priority | Assignee | Title |
10467626, | Sep 02 2011 | PAYPAL, INC. | Secure elements broker (SEB) for application communication channel selector optimization |
11521194, | Jun 06 2008 | PAYPAL, INC. | Trusted service manager (TSM) architectures and methods |
11595820, | Sep 02 2011 | PAYPAL, INC. | Secure elements broker (SEB) for application communication channel selector optimization |
ER4022, |
Patent | Priority | Assignee | Title |
6607136, | Sep 16 1998 | SONIXIO, INC | Physical presence digital authentication system |
7203477, | Feb 09 2000 | Apriva, LLC | System and method for deploying application programs |
7469151, | Sep 01 2006 | MasterCard International Incorporated | Methods, systems and computer program products for over the air (OTA) provisioning of soft cards on devices with wireless communications capabilities |
7562813, | May 10 2006 | First Data Corporation | System and method for activating telephone-based payment instrument |
7873573, | Mar 30 2006 | OBOPAY MOBILE TECHNOLOGY INDIA PRIVATE LIMITED | Virtual pooled account for mobile banking |
8121945, | Jul 06 2006 | Qualcomm Incorporated | Methods and systems for payment method selection by a payee in a mobile environment |
20040107170, | |||
20040159700, | |||
20050021400, | |||
20050027543, | |||
20050187873, | |||
20050269401, | |||
20050269402, | |||
20060040667, | |||
20060156385, | |||
20060165060, | |||
20070179885, | |||
20070233615, | |||
20070293155, | |||
20080126145, | |||
20080270302, | |||
20090024533, | |||
20090069050, | |||
20090210308, | |||
20090327131, | |||
20100057580, | |||
20100312700, | |||
20110140841, | |||
20110218911, | |||
20120074232, | |||
20120095852, | |||
20120136732, | |||
20120136786, | |||
20140222682, | |||
WO2010033944, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Sep 28 2010 | BARCLAYS BANK PLC | (assignment on the face of the patent) | / | |||
Oct 01 2010 | BAUER, JOHN | BARCLAYS BANK PLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025619 | /0121 | |
Oct 04 2010 | MCMILLEN, GLENN CURTISS | BARCLAYS BANK PLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025619 | /0121 | |
Oct 18 2010 | CROZIER, ERIC | BARCLAYS BANK PLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025619 | /0121 | |
Oct 25 2010 | SCHUETZ, CHRISTINE ANN | BARCLAYS BANK PLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025619 | /0121 | |
Nov 04 2010 | LLOYD, GARRY | BARCLAYS BANK PLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025619 | /0121 | |
Aug 29 2017 | BARCLAYS BANK PLC | BARCLAYS SERVICES LIMITED | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 047400 | /0169 | |
May 07 2019 | BARCLAYS SERVICES LIMITED | Barclays Execution Services Limited | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 051085 | /0309 |
Date | Maintenance Fee Events |
Jul 16 2020 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Date | Maintenance Schedule |
Jan 31 2020 | 4 years fee payment window open |
Jul 31 2020 | 6 months grace period start (w surcharge) |
Jan 31 2021 | patent expiry (for year 4) |
Jan 31 2023 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jan 31 2024 | 8 years fee payment window open |
Jul 31 2024 | 6 months grace period start (w surcharge) |
Jan 31 2025 | patent expiry (for year 8) |
Jan 31 2027 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jan 31 2028 | 12 years fee payment window open |
Jul 31 2028 | 6 months grace period start (w surcharge) |
Jan 31 2029 | patent expiry (for year 12) |
Jan 31 2031 | 2 years to revive unintentionally abandoned end. (for year 12) |