PAYMENT SERVICE TO EFFICIENTLY ENABLE ELECTRONIC PAYMENT

• US 20100325042A1
• Filed: 08/30/2010
• Published: 12/23/2010
• Est. Priority Date: 03/21/2003
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Listwon, Benjamin Gregg, Levchin, Max R., Kang, David Young-June, Li, David Ching
• Granted Patent: US 7,930,247 B2
• Time in Patent Office: Days
• US Class Current: 705/40
• 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/04 Payment circuits
• 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/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• 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: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0609 Buyer or seller confidence or verification
• CPC Class Codes: G06Q 30/0613 Third-party assisted
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal

Abstract

A method to redirect a browser client is disclosed. The method comprises storing information at a payment service web site that includes a return URL (uniform resource locator) corresponding to a web-based interface hosted by a merchant web site. Next, the method comprise extracting the return URL embedded in the information and comparing, the return URL to a reference return URL corresponding to the web-based interface hosted by the merchant web site. Finally, the method comprises identifying the return URL matches the reference return URL and redirecting the browser client to the web-based interface hosted by the merchant web site responsive to the identifying the match.

Claims

1. A computer implemented method to redirect a browser client, the method comprising:

storing, using one or more processors, information at a payment service web site, the information including a return URL (uniform resource locator) corresponding to a web-based interface hosted by a merchant web site;

extracting, using the one or more processors, the return URL embedded in the information;

comparing, using the one or more processors, the return URL that is extracted from the information to a reference return URL corresponding to the web-based interface hosted by the merchant web site;

identifying the return URL matches the reference return URL; and

redirecting, using the one or more processors, the browser client to the web-based interface hosted by the merchant web site responsive to the identifying the match.

2. The computer implemented method of claim 1, further comprising authenticating the merchant web site.

3. The computer implemented method of claim 2, wherein the authenticating the merchant web site comprises:

receiving a merchant identity (ID) from the merchant web site; and

identifying the merchant ID in a merchant profile that is associated with a merchant to authenticate the merchant as enabled for transactions including the payment service web site.

4. The computer implemented method of claim 3, wherein the merchant ID includes an email address.

5. The computer implemented method of claim 3, wherein the receiving the information includes the payment service web site receiving a URL (uniform resource locator).

6. The computer implemented method of claim 1, further comprising providing an API (application program interface) to the merchant web site.

7. The computer implemented method of claim 1, wherein the web-based interface hosted by the merchant web site does not include an option to enable a consumer user to make payment of the one or more products via the payment service web site.

8. The computer implemented method of claim 1, further comprising communicating an interface to enable an administrator for the merchant web site to register a plurality of reference return URLs with the payment service web site.

9. The computer implemented method of claim 8, wherein the plurality of reference return URLs respectively correspond to a plurality of web pages hosted by the merchant web site.

10. The computer implemented method of claim 1, further comprising communicating a reply that includes an authorization to use the payment service web site.

11. The computer implemented method of claim 1, further comprising:

receiving the information, via the browser client, from the merchant web site, the information including the return URL; and

retrieving the reference return URL from a user profile that is associated with the merchant web site to be used'"'"'for transactions involving the merchant web site.

12. A tangible machine readable media that stores instructions that, when executed by a machine, cause the machine to:

store information at a payment service web site, the information includes a return URL (uniform resource locator) that corresponds to a web-based interface hosted by a merchant web site;

extract the return URL embedded in the information;

compare the return URL that is extracted from the information to a reference return URL that corresponds to the web-based interface hosted by the merchant web site;

identify the return URL matches the reference return URL; and

redirect the browser client to the web-based interface hosted by the merchant web site responsive to the identification of the match.

13. The computer implemented method of claim 12, further comprising authenticating the merchant web site.

14. The computer implemented method of claim 13, wherein the authenticating the merchant web site comprises:

receiving a merchant identity (ID) from the merchant web site; and

identifying the merchant ID in a merchant profile that is associated with a merchant to authenticate the merchant as enabled for transactions including the payment service web site.

15. The computer implemented method of claim 14, wherein the merchant ID includes an email address.

16. The computer implemented method of claim 14, wherein the receiving the information includes receiving a URL (uniform resource locator).

17. The computer implemented method of claim 12, further comprising providing an API (application program interface) to the merchant web site.

18. The computer implemented method of claim 12, wherein the web-based interface hosted by the merchant web site does not include an option to enable a consumer user to make payment of the one or more products via the payment service web site.

19. The computer implemented method of claim 12, further comprising communicating an interface to enable an administrator for the merchant web site to register a plurality of reference return URLs with the payment service web site.

20. The computer implemented method of claim 19, wherein the plurality of reference return URLs respectively correspond to a plurality of web pages hosted by the merchant web site.

21. The computer implemented method of claim 12, further comprising communicating a reply that includes an authorization to use the payment service.

22. The computer implemented method of claim 12, further comprising:

receiving the information, via the browser client, from the merchant web site, the information including the return URL; and

retrieving the reference return URL from a user profile that is associated with the merchant web site to be used for transactions involving the merchant web site.