Payment service capable of being integrated with merchant sites

• US 9,779,436 B2
• Filed: 12/19/2013
• Issued: 10/03/2017
• Est. Priority Date: 12/09/1999
• Status: Expired due to Term

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Bui, Hong Q.
• Primary Examiner(s): Frenel, Vanel
• Application Number:
  US14/135,134
• Publication Number:
  US 20150206215A1
• Time in Patent Office: 1,384 Days
• Field of Search: 705 35- 38, 705 44, 705 267, 235379
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0613 Third-party assisted
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• CPC Class Codes: G06Q 30/0643 Graphical representation of items or shoppers
• CPC Class Codes: G06Q 40/06 Asset management; Financial planning or analysis
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers

Abstract

A computer-implemented service integrates with merchant sites to enable registered users of the service to perform purchase transactions on the merchant sites. In one embodiment, a merchant can incorporate a reference to a display object served by the service into coding of a page of the merchant'"'"'s site. When the page is loaded by a user'"'"'s browser, the reference causes the browser to request the display object from the service for display on the page. If the user is recognized by the service, the service may return a personalized display object that includes functionality for the user to perform a purchase transaction using the service. Also disclosed are embodiments that enable users to initiate transfers of personal account information to the merchant sites.

Claims

1. A system, comprising:

a first server system that operates in a first network domain, said first server system storing account information, including payment information, of a user, said first server system providing a service for enabling users to place orders on merchant systems outside the first network domain without having to create accounts with, and without having to supply payment information to, such merchant systems; and

a second server system that operates in a second network domain that is distinct from the first network domain, said second server system hosting a merchant interface of a merchant, said merchant interface including a page that includes a reference to a display object served by the first server system, said reference configured to cause user computing devices that load the page from the second server system to request the display object from the first server system for display on the page;

said first server system operative to authenticate the user and to transmit, to a user computing device of the user, identification data for storage on the user computing device, said identification data associated with the first network domain but not the second network domain, said identification data including information associated with the user;

said first server system configured to respond to a request from the user computing device for the display object by at least (1) using the identification data, as returned by the user computing device, to associate the request for the display object with the user, and (2) returning to the user computing device a personalized display object for display on the page of the merchant interface, said personalized display object providing functionality for the user to use the service to place an order on the merchant interface, whereby the user can place said order on the merchant interface without creating an account with, and without supplying payment information to, the second server system.

2. The system of claim 1, wherein the first server system is responsive to placement of the order by the user via the personalized display object by using the stored payment information to charge the user for the order as a payment intermediary.

3. The system of claim 1, wherein the personalized display object includes a text entry area for user entry of a password or passcode, and the first server system is configured to use the password or passcode as entered into said text entry area to authenticate the user.

4. The system of claim 1, wherein the first server system is responsive to placement of the order via the personalized display object by sending information associated with the order and the user to the merchant.

5. The system of claim 1, wherein the personalized display object is personalized with a name of the user.

6. The system of claim 1, wherein the first server system is additionally responsive to placement of the order by transmitting to the user computing device a redirect URL that redirects the user computing device to a second page of the merchant interface, said redirect URL encoded with information that enables the second server system to identify the user and personalize the second page for the user.

7. The system of claim 6, wherein the second page is an order history page.

8. The system of claim 1, wherein the personalized display object is configured for display as a box on said page.

9. The system of claim 1, wherein the personalized display object comprises a frame.

10. The system of claim 1, wherein the personalized display object comprises a personalized graphic.

11. The system of claim 1, wherein the first server system provides functionality for the user to log into the service and view a history of purchase transactions performed by the user across a plurality of merchant interfaces.

12. A system, comprising:

a server that operates in a first network domain, said server programmed to provide a payment service that enables users to perform payment transactions on merchant interfaces, including a merchant interface associated with a second network domain that is distinct from the first network domain; and

a database in communication with the server, said database storing account information, including payment information, of users registered with the payment service;

said server programmed to implement a process that comprises;

authenticating a user with the payment service;

transmitting identification data associated with the payment service to a user computing device associated with the user for storage thereon, said identification data corresponding to the first network domain but not the second network domain;

subsequently receiving, from the user computing device, said identification data and a request for a display object for display on a page of the merchant interface, said request for the display object generated by the user computing device in response to a reference included in coding of said page; and

responding to the request by transmitting to the user computing device, for display on the page of the merchant interface, a personalized display object that includes user information associated with the identification data, said personalized display object providing functionality for the user to use the payment service to place an order with a merchant;

said server thereby enabling the user to place an order with the merchant without having an account with, and without providing payment information to, the merchant.

13. The system of claim 12, wherein the server is additionally configured to use the payment information to charge the user for the order as a payment intermediary.

14. The system of claim 12, wherein the personalized display object includes a text entry box for user entry of a password or passcode, and the server is configured to use the password or passcode as entered into the text entry box to authenticate the user with the payment service.

15. The system of claim 12, wherein the personalized display object is configured for display as a box on said page.

16. The system of claim 12, wherein the personalized display object is configured for display as a frame on said page.

17. The system of claim 12, wherein the personalized display object enables the user to authorize a purchase transaction with a single selection action.

18. The system of claim 12, wherein the user information associated with the identification data includes a name of the user.

19. The system of claim 12, wherein the server is configured to send shipping information of the user to the merchant in connection with the order.

20. The system of claim 12, wherein the server is responsive to placement of the order by transmitting to the user computing device a redirect URL that redirects the user computing device to a second page of the merchant interface, said redirect URL encoded with information that identifies the user.

21. A method comprising:

registering a user with a payment service that provides functionality for users to pay for items on merchant systems without creating accounts on, and without providing payment information to, said merchant systems, wherein registering the user comprises collecting and storing authentication information and payment information of the user, said payment service hosted on a first server system in a first network domain;

transmitting identification data to a user computing device of the user for storage thereon, said identification data corresponding to the first network domain and including information that enables the first server system to identify the user;

receiving, by the first server system, from the user computing device, the identification data and a request for a display object for display on a page of a merchant system, said merchant system hosted on a second server system in a second network domain, wherein the request is generated by the user computing device based on a reference included in coding of said page; and

responding, by the first server system, to the request for the display object by transmitting to the user computing device a personalized display object for display on the page of the merchant system, said personalized display object personalized with information associated with the user, said personalized display object providing functionality for the user to initiate a purchase transaction in which an order is placed with the merchant system and in which the payment service, operating as a payment intermediary, uses the payment information to charge the user for the order.

22. The method of claim 21, wherein the display object includes an area for user entry of a password or passcode for authenticating with the payment service.

23. The method of claim 21, wherein the personalized display object is personalized with a name of the user.

24. The method of claim 21, wherein the personalized display object is configured for display as a box on said page.

25. The method of claim 21, wherein the personalized display object is configured for display as a frame.

26. The method of claim 21, further comprising responding, by the first server system, to placement of the order by transmitting to the user computing device a redirect URL that redirects the user computing device to a second page of the merchant system, said redirect URL encoded with information that enables the second server system to identify the user.

27. A computer-implemented method of providing a payment service, the method comprising:

registering a user and a merchant with a computer-implemented service that acts as a payment intermediary between users and merchants, said service comprising a server that operates in a first network domain that is separate from a network domain of a merchant system of said merchant, said service being separate from the merchant system;

receiving, at the server, a request to use the service to perform a purchase transaction, said request generated in response to a user interaction with an interface of the merchant system;

responding to the request with said server by generating and returning an object configured to provide a selectable object on the interface of the merchant system, said selectable object being selectable by the user to place an order;

receiving, with said server, a message generated in response to user selection of the selectable object as displayed on the interface of the merchant system, said message corresponding to an order placed by the user; and

in response to the message, charging the user on behalf of the merchant, such that the user is charged by said service with said service acting as a payment intermediary between the user and the merchant;

wherein the method is performed in its entirety by said computer-implemented service.

28. The computer-implemented method of claim 27, wherein selectable object is a selectable purchase object displayed on the interface of the merchant system.