Third party privacy system

• US 20050027618A1
• Filed: 08/24/2004
• Published: 02/03/2005
• Est. Priority Date: 01/17/1996
• Status: Abandoned Application

• Current Assignee: Hanger Solutions, LLC (IP Investments Group LLC)
• Original Assignee: Privacy Infrastructure Incorporated
• Inventors: Peckover, Douglas L., Zucker, Jeffrey Mark, Poore, Ralph Spencer
• Application Number:
  US10/924,626
• Publication Number:
  US 20050027618A1
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 21/6254 by anonymising data, e.g. decorrelating personal data from the owner's identification
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0615 Anonymizing

Abstract

A system and method of providing privacy through anonymity is described. As one aspect of the invention, a person registers at a privacy server and is given a pseudo identity that can be used to browse, register, purchase, pay for, and take delivery of products and services. Transactions are completed with the privacy server on a need-to-know basis. A seller communicates with the privacy server but only sees a demand, not the identity of the buyer. The financial institution communicates with the privacy server and sees the payment, not the merchandise. The freight company communicates with the privacy server and sees the package, not its contents. The privacy server operates in a manner that assures privacy and anonymity for the buyer and, if necessary, both the seller as well.

Claims

1-5. -5. (Canceled).

6. A method comprising:

establishing for a first user of an electronic network a key with a single-use characteristic, the key including a pseudo payment type; and

using the key and the single-use characteristic thereof to facilitate through the network a purchase by the first user of something from a second user, including using the pseudo payment type to facilitate payment for the purchase to the second user on behalf of the first user.

7. A method according to claim 6, including configuring the pseudo payment type to contain an identification of a financial institution which is different from each of the first and second users.

8. A method according to claim 7, wherein the using of the pseudo payment type includes communicating through the network with the financial institution, the financial institution making a payment to the second user on behalf of the first user.

9. A method according to claim 6,

wherein the first user maintains an actual payment type;

and

wherein the using of the pseudo payment type to facilitate payment includes making a payment to the second user on behalf of the first user under the pseudo payment type, while making a charge against the actual payment type without revealing the actual payment type to the second user.

10. A method according to claim 9, including:

selecting as the actual payment type an actual credit account; and

configuring the pseudo payment type to appear to be a credit account.

11. A method according to claim 6, including configuring the key to include a pseudo identity for the first user, the using of the key including providing the pseudo identity to the second user without revealing to the second user an actual identity of the first user.

12. A method according to claim 11, including configuring the pseudo identity to be a single-use pseudo identity, the single-use pseudo identity serving as the single-use characteristic of the key.

13. A method according to claim 6, including configuring the pseudo payment type to include a pseudo expiration date which is provided to the second user.

14. A method according to claim 6, including establishing a pseudo identity for the second user, the pseudo identity of the second user being provided to the first user without revealing to the first user an actual identity of the second user.

15. An apparatus comprising an electronic system that includes:

a first portion which establishes for a first user of an electronic network a key with a single-use characteristic, the key including a pseudo payment type; and

a second portion which facilitates use of the key and the single-use characteristic thereof to effect through the network a purchase by the first user of something from a second user, including use of the pseudo payment type to facilitate payment for the purchase to the second user on behalf of the first user.

16. An apparatus according to claim 15, wherein the pseudo payment type contains an identification of a financial institution which is different from each of the first and second users.

17. An apparatus according to claim 16, wherein the use of the pseudo payment type includes the second portion facilitating communication through the network with the financial institution to arrange for the financial institution to make a payment to the second user on behalf of the first user.

18. An apparatus according to claim 15,

wherein the first user maintains an actual payment type;

and

wherein the use of the pseudo payment type includes the second portion facilitating payment of an amount to the second user on behalf of the first user under the pseudo payment type, while making a charge for the amount against the actual payment type without revealing the actual payment type to the second user.

19. An apparatus according to claim 15, wherein the first portion configures the key to include a pseudo identity for the first user, the use of the key including provision of the pseudo identity to the second user without revealing to the second user an actual identity of the first user.

20. An apparatus according to claim 19, wherein the first portion configures the pseudo identity to be a single-use pseudo identity which serves as the single-use characteristic of the key.

21. An apparatus according to claim 15, wherein the first portion configures the pseudo payment type to include a pseudo expiration date which is provided to the second user.

22. An apparatus according to claim 15, wherein the first portion establishes for the second user a pseudo identity that is provided to the first user without revealing to the first user an actual identity of the second user.

23. A method comprising:

establishing at a financial institution a pseudo payment type for a user; and

using the pseudo payment type to make a monetary payment on behalf of the user to a party other than the financial institution, without revealing to that party an actual identity of the user.

24. A method according to claim 23, including configuring the pseudo payment type to include at least one of a pseudo number, a pseudo name, and a pseudo expiration date.

25. A method according to claim 23, including configuring the pseudo payment type to include one of a pseudo credit card number, a pseudo debit card number, a pseudo bank account number, and a pseudo frequent flyer account number.

26. A method according to claim 23,

including identifying for the financial institution an actual payment type of the user;

and

wherein the using of the pseudo payment type includes making a charge against the actual payment type, without revealing the actual payment type to the party receiving the payment under the pseudo payment type.

27. A method according to claim 23, including establishing at the financial institution a further pseudo payment type for the user.

28. A method according to claim 27,

including identifying for the financial institution two actual payment types of the user which are different;

including associating each of the actual payment types with a respective one of the pseudo payment types; and

wherein using of either pseudo payment type includes making a charge against the associated actual payment type, without revealing the associated actual payment type to the party receiving the monetary payment.

29. A method according to claim 27, including establishing at the financial institution a rule set defining when to use each of the pseudo payment types.

30. A method according to claim 29,

including establishing at a privacy server separate from the financial institution a pseudo identity for the user;

and

withholding from the privacy server information regarding the actual payment types and the rule set.

31. A method according to claim 30, including:

transmitting from a selected party to the privacy server a request for payment information;

responding to the request by transmitting from the privacy server to the selected party a list of the pseudo payment types in a selected order;

sending from the selected party to the financial institution an authentication request for the first pseudo payment type in the list; and

responding to a denial of authentication for the first pseudo payment type in the list by sending from the selected party to the financial institution an authentication request for the second pseudo payment type in the list.

32. A method according to claim 23, including establishing at a privacy server separate from the financial institution a pseudo identity for the user.

33. A method according to claim 32, including withholding from the privacy server information regarding the pseudo payment type.

34. A method according to claim 32, including registering the financial institution with the privacy server in advance of the establishing of the pseudo payment type.

35. An apparatus comprising an electronic system that includes:

a first portion which establishes at a financial institution a pseudo payment type for a user; and

a second portion which makes under the pseudo payment type a monetary payment on behalf of the user to a party other than the financial institution, without revealing to that party an actual identity of the user.

36. An apparatus according to claim 35, wherein the first portion configures the pseudo payment type to include at least one of a pseudo number, a pseudo name, and a pseudo expiration date.

37. An apparatus according to claim 35, wherein the first portion configures the pseudo payment type to include one of a pseudo credit card number, a pseudo debit card number, a pseudo bank account number, and a pseudo frequent flyer account number.

38. An apparatus according to claim 35,

wherein the first portion accepts information identifying an actual payment type of the user;

and

wherein the second portion makes a charge against the actual payment type, without revealing the actual payment type to the party receiving the monetary payment under the pseudo payment type.

39. An apparatus according to claim 35, wherein the first portion establishes at the financial institution a further pseudo payment type for the user.

40. An apparatus according to claim 39, wherein the first portion:

accepts information identifying two actual payment types of the user that are different;

associates each of the actual payment types with a respective one of the pseudo payment types; and

makes a charge against a respective actual payment type in association with each monetary payment made under any pseudo payment type, without revealing the associated actual payment type to the party receiving the monetary payment under the pseudo payment type.

41. An apparatus according to claim 39, wherein the first portion maintains a rule set defining when to use each of the pseudo payment types.

42. An apparatus according to claim 41,

including a privacy server;

including a third portion which establishes at the privacy server a pseudo identity for the user; and

wherein the first portion withholds from the third portion information regarding the actual payment types and the rule set.

43. An apparatus according to claim 42,

including a fourth portion which is associated with a selected party and which transmits from the selected party to the third portion at the privacy server a request for payment information;

wherein the third portion at the privacy server responds to the request by transmitting to the fourth portion a list of the pseudo payment types in a selected order;

wherein the fourth portion thereafter sends to the first portion a request for payment authentication by the financial institution with respect to the first pseudo payment type in the list; and

wherein the fourth portion responds to a denial of authentication for the first pseudo payment type in the list by sending to the first portion a request for payment authentication by the financial institution with respect to the second pseudo payment type in the list.

44. An apparatus according to claim 35, including:

a privacy server; and

a third portion which establishes at the privacy server a pseudo identity for the user.

45. An apparatus according to claim 44, wherein the first portion withholds from the third portion information regarding the pseudo payment type.

46. An apparatus according to claim 44, wherein the third portion registers the financial institution before the first portion establishes the pseudo payment type.