Secure account provisioning

• US 10,699,267 B2
• Filed: 12/21/2016
• Issued: 06/30/2020
• Est. Priority Date: 09/28/2010
• Status: Active Grant

• Current Assignee: Barclays Execution Services Ltd. (Barclays PLC)
• Original Assignee: Barclays Execution Services Ltd. (Barclays PLC)
• Inventors: Bauer, John, McMillen, Glenn Curtiss, Crozier, Eric, Schuetz, Christine Ann, Lloyd, Garry
• Primary Examiner(s): Yu, Ariel J
• Assistant Examiner(s): Amsdell, Dana
• Application Number:
  US15/386,487
• Publication Number:
  US 20170116598A1
• Time in Patent Office: 1,287 Days
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4014 Identity check for transactions

Abstract

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.

Claims

1. A mobile payment account system comprising one or more processors that:

transmit, from a server to a portable electronic device, data to pre-install a wallet application module on the portable electronic device, wherein prior to the transmission, the wallet application module is not associated with a new mobile payment account;

receive, by the server from the portable electronic device, a request from the pre-installed wallet application module to create the new mobile payment account, the request including data identifying the portable electronic device and an associated user;

create, by the server in response to receiving the request, a new 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;

transmit, by the server to the portable electronic device, 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 a first one of a plurality of states where the new mobile payment account is not available for use by the wallet application module to carry out transactions; and

responsive to verifying the identity of the associated user, sent by the server, the activation servicing state of the new mobile payment account to a different one of the plurality of states where the new mobile payment account is available for use by the wallet application module to carry out transactions,

wherein the server verifies the identity of the associated user by receiving, from the portable electronic device, a validation answer to at least one validation question in the form of identification and validation questions and answers stored on a middleware server or payment account issuer or provided by a third party, and automatically authenticates the user based on the received validation answer, and

wherein the server determines a number of validation questions to be transmitted to the portable electronic device based on a determined level of security associated with the user.

2. The system of claim 1, wherein the server is a middleware server and wherein the middleware server creates the new mobile payment account by provisioning a request to a second server.

3. The system of claim 1, wherein the validation questions and answers are based on identification and validation information associated with the new mobile payment account.

4. The system of claim 1, wherein the identification and validation information is not transmitted to the portable electronic device.

5. The system of claim 1, wherein the one or more processors are configured to automatically verify the identity of the associated user associated substantially in real-time.

6. The system of claim 1, wherein the one or more processors are further configured to create the mobile payment account by transmitting the data included in the received request to create a mobile payment account to a payment account issuer, receive 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.

7. The system of claim 1, wherein the one or more processors are further configured to receive a request from the wallet application module to initiate the identity verification process in response to notification by the wallet application module that the mobile payment account is in the inactive state.

8. The system of claim 1, further comprising receiving data indicating that the mobile wallet application is configured for user access security from the wallet application module, before setting the activation servicing state of the mobile payment account to an active state.

9. The system of claim 8, wherein the user access security comprises setting an access PIN or passcode for the wallet application module.

10. The system of claim 1, wherein the mobile payment account is linked to multiple funding sources.

11. The system of claim 10, wherein the multiple funding sources include one or more of a pre-paid account, deposit account, and credit account.

12. 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, to a remote server, a request to create a new mobile payment account at the remote server, the request including data identifying the portable electronic device and an associated user, wherein prior to the transmission, the wallet application module is not associated with the new mobile payment account;

receive, from the remote server, and store data identifying the new mobile payment account in a secure memory, wherein the mobile payment account has an activation servicing state that is initially set to a first one of a plurality of states where the new mobile payment account is not available for use by the wallet application module to carry out transactions;

prompt the user to initiate an identity verification process with the at remote server;

transmit, to the remote server, user input for identity verification by the remote server;

wherein the remote server verifies the identity of the user by receiving, from the portable electronic device, a validation answer to at least one validation question in the form of identification and validation questions and answers stored on a middleware server or payment account issuer or provided by a third party, and automatically authenticates the user based on the received validation answer, and

wherein the server determines a number of validation questions to be transmitted to the portable electronic based on a determined level of security associated with the user; and

receive, in response to the user identity verification, data from the remote server indicating that the activation servicing state of the new mobile payment account is set to an active state a different one of the plurality of states where the new mobile payment account is available for use by the wallet application module to carry out transactions.

13. The portable electronic device of claim 12, further comprising receiving user input to configure user access security of the mobile wallet application, and transmitting data indicating that the mobile wallet application is configured for user access security to the remote server, before data is received from the remote server indicating that the activation servicing state of the mobile payment account is set to an active state.

14. The portable electronic device of claim 13, wherein the user input to configure user access security of the mobile wallet application comprises setting an access PIN or passcode.

15. The portable electronic device of claim 12, wherein the mobile payment account is linked to multiple funding sources.

16. The portable electronic device of claim 15, wherein the multiple funding sources include one or more of a pre-paid account, deposit account, and credit account.

17. A non-transitory computer-readable medium comprising computer-executable instructions, that when executed by a processor of a server, perform a method of:

transmitting data to pre-install a wallet application module on a portable electronic device, wherein prior to the transmission, the wallet application module is not associated with a new mobile payment account;

receiving a request from the pre-installed wallet application module to create the new mobile payment account, the request including data identifying the portable electronic device and an associated user;

creating, in response to receiving the request, a new 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;

transmitting 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 a first one of a plurality of states where the new mobile payment account is not available for use by the wallet application module to carry out transactions; and

responsive to verifying the identity of the associated user, set the activation servicing state of the new mobile payment account to a different one of the plurality of states where the new mobile payment account is available for use by the wallet application module to carry out transactions;

wherein said computer readable medium further comprises computer-executable instructions for verifying the identity of the associated user by receiving, from the portable electronic device, a validation answer to at least one validation question, and automatically authenticates the user based on the received validation answer,

wherein said computer readable medium further comprises computer-executable instructions for verifying the identity of the associated user further based on additional identification and validation information provided by a database that is remote from the server and the portable electronic device, and

wherein the server determines a number of validation questions to be transmitted to the portable electronic device based on a determined level of security associated with the user.

18. The non-transitory computer readable storage medium of claim 17, wherein the remote database stores public records and wherein the validation information is a part of the public records.

19. The non-transitory computer readable storage medium of claim 17, wherein said computer readable medium further comprises computer-executable instructions for verifying the identity of the associated user based on identification and validation information associated with the new mobile payment account.

20. The non-transitory computer readable storage medium of claim 18, wherein said computer readable medium further comprises computer-executable instructions for determining a number of validation questions to be transmitted to the portable electronic device based on a determined level of security associated with the user.

21. The non-transitory computer readable storage medium of claim 17, wherein said computer readable medium further comprises computer-executable instructions for automatically verifying the identity of the associated user associated substantially in real-time.

22. The non-transitory computer readable storage medium of claim 17, wherein said computer readable medium further comprises computer-executable instructions for creating the mobile payment account by transmitting the data included in the received request to create a mobile payment account to a payment account issuer, receive 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.

23. The non-transitory computer readable storage medium of claim 17, wherein said computer readable medium further comprises computer-executable instructions for receiving a request from the wallet application module to initiate the identity verification process in response to notification by the wallet application module that the mobile payment account is in the inactive state.

24. The non-transitory computer readable storage medium of claim 17, wherein said computer readable medium further comprises computer-executable instructions for receiving data indicating that the mobile wallet application is configured for user access security from the wallet application module, before setting the activation servicing state of the mobile payment account to an active state.

25. The non-transitory computer readable storage medium of claim 17, wherein said computer readable medium further comprises computer-executable instructions for linking the mobile payment account to multiple funding sources.