Widget-based integration of payment gateway functionality into transactional sites

• US 9,747,621 B1
• Filed: 09/23/2008
• Issued: 08/29/2017
• Est. Priority Date: 09/23/2008
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Kuruvila, Vinay
• Primary Examiner(s): Shaikh, Mohammad Z
• Application Number:
  US12/236,285
• Time in Patent Office: 3,262 Days
• Field of Search: 705 35- 42
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

Various embodiments of a payment service are disclosed. In some embodiments, a merchant can enable customer use of the payment service by adding widget code to a web page, such as a catalog or shopping cart page, of the merchant'"'"'s site. Thereafter, a user can invoke the payment service and complete a purchase transaction directly from the merchant site, without navigating or being redirected to a separate payment service site. In some embodiments, the user can complete the transaction without having or creating an account with the payment service.

Claims

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

automatically generating, by a server system of the payment service, a widget code segment;

communicating the widget code segment to a remote merchant server computer over the Internet, via a first network connection between the server system of the payment service and the remote merchant server computer;

the widget code segment, when loaded by a browser as part of a merchant web page of a merchant web site comprising a shopping cart, configured to;

add a first control selectable by a user to cause a payment form to be displayed on the merchant web page, the first control comprising a checkout button associated with the shopping cart, the payment form configured to receive payment instrument information and shipping information;

in response to user selection of the first control, cause a second control selectable by the user to be displayed on the merchant web page such that the user can complete a purchase transaction for one or more items of the merchant using the merchant web page and without having to sign in to or create an account with the payment service or register with the payment service, and without being redirected to a web site of the payment service or otherwise navigating away from the merchant web page; and

in response to user selection of the second control, cause an application programming interface to be called to establish a second connection over the Internet with a payment processing service executing on the server system of the payment service, the second connection using a secure transfer protocol;

receiving, by the server system of the payment service via the second network connection, a request from the computing device of a user, the request generated in response to user selection of the second control as displayed on the merchant web page, the request including the payment instrument information as entered into the payment form displayed on the merchant web page; and

processing the payment instrument information by the payment processing service of the server system of the payment service,

the server system of the payment service being separate from a server system that hosts the merchant web page, wherein only a portion of the merchant web page is refreshed during the period from user selection of the first control to the completion of the purchase transaction to present fields for user-entry of payment instrument information and shipping information, and wherein the remaining portion of the merchant web page, which presents graphical depictions of one or more items included in the shopping cart and selected for purchase, remains constant, wherein the code segment allows the user to interact with the payment service directly from the merchant web page to cause the transaction to be executed to completion, and without displaying to the user any indication that the payment is being processed by a party other than the merchant.

2. The method of claim 1, wherein the code segment does not specify each item or group of items of the merchant or a transaction price associated with each item or group of items of the merchant.

3. The method of claim 1, wherein the code segment specifies each item or group of items of the merchant and a transaction price associated with each item or group of items of the merchant.

4. The method of claim 3, wherein the code segment is adapted to be incorporated by the merchant into the merchant web page without modification or programming.

5. The method of claim 1, wherein the payment service does not retrieve pre-existing payment instrument information of the user.

6. The method of claim 1, wherein the payment service allows the user to login to a pre-existing account of the user.

7. The method of claim 1, wherein the payment service does not send a browser cookie to the computing device of the user or receive a browser cookie from the computing device of the user in performance of the purchase transaction.

8. The method of claim 1, wherein the code segment comprises JavaScript.

9. A computer-readable medium which stores executable instructions that embody the method of claim 1.

10. A system for providing a payment service, comprising:

a computer system comprising one or more physical servers, said computer system configured to at least;

automatically generate a widget code segment;

communicate the widget code segment to a remote merchant server computer over the Internet, via a first network connection between the computer system and the remote merchant server computer;

the widget code, when loaded by a browser as part of a merchant web page of a merchant web site, configured to;

add a first control selectable by a user to cause a payment form to be displayed on the merchant web page, the payment form configured to receive payment instrument information from the user;

in response to user selection of the first control, cause a second control selectable by the user to be displayed on the merchant web page such that the user can complete a purchase transaction for one or more items of the merchant using the merchant web page and without having to sign in to or create an account with the payment service or register with the payment service, and without being redirected to a web site of the payment service or otherwise navigating away from the merchant web page;

in response to user selection of the second control, cause an application programming interface to be called to establish a second connection over the Internet with the computer system, the second connection using a secure transfer protocol;

receive a request from a computing device of a user via the second network connection, the request generated in response to user selection of the second control as displayed on the merchant web page, the request including the payment instrument information as entered into the payment form displayed on the merchant web page; and

process the payment instrument information, said computer system being separate from a server system that hosts the merchant web page,

wherein only a portion of the merchant web page is refreshed during the period from user selection of the first control to the completion of the purchase transaction to present fields for user-entry of payment instrument information, and wherein a remaining portion of the merchant web page, which displays graphical representations of one or more items selected for purchase, remains constant,

further wherein the widget code segment allows the user to interact with the payment service directly from the merchant web page to cause the purchase transaction to be executed to completion, and without displaying to the user any indication that the payment is being processed by a party other than the merchant.

11. The system of claim 10, wherein the code segment allows the user to interact with the payment service directly from the merchant web page to cause the transaction to be executed to completion.

12. The system of claim 10, wherein the code segment does not specify each item or group of items of the merchant or a transaction price associated with each item or group of items of the merchant.

13. The system of claim 12, wherein the merchant web page comprises a shopping cart and the first control comprises a checkout button associated with the shopping cart.

14. The system of claim 10, wherein the code segment specifies each item or group of items of the merchant and a transaction price associated with each item or group of items of the merchant.

15. The system of claim 14, wherein the code segment is adapted to be incorporated by the merchant into the merchant web page without modification or programming.

16. The system of claim 10, wherein the payment service does not retrieve pre-existing payment instrument information of the user.

17. The system of claim 10, wherein the payment service allows the user to login to a pre-existing account of the user.

18. The system of claim 10, wherein the payment service does not send a browser cookie to the computing device of the user or receive a browser cookie from the computing device of the user in performance of the purchase transaction.

19. The system of claim 10, wherein the code segment comprises JavaScript.

20. The method of 1, wherein the server system of the payment service does not interact with the computing device of the user as part of the purchase transaction until receiving the request from the computing device of the user.

21. The system of 10, wherein the computer system does not interact with the computing device of the user as part of the purchase transaction until receiving the request from the computing device of the user.