US 9,898,740 B2Grant
Online challenge-response
Issue Date:2018-02-20
•21 Claims
•18 Drawing Sheets
Abstract
Embodiments of the invention enable cardholders conducting an online transaction to be authenticated in real-time using a challenge-response application. The challenge-response application can be administered by an issuer or by a third party on-behalf-of an issuer. A challenge question can be presented to the cardholder, and the cardholder's response can be verified. The challenge question presented can be selected based on an analysis of the risk of the transaction and potentially other factors. A variety of dynamic challenge questions can be used without the need for the cardholder to enroll into the program. Additionally, there are many flexible implementation options of the challenge-response application that can be adjusted based on factors such as the location of the merchant or the location of the consumer.
Metadata
Assignee
- Visa International Service Association
Inventors
- Kevin Weller
- Kim Steele
- Krishna Koganti
- Patrick Faith
Application Information
Application Number:US 14/273,331
Filing Date:2014-05-08
Priority Date:2008-11-06
Art Unit:3695
Classifications
IPC:
G06Q40/00G06Q20/40G06Q20/12G06F21/31G06Q30/06H04L9/32G06Q50/26
Patent Drawings (18 sheets)
Description
Cross-References to Related Applications
[0001] This application is a continuation application of U.S. patent application Ser. No. 13/964,992, filed on Aug. 12, 2013, which is a continuation application of U.S. patent application Ser. No. 12/613,395, filed on Nov. 5, 2009, now U.S. Pat. No. 8,533,118 and issued Sep. 10, 2013, which is a non-provisional of and claims the benefit of U.S. Patent Application No. 61/112,124, entitled “Online Challenge-Response,” filed on Nov. 6, 2008, which is herein incorporated by reference in its entirety for all purposes.
Background
[0002] A large number of merchants maintain an online presence through the use of the Internet and the World Wide Web. In fact, some merchants maintain no physical stores at all. Instead, these merchants conduct all of their transactions over the Internet. Merchants engaging in electronic commerce are sometimes referred to as e-commerce merchants or online merchants. E-commerce merchants face many challenges compared to physical merchants.
[0003] Transactions conducted at a physical store may use payment instruments that also have a physical manifestation. For example, cash and personal checks are common physical payment instruments. Even when transaction accounts, such as credit or debit accounts, are used, the purchaser will typically be in possession of a physical token representing the account. A token, such as a credit card, can be examined by a merchant to confirm that the purchaser is in possession of the token and, to some extent, confirm the purchaser is authorized to use the token. For example, a merchant may examine the signature panel on the rear of a transaction card and compare it with a signature of the person using the transaction card. A match can be an indication that the user is authorized to use the card.
[0004] The use of physical payment instruments, such as cash and checks, in an e-commerce environment is typically not practical. As such, the use of transaction accounts in e-commerce is very common. Unfortunately, the use of transaction accounts has also lead to an increase in the potential for fraudulent use. The techniques used by a physical merchant to prevent fraud, such as verifying that the purchaser is in possession of the token and that signatures match, are typically not available in an e-commerce environment. An online merchant is typically able to obtain the transaction account number, the expiration date, and potentially additional token identifying information (e.g. cardholder verification value—the 3 digit number in the signature panel of most transaction cards) from the user during a checkout process on the e-commerce site. However, the merchant has no way of verifying that the user is actually in possession of the transaction card. Furthermore, even if the user is in possession of the transaction card, the merchant is not able to verify that the purchaser is authorized to use the transaction card.
[0005] Electronic commerce card associations and issuers have also instituted authentication systems to ensure that electronic commerce cards are only used by authorized cardholders. One example of an authentication system enables a cardholder to associate a password or other identifying information with an electronic commerce card. To make a purchase online, the consumer must provide the password, or other identifying information, associated with the electronic commerce card. This ensures that the person possessing the electronic commerce card is actually authorized to use the electronic commerce card.
[0006] While such authentication methods are effective, a number of improvements can be made. Better ways to authenticate consumers are desirable. Embodiments of the invention address the above problems, and other problems, individually and collectively.
Brief Summary
[0007] Embodiments of the invention enable cardholders conducting an online transaction to be authenticated in real-time using a challenge-response application. Other embodiments of the invention enable cardholders conducting an online transaction to be authenticated in real-time using a challenge-response application that has been integrated with a password-based authentication system. Challenge-response applications provide the opportunity to reduce lost-stolen and counterfeit fraud, and provide a streamlined and enhanced referral process. The challenge-response application can be administered by an issuer or by a third party on behalf of an issuer. A challenge question can be presented to the cardholder, and the cardholder's response can be verified. The challenge question presented can be selected based on an analysis of the risk of the transaction (e.g., first time buyer, large ticket size, type of goods) and potentially other factors (e.g., first time buyer, non-US IP address, large ticket size, high risk merchant categories, geo-location of device, frequency, time of day, etc.). A variety of static, semi-dynamic, and dynamic challenge questions can be used without the need for the cardholder to enroll into the program. Additionally, there are many flexible implementation options of the challenge-response application that can be adjusted based on factors such as the location of the merchant or the location of the cardholder.
[0008] The challenges can be based on cardholder personal information (e.g., last four digits of your social security number, the month and day of your birthday) and on purchase transaction information (e.g., on which airlines did you purchase a ticket from in the past 60 days, in which states did you complete an in-store purchase in the past 30 days). Multiple challenges can also be presented, and the use of multiple challenges may allow for questions relating to both personal information and purchase transaction information.
[0009] Responses and cardholder device information can be used to authenticate the cardholder real-time, or can also be stored and sent to a forensic server for later offline analysis. Collected device information may include data such as the cardholder's IP address, browser version, browser language, date, time, and other device related information. The information can be used to help to determine the risk-level of the purchase, as well as to authenticate the cardholder. For example, a United States issued card being used from a location outside of the United States presents a higher risk than the same card being used from a location close to the cardholder's residence. Also, over time, it is possible to track and associate transaction history with specific devices to provide additional risk management capabilities. For example, if no fraud has occurred on a device over the past year, the device presents a lower risk than a device that has been fraudulently used in the recent past.
[0010] Challenges and response can also be used in conjunction with a password-based authentication system. Challenges and responses can be used in combination with passwords for various transactions. Challenges and responses can also be used for other related aspects of a password-based authentication system, such as password recovery.
[0011] One embodiment is directed to a method comprising: receiving an authentication request from a merchant's e-commerce site to authenticate a user engaging in a transaction on the e-commerce site; redirecting the user to a transaction routing system; determining at the transaction routing system, an issuer system, or both, if the user should be authenticated using a challenge response sequence, the determination based on a profile of the transaction or the user; issuing a challenge message to the user from the transaction routing system, the issuer system, or both, the challenge message being static, dynamic or semi-dynamic; receiving a response from the user; approving or denying the authentication based on the response; and sending an authentication status to the merchant's e-commerce site indicating if the user has been authenticated, wherein if the user is authenticated the merchant's e-commerce site proceeds to obtain authorization for the transaction.
[0012] Another embodiment is directed to transaction routing system comprising: a processor; and a memory coupled to the processor, the memory comprising computer code for receiving an authentication request from a merchant's e-commerce site to authenticate a user engaging in a transaction on the e-commerce site, computer code for redirecting the user to a transaction routing system, computer code for determining at the transaction routing system, an issuer system, or both, if the user should be authenticated using a challenge response sequence, the determination based on a profile of the transaction or the user, computer code for issuing a challenge message to the user from the transaction routing system, the issuer system, or both, the challenge message being static, dynamic or semi-dynamic, computer code for receiving a response from the user, computer code for approving or denying the authentication based on the response, and computer code for sending an authentication status to the merchant's e-commerce site indicating if the user has been authenticated, wherein if the user is authenticated the merchant's e-commerce site proceeds to obtain authorization for the transaction.
[0013] Yet another embodiment is directed to a method comprising: receiving an authentication request from a merchant's e-commerce site to authenticate a user engaging in a transaction on the e-commerce site; redirecting the user to a transaction routing system; determining at the transaction routing system, an issuer system, or both, if the user should be authenticated using a challenge response sequence, the determination based on a profile of the transaction or the user; issuing a challenge message to the user from the transaction routing system, the issuer system, or both, over a first communications network, the challenge message being static, dynamic or semi-dynamic; sending at least a portion of an expected challenge response to the user via a second communications network; receiving a challenge response from the user over the first communication network, the response containing at least a portion of the expected challenge response; approving or denying the authentication based on the challenge response message; and sending an authentication status to the merchant's e-commerce site indicating if the user has been authenticated, wherein if the user is authenticated the merchant's e-commerce site proceeds to obtain authorization for the transaction.
[0014] Other embodiments of the invention are directed to users using phones to engage in transactions processed according to the above systems and methods.
Brief Description of the Drawings
[0015] FIGS. 1-12 shows various block diagrams of embodiments of a system that can be used in some embodiments of the invention.
[0016] FIG. 13 shows a block diagram of a computer system that can be used according to various embodiments.
[0017] FIGS. 14-17 show screenshots that can be used in embodiments of the invention.
Detailed Description
[0018] Challenge-Response is an authentication mechanism whereby a cardholder is asked a question whose answer would presumably only be known by the cardholder. In some cases, the question may require a static answer, such as “What are the last four digits of your social security number?” In other cases, the question may be based on a cardholder's transaction history, and thus may require a more dynamic answer. An example of such a question could be “Did you eat at an Italian restaurant yesterday?” Unlike a static password challenge, Challenge-Response questions can be created dynamically, and may vary depending on the particular characteristics of the current transaction.
[0019] Embodiments of this disclosure integrate Challenge-Response authentication into existing authentication systems that use password mechanisms to help authenticate transactions. A payment processing network or an issuer may initiate a Challenge-Response sequence in order to authenticate a cardholder performing a transaction. In some cases, this may be done in addition to password authentication previously enabled by the system. Challenge-Response sequences may be initiated by payment processing networks or issuers based on specified criteria and can be performed by either party.
[0020] The criteria used to determine when Challenge-Response authentication will be utilized can be very complex, including parameters such as transaction geographic location, merchant type, transaction amount, or any of a host of other parameters. Furthermore, external risk evaluation and assessment systems may be used as inputs to the decision making process. Additionally, characteristics of the device being used to perform a transaction can also be an input to the decision making process. In some cases the device itself can become part of the Challenge-Response mechanism.
[0021] A device that is not directly involved in the transaction may also become part of the Challenge-Response sequence. For example, a cardholder may initiate a purchase on a merchant's web site using his personal computer. Using an existing password system, the system may decide to issue a challenge to the cardholder instructing the cardholder to enter the contents of a text message that is being sent to the cardholder's mobile phone. The system can then send a text message to the cardholder containing the desired response. By responding to the challenge with the contents of the text message, the cardholder has further authenticated that he is in possession of a device that should only be in the possession of an authorized cardholder. By varying the contents of the text message for each transaction, a “One Time Password” is created, thus ensuring that if a single text message is intercepted, it is of no value for future authentications.
[0022] Before describing various embodiments of the invention in more detail, it may be useful to define some general terms that are frequently used to describe the embodiments.
[0023] As used herein, an “issuer” can refer to any suitable entity that may open and maintain an account associated with consumer. Some examples of issuers may be a bank, a business entity such as a retail store, or a governmental entity. In many cases, issuer may also issue an electronic commerce cards to consumer. The issuer typically has an established relationship with the consumer and therefore has data that can be used to authenticate the consumer. Such data may include the consumer's social security number, birthday, account number, shipping address, preferences, etc.
[0024] As used herein, an “acquirer” is typically a business entity, e.g., a commercial bank that has a business relationship with a particular merchant. Some entities can perform both issuer and acquirer functions. Embodiments of the invention encompass such single entity issuer-acquirers.
[0025] As used herein, a “cardholder” can refer to a consumer who has an account with an issuer that can be used to conduct transactions with merchants. A cardholder may have one or more portable consumer devices associated with the account, such as a credit card, debit card, mobile phone, etc., that can assist in the use of the account to conduct a transaction.
[0026] As used herein, a “server” is typically a powerful computer or cluster of computers. For example, a server may be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, a server may be a database server coupled to a web server. Moreover, a server can behave as a single computer, which services the requests of one or more client computers or portable electronic devices.
[0027] As used herein, in some embodiments, a “merchant server” can refer to a server used to provide an online storefront for consumers to shop and also to conduct online transactions with consumers once the consumers have decided to purchase goods from the merchant.
[0028] As used herein, in some embodiments, a “merchant plug-in” or “MPI” can refer to a component that performs various authentication functions on behalf of the merchant. The merchant plug-in may be embodied by suitable hardware and/or software that are accessible to a merchant. For example, the MPI may be software running on the merchant server or it may be a component run on a different server accessible by the merchant. The MPI may be able to perform functions such as initiating the authentication request, determining whether authentication is available for a card number, validating a digital signature in an authentication message, interpreting the authentication results, and other functions.
[0029] As used herein, in some embodiments, an “access control server” (or “ACS”) can refer to a server computer that provides issuers, or other entities capable of authenticating a consumer conducting an online transaction, with the ability to authenticate consumers during an online transaction. As used herein, an “issuer ACS” refers to an ACS managed by an issuer. Often, ACS and issuer ACS are used interchangeably in this disclosure. An ACS performs the requested authentication services and provides digitally signed responses to entities requesting authentication. An ACS may be shared by multiple parties. Alternatively, a party may have multiple access control servers, each associated with a different subset of the consumers.
[0030] As used herein, in some embodiments, an “AHS” can refer to an authentication history server. An AHS is a server which can receive and archive the result of authentication attempts in an authentication system. An AHS may record both successful and unsuccessful authentication attempts. An AHS may receive data relating to authentications from issuers, payment processing networks, or any other entity involved in the authentication process. The data stored by the AHS can later be analyzed for various purposes.
[0031] As used herein, in some embodiments, a “directory server” or “DS” can refer to a server computer that can be used to route messages containing enrolment and authentication information between a merchant plug-in (MPI) and an ACS. The directory server can also determine whether a consumer can utilize the authentication services and can apply business rules to modify the response to the MPI. In some embodiments, the directory server can be operated by a service organization such as Visa.
[0032] As used herein, in some embodiments, a “TRS/Online C-R” can refer to a server computer running a transaction routing service and an online challenge-response service. A transaction routing service is capable of routing online transactions between cardholders, issuers, and payment processing networks. A transaction routing service can also provide interfaces to various services. For example, it may provide an interface to an authentication service, a notification service, a third Party Data Source, a third party device identification service, etc. This disclosure often refers to the services offered by a TRS/Online C-R as being offered from the same server computer; however, one skilled in the art will recognize that it is possible to also break up the various services offered by a TRS/Online C-R so that they run on different computers.
[0033] In embodiments of the invention, the TRS/Online C-R, alone or in combination with other components (e.g., a risk scoring server) may comprise a processor, and a computer readable medium. The computer readable medium may comprise code, executable by the processor, for implementing a method comprising: a) receiving a request for consumer authentication at a server computer, the request including information about the transaction being conducted and information on an account being used to conduct the transaction; b) determining a risk score for the transaction at the server computer; c) sending an authentication challenge to the consumer when the risk score exceeds a threshold, the authentication challenge comprising a question whose response is dynamic or semi-dynamic; d) receiving a consumer response to the authentication challenge; e) comparing the response to an expected response; and f) authenticating the consumer conducting the transaction when the response and the consumer response are substantially the same
[0034] A TRS/Online C-R component may contain several different modules. For example, it may include a device information module, a risk analyzer module, and a challenge optimizer module. A device information module may collect cardholder device information (e.g., IP address, browser version, browser language) and use the information to help determine the risk level of the transaction and use the information to help authenticate the cardholder. A risk analyzer module may assess a transaction risk level using device information, transaction characteristics, account characteristics, transaction history, or other relevant pieces of data. A risk analyzer module may also use other internal or third party services to help determine the risk level. A challenge optimizer module may analyze data such as the cardholder account, merchant, and transaction characteristics to determine an appropriate challenge question for each transaction. The challenge optimizer module may also validate the response. In the context of the disclosure below, the functionality is often represented as being managed by a single server computer. However, one skilled in the art will recognize that many of the functions can be broken up and managed by many different systems.
[0035] The risk score (which may be alternatively referred to as a risk level) may be of any suitable characteristic and may be determined (e.g., calculated) using any suitable procedure. A risk score may be characterized by a number or other type of label (e.g., low, medium, or high). The risk score may be calculated, or may be determined from prior data using a lookup table or the like. The risk score may be derived from the previously describer parameters (e.g., device information, transaction information, geographic location, etc) and other information.
[0036] In embodiments where an TRS/Online C-R is responsible for selecting a challenge, presenting a challenge to a cardholder, and validating the response from the cardholder, the TRS/Online C-R may have access to a challenge question engine. The TRS/Online C-R may also be in communication with a transaction history database and a challenge question database. The challenge question engine may extract challenge questions from the challenge question database. Alternatively or additionally, the challenge question engine may generate challenge questions using information in the transaction history database. The transaction history database may include transaction data for debit, credit, and pre-paid cards used by the cardholder or other individuals.
[0037] As used herein, in some embodiments, a notification server can refer to a server capable of sending a message (e.g., purchase confirmation, one time password, marketing offer, or any other type of message) to a cardholder device (e.g., PC, mobile phone, PDA, telephone). The message can be triggered by an event such as payment authorization, cardholder authentication attempt, meeting a defined threshold, etc. Embodiments of the invention may use a notification server to communicate with a consumer.
[0038] As used herein, in some embodiments, a “challenge” can refer the one or more questions based on cardholder personal information or previous transactions that are presented to a cardholder in an attempt to authenticate the cardholder conducting a transaction.
[0039] The challenges may also have static, semi-dynamic, or dynamic answers. For example, the question “What is your birthday?” requires a static answer, since the answer does not change. The question “What is your zip-code?” requires a semi-dynamic answer, since it could change or can change infrequently. Lastly, the question “What did you purchase yesterday at 4 pm?” would require a dynamic answer since the answer changes frequently. Thus, in preferred embodiments, the challenge questions would preferably be based on real time information that is easily accessible at the time of the transaction. By providing specific knowledge-based consumer challenges, the authentication of the consumer can be improved.
[0040] In some embodiments, a consumer may determine the kinds and/or quantity of challenge questions to ask himself or herself. For example, the consumer may specify that the consumer wants to be asked three challenge questions if the consumer visits a jewelry store, but only one question if the consumer visits a fast food restaurant. The types of questions posed by the consumer may be based on the merchant type, frequency of purchasing, etc.
[0041] As used herein, in some embodiments, “cardholder personal information” can refer to information about the consumer that can be obtained from a message exchange with or file from the issuer, a payment processing network, or another third party. Cardholder personal information can include information such as the last four digits of a social security number, a cardholder's birthday or zip code, address, previous address, schools attended, professional licenses obtained, relatives, type of vehicles owned, monthly payments for loans, etc.
[0042] As used herein, in some embodiments, “purchase transaction information” can refer to information related to the previous transactions conducted by a cardholder. For example, purchase transaction information may include information related to the merchants that participated in previous transactions, the location of previous transactions, the amount of previous transactions, etc. Transactions can include purchases, cash advances, disputes and returns/credits maintained by a payment processing network or an issuer.
[0043] FIGS. 1-14 illustrate various embodiments of systems along with the dataflow within those systems to implement an online challenge-response system in an integrated manner with an existing authentication system. The systems illustrated in FIGS. 1-14 share many common components and often have similar dataflows. Although not explicitly described, many of the communications shown in FIGS. 1-14 can be digitally signed using well-known techniques so that messages cannot be tampered with or altered by any of the parties that handle messages in transit. The embodiments illustrated in FIG. 1-14 shows the flexibility of embodiments of the invention.
[0044] Additionally, the embodiments illustrated in FIGS. 1-14 can be combined in numerous ways. For example, some issuers may prefer for a challenge to be issued on their behalf, while other issuers may wish to perform the challenge themselves. One skilled in the art will recognize that these types of combinations can be created by configuring the system to recognize these various permutations. Similarly, different dataflows can be used based on the merchant's preferences, cardholder's preferences, various regulations based on the location of the merchant, cardholder, issuer, etc. Many of the variables that can be used to determine the authentication dataflow used for a given transaction can come into play at once. For example, the authentication system may use one dataflow for a transaction being conducted in Europe with Issuer A, a second dataflow for a transaction being conducted in the United States with Issuer A, and a third data flow for a transaction being conducted in the United States with Issuer B. All of the possible dataflow configurations can be represented as a multi-dimension decision matrix. The dimensions of the matrix correspond to the variables used to determine the dataflow for a transaction, and the value at a particular matrix location corresponds to the particular data flow to be used.
[0045] Furthermore, details within a particular dataflow can also be determined by the decision matrix. For example, one issuer may wish to use dynamic challenges for transactions over $1000 and static challenges for transactions less than $1000. Another issuer may wish to use multiple dynamic and static challenges for transactions over $1000 while not using any challenge for transactions less than $1000. Still another issuer may want to rely on static challenges and password authentication. One skilled in the art will recognize that there are many different permutations of the authentication processes that can be used, and that each of these permutations can easily be configured and applied if represented in the system as a multi-dimensional matrix. A system attempting to determine the appropriate dataflow for a transaction simply needs to lookup the appropriate dataflow based on the relevant variables of the matrix. This process can occur quickly so that authentication can proceed as desired. Although this decision process may not be explicitly referenced in FIGS. 1-14 , it should be understood that this process can occur at any point during the authentication processes described in FIGS. 1-14 .
[0046] FIG. 1 depicts one exemplary embodiment. FIG. 1 illustrates the various components of an online challenge-response system that is integrated with a password-based authentication system. The messages that are transmitted between the various components of the system enable challenges to be used to authenticate cardholders conducting online transactions. In particular, FIG. 1 illustrates a challenge response that is conducted on behalf on an issuer.
[0047] In the embodiment illustrated in FIG. 1 , the risk of a transaction is assessed and a challenge-response sequence is conducted if the risk of the transaction is above a defined risk-threshold. The cardholder's response to the challenge is validated, and the result of the challenge-response sequence is sent to the merchant. In the embodiment illustrated in FIG. 1 , issuers do not have to modify any existing password-based authentication system components that may currently be deployed since the challenge-response is conducted on their behalf.
[0048] In step 11 in FIG. 1 , a cardholder 1010, using an application such as a web browser on a suitable communication device, may initiate a purchase transaction with an e-commerce merchant 1020. Typically, the cardholder 1010 will visit a merchant server that hosts a website managed by the merchant 1020, select various items to buy, and conduct a standard online checkout process. During the checkout process, the cardholder 1010 will typically enter the account information of the payment account to be charged for the transaction.
[0049] In steps 12 and 13, an authentication process begins. The merchant 1020 attempts to locate an authentication service, if any, associated with the electronic commerce card issuer of the payment account of the cardholder 1010. A directory server 1030 can maintain a directory that specifies the location and capabilities of various card issuer systems. The capabilities of card issuer systems include whether the card issuer system supports authentication.
[0050] As shown in FIG. 1 , the merchant 1020 may send a verifying enrollment request (VEReq) to a directory server 1030 to locate the appropriate card issuer system according to the specifications of the authentication system. The VEReq typically includes at least a portion of the electronic commerce card information. This information can be used by the directory server 1030 to identify the card issuer system associated with the cardholder's electronic commerce card. In an embodiment, all authentication-related communication is coordinated by a merchant plug-in 1025 integrated with the website managed by the merchant 1020. In an embodiment, each electronic commerce card issuer is assigned a different range of electronic commerce card numbers. In this embodiment, the directory server 1030 includes a list of all electronic commerce card issuers and their associated electronic commerce card number ranges. By comparing the electronic commerce card information with the list of electronic commerce card issuers, the directory server 1030 is able to identify the appropriate card issuer system.
[0051] It is at this point that the embodiment illustrated in FIG. 1 may begin a dataflow that differs from the dataflow of existing password-based authentication systems. According to some password-based authentication systems, after identifying the card issuer system, the directory server 1030 then determines if the card issuer supports password-based authentication. If the card issuer does not support password-based authentication, then the authentication process may be halted. If password-based authentication is supported, the directory server 1030 could then forward the VEReq to an access control server (ACS) 1050 associated with the card issuer's authentication service. The ACS 1050 could then determine whether the card information provided in the VEReq can be authenticated. Card information may not be able to be authenticated by the ACS 1050 if, for example, the card information does not include a valid electronic commerce card number, or if there is no authentication information, such as a password or other identifying information, associated with the electronic commerce card number.
[0052] If the electronic commerce card information provided in the VEReq can be authenticated (e.g., using a password, semi-static, or dynamic challenge), a verified enrollment response (VERes) can be generated. (It is noted that the challenge-response approach can be integrated with a password authentication approach, but it can also be implemented using similar transaction flows without password authentication-challenge-response can be implemented independent of password authentication.) The VERes includes a message indicating that the ACS 1050 can authenticate the electronic commerce card information and a pseudonym corresponding to the card number. The pseudonym can be any type of code or number that can be uniquely linked to card information by the ACS 1050 at a later time. The VERes also includes a URL to be accessed by the cardholder 1010 for authentication. The URL can be associated with a web site provided by the ACS 1050. Upon receiving a VERes from the ACS 1050, the directory server 1030 forwards the VERes to the merchant 1020.
[0053] In some later described embodiments, the VEReq/VERes sequence described above is carried out as above in order to proceed with a password-based authentication. However, in the embodiment illustrated in FIG. 1 , the directory server 1030 may not contact the ACS 1050 at this step. In the embodiment illustrated in FIG. 1 , the directory server 1030 has been configured to contact a transaction routing system/online challenge-response server (TRS/Online C-R) 1040. The TRS/Online C-R 1040 then generates a VERes that is configured for a challenge-response based authentication instead of a password-based authentication. The VERes can be sent back to the merchant 1020 in the same way that a VERes would be sent back to the merchant 1020 in a password-based authentication process. Subsequently, a payer authentication request sent by the merchant 1020 to the cardholder 1010 can be configured for the challenge-response process. For example, instead of including a URL associated with a web site provided by the ACS 1050, the URL may be associated with a URL associated with the TRS/Online C-R 1040 so that the TRS/Online C-R 1040 can issue a challenge to the cardholder 1010.
[0054] In step 14, the MPI 1025 redirects the cardholder 1010 to the TRS/Online C-R 1040 in order to authenticate the cardholder. This redirect can be based, at least in part, on information contained within the VERes. For example, the MPI 1025 can generate a payer authentication request (PAReq) based on information contained in the VERes, and the MPI 1025 can then send the generated PAReq to the cardholder 1010. A browser used by the cardholder 1010 can analyze the received PAReq and determine that the TRS/Online C-R 1040 should be contacted. According to various password-based authentication systems, the browser would contact an ACS 1050, instead of the TRS/Online C-R, at this step to begin a password authentication process.
[0055] In step 15, the TRS/Online C-R 1040 can analyze a plurality of factors to determine if a challenge-response authentication should be performed. Examples of such factors can include information regarding the device being used by the cardholder 1010 to perform the transaction, various transaction characteristics, such as amounts, transaction history, etc. In some cases, external systems such as a risk-scoring server 1090 or similar services may be invoked to establish a risk score or risk type for the transaction. Also certain issuers may wish to maintain a traditional password-based authentication system, some issuers would prefer to use challenge-response authentication, and some issuers may wish to perform both types of authentication. As previously explained, there can be many variables considered by the TRS/Online C-R 1040 to decide how to proceed with authentication. According to some embodiments, if the TRS/Online C-R 1040 determines that a challenge-response should not be used, then authentication may stop. Alternatively, authentication may proceed with a password-based authentication. If the TRS/Online C-R 1040 determines that a challenge-response authentication should be performed, a challenge question may be generated and sent to the cardholder 1010.
[0056] The cardholder 1010 may then respond to the challenge. In some cases, the response to the challenge question may be sent to the cardholder via separate channel, such as a mobile phone text message, while in other cases, the response will require information that should only be known by the cardholder. The TRS/Online C-R can then verify the response received from the cardholder 1010. Optionally, the authentication result can be sent to the issuer.
[0057] As previously mentioned, modules with the TRS/Online C-R 1040 may use modules such as a device information module, a risk analyzer module, and a challenge optimizer module to perform some of the various steps mentioned in step 15.
[0058] At step 16, the result of the cardholder authentication can be returned to the merchant 1020 through the cardholder 1010 in a payer authentication response (PARes). Furthermore, persistent records of the authentication transaction can be created and stored at step 17. As illustrated in FIG. 1 , information concerning the authentication can be sent to an Authentication History Server (AHS) 1060. According to some embodiments, the AHS 1060 may confirm receipt of the information to the TRS/Online C-R 1040.
[0059] After receiving a valid authentication of the cardholder, the merchant system can then proceed at step 18 to perform a normal transaction authorization through its established acquirer 1070. The merchant can send the authentication results to the acquirer for use in authorization.
[0060] FIGS. 2-14 show many different variations on the system and process outlined in FIG. 1 . Many steps that are similar to what was described in FIG. 1 will be only briefly described. It should be understood, however, that many of the steps in FIGS. 2-14 that are analogous to what was described in FIG. 1 and contain just as much complexity as what was described in FIG. 1 .
[0061] FIG. 2 depicts one exemplary embodiment. In particular, FIG. 2 illustrates an embodiment in which a risk level is determined and sent to an issuer. The issuer then conducts a challenge-response authentication.
[0062] At step 21, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0063] At step 22, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0064] At step 23, the ACS 1050 responds to the VEReq with a VERes sent to the TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0065] At step 24, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 determines a risk level for the transaction. In some embodiments, the TRS/Online may use a risk analyzer to determine the risk level. The risk level can be determined using many of the variables previously described. The TRS/Online C-R 1040 can then send the PAReq to the ACS 1050 along with the determined risk level.
[0066] At step 25, the ACS 1050 assesses risk level and presents challenge for high-risk transactions. If a challenge is received, the cardholder responds to the challenge. The ACS 1050 then validates the response. As shown in FIG. 2 , the dataflow at step 25 flows through the TRS/Online-CR 1040. According to other embodiments, the ACS 1050 and cardholder 1010 may be in direct communication.
[0067] At step 26, a PARes is generated based on the response of the cardholder 1010 to the challenge. The ACS 1050 can send the PARes to the TRS/Online C-R 1040. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0068] At step 27, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 28, the ACS 1050 can send data to be archived to the AHS 1060.
[0069] At step 29, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0070] FIG. 3 depicts one exemplary embodiment. In particular, FIG. 3 illustrates an embodiment in which the issuer determines the risk level and performs challenge-response sequence using an existing password-based authentication platform to conduct challenge-response process. The password-based authentication platform does not need to be modified in this embodiment. Variations of this embodiment could be implemented without using a TRS/Online C-R.
[0071] At step 31, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0072] At step 32, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0073] At step 33, the ACS 1050 responds to the VEReq with a VERes sent to the TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0074] At step 34, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0075] At step 35, the ACS 1050 determines and assesses risk level and presents challenge for high-risk transactions. If a challenge is received, the cardholder responds to the challenge. The ACS 1050 then validates the response. As shown in FIG. 3 , the dataflow at step 35 flows through the TRS/Online-CR 1040. According to other embodiments, the ACS 1050 and cardholder 1010 may be in direct communication.
[0076] At step 36 a PARes is generated based on the response of the cardholder 1010 to the challenge. The ACS 1050 sends PARes to TRS/Online C-R 1040. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0077] At step 37, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 38, the ACS 1050 can send data to be archived to the AHS 1060.
[0078] At step 39, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0079] FIG. 4 depicts one exemplary embodiment. In particular, FIG. 4 illustrates an embodiment in which a challenge is presented by the TRS/Online C-R when the issuer is not able to authenticate a cardholder using a password-based authentication process. As used herein, an “attempted” authentication refers to the situation where an issuer is unable to authenticate a cardholder using a password-based authentication process. As previously mentioned, there are a number of reasons why an issuer may be unable to authenticate a cardholder. For example, a cardholder may not have established a password for the account used in a transaction. More information on attempted authentications can be found in U.S. Pat. No. 7,039,611, which is incorporated in its entirety for all purposes. According to various embodiments, all attempted authentications can be authenticated using a challenge-response. Alternatively, only attempted transactions above a certain risk threshold may be authenticated using a challenge-response.
[0080] At step 41, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0081] At step 42, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0082] At step 43, the ACS 1050 responds to the VEReq with a VERes sent to TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0083] At step 44, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0084] At step 45, the ACS 1050 may determine that it is unable to authenticate the cardholder 1050 using a password-based authentication, and creates an “attempted authentication” response. For example, the cardholder 1050 may not be able to be authenticated because the cardholder has not configured a password for the account being used to conduct the transaction. According to some embodiments, it may be determined at an earlier time that password authentication cannot occur. For example, at step 42 it may be determined that the ACS 1050 is not capable of performing password-based authentication. Regardless of how or when it is determined that password-based authentication cannot occur, the TRS/Online C-R 1040 is informed that password-based authentication cannot occur at step 45.
[0085] At step 46, the TRS/Online C-R 1040 conducts challenge-response authentication for attempted authenticated transactions. The TRS/Online C-R 1040 may determine the risk-level on the attempted authenticated transaction. The TRS/Online C-R 1040 may then present a question if the attempted transaction is a high-risk transaction. Alternatively, all attempted transactions may be presented a question. The TRS/Online C-R 1040 can then validate the response received from the cardholder 1010.
[0086] At step 47 a PARes is generated based on the response of the cardholder 1010 to the challenge by the TRS/Online C-R 1040. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0087] At step 48, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use.
[0088] At step 49, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0089] FIG. 5 depicts one exemplary embodiment. In particular, FIG. 5 illustrates an embodiment in which a challenge is presented for transactions that have also been authenticated using a password-based authentication. A challenge can be presented for transactions above a certain risk threshold. The challenge can be presented in addition to the issuer validating the password, and thus the embodiment illustrated in FIG. 5 provides an additional layer of security. The challenge can be presented after the issuer has authenticated the cardholder using the password-based authentication.
[0090] At step 51, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0091] At step 52, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0092] At step 53, the ACS 1050 responds with a VERes to TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0093] At step 54, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0094] At step 55, as previously described in relation to password-based authentication processes, the ACS 1050 authenticates cardholder's 1010 password via an exchange with the cardholder 1010. The exchange may occur via the TRS/Online C-R or it may occur directly between the ACS 1050 and the cardholder 1050. Additional information on this password exchange can be found, for example, in U.S. Pat. No. 7,039,611.
[0095] At step 56 a PARes is generated based on the password-based authentication of the cardholder 1010. The ACS 1050 sends PARes to TRS/Online C-R 1040.
[0096] At step 57, the TRS/Online C-R 1040 conducts a challenge-response sequence for the password-authenticated transaction. The TRS/Online C-R 1040 may determine the risk-level of the password-authenticated transaction. The TRS/Online C-R 1040 may then present one or more questions if the transaction is a high-risk transaction. The TRS/Online C-R 1040 can then validate the response from the cardholder 101.
[0097] At step 58, another PARes is generated by the TRS/Online C-R 1040 based on the response of the cardholder 1010 to the challenge. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0098] At step 59, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 510, the ACS 1050 can send data to be archived to the AHS 1060.
[0099] At step 511, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0100] FIG. 6 depicts one exemplary embodiment. In particular, FIG. 6 illustrates an embodiment similar to the embodiment illustrated in FIG. 5 , except that in FIG. 6 the challenge is presented while the issuer is authenticating the cardholder.
[0101] At step 61, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0102] At step 62, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0103] At step 63, the ACS 1050 responds with a VERes to TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0104] At step 64, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0105] At step 65, the password-based and challenge-response authentication process begin in parallel. The ACS 1050 authenticates cardholder's 1010 password via an exchange with cardholder 1010 that can occur through the TRS/Online C-R 1040. Meanwhile, the TRS/Online C-R 1040 determines the risk level of the transaction and inserts a challenge into the ACS 1050 password validation step for high-risk transactions. For example, when the ACS requests that the cardholder submit the password associated with the account used in the transaction, the TRS/Online C-R, when forwarding this request, can add a challenge to this password request. The TRS/Online C-R 1040 can validate the response to challenge and send authentication result to ACS 1050. The ACS 1050 can also validate the password submitted by the cardholder 1010.
[0106] At step 66, a PARes can be generated based on the response of the cardholder 1010 to the challenge and on the response of the cardholder 1010 to the password-based authentication. The PARes can then be sent to the merchant 1020 via the cardholder 1010. In one embodiment, the ACS 1050 is informed of the result of the challenge-response and generates the PARes. In another embodiment, the TRS/Online C-R 1040 is informed of the result of the password-based authentication and generates the PARes.
[0107] At step 67, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 68, the ACS 1050 can send data to be archived to the AHS 1060.
[0108] At step 69, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0109] FIG. 7 depicts one exemplary embodiment. In particular, FIG. 7 illustrates an embodiment in which a challenge is presented while a cardholder enrolls in a password-based authentication during the course of conducting a transaction. As with other embodiments, a challenge can be presented for transactions above a certain risk threshold. The challenge is presented in addition to the issuer validating other cardholder responses in order to provide an additional layer of security.
[0110] At step 71, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0111] At step 72, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0112] At step 73, the ACS 1050 responds with a VERes to TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0113] At step 74, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0114] At step 75, the ACS 1050 authenticates that the cardholder 1010 is an authorized user of the account used in the transaction using well-known means. The ACS 1050 then allows the cardholder 1010 to create a password that can be used for future password-based authentication. In the embodiment illustrated in FIG. 7 , this communication takes place through the TRS/Online C-R 1040, but in other embodiments, the ACS 1050 may communicate directly with the cardholder 1010.
[0115] At step 76, a PARes is generated based on the enrollment of the cardholder 1010. The ACS 1050 sends PARes to TRS/Online C-R 1040.
[0116] At step 77, the TRS/Online C-R 1040 can determine the risk level of the transaction and present a challenge to the cardholder 1010 for high-risk transactions. The TRS/Online C-R 1040 can validate the response to challenge.
[0117] At step 78, a PARes can be generated based on the response of the cardholder 1010 to the challenge. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0118] At step 79, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 710, the ACS 1050 can send data to be archived to the AHS 1060.
[0119] At step 711, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0120] FIG. 8 depicts one exemplary embodiment. In particular, FIG. 8 illustrates an embodiment, similar to the embodiment illustrated in FIG. 7 , in which a challenge is presented while a cardholder enrolls in a password-based authentication during the course of conducting a transaction. The difference in FIG. 8 is that the challenge is presented to the cardholder as a part of the authentication used to create the password. As with other embodiments, a challenge can be presented for transactions above a certain risk threshold. This approach provides an additional layer of security for the enrollment process.
[0121] At step 81, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0122] At step 82, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0123] At step 83, the ACS 1050 responds with a VERes to TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0124] At step 84, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0125] At step 85, the ACS 1050 authenticates that the cardholder 1010 is an authorized user of the account used in the transaction using well-known means. The TRS/Online C-R 1040 can then determine the risk level of the transaction and present a challenge to the cardholder 1010 for high-risk transactions. The TRS/Online C-R 1040 can validate the response to challenge and inform the ACS 1050 of the result of the challenge-response. The ACS 1050 can then use the result of the challenge to help determine whether to allow the cardholder 1010 to create a password that can be used for future password-based authentication. In the embodiment illustrated in FIG. 8 , the communications that take place during this step are transmitted through the TRS/Online C-R 1040, but in other embodiments, the ACS 1050 may communicate directly with the cardholder 1010 for some of the various communications involved in step 85.
[0126] At step 86, a PARes is generated based on the enrollment of the cardholder 1010. The ACS 1050 sends PARes to TRS/Online C-R 1040. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0127] At step 87, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 88, the ACS 1050 can send data to be archived to the AHS 1060.
[0128] At step 89, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0129] FIG. 9 depicts one exemplary embodiment. In particular, FIG. 9 illustrates an embodiment in which a challenge is presented while a cardholder goes through a password recovery process in a password-based authentication system during the course of conducting a transaction. The challenge is presented in addition to other issuer questions. As with other embodiments, a challenge can be presented for transactions above a certain risk threshold. This approach provides an additional layer of security for the re-activating process. One skilled in the art will recognize based on this description, and on the other previous descriptions, that a challenge could alternatively be presented simultaneously with an issuer's questions during a password recovery process or in place of an issuer's questions during a password recovery process.
[0130] At step 91, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0131] At step 92, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0132] At step 93, the ACS 1050 responds with a VERes to TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0133] At step 94, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0134] At step 95, the cardholder 1010 begins a password recovery process, and the ACS 1050 authenticates cardholder 1010 via a question exchange with the cardholder 1010. This transaction flow may take place via the TRS/Online C-R 1040. The TRS/Online C-R 1040 also determines the risk-level of the transaction and may insert additional challenge-questions in sequence if the risk level exceeds a threshold. The TRS/Online CR can validate the cardholder's 1010 challenge responses, and sends result to ACS 1050. The ACS 1050 can then determine whether to allow the cardholder 101 to reset their password based on the response to the issuer's questions and on the result of the challenge-response.
[0135] At step 96, a PARes is generated based on the password reset of the cardholder 1010. The ACS 1050 sends PARes to TRS/Online C-R 1040. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0136] At step 97, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 98, the ACS 1050 can send data to be archived to the AHS 1060.
[0137] At step 99, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0138] FIG. 10 depicts one exemplary embodiment. In particular, FIG. 10 illustrates an embodiment in which a challenge is presented in place of any authentication conducted by the issuer when the issuer is unable to authenticate the cardholder. This embodiment is similar to the “attempted” authentication embodiment except that no “attempted” authentication response is generated.
[0139] At step 121, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0140] At step 122, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0141] At step 123, the ACS 1050 responds with a VERes to TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0142] At step 124, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040, and the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0143] At step 125, the ACS 1050 is unable to authenticate the cardholder 1010 and creates an authentication request. The authentication request is sent to the TRS/Online C-R 1040 and to request that the TRS/Online C-R 1040 authenticate the cardholder 1010 on behalf of the ACS 1050.
[0144] At step 126, the TRS/Online C-R 1040 conducts challenge-response authentication for the transaction. The TRS/Online C-R 1040 may determine the risk-level of the transaction. The TRS/Online C-R 1040 may then present a question if the transaction is a high-risk transaction. Alternatively, all transactions may be presented a question. The TRS/Online C-R 1040 can then validate the response received from the cardholder 1010. The result of the validation can be sent to the ACS 1050.
[0145] At step 127, a PARes is generated based on the response of the cardholder 1010 to the challenge by the TRS/Online C-R 1040. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0146] At step 128, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 129, the ACS 1050 can send data to be archived to the AHS 1060.
[0147] At step 1210, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0148] FIG. 11 depicts one exemplary embodiment. In particular, FIG. 11 illustrates an embodiment in which cardholder device information is collected on password-based authentications that pass through the system. This information could be used real-time in determining the risk-level of a transaction, or could be used to help authenticate the cardholder, or could be used for offline forensic analysis.
[0149] At step 131, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0150] At step 132, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040. The TRS/Online C-R 1040 then forwards the VEReq to the appropriate ACS 1050 for the account being used in the transaction.
[0151] At step 133, the ACS 1050 responds with a VERes to TRS/Online C-R 1040. The TRS/Online C-R 1040 forwards the VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0152] At step 134, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 then sends the PAReq to the TRS/Online C-R 1040. At this point, the TRS/Online C-R 1040 can collect cardholder 1010 device information. For example, if the cardholder 1010 is using a web browser on a personal computer, the TRS/Online C-R 1040 may collect the IP address, browser version, and other similar information. If the cardholder 1010 is using a device such as a mobile phone, then the mobile phone number may be collected. One skilled in the art will recognize that many different pieces of device information can be gathered depending on the device. Additionally, a module such as a device information module within the TRS/Online C-R 1040 may perform the device information gathering. The transaction risk could also be assessed using the device information, transaction characteristics, account characteristics, and transaction history. TRS/Online C-R 1040 can pass device information and risk information to ACS 1050 in a PAReq or could send this information to the merchant 1020 in a PARes. At this point, the TRS/Online C-R 1040 can then send the PAReq to the ACS 1050.
[0153] At step 135, as previously described in relation to password-based authentication processes, the ACS 1050 authenticates cardholder's 1010 password via an exchange with the cardholder 1010. The exchange may occur via the TRS/Online C-R or it may occur directly between the ACS 1050 and the cardholder 1050. The ACS 1050 can use the device and risk information to help in making an authentication decision.
[0154] At step 136, a PARes is generated based on the authentication decision made by the ACS 1050. The PARes can be sent from the ACS 1050 to the TRS/Online C-R 1040. The PARes can then be sent to the merchant 1020 via the cardholder 1010.
[0155] At step 137, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. Additionally or alternatively at step 138, the ACS 1050 can send data to be archived to the AHS 1060.
[0156] At step 139, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0157] FIG. 12 depicts one exemplary embodiment. In particular, FIG. 12 illustrates an embodiment a one-time password (OTP) is sent to the cardholder. An OTP can be sent to the cardholder via text message, e-mail, or telephone call. The cardholder enters OTP in a challenge screen and the OTP can be verified to authenticate the cardholder. Note, the OTP will be different each time the process is used for each transaction, thus this approach provides a higher level of security by using a dynamic password.
[0158] At step 141, a cardholder 1010 conducts a transaction at an online merchant 1020.
[0159] At step 142, a VEReq is generated by an MPI 1025 and sent to a directory server 1030. The directory server 1030 forwards the VEReq to a TRS/Online C-R 1040.
[0160] At step 143, the TRS/Online C-R 1040 responds with a VERes to the directory server 1030, and the directory server forwards the VERes to the merchant 1020.
[0161] At step 144, the merchant 1020 sends a PAReq to the cardholder 1010. The cardholder 1010 sends the PAReq to the TRS/Online C-R 1040.
[0162] At step 145, the TRS/Online C-R 1040 collects cardholder device information, assesses transaction risk using the device information, transaction characteristics, account characteristics, and transaction history, and presents a challenge for higher-risk transactions. The TRS/Online C-R 1040 may request risk information from risk-scoring server 1090. The TRS/Online C-R 1040 also sends a message to inform a notification server 1095 to send a one-time password to the cardholder 1010. OTP may be transmitted as email, text message to phone or other device, or voice message to phone. The cardholder 1010 can then enter the OTP into challenge page. The TRS/Online C-R 1040 can validate the OTP.
[0163] At step 146, a PARes is generated based on the validation made by the TRS/Online C-R 1040. The PARes can be sent from the TRS/Online C-R 1040 to the merchant 1020 via the cardholder 1010.
[0164] At step 147, the PARes can be sent to the AHS 1060 from the TRS/Online C-R 1040 for later use. TRS/Online C-R 1040 may also forward a copy of PARes to the ACS 1050.
[0165] At step 148, the merchant 1020 validates that the PARes has not been altered and forwards an authorization request containing authentication results to the acquirer 1070.
[0166] FIG. 13 shows typical components or subsystems of a computer apparatus. Such components or any subset of such components (e.g., the directory server, the risk scoring server, the TRS/Online C-R, the AHS, the ACS, computer running the merchant plug in, computer or device operated by the cardholder, or any suitable combination of the foregoing) may be present in various components shown in FIGS. 1-12 . The subsystems shown in FIG. 13 are interconnected via a system bus 775. Additional subsystems such as a printer 774, keyboard 778, fixed disk 779, monitor 776, which is coupled to display adapter 782, and others are shown. Peripherals and input/output (I/O) devices, which couple to I/O controller 771, can be connected to the computer system by any number of means known in the art, such as serial port 777. For example, serial port 777 or external interface 781 can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner. The interconnection via system bus 775 allows the central processor 773 to communicate with each subsystem and to control the execution of instructions from system memory 772 or the fixed disk 779, as well as the exchange of information between subsystems. The system memory 772 and/or the fixed disk 779 may embody a computer readable medium.
[0167] Additional details regarding the risk assessment process which can be used in any of the previously described embodiments are below. In the specific examples below, issuer based decision processing is discussed in detail. Although an issuer is discussed in the following specific examples, it is understood that other parties including a payment processing organization that operates a payment processing network may alternatively perform the foregoing functions.
[0168] As explained above, in some embodiments of invention an issuer or other party can receive an authentication request (PAReq) from a merchant, and it can base its authentication decision according to level of risk at the time the transaction occurs. The risk level can be determined using a risk model that assesses several characteristics, which may include, for example: an IP address, geo-location of the device, device information, transaction characteristics (e.g. amount, frequency, time of day), and previous transaction history.
[0169] The levels of risk can be defined in any suitable manner. The risk levels may alternatively be referred to as risk scores. For example, the levels of risk may be defined as the follows: “Low risk transactions” are passively authenticated; in the majority of cases, the cardholder is not cognizant of the authentication process. Cardholders may see “processing” or “purchase verifying” message displayed while the issuer is assessing the risk and determining its response. “Medium-high risk transactions” can be presented with two to three challenge questions before completing the sale. The challenge questions can be based on in-wallet and out-of-wallet data and will be validated by the issuer in real time. For “very high risk transactions,” the issuer will not present a challenge question and will return an authentication failed response to the cardholder and merchant. In all the scenarios described above an authentication response can be sent to the merchant (e.g., pass, fail, passive authentication, attempt or unavailable).
[0170] In embodiments of the invention, the issuer authenticates the cardholder using a risk assessment tool (e.g., the TRS/Online C-R described above) and sends the appropriate response back to the merchant (e.g. pass, fail, passive authentication, attempt or unavailable). Based on the risk score generated by the risk tool, the risk assessment tool can respond in different ways. For some risk scores, there can be no response. For other risk scores, a challenge request can be sent or a failed transaction response can be sent. In other embodiments, the number of challenge requests may vary depending upon the risk score. As illustrated below, in some embodiments, the risk assessment tool can provide no challenge request if the risk score is low, and can provide a failed transaction message if the risk score is high. If the risk score is in a medium range, the risk score can determine the number of challenge requests that are provided to the user. For example, if the medium risk range is 3-7 on a scale of 1-10 (10 being risky and 1 being safe), a risk score of 4 may indicate that 1 challenge request is to be provided to the cardholder, while a risk score of 6 may indicated that three challenges are to be provided to the cardholder.
[0171] Illustratively, if the issuer determines that the transaction is “low risk,” then the cardholder will see “processing” or “purchase verifying” and will be automatically directed to the merchant's final check-out page. The issuer can then send an attempted authentication status (i.e. ECI 6) or a passive authentication status to the merchant. If the issuer determines that the transaction falls within the range of “medium-high risk,” the cardholder can be presented with two to three challenge questions (or more) and may be required to authenticate before completing the sale. See, for example, FIG. 14 . The cardholder enters the information requested by the issuer and clicks “Submit.” The issuer then determines whether the information provided is correct. If the cardholder provides invalid authentication data and exceeds the issuer-defined entry attempts, the cardholder will be presented with the “Transaction Suspended” screen. See FIG. 15 .
[0172] If the issuer determines that the transaction is “very high risk,” the cardholder will be presented with information notifying them that the transaction failed.
[0173] The Access Control Server (ACS) returns the digitally-signed Payer Authentication Response to the merchant plug in via the cardholder's device.
[0174] The ACS formats a Payer Authentication Response with appropriate values, including authentication status, Electronic Commerce Indicator (ECI) and Cardholder Authentication Verification Value (CAW). More information on the ECI is provided below, in Table 1.
[0175] Whether or not authentication was successful, the ACS sends a copy of the Payer Authentication Response, plus related data, to the Authentication History Server. The server serves as the database of record for dispute resolution. Based on the data received from the MPI, the merchant determines whether to proceed with authorization.
[0176] If the Payer Authentication Response indicates that authentication failed then the merchant is required, or may be required, to ask for another form of payment from the cardholder. If authorization is appropriate, the merchant follows its standard procedure to authorize the transaction.
[0177] In some embodiments, the issuer provides an authentication status response to the merchant for every authentication request. Table 1 below lists the possible outcomes of payment authentication and the codes used to communicate the issuer's authentication decision. The values listed are those inserted in the “Transaction Status” field and the Electronic Commerce (ECI) field of the PARes message that is returned to the merchant.
[0178]
| TABLE 1 | ||
|---|---|---|
| Issuer Authentication Results Values | ||
| Transaction | ECI | |
| Authentication Result Determine by Issuer ACS | Status Values | Value |
| Authentication Successful: | Y | 5 |
| The cardholder's authentication information was | ||
| successfully validated. | ||
| Authentication Failed - Invalid Authentication | N | N/A |
| Data: | or 7 | |
| The cardholder's authentication information failed | ||
| validation or issuer determined the transaction | ||
| was very high risk. | ||
| Authentication Failed - Very High Risk: Issuer or | F | N/A |
| third party determined during its risk assessment | ||
| that the transaction was not initiated by the | ||
| cardholder | ||
| Authentication Attempt: | A | 6 |
| Issuer determined that the transaction was low | ||
| risk and did not prompt the cardholder to | ||
| authenticate or the issuer was not available and | ||
| stand-in processing is provided | ||
| Passive Authentication - Issuer or Third Party | P | 6 |
| determined that enough information was provided | ||
| in the authentication transaction record to | ||
| determine cardholder identity | ||
| Authentication Could Not Be Performed: | U | 7 |
| This is a neutral response status indicating that | ||
| the issuer was not able to perform cardholder | ||
| authentication. | ||
[0179] Embodiments of the invention may also include an authentication challenge screen to address the situation where the number of entry attempts is exceeded. Issuers can determine the number of attempts permitted for the cardholder to provide the correct authentication data before terminating the authentication session (e.g., three to five incorrect data entry attempts). When the issuer-defined number of attempts has been exceeded, the issuer ACS can return a “failed authentication” transaction status in the PARes. The Issuer ACS can send a message in response to failed attempts.
[0180] Embodiments of the invention may also include an authentication challenge screen when incorrect authentication data is provided. The cardholder is given an issuer-determined number of attempts to enter the authentication data correctly. If the authentication data is entered incorrectly, the cardholder will be prompted to check and re-enter the correct information
[0181] As noted above, various cardholder authentication tokens may be used in embodiments of the invention. One aspect to cardholder authentication is the accurate verification of the cardholder's identity as the account holder. The appropriate application of cardholder authentication can increase security while balancing cardholder's need for convenience and speed. Issuers can carefully consider the data elements to verify the cardholder. These elements must include both in-wallet and out-of-wallet data elements. Issuers generally do not ask cardholders to provide more than three data elements during the authentication process. Table 2 below provides a variety of examples to assist issuers in developing cardholder authentication methods.
[0182]
| TABLE 2 | |
|---|---|
| Cardholder Authentication Tokens | |
| Data Categories | Examples of Authentication Tokens |
| Card Information (in-wallet) | Expiration Date |
| CVV2 (Card Verification Value) | |
| Cardholder Information (out- | Name on Card |
| of-wallet) | Last four digits of Social Security Number |
| or National Identification | |
| Date of birth | |
| Telephone number (mobile or home) | |
| Address | |
| Previous address | |
| Relative names | |
| Relative address, city, or state | |
| Monthly loan payments | |
| Place of birth | |
| Zip Code (US only) | |
| Mother's maiden name | |
| I. Alternative Method | One time passwords |
[0183] Table 2 described above provides some examples of cardholder authentication tokens that are static or semi-dynamic. As discussed above, cardholder authentication challenge questions can also be based on a cardholders transaction history, which will generally be more dynamic than those tokens presented in Table 2. Table 3 lists some exemplary cardholder authentication tokens that are more dynamic based on transaction history, and further may be based on complex questions determined by that transaction history.
[0184]
| TABLE 3 | ||
|---|---|---|
| Complex Question Categories | ||
| Group Categories | Question Group | Example |
| Event | Repetitive | Which company provides your |
| Recurring | mobile service? | |
| Seasonal | ||
| Unusual | At what car dealership did you | |
| AMT | make a large purchase at in | |
| Location | February? | |
| (geographic) | ||
| Merchant | ||
| Date/Time | ||
| Exception | At what department store did | |
| Chargeback | you have a return for $110.93? | |
| Returns | ||
| Fact | Fact | About how many transaction per |
| month for this card? | ||
| Trivial | What month was a purchase | |
| conducted? | ||
| Inference | Preference | Do you prefer McDonald's or |
| Burger King? | ||
| Cubs or White Sox? | ||
| Life Event | To what university do you pay | |
| tuition? | ||
| From what city did you move | ||
| last fall? | ||
[0185] The exemplary group categories describe groups that contain exemplary challenge questions. For example, the Event category may describe several question groups that are based on transactions conducted by the cardholder. Repetitive transactions or those occurring seasonally may allow a challenge question to be generated based on the particular merchant involved in those transactions. Additionally, unusual transactions, such as a large purchase made at a car dealership, could be used as a challenge question. Determining if a transaction is unusual could be based on the transaction type, such as AMT (automated money transfer), the location of the transaction, the merchant, or the date/time of the transaction. Once a transaction is determined to be unusual, it may be used in a challenge question. Additionally, questions may be based on unusual events. For example, returns or disputes that result in a chargeback.
[0186] Challenge questions can also be based on facts related to the transactions conducted with the card. For example, the number of transactions per month typically conducted with the account. Such information is obtainable by analyzing the transaction history of the account. Furthermore, simple trivial challenge questions, such as in what month was a purchase conducted, may be used.
[0187] Additionally, transaction data may be used to create challenge questions that are based on inferences gained from analyzing transaction details. Inferences can be made with respect to a cardholder's preferences based on transaction history. For example, large numbers of transactions at a particular fast food restaurant or purchases related to a particular sports team may indicate a cardholders preference for that restaurant or sports team.
[0188] Additionally, inferences could be made about certain life events associated with the cardholder. For example, if the city in which the majority of transactions occurs changes from one month to another, and inference may be made that the cardholder moved. In addition, if transactions to an education institution are made, an inference could be made that the transactions are related to tuition.
[0189] Although several examples of complex question types based on transaction history have been presented in Table 3, this is merely exemplary and is not limiting. Any number of additional categories, groups, and questions have also been contemplated.
[0190] FIG. 16 depicts an exemplary screen shot of a complex question based on a transaction history that may be presented to a cardholder. The cardholder may be requested to select one or more transactions that he recognizes. This is a very simple challenge to implement, as it only requires the selection of any number of transactions from the transaction history and any number of transactions that are not in the transaction history. The cardholder is also given the option to respond that none of the transactions are recognized. By not letting the recipient of the challenge question know how many correct response, or even if there are any correct responses, in such a question reduces the possibility that a random guess would result in a correct answer. In the event that the user does not answer the challenge question correctly, a new set of transactions can be chosen to present in a subsequent question, such that no information about the transaction history could be gained by repeated guessing.
[0191] FIG. 17 depicts an exemplary screen shot of a different complex question based on a transaction history that may be presented to a cardholder. The cardholder may be asked which cities he visited in the past ninety days. Just as above, the answer to the question could be determined by reviewing the transaction history of the user. Again, the questions are presented such that a random guess will have a low likelihood of properly selecting the correct response or responses.
[0192] Challenge questions based on transaction data may be selected so that they are easily answered by a cardholder. The questions are typically simple and based on easily recallable and/or memorable transactions. Furthermore, the questions selected should be difficult for a fraudulent user to answer with any greater success than with a random guess. Furthermore, repeated attempts at answering the challenge question should not leak any cardholder transaction information.
[0193] The above description is illustrative and is not restrictive. Many variations of the disclosure will become apparent to those skilled in the art upon review of the disclosure. The scope of the disclosure should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
[0194] Further, while the present invention has been described using a particular combination of hardware and software in the form of control logic and programming code and instructions, it should be recognized that other combinations of hardware and software are also within the scope of the present invention. The present invention may be implemented only in hardware, or only in software, or using combinations thereof.
[0195] Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.
[0196] It is understood that the examples and embodiments described herein are for illustrative purposes only and that various modifications or changes in light thereof will be suggested to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the appended claims. All publications, patents, and patent applications cited in this patent are hereby incorporated by reference for all purposes.
[0197] In general, the steps associated with the various methods of the present invention may be widely varied. For instance, steps may be added, removed, reordered, and altered. The present examples are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope of the appended claims.
[0198] A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.
[0199] One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the disclosure.
Claims
What is claimed is:
1. A method of authenticating a consumer conducting a transaction with a merchant, the method comprising:
sending, by a client computer, a transaction request to a merchant computer, the transaction request including information associated with an account being used to conduct the transaction, wherein the merchant computer is configured to send a request message to a server computer, wherein the server computer is configured to determine that an authentication challenge will be sent to the client computer based upon a risk determination that a risk threshold has been exceeded and is configured to determine that the authentication challenge will not be sent if the risk threshold is not exceeded;
receiving, by the client computer from the merchant computer, a uniform resource locator associated with the server computer to be utilized for a consumer authentication;
gathering and sending characteristics of the client computer to the server computer, wherein the risk determination is based upon characteristics of the transaction and the characteristics of the client computer;
sending, by the client computer using the uniform resource locator, a request to the server computer for the consumer authentication;
receiving, by the client computer, the authentication challenge from the server computer after the server computer determines that the risk threshold has been exceeded, wherein the authentication challenge is received using the uniform resource locator, and wherein the authentication challenge is dynamically generated by the server computer based on transaction history associated with the account;
sending, by the client computer, a challenge response to the server computer, wherein the server computer compares the challenge response to an expected response;
receiving, by the client computer from the server computer, a result of the consumer authentication; and
sending, by the client computer, the result of the consumer authentication to the merchant computer, wherein the merchant computer thereafter initiates authorization processing.
2. The method of claim 1, wherein the risk determination is a risk score.
3. The method of claim 1 wherein the result of the consumer authentication is sent in a payer authentication response.
4. The method of claim 1, wherein the merchant computer is configured to send the request message to the server computer via a directory server.
5. The method of claim 1, wherein the transaction is a credit card transaction.
6. The method of claim 1, further comprising:
sending information regarding the result of the consumer authentication to an authentication history server.
7. The method of claim 1, wherein the authentication challenge comprises a password challenge.
8. The method of claim 1, wherein authorization processing occurs through an acquirer.
9. A client computer comprising a processor and the computer readable medium coupled to the processor, the computer readable medium comprising code executable by the processor to implement a method comprising:
sending, by the client computer, a transaction request to a merchant computer, the transaction request including information associated with an account being used to conduct the transaction, wherein the merchant computer is configured to send a request message to a server computer, wherein the server computer is configured to determine that an authentication challenge will be sent to the client computer based upon a risk determination that a risk threshold has been exceeded and is configured to determine that the authentication challenge will not be sent if the risk threshold is not exceeded;
receiving, by the client computer from the merchant computer, a uniform resource locator associated with the server computer to be utilized for a consumer authentication;
gathering and sending characteristics of the client computer to the server computer, wherein the risk determination is based upon characteristics of the transaction and the characteristics of the client computer;
sending, by the client computer using the uniform resource locator, a request to the server computer for the consumer authentication;
receiving, by the client computer, the authentication challenge from the server computer after the server computer determines that the risk threshold has been exceeded, wherein the authentication challenge is received using the uniform resource locator, and wherein the authentication challenge is dynamically generated by the server computer based on transaction history associated with the account;
sending, by the client computer, a challenge response to the server computer, wherein the server computer compares the challenge response to an expected response;
receiving, by the client computer from the server computer, a result of the consumer authentication; and
sending, by the client computer, the result of the consumer authentication to the merchant computer, wherein the merchant computer thereafter initiates authorization processing.
10. The client computer of claim 9, wherein the risk determination is a risk score.
11. The client computer of claim 9, wherein the result of the consumer authentication is sent in a payer authentication response.
12. The client computer of claim 9, wherein the merchant computer is configured to send the request message to the server computer via a directory server.
13. The client computer of claim 9, wherein the transaction is a credit card transaction.
14. The client computer of claim 9, wherein the method further comprises:
sending information regarding the result of the consumer authentication to an authentication history server.
15. The client computer of claim 9, wherein the authentication challenge comprises a password challenge.
16. The client computer of claim 9, wherein authorization processing occurs through an acquirer.
17. A system comprising:
the client computer of claim 9; and
the server computer coupled to the client computer.
18. The system of claim 17, further comprising the merchant computer coupled to the client computer.
19. The method of claim 1, wherein the request that is sent from the client computer to the server computer for the consumer authentication includes at least one of an IP address associated with the client computer, a browser version associated with a browser in the client computer, and a browser language associated with the browser.
20. The method of claim 1, wherein the request that is sent from the client computer to the server computer for the consumer authentication includes the characteristics of the client computer, and wherein the characteristics of the client computer include an IP address associated with the client computer, a browser version associated with a browser in the client computer, and a browser language associated with the browser.
21. The method of claim 1, wherein sending the characteristics of the client computer to the server computer and sending the request to the server computer for the consumer authentication occur in a single message transmission.
Patent Citations (612)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4528442(A) | 1985-07-01 | Endo | Applicant |
| US5177342(A) | 1993-01-01 | Adams | Applicant |
| US5254843(A) | 1993-10-01 | Hynes | Applicant |
| US5311594(A) | 1994-05-01 | Penzias | Applicant |
| US5420926(A) | 1995-05-01 | Low | Applicant |
| US5434398(A) | 1995-07-01 | Goldberg | Applicant |
| US5465387(A) | 1995-11-01 | Mukherjee | Applicant |
| US5513250(A) | 1996-04-01 | McAllister | Applicant |
| US5530438(A) | 1996-06-01 | Bickham et al. | Applicant |
| US5539810(A) | 1996-07-01 | Kennedy, III | Applicant |
| US5613012(A) | 1997-03-01 | Hoffman | Applicant |
| US5615110(A) | 1997-03-01 | Wong | Applicant |
| US5625689(A) | 1997-04-01 | Indeck | Applicant |
| US5627355(A) | 1997-05-01 | Rahman | Applicant |
| US5708422(A) | 1998-01-01 | Blonder | Applicant |
| US5740244(A) | 1998-04-01 | Indeck | Applicant |
| US5774525(A) | 1998-06-01 | Kanevsky et al. | Applicant |
| US5781438(A) | 1998-07-01 | Lee | Applicant |
| US5812668(A) | 1998-09-01 | Weber | Applicant |
| US5819226(A) | 1998-10-01 | Gopinatham | Applicant |
| US5834747(A) | 1998-11-01 | Cooper | Applicant |
| US5872834(A) | 1999-02-01 | Teitelbaum | Applicant |
| US5878337(A) | 1999-03-01 | Joao | Applicant |
| US5883810(A) | 1999-03-01 | Franklin | Applicant |
| US5903830(A) | 1999-05-01 | Joao | Applicant |
| US5914472(A) | 1999-06-01 | Foladare | Applicant |
| US5920628(A) | 1999-07-01 | Indeck | Applicant |
| US5953710(A) | 1999-09-01 | Fleming | Applicant |
| US5956699(A) | 1999-09-01 | Wong | Applicant |
| US5988497(A) | 1999-11-01 | Wallace | Applicant |
| US6000832(A) | 1999-12-01 | Franklin | Applicant |
| US6012144(A) | 2000-01-01 | Pickett | Applicant |
| US6014635(A) | 2000-01-01 | Harris | Applicant |
| US6029154(A) | 2000-02-01 | Pettitt | Applicant |
| US6044360(A) | 2000-03-01 | Picciallo | Applicant |
| US6047268(A) | 2000-04-01 | Bartoli | Applicant |
| US6064990(A) | 2000-05-01 | Goldsmith | Applicant |
| US6095413(A) | 2000-08-01 | Tetro | Applicant |
| US6157707(A) | 2000-12-01 | Baulier | Applicant |
| US6163771(A) | 2000-12-01 | Walker | Applicant |
| US6219793(B1) | 2001-04-01 | Li | Applicant |
| US6227447(B1) | 2001-05-01 | Campisano | Applicant |
| US6236981(B1) | 2001-05-01 | Hill | Applicant |
| US6263447(B1) | 2001-06-01 | French et al. | Applicant |
| US6260146(B1) | 2001-07-01 | Mos | Applicant |
| US6267292(B1) | 2001-07-01 | Walker | Applicant |
| US6308890(B1) | 2001-10-01 | Cooper | Applicant |
| US6327578(B1) | 2001-12-01 | Linehan | Applicant |
| US6330550(B1) | 2001-12-01 | Brisebois | Applicant |
| US6341724(B2) | 2002-01-01 | Campisano | Applicant |
| US6422462(B1) | 2002-07-01 | Cohen | Applicant |
| US6425523(B1) | 2002-07-01 | Shem Ur | Applicant |
| US6442532(B1) | 2002-08-01 | Kawan | Applicant |
| US6496936(B1) | 2002-12-01 | French | Applicant |
| US6505171(B1) | 2003-01-01 | Cohen | Applicant |
| US6529725(B1) | 2003-03-01 | Joao et al. | Applicant |
| US6535855(B1) | 2003-03-01 | Cahill et al. | Applicant |
| US6560581(B1) | 2003-05-01 | Fox | Applicant |
| US6592044(B1) | 2003-07-01 | Wong | Applicant |
| US6612488(B2) | 2003-09-01 | Suzuki | Applicant |
| US6632248(B1) | 2003-10-01 | Isaac | Applicant |
| US6636833(B1) | 2003-10-01 | Flitcroft | Applicant |
| US6675153(B1) | 2004-01-01 | Cook | Applicant |
| US6684250(B2) | 2004-01-01 | Anderson et al. | Applicant |
| US6714918(B2) | 2004-03-01 | Hillmer | Applicant |
| US6732082(B1) | 2004-05-01 | Gavan | Applicant |
| US6748367(B1) | 2004-06-01 | Lee | Applicant |
| US6805287(B2) | 2004-10-01 | Bishop | Applicant |
| US6832721(B2) | 2004-12-01 | Fujii | Applicant |
| US6836670(B2) | 2004-12-01 | Castrogiovanni | Applicant |
| US6857073(B2) | 2005-02-01 | French et al. | Applicant |
| US6879965(B2) | 2005-04-01 | Fung | Applicant |
| US6899269(B1) | 2005-05-01 | Deland | Applicant |
| US6901387(B2) | 2005-05-01 | Wells | Applicant |
| US6913194(B2) | 2005-07-01 | Suzuki | Applicant |
| US6931382(B2) | 2005-08-01 | Laage | Applicant |
| US6938019(B1) | 2005-08-01 | Uzo | Applicant |
| US6941285(B2) | 2005-09-01 | Sarcanin | Applicant |
| US6980670(B1) | 2005-12-01 | Hoffman | Applicant |
| US6990470(B2) | 2006-01-01 | Hogan | Applicant |
| US6991157(B2) | 2006-01-01 | Bishop | Applicant |
| US7003497(B2) | 2006-02-01 | Maes | Applicant |
| US7004382(B2) | 2006-02-01 | Sandru | Applicant |
| US7024396(B2) | 2006-04-01 | Woodward | Applicant |
| US7044394(B2) | 2006-05-01 | Brown | Applicant |
| US7051002(B2) | 2006-05-01 | Keresman, III | Applicant |
| US7051929(B2) | 2006-05-01 | Li | Applicant |
| US7069249(B2) | 2006-06-01 | Stolfo | Applicant |
| US7096003(B2) | 2006-08-01 | Joao | Applicant |
| US7100049(B2) | 2006-08-01 | Gasparini | Applicant |
| US7103576(B2) | 2006-09-01 | Mann, III | Applicant |
| US7113930(B2) | 2006-09-01 | Eccles | Applicant |
| US7136835(B1) | 2006-11-01 | Flitcroft | Applicant |
| US7143095(B2) | 2006-11-01 | Barrett | Applicant |
| US7165051(B2) | 2007-01-01 | Ronning | Applicant |
| US7177835(B1) | 2007-02-01 | Walker | Applicant |
| US7177848(B2) | 2007-02-01 | Hogan | Applicant |
| US7194437(B1) | 2007-03-01 | Britto | Applicant |
| US7225156(B2) | 2007-05-01 | Fisher | Applicant |
| US7231657(B2) | 2007-06-01 | Honarvar | Applicant |
| US7249093(B1) | 2007-07-01 | King | Applicant |
| US7264154(B2) | 2007-09-01 | Harris | Applicant |
| US7272728(B2) | 2007-09-01 | Pierson | Applicant |
| US7273168(B2) | 2007-09-01 | Linlor | Applicant |
| US7287692(B1) | 2007-10-01 | Patel | Applicant |
| US7292999(B2) | 2007-11-01 | Hobson | Applicant |
| US7319978(B2) | 2008-01-01 | Minamishin | Applicant |
| US7330871(B2) | 2008-02-01 | Barber | Applicant |
| US7343149(B2) | 2008-03-01 | Benco | Applicant |
| US7343351(B1) | 2008-03-01 | Bishop et al. | Applicant |
| US7350230(B2) | 2008-03-01 | Forrest | Applicant |
| US7353382(B2) | 2008-04-01 | Labrou | Applicant |
| US7357310(B2) | 2008-04-01 | Calabrese et al. | Applicant |
| US7363257(B2) | 2008-04-01 | Kunz | Applicant |
| US7373669(B2) | 2008-05-01 | Eisen | Applicant |
| US7379919(B2) | 2008-05-01 | Hogan | Applicant |
| USRE40444(E) | 2008-07-01 | Linehan | Applicant |
| US7415443(B2) | 2008-08-01 | Hobson | Applicant |
| US7430537(B2) | 2008-09-01 | Templeton | Examiner |
| US7444676(B1) | 2008-10-01 | Asghari-Kamrani | Applicant |
| US7469151(B2) | 2008-12-01 | Khan | Applicant |
| US7483858(B2) | 2009-01-01 | Foran | Applicant |
| US7500607(B2) | 2009-03-01 | Williams | Applicant |
| US7523067(B1) | 2009-04-01 | Nakajima | Applicant |
| US7545748(B1) | 2009-04-01 | Riddle | Applicant |
| US7548889(B2) | 2009-06-01 | Bhambri | Applicant |
| US7548890(B2) | 2009-06-01 | Shakkarwar | Applicant |
| US7567934(B2) | 2009-07-01 | Flitcroft | Applicant |
| US7567936(B1) | 2009-07-01 | Peckover | Applicant |
| US7571139(B1) | 2009-08-01 | Giordano | Applicant |
| US7571142(B1) | 2009-08-01 | Flitcroft | Applicant |
| US7580898(B2) | 2009-08-01 | Brown | Applicant |
| US7584153(B2) | 2009-09-01 | Brown | Applicant |
| US7593896(B1) | 2009-09-01 | Flitcroft | Applicant |
| US7606560(B2) | 2009-10-01 | Labrou | Applicant |
| US7606770(B2) | 2009-10-01 | Pinnell | Applicant |
| US7620600(B2) | 2009-11-01 | Patil | Applicant |
| US7627531(B2) | 2009-12-01 | Breck | Applicant |
| US7627895(B2) | 2009-12-01 | Gifford | Applicant |
| US7650314(B1) | 2010-01-01 | Saunders | Applicant |
| US7685037(B2) | 2010-03-01 | Reiners | Applicant |
| US7702578(B2) | 2010-04-01 | Fung | Applicant |
| US7707120(B2) | 2010-04-01 | Dominguez | Applicant |
| US7712655(B2) | 2010-05-01 | Wong | Applicant |
| US7734527(B2) | 2010-06-01 | Uzo | Applicant |
| US7740168(B2) | 2010-06-01 | Hammad | Applicant |
| US7752084(B2) | 2010-07-01 | Pettitt | Applicant |
| US7753265(B2) | 2010-07-01 | Harris | Applicant |
| US7770789(B2) | 2010-08-01 | Oder, II | Applicant |
| US7784685(B1) | 2010-08-01 | Hopkins, III | Applicant |
| US7793851(B2) | 2010-09-01 | Mullen | Applicant |
| US7801826(B2) | 2010-09-01 | Labrou | Applicant |
| US7805376(B2) | 2010-09-01 | Smith | Applicant |
| US7805378(B2) | 2010-09-01 | Berardi | Applicant |
| US7810165(B2) | 2010-10-01 | Hammad | Applicant |
| US7819322(B2) | 2010-10-01 | Hammad | Applicant |
| US7828220(B2) | 2010-11-01 | Mullen | Applicant |
| US7835960(B2) | 2010-11-01 | Breck | Applicant |
| US7841523(B2) | 2010-11-01 | Oder, II | Applicant |
| US7841539(B2) | 2010-11-01 | Hewton | Applicant |
| US7844550(B2) | 2010-11-01 | Walker | Applicant |
| US7849020(B2) | 2010-12-01 | Johnson | Applicant |
| US7853529(B1) | 2010-12-01 | Walker | Applicant |
| US7853995(B2) | 2010-12-01 | Chow | Applicant |
| US7865414(B2) | 2011-01-01 | Fung | Applicant |
| US7873579(B2) | 2011-01-01 | Hobson | Applicant |
| US7873580(B2) | 2011-01-01 | Hobson | Applicant |
| US7890393(B2) | 2011-02-01 | Talbert | Applicant |
| US7891563(B2) | 2011-02-01 | Oder, II | Applicant |
| US7896238(B2) | 2011-03-01 | Fein | Applicant |
| US7922082(B2) | 2011-04-01 | Muscato | Applicant |
| US7931195(B2) | 2011-04-01 | Mullen | Applicant |
| US7938318(B2) | 2011-05-01 | Fein | Applicant |
| US7954705(B2) | 2011-06-01 | Mullen | Applicant |
| US7959076(B1) | 2011-06-01 | Hopkins, III | Applicant |
| US7996288(B1) | 2011-08-01 | Stolfo | Applicant |
| US8025223(B2) | 2011-09-01 | Saunders | Applicant |
| US8046256(B2) | 2011-10-01 | Chien | Applicant |
| US8060448(B2) | 2011-11-01 | Jones | Applicant |
| US8060449(B1) | 2011-11-01 | Zhu | Applicant |
| US8074877(B2) | 2011-12-01 | Mullen | Applicant |
| US8074879(B2) | 2011-12-01 | Harris | Applicant |
| US8082210(B2) | 2011-12-01 | Hansen | Applicant |
| US8095113(B2) | 2012-01-01 | Kean | Applicant |
| US8104679(B2) | 2012-01-01 | Brown | Applicant |
| USRE43157(E) | 2012-02-01 | Bishop | Applicant |
| US8109436(B1) | 2012-02-01 | Hopkins, III | Applicant |
| US8121942(B2) | 2012-02-01 | Carlson et al. | Applicant |
| US8121956(B2) | 2012-02-01 | Carlson | Applicant |
| US8126449(B2) | 2012-02-01 | Beenau | Applicant |
| US8171525(B1) | 2012-05-01 | Pelly | Applicant |
| US8196813(B2) | 2012-06-01 | Vadhri | Applicant |
| US8205791(B2) | 2012-06-01 | Randazza | Applicant |
| US8224702(B2) | 2012-07-01 | Mengerink | Applicant |
| US8225385(B2) | 2012-07-01 | Chow | Applicant |
| US8265993(B2) | 2012-09-01 | Chien | Applicant |
| US8280777(B2) | 2012-10-01 | Mengerink | Applicant |
| US8328095(B2) | 2012-12-01 | Oder, II | Applicant |
| US8376225(B1) | 2013-02-01 | Hopkins, III | Applicant |
| US8380177(B2) | 2013-02-01 | Laracey | Applicant |
| US8387873(B2) | 2013-03-01 | Saunders | Applicant |
| US8401539(B2) | 2013-03-01 | Beenau | Applicant |
| US8401898(B2) | 2013-03-01 | Chien | Applicant |
| US8403211(B2) | 2013-03-01 | Brooks | Applicant |
| US8412623(B2) | 2013-04-01 | Moon | Applicant |
| US8412837(B1) | 2013-04-01 | Emigh | Applicant |
| US8417642(B2) | 2013-04-01 | Oren | Applicant |
| US8447699(B2) | 2013-05-01 | Batada | Applicant |
| US8453223(B2) | 2013-05-01 | Svigals | Applicant |
| US8453925(B2) | 2013-06-01 | Fisher | Applicant |
| US8458487(B1) | 2013-06-01 | Palgon | Applicant |
| US8484134(B2) | 2013-07-01 | Hobson | Applicant |
| US8485437(B2) | 2013-07-01 | Mullen | Applicant |
| US8494959(B2) | 2013-07-01 | Hathaway | Applicant |
| US8498908(B2) | 2013-07-01 | Mengerink | Applicant |
| US8504478(B2) | 2013-08-01 | Saunders | Applicant |
| US8510816(B2) | 2013-08-01 | Quach | Applicant |
| US8533118(B2) | 2013-09-01 | Weller et al. | Applicant |
| US8538845(B2) | 2013-09-01 | Liberty | Applicant |
| US8555079(B2) | 2013-10-01 | Shablygin | Applicant |
| US8566168(B1) | 2013-10-01 | Bierbaum | Applicant |
| US8567670(B2) | 2013-10-01 | Stanfield | Applicant |
| US8571939(B2) | 2013-10-01 | Lindsey | Applicant |
| US8577336(B2) | 2013-11-01 | Mechaley, Jr. | Applicant |
| US8577803(B2) | 2013-11-01 | Chatterjee | Applicant |
| US8578176(B2) | 2013-11-01 | Mattsson | Applicant |
| US8583494(B2) | 2013-11-01 | Fisher | Applicant |
| US8584251(B2) | 2013-11-01 | Mcguire | Applicant |
| US8589237(B2) | 2013-11-01 | Fisher | Applicant |
| US8589271(B2) | 2013-11-01 | Evans | Applicant |
| US8595098(B2) | 2013-11-01 | Starai | Applicant |
| US8595812(B2) | 2013-11-01 | Bomar | Applicant |
| US8595850(B2) | 2013-11-01 | Spies | Applicant |
| US8606638(B2) | 2013-12-01 | Dragt | Applicant |
| US8606720(B1) | 2013-12-01 | Baker | Applicant |
| US8615468(B2) | 2013-12-01 | Varadarajan | Applicant |
| US8620754(B2) | 2013-12-01 | Fisher | Applicant |
| US8635157(B2) | 2014-01-01 | Smith | Applicant |
| US8646059(B1) | 2014-02-01 | Von Behren | Applicant |
| US8651374(B2) | 2014-02-01 | Brabson | Applicant |
| US8656180(B2) | 2014-02-01 | Shablygin | Applicant |
| US8688543(B2) | 2014-04-01 | Dominguez | Applicant |
| US8706621(B2) | 2014-04-01 | Carlson et al. | Applicant |
| US8744958(B2) | 2014-06-01 | Carlson et al. | Applicant |
| US2001/0029485(A1) | 2001-10-01 | Brody | Applicant |
| US2001/0034720(A1) | 2001-10-01 | Armes | Applicant |
| US2001/0054003(A1) | 2001-12-01 | Chien | Applicant |
| US2001/0056409(A1) | 2001-12-01 | Bellovin et al. | Applicant |
| US2002/0007320(A1) | 2002-01-01 | Hogan | Applicant |
| US2002/0007352(A1) | 2002-01-01 | Fieschi | Applicant |
| US2002/0016749(A1) | 2002-02-01 | Borecki | Applicant |
| US2002/0029193(A1) | 2002-03-01 | Ranjan | Applicant |
| US2002/0035548(A1) | 2002-03-01 | Hogan | Applicant |
| US2002/0035622(A1) | 2002-03-01 | Barber | Applicant |
| US2002/0062257(A1) | 2002-05-01 | Minamishin et al. | Applicant |
| US2002/0073045(A1) | 2002-06-01 | Rubin | Applicant |
| US2002/0077978(A1) | 2002-06-01 | O'Leary | Applicant |
| US2002/0087344(A1) | 2002-07-01 | Billings et al. | Applicant |
| US2002/0091562(A1) | 2002-07-01 | Siegel | Applicant |
| US2002/0108062(A1) | 2002-08-01 | Nakajima | Applicant |
| US2002/0111919(A1) | 2002-08-01 | Weller et al. | Applicant |
| US2002/0116341(A1) | 2002-08-01 | Hogan | Applicant |
| US2002/0120846(A1) | 2002-08-01 | Stewart | Applicant |
| US2002/0133462(A1) | 2002-09-01 | Shteyn | Applicant |
| US2002/0133467(A1) | 2002-09-01 | Hobson | Applicant |
| US2002/0147913(A1) | 2002-10-01 | Lun Yip | Applicant |
| US2003/0028481(A1) | 2003-02-01 | Flitcroft | Applicant |
| US2003/0050896(A1) | 2003-03-01 | Wiederin | Applicant |
| US2003/0130955(A1) | 2003-07-01 | Hawthorne | Applicant |
| US2003/0140004(A1) | 2003-07-01 | O'Leary | Applicant |
| US2003/0154139(A1) | 2003-08-01 | Woo | Applicant |
| US2003/0154406(A1) | 2003-08-01 | Honarvar | Applicant |
| US2003/0191709(A1) | 2003-10-01 | Elston | Applicant |
| US2003/0191945(A1) | 2003-10-01 | Keech | Applicant |
| US2003/0208684(A1) | 2003-11-01 | Camacho | Applicant |
| US2004/0010462(A1) | 2004-01-01 | Moon | Applicant |
| US2004/0019564(A1) | 2004-01-01 | Goldthwaite | Applicant |
| US2004/0050928(A1) | 2004-03-01 | Bishop | Applicant |
| US2004/0059682(A1) | 2004-03-01 | Hasumi | Applicant |
| US2004/0078340(A1) | 2004-04-01 | Evans | Applicant |
| US2004/0093281(A1) | 2004-05-01 | Silverstein | Applicant |
| US2004/0107170(A1) | 2004-06-01 | Labrou | Applicant |
| US2004/0139008(A1) | 2004-07-01 | Mascavage | Applicant |
| US2004/0143532(A1) | 2004-07-01 | Lee | Applicant |
| US2004/0158532(A1) | 2004-08-01 | Breck | Applicant |
| US2004/0171406(A1) | 2004-09-01 | Purk | Applicant |
| US2004/0185830(A1) | 2004-09-01 | Joao | Applicant |
| US2004/0210449(A1) | 2004-10-01 | Breck | Applicant |
| US2004/0210498(A1) | 2004-10-01 | Freund | Applicant |
| US2004/0210536(A1) | 2004-10-01 | Gudelj | Applicant |
| US2004/0232225(A1) | 2004-11-01 | Bishop | Applicant |
| US2004/0260646(A1) | 2004-12-01 | Berardi | Applicant |
| US2005/0037735(A1) | 2005-02-01 | Coutts | Applicant |
| US2005/0080730(A1) | 2005-04-01 | Sorrentino | Applicant |
| US2005/0097320(A1) | 2005-05-01 | Golan | Applicant |
| US2005/0108178(A1) | 2005-05-01 | York | Applicant |
| US2005/0119978(A1) | 2005-06-01 | Ates | Applicant |
| US2005/0122209(A1) | 2005-06-01 | Black | Applicant |
| US2005/0170814(A1) | 2005-08-01 | Joao | Applicant |
| US2005/0199709(A1) | 2005-09-01 | Linlor | Applicant |
| US2005/0240527(A1) | 2005-10-01 | Goldman | Applicant |
| US2005/0246278(A1) | 2005-11-01 | Gerber et al. | Applicant |
| US2005/0246293(A1) | 2005-11-01 | Ong | Applicant |
| US2005/0269401(A1) | 2005-12-01 | Spitzer | Applicant |
| US2005/0269402(A1) | 2005-12-01 | Spitzer | Applicant |
| US2005/0273442(A1) | 2005-12-01 | Bennett | Applicant |
| US2005/0278542(A1) | 2005-12-01 | Pierson et al. | Applicant |
| US2006/0010072(A1) | 2006-01-01 | Eisen | Applicant |
| US2006/0059110(A1) | 2006-03-01 | Madhok | Applicant |
| US2006/0156385(A1) | 2006-07-01 | Chiviendacz | Applicant |
| US2006/0202025(A1) | 2006-09-01 | Calabrese | Applicant |
| US2006/0235795(A1) | 2006-10-01 | Johnson | Applicant |
| US2006/0237528(A1) | 2006-10-01 | Bishop | Applicant |
| US2006/0278704(A1) | 2006-12-01 | Saunders | Applicant |
| US2006/0281439(A1) | 2006-12-01 | Benco | Applicant |
| US2006/0282382(A1) | 2006-12-01 | Balasubramanian | Applicant |
| US2007/0006286(A1) | 2007-01-01 | Singhal | Applicant |
| US2007/0107044(A1) | 2007-05-01 | Yuen | Applicant |
| US2007/0124801(A1) | 2007-05-01 | Thomas | Applicant |
| US2007/0129955(A1) | 2007-06-01 | Dalmia | Applicant |
| US2007/0136193(A1) | 2007-06-01 | Starr | Applicant |
| US2007/0136211(A1) | 2007-06-01 | Brown | Applicant |
| US2007/0143230(A1) | 2007-06-01 | Narainsamy | Applicant |
| US2007/0170247(A1) | 2007-07-01 | Friedman | Applicant |
| US2007/0174448(A1) | 2007-07-01 | Ahuja et al. | Applicant |
| US2007/0179885(A1) | 2007-08-01 | Bird | Applicant |
| US2007/0208671(A1) | 2007-09-01 | Brown | Applicant |
| US2007/0214151(A1) | 2007-09-01 | Thomas et al. | Applicant |
| US2007/0234409(A1) | 2007-10-01 | Eisen | Applicant |
| US2007/0239606(A1) | 2007-10-01 | Eisen | Applicant |
| US2007/0244830(A1) | 2007-10-01 | Hilderman | Applicant |
| US2007/0245414(A1) | 2007-10-01 | Chan | Applicant |
| US2007/0288377(A1) | 2007-12-01 | Shaked | Applicant |
| US2007/0291995(A1) | 2007-12-01 | Rivera | Applicant |
| US2008/0005037(A1) | 2008-01-01 | Hammad | Applicant |
| US2008/0015988(A1) | 2008-01-01 | Brown | Applicant |
| US2008/0029607(A1) | 2008-02-01 | Mullen | Applicant |
| US2008/0034428(A1) | 2008-02-01 | Bejar | Applicant |
| US2008/0035738(A1) | 2008-02-01 | Mullen | Applicant |
| US2008/0039209(A1) | 2008-02-01 | Chen | Examiner |
| US2008/0040276(A1) | 2008-02-01 | Hammad | Applicant |
| US2008/0046723(A1) | 2008-02-01 | Weber | Applicant |
| US2008/0046968(A1) | 2008-02-01 | Cline | Applicant |
| US2008/0052226(A1) | 2008-02-01 | Agarwal | Applicant |
| US2008/0054068(A1) | 2008-03-01 | Mullen | Applicant |
| US2008/0054079(A1) | 2008-03-01 | Mullen | Applicant |
| US2008/0054081(A1) | 2008-03-01 | Mullen | Applicant |
| US2008/0065553(A1) | 2008-03-01 | Faith | Applicant |
| US2008/0065554(A1) | 2008-03-01 | Hogan | Applicant |
| US2008/0065555(A1) | 2008-03-01 | Mullen | Applicant |
| US2008/0077526(A1) | 2008-03-01 | Arumugam | Applicant |
| US2008/0087722(A1) | 2008-04-01 | Collins | Applicant |
| US2008/0099552(A1) | 2008-05-01 | Grillion | Applicant |
| US2008/0103972(A1) | 2008-05-01 | Lanc | Applicant |
| US2008/0103982(A1) | 2008-05-01 | Hammad | Applicant |
| US2008/0104684(A1) | 2008-05-01 | Lunde et al. | Applicant |
| US2008/0120507(A1) | 2008-05-01 | Shakkarwar | Applicant |
| US2008/0133420(A1) | 2008-06-01 | Barber | Applicant |
| US2008/0154760(A1) | 2008-06-01 | Calabrese et al. | Applicant |
| US2008/0162295(A1) | 2008-07-01 | Bedier | Applicant |
| US2008/0183593(A1) | 2008-07-01 | Dierks | Applicant |
| US2008/0189186(A1) | 2008-08-01 | Choi | Applicant |
| US2008/0201264(A1) | 2008-08-01 | Brown | Applicant |
| US2008/0201265(A1) | 2008-08-01 | Hewton | Applicant |
| US2008/0208761(A1) | 2008-08-01 | Autry | Applicant |
| US2008/0228646(A1) | 2008-09-01 | Myers | Applicant |
| US2008/0243702(A1) | 2008-10-01 | Hart | Applicant |
| US2008/0244744(A1) | 2008-10-01 | Thomas et al. | Applicant |
| US2008/0245855(A1) | 2008-10-01 | Fein | Applicant |
| US2008/0245861(A1) | 2008-10-01 | Fein | Applicant |
| US2008/0255992(A1) | 2008-10-01 | Lin | Applicant |
| US2008/0257959(A1) | 2008-10-01 | Oved | Applicant |
| US2008/0283591(A1) | 2008-11-01 | Oder, II | Applicant |
| US2008/0288384(A1) | 2008-11-01 | Collins et al. | Applicant |
| US2008/0288405(A1) | 2008-11-01 | John | Applicant |
| US2008/0298588(A1) | 2008-12-01 | Shakkarwar | Applicant |
| US2008/0302869(A1) | 2008-12-01 | Mullen | Applicant |
| US2008/0302876(A1) | 2008-12-01 | Mullen | Applicant |
| US2008/0319869(A1) | 2008-12-01 | Carlson | Applicant |
| US2008/0319896(A1) | 2008-12-01 | Carlson | Applicant |
| US2008/0319904(A1) | 2008-12-01 | Carlson | Applicant |
| US2009/0006262(A1) | 2009-01-01 | Brown | Applicant |
| US2009/0010488(A1) | 2009-01-01 | Matsuoka | Applicant |
| US2009/0037213(A1) | 2009-02-01 | Eisen | Applicant |
| US2009/0037333(A1) | 2009-02-01 | Flitcroft | Applicant |
| US2009/0043702(A1) | 2009-02-01 | Bennett | Applicant |
| US2009/0048971(A1) | 2009-02-01 | Hathaway | Applicant |
| US2009/0048975(A1) | 2009-02-01 | Felger | Applicant |
| US2009/0049529(A1) | 2009-02-01 | Felger | Applicant |
| US2009/0055315(A1) | 2009-02-01 | Felger | Applicant |
| US2009/0083184(A1) | 2009-02-01 | Eisen | Applicant |
| US2009/0099961(A1) | 2009-04-01 | Ogilvy | Applicant |
| US2009/0106112(A1) | 2009-04-01 | Dalmia | Applicant |
| US2009/0106160(A1) | 2009-04-01 | Skowronek | Applicant |
| US2009/0134217(A1) | 2009-05-01 | Flitcroft | Applicant |
| US2009/0157555(A1) | 2009-06-01 | Biffle | Applicant |
| US2009/0159673(A1) | 2009-06-01 | Mullen | Applicant |
| US2009/0159700(A1) | 2009-06-01 | Mullen | Applicant |
| US2009/0159707(A1) | 2009-06-01 | Mullen | Applicant |
| US2009/0173782(A1) | 2009-07-01 | Muscato | Applicant |
| US2009/0200371(A1) | 2009-08-01 | Kean | Applicant |
| US2009/0204524(A1) | 2009-08-01 | McGeeorge | Applicant |
| US2009/0248583(A1) | 2009-10-01 | Chhabra | Applicant |
| US2009/0271306(A1) | 2009-10-01 | Pierson | Applicant |
| US2009/0276347(A1) | 2009-11-01 | Kargman | Applicant |
| US2009/0294527(A1) | 2009-12-01 | Brabson | Applicant |
| US2009/0307139(A1) | 2009-12-01 | Mardikar | Applicant |
| US2009/0308921(A1) | 2009-12-01 | Mullen | Applicant |
| US2009/0327131(A1) | 2009-12-01 | Beenau | Applicant |
| US2010/0008535(A1) | 2010-01-01 | Abulafia | Applicant |
| US2010/0036749(A1) | 2010-02-01 | Barber | Applicant |
| US2010/0088237(A1) | 2010-04-01 | Wankmueller | Applicant |
| US2010/0094755(A1) | 2010-04-01 | Kloster | Applicant |
| US2010/0106644(A1) | 2010-04-01 | Annan | Applicant |
| US2010/0120408(A1) | 2010-05-01 | Beenau | Applicant |
| US2010/0133334(A1) | 2010-06-01 | Vadhri | Applicant |
| US2010/0138347(A1) | 2010-06-01 | Chen | Applicant |
| US2010/0145860(A1) | 2010-06-01 | Pelegero | Applicant |
| US2010/0161433(A1) | 2010-06-01 | White | Applicant |
| US2010/0185545(A1) | 2010-07-01 | Royyuru | Applicant |
| US2010/0211505(A1) | 2010-08-01 | Saunders | Applicant |
| US2010/0223186(A1) | 2010-09-01 | Hogan | Applicant |
| US2010/0228668(A1) | 2010-09-01 | Hogan | Applicant |
| US2010/0235284(A1) | 2010-09-01 | Moore | Applicant |
| US2010/0258620(A1) | 2010-10-01 | Torreyson | Applicant |
| US2010/0291904(A1) | 2010-11-01 | Musfeldt | Applicant |
| US2010/0306076(A1) | 2010-12-01 | Taveau | Applicant |
| US2010/0325041(A1) | 2010-12-01 | Berardi | Applicant |
| US2011/0010292(A1) | 2011-01-01 | Giordano | Applicant |
| US2011/0016047(A1) | 2011-01-01 | Wu | Applicant |
| US2011/0016320(A1) | 2011-01-01 | Bergsten | Applicant |
| US2011/0029902(A1) | 2011-02-01 | Bailey | Applicant |
| US2011/0040640(A1) | 2011-02-01 | Erikson | Applicant |
| US2011/0083018(A1) | 2011-04-01 | Kesanupalli | Applicant |
| US2011/0087596(A1) | 2011-04-01 | Dorsey | Applicant |
| US2011/0093397(A1) | 2011-04-01 | Carlson | Applicant |
| US2011/0125597(A1) | 2011-05-01 | Oder, II | Applicant |
| US2011/0153437(A1) | 2011-06-01 | Archer | Applicant |
| US2011/0154466(A1) | 2011-06-01 | Harper | Applicant |
| US2011/0161233(A1) | 2011-06-01 | Tieken | Applicant |
| US2011/0191244(A1) | 2011-08-01 | Dai | Applicant |
| US2011/0238511(A1) | 2011-09-01 | Park | Applicant |
| US2011/0238573(A1) | 2011-09-01 | Varadarajan | Applicant |
| US2011/0246317(A1) | 2011-10-01 | Coppinger | Applicant |
| US2011/0272471(A1) | 2011-11-01 | Mullen | Applicant |
| US2011/0272478(A1) | 2011-11-01 | Mullen | Applicant |
| US2011/0276380(A1) | 2011-11-01 | Mullen | Applicant |
| US2011/0276381(A1) | 2011-11-01 | Mullen | Applicant |
| US2011/0276424(A1) | 2011-11-01 | Mullen | Applicant |
| US2011/0276425(A1) | 2011-11-01 | Mullen | Applicant |
| US2011/0295745(A1) | 2011-12-01 | White | Applicant |
| US2011/0302081(A1) | 2011-12-01 | Saunders | Applicant |
| US2012/0028609(A1) | 2012-02-01 | Hruska | Applicant |
| US2012/0035998(A1) | 2012-02-01 | Chien | Applicant |
| US2012/0041881(A1) | 2012-02-01 | Basu | Applicant |
| US2012/0047237(A1) | 2012-02-01 | Arvidsson | Applicant |
| US2012/0066078(A1) | 2012-03-01 | Kingston | Applicant |
| US2012/0072350(A1) | 2012-03-01 | Goldthwaite | Applicant |
| US2012/0078735(A1) | 2012-03-01 | Bauer | Applicant |
| US2012/0078798(A1) | 2012-03-01 | Downing | Applicant |
| US2012/0078799(A1) | 2012-03-01 | Jackson | Applicant |
| US2012/0095852(A1) | 2012-04-01 | Bauer | Applicant |
| US2012/0095865(A1) | 2012-04-01 | Doherty | Applicant |
| US2012/0116902(A1) | 2012-05-01 | Cardina | Applicant |
| US2012/0116975(A1) | 2012-05-01 | Carlson | Applicant |
| US2012/0123882(A1) | 2012-05-01 | Carlson | Applicant |
| US2012/0123940(A1) | 2012-05-01 | Killian | Applicant |
| US2012/0129514(A1) | 2012-05-01 | Beenau | Applicant |
| US2012/0143767(A1) | 2012-06-01 | Abadir | Applicant |
| US2012/0143772(A1) | 2012-06-01 | Abadir | Applicant |
| US2012/0150744(A1) | 2012-06-01 | Carlson et al. | Applicant |
| US2012/0158580(A1) | 2012-06-01 | Eram | Applicant |
| US2012/0158593(A1) | 2012-06-01 | Garfinkle | Applicant |
| US2012/0173431(A1) | 2012-07-01 | Ritchie | Applicant |
| US2012/0185386(A1) | 2012-07-01 | Salama | Applicant |
| US2012/0197807(A1) | 2012-08-01 | Schlesser | Applicant |
| US2012/0203664(A1) | 2012-08-01 | Torossian | Applicant |
| US2012/0203666(A1) | 2012-08-01 | Torossian | Applicant |
| US2012/0215688(A1) | 2012-08-01 | Musser | Applicant |
| US2012/0215696(A1) | 2012-08-01 | Salonen | Applicant |
| US2012/0231844(A1) | 2012-09-01 | Coppinger | Applicant |
| US2012/0233004(A1) | 2012-09-01 | Bercaw | Applicant |
| US2012/0246070(A1) | 2012-09-01 | Vadhri | Applicant |
| US2012/0246071(A1) | 2012-09-01 | Jain | Applicant |
| US2012/0265631(A1) | 2012-10-01 | Cronic | Applicant |
| US2012/0271770(A1) | 2012-10-01 | Harris | Applicant |
| US2012/0297446(A1) | 2012-11-01 | Webb | Applicant |
| US2012/0300932(A1) | 2012-11-01 | Cambridge | Applicant |
| US2012/0303503(A1) | 2012-11-01 | Cambridge | Applicant |
| US2012/0303961(A1) | 2012-11-01 | Kean | Applicant |
| US2012/0304273(A1) | 2012-11-01 | Bailey | Applicant |
| US2012/0310725(A1) | 2012-12-01 | Chien | Applicant |
| US2012/0310831(A1) | 2012-12-01 | Harris | Applicant |
| US2012/0316992(A1) | 2012-12-01 | Oborne | Applicant |
| US2012/0317035(A1) | 2012-12-01 | Royyuru | Applicant |
| US2012/0317036(A1) | 2012-12-01 | Bower | Applicant |
| US2013/0017784(A1) | 2013-01-01 | Fisher | Applicant |
| US2013/0019098(A1) | 2013-01-01 | Gupta | Applicant |
| US2013/0054337(A1) | 2013-02-01 | Brendell | Applicant |
| US2013/0054466(A1) | 2013-02-01 | Muscato | Applicant |
| US2013/0054474(A1) | 2013-02-01 | Yeager | Applicant |
| US2013/0081122(A1) | 2013-03-01 | Svigals | Applicant |
| US2013/0091028(A1) | 2013-04-01 | Oder, II | Applicant |
| US2013/0110658(A1) | 2013-05-01 | Lyman | Applicant |
| US2013/0111599(A1) | 2013-05-01 | Gargiulo | Applicant |
| US2013/0117185(A1) | 2013-05-01 | Collison | Applicant |
| US2013/0124290(A1) | 2013-05-01 | Fisher | Applicant |
| US2013/0124291(A1) | 2013-05-01 | Fisher | Applicant |
| US2013/0124364(A1) | 2013-05-01 | Mittal | Applicant |
| US2013/0138525(A1) | 2013-05-01 | Bercaw | Applicant |
| US2013/0144888(A1) | 2013-06-01 | Faith | Applicant |
| US2013/0145148(A1) | 2013-06-01 | Shablygin | Applicant |
| US2013/0145172(A1) | 2013-06-01 | Shablygin | Applicant |
| US2013/0159178(A1) | 2013-06-01 | Colon | Applicant |
| US2013/0166402(A1) | 2013-06-01 | Parento | Applicant |
| US2013/0166456(A1) | 2013-06-01 | Zhang | Applicant |
| US2013/0173736(A1) | 2013-07-01 | Krzeminski | Applicant |
| US2013/0185202(A1) | 2013-07-01 | Goldthwaite | Applicant |
| US2013/0191286(A1) | 2013-07-01 | Cronic | Applicant |
| US2013/0191289(A1) | 2013-07-01 | Cronic | Applicant |
| US2013/0198071(A1) | 2013-08-01 | Jurss | Applicant |
| US2013/0200146(A1) | 2013-08-01 | Moghadam | Applicant |
| US2013/0204787(A1) | 2013-08-01 | Dubois | Applicant |
| US2013/0204793(A1) | 2013-08-01 | Kerridge | Applicant |
| US2013/0212007(A1) | 2013-08-01 | Mattsson | Applicant |
| US2013/0212017(A1) | 2013-08-01 | Bangia | Applicant |
| US2013/0212019(A1) | 2013-08-01 | Mattsson | Applicant |
| US2013/0212024(A1) | 2013-08-01 | Mattsson | Applicant |
| US2013/0212666(A1) | 2013-08-01 | Mattsson | Applicant |
| US2013/0218698(A1) | 2013-08-01 | Moon | Applicant |
| US2013/0226813(A1) | 2013-08-01 | Voltz | Applicant |
| US2013/0246202(A1) | 2013-09-01 | Tobin | Applicant |
| US2013/0246203(A1) | 2013-09-01 | Laracey | Applicant |
| US2013/0246258(A1) | 2013-09-01 | Dessert | Applicant |
| US2013/0246259(A1) | 2013-09-01 | Dessert | Applicant |
| US2013/0246267(A1) | 2013-09-01 | Tobin | Applicant |
| US2013/0254028(A1) | 2013-09-01 | Salci | Applicant |
| US2013/0254052(A1) | 2013-09-01 | Royyuru | Applicant |
| US2013/0254102(A1) | 2013-09-01 | Royyuru | Applicant |
| US2013/0254117(A1) | 2013-09-01 | Von Mueller | Applicant |
| US2013/0262296(A1) | 2013-10-01 | Thomas | Applicant |
| US2013/0262302(A1) | 2013-10-01 | Lettow | Applicant |
| US2013/0262315(A1) | 2013-10-01 | Hruska | Applicant |
| US2013/0262316(A1) | 2013-10-01 | Hruska | Applicant |
| US2013/0262317(A1) | 2013-10-01 | Collinge | Applicant |
| US2013/0275300(A1) | 2013-10-01 | Killian | Applicant |
| US2013/0275307(A1) | 2013-10-01 | Khan | Applicant |
| US2013/0275308(A1) | 2013-10-01 | Paraskeva | Applicant |
| US2013/0282502(A1) | 2013-10-01 | Jooste | Applicant |
| US2013/0282575(A1) | 2013-10-01 | Mullen | Applicant |
| US2013/0282588(A1) | 2013-10-01 | Hruska | Applicant |
| US2013/0297504(A1) | 2013-11-01 | Nwokolo | Applicant |
| US2013/0297508(A1) | 2013-11-01 | Belamant | Applicant |
| US2013/0304649(A1) | 2013-11-01 | Cronic | Applicant |
| US2013/0308778(A1) | 2013-11-01 | Fosmark | Applicant |
| US2013/0311382(A1) | 2013-11-01 | Fosmark | Applicant |
| US2013/0317982(A1) | 2013-11-01 | Mengerink | Applicant |
| US2013/0332344(A1) | 2013-12-01 | Weber | Applicant |
| US2013/0339253(A1) | 2013-12-01 | Sincai | Applicant |
| US2013/0346314(A1) | 2013-12-01 | Mogollon | Applicant |
| US2014/0007213(A1) | 2014-01-01 | Sanin | Applicant |
| US2014/0013106(A1) | 2014-01-01 | Redpath | Applicant |
| US2014/0013114(A1) | 2014-01-01 | Redpath | Applicant |
| US2014/0025581(A1) | 2014-01-01 | Calman | Applicant |
| US2014/0025585(A1) | 2014-01-01 | Calman | Applicant |
| US2014/0025958(A1) | 2014-01-01 | Calman | Applicant |
| US2014/0032417(A1) | 2014-01-01 | Mattsson | Applicant |
| US2014/0032418(A1) | 2014-01-01 | Weber | Applicant |
| US2014/0040137(A1) | 2014-02-01 | Carlson | Applicant |
| US2014/0040139(A1) | 2014-02-01 | Brudnicki | Applicant |
| US2014/0040144(A1) | 2014-02-01 | Plomske | Applicant |
| US2014/0040145(A1) | 2014-02-01 | Ozvat | Applicant |
| US2014/0040148(A1) | 2014-02-01 | Ozvat | Applicant |
| US2014/0040628(A1) | 2014-02-01 | Fort | Applicant |
| US2014/0041018(A1) | 2014-02-01 | Bomar | Applicant |
| US2014/0046853(A1) | 2014-02-01 | Spies | Applicant |
| US2014/0052532(A1) | 2014-02-01 | Tsai | Applicant |
| US2014/0052620(A1) | 2014-02-01 | Rogers | Applicant |
| US2014/0052637(A1) | 2014-02-01 | Jooste | Applicant |
| EP861461(B1) | 2008-10-01 | Applicant | |
| EP2156397(A1) | 2010-02-01 | Applicant | |
| KR2001-0044769(A) | 2001-06-01 | Applicant | |
| KR10-2002-0007303(A) | 2002-01-01 | Applicant | |
| KR10-2004-0067372(A) | 2004-07-01 | Applicant | |
| KR10-2006-0018792(A) | 2006-03-01 | Applicant | |
| KR10-2006-0079290(A) | 2006-07-01 | Applicant | |
| KR10-2007-0007044(A) | 2007-01-01 | Applicant | |
| KR10-2008-0083077(A) | 2008-09-01 | Applicant | |
| WO-48108(A1) | 2000-08-01 | Applicant | |
| WO-48360(A1) | 2000-08-01 | Applicant | |
| WO2001/035304(A1) | 2001-05-01 | Applicant | |
| WO2001/035304(A9) | 2001-05-01 | Applicant | |
| WO2004/042536(A2) | 2004-05-01 | Applicant | |
| WO2004/091170(A2) | 2004-10-01 | Applicant | |
| WO2005/001618(A2) | 2005-01-01 | Applicant | |
| WO2005/001635(A2) | 2005-01-01 | Applicant | |
| WO2005-111957(A1) | 2005-11-01 | Applicant | |
| WO2006/113834(A2) | 2006-10-01 | Applicant | |
| WO2008-102930(A1) | 2008-08-01 | Applicant | |
| WO2008/115620(A2) | 2008-09-01 | Applicant | |
| WO2009/002980(A2) | 2008-12-01 | Applicant | |
| WO2009/003030(A2) | 2008-12-01 | Applicant | |
| WO2009/032523(A1) | 2009-03-01 | Applicant | |
| WO2010/078522(A1) | 2010-07-01 | Applicant | |
| WO2012/068078(A2) | 2012-05-01 | Applicant | |
| WO2012/098556(A1) | 2012-07-01 | Applicant | |
| WO2012/142370(A2) | 2012-10-01 | Applicant | |
| WO2012/167941(A1) | 2012-12-01 | Applicant | |
| WO2013/048538(A1) | 2013-04-01 | Applicant | |
| WO2013/056104(A1) | 2013-04-01 | Applicant | |
| WO2013/119914(A1) | 2013-08-01 | Applicant | |
| WO2013/179271(A2) | 2013-12-01 | Applicant |
Non-Patent Literature (40)
- “Google Checkout XML API Developer's Guide”; 2008; 73 pages.Applicant
- “Google Checkout HTML API Developer's Guide”; 2008; 46 pages.Applicant
- PayPal™; Developer Central: Custom Integration with Express Checkout; 2008; 3 pages.Applicant
- PayPal™; “Website Payments Standard Integration Guide”; Jan. 2008; 194 pages.Applicant
- PayPal™; Express Checkout Integration Guide; Feb. 2008; 70 pages.Applicant
- PayPal™; Name-Value Pair API Developer Guide and Reference; Feb. 2008; 227 pages.Applicant
- U.S. Appl. No. 12/143,509, filed Jun. 20, 2008.Applicant
- International Search Report dated Dec. 31, 2008, for PCT Patent Application No. PCT/US2008/068003, 2 pages.Applicant
- Written Opinion of the International Searching Authority dated Dec. 31, 2008, for PCT Patent Application No. PCT/US2008/068003, 5 pages.Applicant
- International Search Report and Written Opinion dated Jan. 9, 2009 for PCT Application No. PCT/US2008/068040, 10 pages.Applicant
- International Preliminary Report on Patentability dated Jan. 5, 2010 for PCT Application No. PCT/US2008/068040, 7 pages.Applicant
- International Search Report of the International Searching Authority for Application No. PCT/US2009/063067, dated May 26, 2010, 10 pages.Applicant
- Written Opinion of the International Searching Authority for Application No. PCT/US2009/063067, dated May 26, 2010, 4 pages.Applicant
- Extended European Search Report dated May 10, 2011, for EP Patent Application No. 0877180.2, 10 pages.Applicant
- Extended European Search Report dated May 11, 2011, for EP Patent Application No. 08771833.4, 4 pages.Applicant
- European Communication dated Jan. 27, 2012, for EP Patent Application No. 08771833.4, 11 pages.Applicant
- European Communication dated Apr. 25, 2012, for EP Patent Application No. 08771810.2, 10 pages.Applicant
- Australian Office Action dated May 4, 2012, for AU Patent Application No. 2008268419, 3 pages.Applicant
- Australian Office Action dated May 11, 2012, for AU Patent Application No. 2008268411, 3 pages.Applicant
- Office Action dated Oct. 16, 2012 for European Patent Application No. 08771833.4, 9 pages.Applicant
- Non-Final Office Action dated Oct. 18, 2012 for U.S. Appl. No. 13/355,270 13 pages.Applicant
- Non-Final Office Action dated Dec. 12, 2012 for U.S. Appl. No. 13/358,475 13 pages.Applicant
- Supplementary European Search Report dated May 10, 2011 for European Patent Application No. EP08771810.2, 10 pages.Applicant
- Office Action dated Dec. 12, 2012 for Australian Patent Application No. 2008268411, 2 pages.Applicant
- Office Action dated Mar. 12, 2013 for Australian Patent Application No. 2008268419, 4 pages.Applicant
- Final Office Action dated Mar. 27, 2013 for U.S. Appl. No. 13/355,270, 8 pages.Applicant
- Final Office Action dated Apr. 29, 2013 for U.S. Appl. No. 13/358,475, 6 pages.Applicant
- Notice of Allowance dated Jul. 12, 2013 for U.S. Appl. No. 13/355,270, 8 pages.Applicant
- Notice of Allowance dated Aug. 9, 2013 for U.S. Appl. No. 13/358,475, 9 pages.Applicant
- Notice of Grant dated Sep. 19, 2013 for Australian Patent Application No. 2008268419, 2 pages.Applicant
- Notice of Grant dated Oct. 3, 2013 for Australian Patent Application No. 2008268411, 2 pages.Applicant
- Notice of Allowance dated Dec. 6, 2013 for U.S. Appl. No. 14/049,873, 11 pages.Applicant
- Australian Office Action dated Jul. 14, 2014 for AU Patent Application No. 2009311303, 4 pages.Applicant
- Non-final Office Action of U.S. Appl. No. 14/260,169 dated Nov. 3, 2014, 8 pages.Applicant
- First Office Action and Examination Search Report, dated Dec. 2, 2014, in Canadian Application No. 2,692,276, 3 pages.Applicant
- Office Action for Australian Patent Application 2009311303, dated Feb. 10, 2015, 4 pages.Applicant
- Office Action for Canadian Patent Application 2,692,275, dated Jan. 27, 2015, 4 pages.Applicant
- Final Office Action, dated Apr. 21, 2015, for U.S. Appl. No. 14/260,169, filed Apr. 23, 2014, 26 pages.Applicant
- Non-Final Office Action, dated Oct. 23, 2015, for U.S. Appl. No. 13/358,472, filed Jan. 25, 2012, 12 pages.Applicant
- Non-Final Office Action, dated Sep. 4, 2015, for U.S. Appl. No. 14/260,169, filed Apr. 23, 2014, 5 pages.Applicant