Electronic commerce system

• US 8,781,965 B2
• Filed: 10/11/2012
• Issued: 07/15/2014
• Est. Priority Date: 10/11/2011
• Status: Active Grant

• Current Assignee: Phyllis A. Huster
• Original Assignee: Phyllis A. Huster
• Inventors: Huster, Phyllis A.
• Primary Examiner(s): Shaikh, Mohammad Z
• Application Number:
  US13/650,033
• Publication Number:
  US 20130091058A1
• Time in Patent Office: 642 Days
• Field of Search: 705 35- 45
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices

Abstract

Embodiments of the present invention provide methods, systems, and computer readable storage media to facilitate a transaction in an electronic commerce system. Aspects of the embodiments include receiving a request at a network-connected transaction server to transfer one or more transaction items involving a first user account on the transaction server, selecting a delivery instrument from one or more available delivery instruments associated with the first user account on the transaction server, authorizing the request based at least upon a unique transaction identifier associated with the request and a unique user device identifier associated with a user access device, transferring a quantity of the one or more transaction items into or out of the selected delivery instrument, wherein the quantity is determined at least based upon the authorized request.

Claims

1. A method to facilitate a transaction, comprising:

receiving, at a network-connected transaction server, a request to transfer one or more transaction items involving a first user account on the transaction server, wherein the transaction server is configured to receive requests from a plurality of user types corresponding to a plurality of transaction types, wherein the transaction items include money, money equivalents, loyalty credits, products, services, and content;

selecting a delivery instrument from one or more available delivery instruments associated with the first user account on the transaction server;

authorizing, by the transaction server, the request based at least upon a unique identifier including a unique transaction identifier associated with the request, a unique user device identifier associated with a user access device, and a unique user identifier, wherein the unique transaction identifier and the unique user device identifier provide a character sequence that represents a device fingerprint, information regarding the transaction items and, wherein the unique identifier includes analytics data encoding information on the user'"'"'s purchase and payment behavior based on past performance, and wherein the unique user identifier has embedded logic configured to cause the unique user identifier to evolve over time based on its security level, so that the unique user identifier becomes more trusted as the user executes more transactions;

validating the transaction using embedded context in the character sequence of the unique identifier; and

transferring a quantity of the one or more transaction items into or out of the selected delivery instrument, wherein the quantity is determined at least based upon the authorized request, wherein the selected delivery instrument are repositories or accounts associated with respective users, merchants, financial or retail institutions, organizations, content providers, or direct users.

2. The method of claim 1, wherein the unique transaction identifier includes an identification of a geographic location associated with the transaction.

3. The method of claim 1, wherein the authorizing the request comprises:

determining a geographic location associated with the unique user device identifier;

comparing the determined geographic location associated with the unique user device identifier with a geographic region associated with the transaction included in the unique transaction identifier; and

permitting the transaction based upon the comparing.

4. The method in claim 3, wherein the authorizing the request further comprises:

writing a transaction record in a log file, wherein the transaction record associates the unique transaction identifier, the associated user identifier, and the associated user device identifier.

5. The method of claim 1, wherein the selecting a delivery instrument comprises:

selecting a financial instrument from the one or more available delivery instruments enrolled in the transaction server and associated with the first user account.

6. The method of claim 5, wherein the one or more available delivery instruments enrolled in the transaction server include a plurality of different financial and non-financial instrument types.

7. The method of claim 5, wherein the selecting is based upon the unique transaction identifier.

8. The method of claim 5 wherein the one or more available delivery instruments enrolled in the transaction server includes at least a money account and a merchant loyalty points account.

9. The method of claim 5, wherein the one or more available delivery instruments enrolled in the transaction server includes at least a money account and a content account associated with a content repository.

10. The method of claim 1, wherein the transferring comprises:

transferring a money amount and at least one of a money amount equivalent or content into or out of the first user account.

11. The method of claim 1, wherein the transferring comprises:

accessing a stored profile associated with the first user account; and

determining the quantity of the one or more transaction items based upon the accessed stored profile.

12. The method of claim 1, wherein the transferring comprises:

transferring the quantity of the one or more transaction items from the first user account to a third-party user using a programming-interface published by the third-party user.

13. The method of claim 12, wherein the third-party user does not have an associated delivery instrument enrolled in the transaction server.

14. The method of claim 1, further comprising:

determining a donation associated with the request, wherein the donation is in addition to the quantity of the one or more transaction items transferred to a second user; and

transferring the donation from the first user account to a third user.

15. The method of claim 14, wherein the donation and the third user are determined based upon the unique transaction identifier.

16. The method of claim 1, further comprising:

detecting a presence of the user access device within at least one of a geographically defined area or a virtual area associated with a second user;

determining a first user associated with the user access device and the first user account;

accessing merchant information associated with the second user to determine one or more available transaction choices;

pushing the one or more available transaction choices to the user access device;

receiving a selection of at least one of the available transaction choices from the first user, wherein the selection is communicated from the user access device to the transaction server; and

communicating the selection to a device associated with the second user.

17. The method of claim 16, wherein the pushed one or more transaction choices include an option to make a donation, and wherein the received selection includes a donation amount, and the method further comprising:

transferring the donation amount from the first user account to a third user.

18. The method of claim 16, further comprising:

selecting, interactively with the first user, suggested transaction choices from merchants in proximity to the geographically defined area or the virtual area, wherein the pushed one or more transaction choices include the selected suggested transaction choices.

19. The method of claim 16, wherein accessing merchant information associated with the second user comprises:

determining the one or more transaction choices based upon the merchant information associated with the second user and profile information of the first user.

20. The method of claim 16, wherein the merchant information is updated in real-time in response to ongoing merchant operations.

21. The method of claim 1, the method further comprising:

transferring content into or out of a second user account associated with the first user on the transaction server in response to the request.

22. The method of claim 21, wherein the transferring content into or out of a second user account comprises:

transferring the content out of a second user account associated with the first user and into a storage location accessible by a second user.

23. The method of claim 21, wherein the transferring content into or out of a second user account comprises:

transferring the content out of a second user account associated with the first user and into a storage location seen as local to the second user device, but logically associated with a storage location accessible by second user device.

24. The method of claim 1, wherein the transaction server provides a merchant exchange which enables the transaction server to communicate with a plurality of merchant types and their associated delivery instruments within the transaction.

25. The method of claim 1, wherein transferring further comprises transferring the quantity of the one or more transaction items between the selected delivery instrument and a second user account on the transaction server.

26. The method of claim 1, wherein the device fingerprint includes a global hash.

27. The method of claim 1, wherein the device fingerprint includes a legacy network number.

28. A system for facilitating a transaction, comprising:

at least one processor;

a network-connected transaction server configured to execute on the at least one processor and further configured to;

receiving, at a network-connected transaction server, a request to transfer one or more transaction items involving a first user account on the transaction server, wherein the transaction server is configured to receive requests from a plurality of user types corresponding to a plurality of transaction types, wherein the transaction items include money, money equivalents, loyalty credits, products, services, and content;

selecting a delivery instrument from one or more available delivery instruments associated with the first user account on the transaction server;

authorizing, by the transaction server, the request based at least upon a unique identifier including a unique transaction identifier associated with the request, a unique user device identifier associated with a user access device, and a unique user identifier, wherein the unique transaction identifier and the unique user device identifier provide a character sequence that represents a device fingerprint, information regarding the transaction items and, wherein the unique identifier includes analytics data encoding information on the user'"'"'s purchase and payment behavior based on past performance, and wherein the unique user identifier has embedded logic configured to cause the unique user identifier to evolve over time based on its security level, so that the unique user identifier becomes more trusted as the user executes more transactions;

validating the transaction using embedded context in the character sequence of the unique identifier; and

transferring a quantity of the one or more transaction items into or out of the selected delivery instrument, wherein the quantity is determined at least based upon the authorized request, wherein the selected delivery instrument are repositories or accounts associated with respective users, merchants, financial or retail institutions, organizations, content providers, or direct users.

29. The system of claim 28, further comprising:

a unique identifier registry communicatively coupled to the transaction server and configured to generate the unique transaction identifier.

30. The system of claim 28, further comprising:

a merchant exchange communicatively coupled to the transaction server and configured to transfer a money amount or a money equivalent from the first user account to an account of a third-party using a software interface published by the third-party, wherein the account of the third-party is not registered on the transaction server.

31. The system of claim 28, further comprising:

at least one user access device configured to;

detect its presence within a geographically or virtually defined area associated with a second user; and

notify the transaction server regarding the detection.

32. The system of claim 28, further comprising:

at least one user access device configured to;

display a menu title and a plurality of menu options on a display of a mobile device, wherein the menu options are displayed as selectable areas arranged around the menu title;

receive a user input selecting one of the menu options;

determine a second menu title based upon the user input; and

display the second menu title and a plurality of second menu options on the display, wherein the second menu options are displayed as selectable areas arranged around the second menu title.

33. The system of claim 28 further comprising:

at least one user access device configured to;

displaying one or more objects on a display, wherein each of the objects represent a transaction choice;

displaying an input area on the display;

receiving a user input, wherein the user input places at least one of the one or more objects in the displayed input area;

responsive to the user input, starting one or more processes to process the respective transaction choices corresponding to the at least one of the one or more objects placed in the displayed input area; and

displaying a result on the display upon completion of at least one of the one or more processes.

34. A non-transitory computer readable storage medium storing instructions that, when executed by a processor, causes the processor to perform a method to facilitate a transaction, comprising;

receiving, at a network-connected transaction server, a request to transfer one or more transaction items involving a first user account on the transaction server, wherein the transaction server is configured to receive requests from a plurality of user types corresponding to a plurality of transaction types, wherein the transaction items include money, money equivalents, loyalty credits, products, services, and content;

selecting a delivery instrument from one or more available delivery instruments associated with the first user account on the transaction server;

authorizing, by the transaction server, the request based at least upon a unique identifier including a unique transaction identifier associated with the request, a unique user device identifier associated with a user access device, and a unique user identifier, wherein the unique transaction identifier and the unique user device identifier provide a character sequence that represents a device fingerprint, information regarding the transaction items and, wherein the unique identifier includes analytics data encoding information on the user'"'"'s purchase and payment behavior based on past performance, and wherein the unique user identifier has embedded logic configured to cause the unique user identifier to evolve over time based on its security level, so that the unique user identifier becomes more trusted as the user executes more transactions;

validating the transaction using embedded context in the character sequence of the unique identifier; and

transferring a quantity of the one or more transaction items into or out of the selected delivery instrument, wherein the quantity is determined at least based upon the authorized request, wherein the selected delivery instrument are repositories or accounts associated with respective users, merchants, financial or retail institutions, organizations, content providers, or direct users.