System and method for electronic wallet conversion

• US 20100332336A9
• Filed: 10/20/2003
• Published: 12/30/2010
• Est. Priority Date: 12/06/2002
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Goldstein, Seth, Sandler, Robert, Lowe, David, Quigley, Benjamin, Jones, Fletcher, Price, Laura, Subramanya, Venkatesh, Mahajan, Rajesh, Muppirala, Prakash, Rawat, Jai
• Granted Patent: US 8,473,355 B2
• Time in Patent Office: Days
• US Class Current: 705/18
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/363 with the personal data of a user
• 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: G07F 7/0866 by active credit-cards adapted therefor G07F7/1008 takes precedence
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: G07F 7/1025 Identification of user by a PIN code

Abstract

A system and method for electronic wallet conversion allows conversion of a basic electronic wallet to a more flexible wallet account, providing additional services and requiring additional authentication. The basic accountholder eventually requires the additional services provided by the more flexible wallet, typically editing rights and making purchases at sites requiring authentication beyond the basic level. To convert the account, the account holder is presented with a one-time challenge and response mechanism that requires the accountholder to summon information that only the account holder would know. If a successful match is made, the account is converted to the more flexible account for all time. The accountholder replaces the one-time challenge and response with a second-level password that grants the accountholder ongoing access to more sensitive wallet features, such as the ability to purchase at sites requiring a second-level password, and editing rights to the information stored in the wallet.

Claims

1. A method of converting an electronic wallet, comprising steps of:

providing an account, the account a first account type providing a first set of services, the first set of services requiring a first level of authentication;

presenting an accountholder a one-time challenge/response mechanism; and

if the accountholder clears the challenge, converting the account to a second account type for all time.

2. The method of claim 1, wherein the challenge/response mechanism requires an accountholder to provide information known only to the accountholder;

and

wherein the second type provides the first set of services plus further services associated therewith, the further services requiring at least one further level of authentication.

3. The method of claim 2, wherein the step of providing the wallet account comprises either of the steps of:

creating the account when making an initial purchase; and

creating a record in a subscriber database.

4. The method of claim 3, wherein subscribers include subscribers to any of:

an online service; and

an ISP (Internet service provider).

5. The method of claim 2, wherein the step of presenting a challenge/response mechanism comprises steps of:

requesting a service from within the account of the first type that is only available from within an account of the second type; and

one time only, prompting the accountholder to provide the information known only to the accountholder.

6. The method of claim 2, wherein the account comprises an electronic wallet, the first type comprising a thin wallet wherein the first set of services comprises at least one low-risk task requiring a low security level.

7. The method of claim 6, wherein the at least one low-risk task comprises any of:

making purchases not exceeding a predetermined purchase amount;

making transactions using default account information; and

making purchases at sites requiring only the first level of authentication.

8. The method of claim 6, wherein the second type comprises a full wallet and the further rights comprise additional tasks requiring greater security than the low level of security.

9. The method of claim 8, wherein the additional tasks comprise any of:

editing the default account information;

editing account preferences;

making purchases that exceed a predetermined purchase amount; and

making purchases at sites that require the at least one level of further authentication.

10. The method of claim 2, further comprising a step of authenticating at the first level to gain access to the first account.

11. The method of claim 10, wherein authenticating at the first level comprises providing a user ID and a first-level password.

14. The method of claim 2, further comprising steps of:

configuring the challenge by an account provider, wherein configuring the challenge includes;

specifying information requested by the challenge; and

specifying a permissible number of response attempts.

15. The method of claim 2, wherein the step of converting the account comprises steps of:

creating a record in a wallet account database;

providing notice of a privacy policy; and

consenting to the privacy policy by the account holder.

16. The method of claim 15, wherein the step of converting the account further comprises a step of:

creating a second-level challenge.

17. The method of claim 16, wherein the step of creating a second-level challenge comprises any of the steps of:

setting a second-level password; and

configuring a security question by the accountholder.

18. The method of claim 17, wherein the at least one further level of authentication requires any of the steps of:

providing the second-level password; and

clearing the security question.

19. The method of claim 18, further comprising a step of:

providing a user interface accessible only to holders of accounts of the second type to edit account information and preferences.

20. The method of claim 19, wherein the account information comprises any of:

first name;

middle initial;

last name;

credit card type;

credit card number;

credit card expiration date;

billing address;

city;

state;

postal code;

country;

daytime phone; and

evening phone.

21. The method of claim 20, wherein first account type comprises a thin wallet, the thin wallet comprising a record in a subscriber database, and wherein the second account type comprises a full wallet, the full wallet comprising the record in the wallet database, wherein full wallet is initially populated with information from the thin wallet.

22. The method of claim 21, further comprising a step of:

providing a wallet server, wherein the wallet server comprises a web server having a wallet application running thereon, the wallet server operative to pull account information from either the subscriber database or the wallet database.

45. The method of claim 2, wherein said at least one further level of authentication comprises accessing said account from a client device previously established as trusted.

46. The method of claim 45, wherein establishing a client as trusted comprises authentication with a second-level password.

47. The method of claim 45, further comprising a step of reestablishing a client as trusted if a trusted state is compromised.

48. The method of claim 45, further comprising a step of providing a visual indicator of a trusted state.

49. The method of claim 45, further comprising a step of providing a security controls panel that permits accountholders to manage authentication for various online products and sites.

12. The method of claim 12, wherein the information known only to the account holder comprises at least a portion of a credit card number stored in the first account.

13. The method of claim 12, further comprising steps of:

if the accountholder doesn'"'"'t clear the challenge, allowing a predetermined number of attempts to enter the information known only to the account holder; and

if the accountholder fails the predetermined number of attempts, allowing the accountholder to provide a new credit card number; and

presenting a challenge based on the new credit card number.

23. A computer program product comprising a tangible medium having computer readable code embodied thereon, the computer code including program code means for performing a method of converting an electronic wallet, the method comprising steps of:

providing an account, the account a first account type providing a first set of services, the first set of services requiring a first level of authentication;

presenting an accountholder a one-time challenge/response mechanism; and

if the accountholder clears the challenge, converting the account to a second account type for all time.

24. The method of claim 23, wherein the challenge/response mechanism requires an accountholder to provide information known only to the accountholder;

and

wherein the second type provides the first set of services plus further services associated therewith, the further services requiring at least one further level of authentication.

25. The method of claim 24, wherein the step of providing the wallet account comprises either of the steps of:

creating the account when making an initial purchase; and

creating a record in a subscriber database.

26. The method of claim 25, wherein subscribers include subscribers to any of:

an online service; and

an ISP (Internet service provider).

27. The method of claim 24, wherein the step of presenting a challenge/response mechanism comprises steps of:

requesting a service from within the account of the first type that is only available from within an account of the second type; and

one time only, prompting the accountholder to provide the information known only to the accountholder.

28. The method of claim 24, wherein the account comprises an electronic wallet, the first type comprising a thin wallet wherein the first set of services comprises at least one low-risk task requiring a low security level.

29. The method of claim 28, wherein the at least one low-risk task comprises any of:

making purchases not exceeding a predetermined purchase amount;

making transactions using default account information; and

making purchases at sites requiring only the first level of authentication.

30. The method of claim 28, wherein the second type comprises a full wallet and the further rights comprise additional tasks requiring greater security than the low level of security.

31. The method of claim 30, wherein the additional tasks comprise any of:

editing the default account information;

editing account preferences;

making purchases that exceed a predetermined purchase amount; and

making purchases at sites that require the at least one level of further authentication.

32. The method of claim 24, further comprising a step of authenticating at the first level to gain access to the first account.

33. The method of claim 32, wherein authenticating at the first level comprises providing a user ID and a first-level password.

34. The method of claim 24, wherein the information known only to the account holder comprises at least a portion of a credit card number stored in the first account.

35. The method of claim 24, further comprising steps of:

if the accountholder doesn'"'"'t clear the challenge, allowing a predetermined number of attempts to enter the information known only to the account holder; and

if the accountholder fails the predetermined number of attempts, allowing the accountholder to provide a new credit card number; and

presenting a challenge based on the new credit card number.

36. The method of claim 24, further comprising steps of:

configuring the challenge by an account provider, wherein configuring the challenge includes;

specifying information requested by the challenge; and

specifying a permissible number of response attempts.

37. The method of claim 24, wherein the step of converting the account comprises steps of:

creating a record in a wallet account database;

providing notice of a privacy policy; and

consenting to the privacy policy by the account holder.

38. The method of claim 37, wherein the step of converting the account further comprises a step of:

creating a second-level challenge.

39. The method of claim 38, wherein the step of creating a second-level challenge comprises any of the steps of:

setting a second-level password; and

configuring a security question by the accountholder.

40. The method of claim 39, wherein the at least one further level of authentication required any of the steps of:

providing the second-level password; and

clearing the security question.

41. The method of claim 40, further comprising a step of:

providing a user interface accessible only to holders of accounts of the second type to edit account information and preferences.

42. The method of claim 41, wherein the account information comprises any of:

first name;

middle initial;

last name;

credit card type;

credit card number;

credit card expiration date;

billing address;

city;

state;

postal code;

country;

daytime phone; and

evening phone.

43. The method of claim 42, wherein first account type comprises a thin wallet, the thin wallet comprising a record in a subscriber database, and wherein the second account type comprises a full wallet, the full wallet comprising the record in the wallet database, wherein full wallet is initially populated with information from the thin wallet.

44. The method of claim 43, further comprising a step of:

providing a wallet server, wherein the wallet server comprises a web server having a wallet application running thereon, the wallet server operative to pull account information from either the subscriber database or the wallet database.

50. A system for converting an electronic wallet comprising:

a wallet server;

a wallet database;

a subscriber database;

wherein the wallet server is in communication with the wallet and the subscriber databases; and

a client in communication with the wallet server, wherein a wallet accountholder requests services from the wallet server;

wherein the server includes means for converting the electronic wallet.

51. The system of claim 50, wherein the means for converting the electronic wallet comprises a computer program embodied on a tangible medium, the computer program including computer code means for:

providing an account, the account a first account type providing a first set of services, the first set of services requiring a first level of authentication;

presenting the accountholder a one-time challenge/response mechanism; and

if the accountholder clears the challenge, converting the account to a second account type for all time.

52. The system of claim 51, wherein the challenge/response mechanism requires an accountholder to provide information known only to the accountholder;

and

wherein the second account type provides the first set of services plus further services associated therewith, the further services requiring at least one further level of authentication.

53. The system of claim 52, wherein the code means for providing the wallet account comprises code means for either of:

creating the account when making an initial purchase; and

creating a record in the subscriber database.

54. The system of claim 53, wherein subscribers include subscribers to any of:

an online service; and

an ISP (Internet service provider).

55. The system of claim 52, wherein the code means for presenting a challenge/response mechanism comprises code means for:

requesting a service from within the account of the first type that is only available from within an account of the second type; and

one time only, prompting the accountholder to provide the information known only to the accountholder.

56. The system of claim 52, wherein the account comprises an electronic wallet, the first type comprising a thin wallet wherein the first set of services comprises at least one low-risk task requiring a low security level.

57. The system of claim 56, wherein the at least one low-risk task comprises any of:

making purchases not exceeding a predetermined purchase amount;

making transactions using default account information; and

making purchases at sites requiring only the first level of authentication.

58. The system of claim 56, wherein the second type comprises a full wallet and the further rights comprise additional tasks requiring greater security than the low level of security.

59. The system of claim 58, wherein the additional tasks comprise any of:

editing default account information;

editing account preferences;

making purchases that exceed a predetermined purchase amount; and

making purchases at sites that require the at least one level of further authentication.

60. The system of claim 52, the program further comprising code means for authenticating at the first level to gain access to the first account.

61. The system of claim 60, wherein the code means for authenticating at the first level includes code means for providing a user ID and a first-level password.

62. The system of claim 52, wherein the information known only to the account holder comprises at least a portion of a credit card number stored in the first account.

63. The system of claim 52, the program further comprising code means for:

if the accountholder doesn'"'"'t clear the challenge, allowing a predetermined number of attempts to enter the information known only to the account holder; and

if the accountholder fails the predetermined number of attempts, allowing the accountholder to provide a new credit card number; and

presenting a challenge based on the new credit card number.

64. The system of claim 52, the program further comprising code means for:

configuring the challenge by an account provider, wherein configuring the challenge includes;

specifying information requested by the challenge; and

specifying a permissible number of response attempts.

65. The system of claim 52, wherein the code means for converting the account comprises code means for:

creating a record in the wallet database;

providing notice of a privacy policy; and

consenting to the privacy policy by the account holder.

66. The system of claim 65, wherein the code means for converting the account further comprises code means for:

creating a second-level challenge.

67. The system of claim 66, wherein the code means for creating a second-level challenge comprises code means for any of:

setting a second-level password

configuring a security question by the accountholder.

68. The system of claim 67, wherein the at least one further level of authentication requires any of the steps of:

providing the second-level password; and

clearing the security question.

69. The system of claim 68, the program further comprising code means for:

providing a user interface accessible only to holders of accounts of the second type to edit account information and preferences.

70. The system of claim 69, wherein the account information comprises any of:

first name;

middle initial;

last name;

credit card type;

credit card number;

credit card expiration date;

billing address;

city;

state;

postal code;

country;

daytime phone; and

evening phone.

71. The system of claim 70, wherein the first account type comprises a thin wallet, the thin wallet comprising a record in the subscriber database, and wherein the second account type comprises a full wallet, the full wallet comprising the record in the wallet database, wherein the full wallet is initially populated with information from the thin wallet.

72. The system of claim 71, wherein the wallet server comprises a web server having the wallet application running thereon, the wallet server operative to pull account information from either the subscriber database or the wallet database.

73. The system of claim 50, further comprising a second server, said second server operative to relay data and requests between said wallet server and said subscriber database.

74. The system of claim 73, further comprising a router, the router operative to link at least a first and a second network, wherein the wallet server occupies the first network and wherein the second server and the subscriber database occupy the second network.

75. The system of claim 74, wherein the wallet database occupies said second network.

76. The system of claim 52, wherein said at least one further level of authentication comprises accessing said account from a client device previously established as trusted.

77. The system of claim 76, wherein establishing a client as trusted comprises authentication with a second-level password.

78. The system of claim 76, said application further comprising code means for reestablishing a client as trusted if a trusted state is compromised.

79. The system of claim 76, said application further comprising code means for providing a visual indicator of a trusted state.

80. The system of claim 76, said application further comprising code means for providing a security controls panel that permits accountholders to manage authentication for various online products and sites.