User enhanced authentication system for online purchases

• US 8,612,305 B2
• Filed: 10/27/2009
• Issued: 12/17/2013
• Est. Priority Date: 10/31/2008
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Dominguez, Ben, Fisher, Douglas, Chan, Julie
• Primary Examiner(s): Misiaszek, Michael
• Application Number:
  US12/606,522
• Publication Number:
  US 20100114740A1
• Time in Patent Office: 1,512 Days
• Field of Search: 705 261- 272
• US Class Current: 705/26.35
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• 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 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/409 Device specific authentication in transaction processing
• 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/0603 Catalogue ordering
• CPC Class Codes: G06Q 30/0609 Buyer or seller confidence or verification
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety

Abstract

Embodiments of the invention are directed to methods, systems, devices and computer-readable media. In embodiments of the invention, a user is authenticated using an authentication process that is capable of authenticating a user using an inline authentication form that can authenticate a consumer without transferring a session maintained by a merchant. The inline authentication form is used if the components of the authentication system are capable of supporting an inline authentication form. If the components of the system cannot support an inline authentication form, a different authentication process is used. In one embodiment, an inline authentication form is presented to the user asynchronously. This inline authentication form may be presented within an iFrame embedded in a merchant'"'"'s checkout page after verifying that the components to be used during the authentication can support the inline authentication form.

Claims

1. A merchant server, the merchant server comprising a processor and a computer readable medium having a computer readable code embodied therein, wherein the computer readable code is adapted to be executed on the processor, wherein the computer readable code is adapted to be executed to implement a method, the method comprising:

sending to a consumer a merchant checkout page, wherein the merchant checkout page is configured to receive from the merchant server an indication of whether an issuer server is configured to authenticate the consumer using an inline authentication form;

sending an enrollment verification request to a directory server; and

receiving an enrollment verification response from the directory server, wherein the enrollment verification response includes an indication of whether the issuer server that is capable of authenticating the consumer conducting an online transaction is configured to authenticate the consumer using the inline authentication form,

wherein the merchant checkout page includes support for a shopping cart, wherein the shopping cart is associated with a session, wherein the inline authentication form is configured to permit the issuer server to authenticate the consumer without navigating away from the session associated with the shopping cart,

wherein the merchant checkout page includes an asynchronous JavaScript interface to receive from the merchant server the indication of whether the issuer server is configured to authenticate the consumer using the inline authentication form.

2. The merchant server of claim 1 wherein the merchant checkout page is configured to send an authentication request message to the issuer server, wherein the authentication request message includes an indication of whether the merchant checkout page is configured to support the inline authentication form when the issuer server is configured to authenticate the consumer using the inline authentication form.

3. The merchant server of claim 1 wherein a standard authentication form is used by the merchant checkout page to authenticate the consumer when the issuer server does not support the inline authentication form.

4. The merchant server of claim 3 wherein the standard authentication form and the inline authentication form use a common authentication protocol to authenticate the consumer.

5. The merchant server of claim 1 wherein a standard authentication form is used by the merchant checkout page to authenticate the consumer when the merchant checkout page does not support the inline authentication form.

6. The merchant server of claim 5 wherein the standard authentication form and the inline authentication form use a common authentication protocol to authenticate the consumer.

7. The merchant server of claim 1 wherein the method further comprises:

processing the online transaction between a merchant and the consumer after the issuer server indicates to the merchant server that the consumer has been successfully authenticated.

8. The merchant server of claim 1 wherein the inline authentication form is implemented using an iFrame in the merchant checkout page.

9. The merchant server of claim 1 wherein the directory server maintains a directory specifying the location and capabilities of different card issuer systems.

10. The merchant server of claim 1 wherein the directory server stops authentication if an issuer associated with the issuer server does not support authentication.

11. The merchant server of claim 1 wherein the enrollment verification request includes electronic card information that identifies an issuer associated with an electronic commerce card.

12. The merchant server of claim 1 wherein the directory server includes a list of all electronic commerce card issuers and their associated electronic commerce card number ranges.

13. The merchant server of claim 5 wherein the method further comprises:

determining whether the merchant checkout page supports inline authentication without transferring the session.

14. The merchant server of claim 13 wherein an authentication request message is sent to an issuer.

15. The merchant server of claim 13 wherein the authentication request message includes an indication of whether the merchant checkout page supports inline authentication and the consumer'"'"'s client can support the inline authentication without transferring the session.

16. The merchant server of claim 1 wherein the enrollment verification request includes a pseudonym that is used by an issuer operating the issuer server to identify an electronic commerce card associated with the pseudonym.

17. The merchant server of claim 1 wherein the inline authentication form is transparent, re-sizable, and movable by the consumer.