Secure remote token release with online authentication

Description

BACKGROUND

With the ever growing number of online or computer accessible accounts that a user may have, usernames and passwords as a form of authentication has become inadequate for securing a user's accounts. For example, remembering usernames and passwords for numerous sites can be challenging, and setting the same password for multiple accounts may increase the likelihood of jeopardizing all accounts when one account is compromised. Password managers can be inconvenient, and storing all of the user's passwords in one place can be risky. Passwords can also be easily phished or captured by malware, and data breaches at service providers can result in the proliferation of passwords across the dark web.

Furthermore, while authorization entities are able to determine whether or not to authorize a transaction based on information for an account, those same authorization entities are not able to authenticate a user of a user device. Hence, they must often rely on another entity, such as the resource provider, to perform authentication of a user. Not all resource providers can provide the same quality of authentication, and this leads to data security problems.

Another issue to be addressed in the area of data security that needs to be addressed, if the problem of transmitting sensitive credentials (e.g., social security numbers, account numbers, etc.) over data networks. The transmission of such data may be subject to man-in-the middle attacks.

Various embodiments of the invention address these and other problems, individually and collectively.

SUMMARY

A system and techniques for authenticating a user while ensuring that the authentication was performed by a legitimate device is described herein. The authentication technique may include registering a user's authentication data such as biometrics data with a communication device. The authentication data can be linked to an account or service provider, and is used to verify the identity of the user when accessing the account. The communication device may be associated with a public/private key pair, where the pubic key is stored on a secure remote server. When the user attempts to access the account or service provider, the user may provide the authentication data to authenticate the user to the communication device. Thereafter, the communication device may sign an authentication indicator using the private key and send the authentication indicator to the secure remote server. Upon verification of the signature using the public key, the secure remote server may grant access to the user, for example, by releasing a token.

One embodiment of the disclosure is directed to a method performed by a secure remote transaction server comprising receiving, from a client device, a request to enroll an account, verifying that the client device has authority to access the account, storing at least a public key of a cryptographic key pair in association with the account, wherein at least a private key of the cryptographic key pair is stored on the client device in association with the account, and generating a token to be associated with the account, the token being stored in association with the account. In some embodiments, the method may further comprise receiving, from an access device, a request to complete a transaction in association with the account, the request including a signed authentication indicator, verifying the authentication indicator using the public key stored in association with the account, and upon verifying the authentication indicator, providing the token to the access device.

Another embodiment of the disclosure is directed to a secure remote transaction server comprising a processor, and a memory including instructions that, when executed with the processor, cause the secure remote transaction server to, at least receive, from a client device, a request to enroll an account, verify that the client device has authority to access the account, store at least a public key of a cryptographic key pair in association with the account, wherein at least a private key of the cryptographic key pair is stored on the client device in association with the account, and generate a token to be associated with the account, the token being stored in association with the account. In some embodiments, the instructions may further cause the secure remote transaction server to receive, from an access device, a request to complete a transaction in association with the account, the request including a signed authentication indicator, verify the authentication indicator using the public key stored in association with the account, and upon verifying the authentication indicator, provide the token to the access device.

Yet another embodiment of the disclosure is directed to a method performed by a communication device comprising receiving a request to register authentication data for an account associated with a service provider, prompting the user to provide the authentication data, receiving the authentication data from the user, registering the authentication data onto the communication device, obtaining a private key of a cryptographic key pair, associating the private key with the account and the authentication data, wherein a secure remote server links a public key of the cryptographic key pair to a token associated with the account.

In some embodiments, the method described above may further comprise receiving a request to access the account, prompting the user to provide the authentication data, receiving the authentication data from the user, comparing the received authentication data with the registered authentication data, determining that the received authentication data matches the registered authentication data, generating an authentication indicator indicating the match, signing the authentication indicator using the private key, and sending the signed authentication indicator to the secure remote server in an access request, wherein the secure remote server releases the token to the service provider to grant the user access to the account in response to verifying the signed authentication indicator using the public key.

Further details regarding embodiments of the invention can be found in the Detailed Description and the Figures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a number of components that may be involved in a system used to implement at least some embodiments of the disclosure;

FIG. 2 depicts an example system architecture that may be implemented to provide secure remote transaction in accordance with embodiments of the disclosure;

FIG. 3 illustrates a registration process for an authentication system, according to some embodiments;

FIG. 4 depicts an example provisioning process by which a user is able to manually add his or her accounts to be processed by the SRT platform and a private key and/or token may be provisioned onto a client device in accordance with some embodiments;

FIG. 5 illustrates a process for authenticating the user with a service provider using the authentication system, according to some embodiments;

FIG. 6 illustrates a process for authenticating the user with a service provider using multiple devices, according to some embodiments;

FIG. 7 illustrates a flow diagram of a process for performing authentication of users in accordance with at least some embodiments;

FIG. 8 illustrates a flow diagram of a process for registering authentication data in accordance with at least some embodiments; and

FIG. 9 illustrates a flow diagram of a process for accessing an account, according to some embodiments.

DETAILED DESCRIPTION

Techniques for enhanced authentication without relying on the use of passwords are described. In some embodiments, a two-factor authentication scheme can be employed in which biometrics is used to authenticate a user on a communication device, and public/private key cryptography is used to authenticate the communication device to a remote server to grant the user access to an account, service, and/or function associated with a service provider. In some embodiments, the service provider can be a token service provider, and the two-factor authentication scheme is used by the system to release a token from the remote server. The token can then be used, for example, to conduct a transaction using the user's account. Various embodiments described herein may be implemented on a secure remote transaction (SRT) platform. An example of an SRT platform upon which embodiments may be implemented is described in greater detail in U.S. patent application Ser. No. 15/927,754, filed on Mar. 21, 2018, which is fully incorporated by reference herein.

Prior to discussing specific embodiments of the invention, some terms may be described in detail.

An “access device” may be any suitable device for communicating with a merchant computer or transaction processing network, and for interacting with a transaction device (e.g., a payment device), a user computer apparatus, and/or a user client device. An access device may generally be located in any suitable location, such as at the location of a merchant. An access device may be in any suitable form. Some examples of access devices include POS devices, cellular phones, PDAs, personal computers (PCs), tablet PCs, hand-held specialized readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, Websites, and the like. An access device may use any suitable contact or contactless mode of operation to send or receive data from, or associated with, a portable communication device. In some embodiments, where an access device may comprise a POS terminal, any suitable POS terminal may be used and may include a reader, a processor, and a computer-readable medium. A reader may include any suitable contact or contactless mode of operation. For example, exemplary card readers can include radio frequency (RF) antennas, optical scanners, bar code readers, or magnetic stripe readers to interact with a portable communication device.

“Account credentials” may include any suitable information associated with an account (e.g. an account and/or portable device associated with the account). Such information may be directly related to the account or may be derived from information related to the account. Examples of account credentials may include a PAN (primary account number or “account number”), user name, expiration date, CVV (card verification value), dCVV (dynamic card verification value), CVV2 (card verification value 2), CVC3 card verification values, etc.

An “acquirer” may typically be a business entity (e.g., a commercial bank) that has a business relationship with a particular merchant or other entity. Some entities can perform both issuer and acquirer functions. Some embodiments may encompass such single entity issuer-acquirers.

“Authentication” or “authenticating” may be the process of proving or verifying certain information, and/or verifying the identity of the source of that information. For example, a user may provide authentication data that is unique or only known to the user to prove the identity of the user. Examples of different types of authentication data may include biometrics (e.g., fingerprint, palm print, face recognition, iris and/or retina recognition, voice recognition, gait, or other human characteristics), passcode, PIN, answers to security question(s), cryptographic response to challenge, human and/or device signature, etc.

An “authorization entity” may be an entity that authorizes a request. Examples of an authorization entity may be an issuer, a governmental agency, a document repository, an access administrator, etc. An “issuer” may typically refer to a business entity (e.g., a bank) that maintains an account for a user that is associated with a client device such as an account enrolled in a mobile application installed on a client device. An authorization entity may also issue account parameters associated with the account to a client device. An authorization entity may be associated with a host system that performs some or all of the functions of the issuer on behalf of the authorization entity.

An “authorization request message” may be an electronic message that is sent to request authorization for a transaction. The authorization request message can be sent to a transaction processing network and/or an issuer of a transaction card (e.g., a payment card). An authorization request message according to some embodiments may comply with ISO 8583, which is a standard for systems that exchange electronic transaction information associated with a transaction made by a user using a transaction device or transaction account. The authorization request message may include information that can be used to identify an account. An authorization request message may also comprise additional data elements such as one or more of a service code, an expiration date, etc. An authorization request message may also comprise transaction information, such as any information associated with a current transaction, such as the transaction amount, merchant identifier, merchant location, etc., as well as any other information that may be utilized in determining whether to identify and/or authorize a transaction. The authorization request message may also include other information such as information that identifies the access device that generated the authorization request message, information about the location of the access device, etc.

An “authorization response message” may be an electronic message reply to an authorization request message. The authorization response message can be generated by an issuing financial institution or a transaction processing network. The authorization response message may include, by way of example only, one or more of the following status indicators: Approval—transaction was approved; Decline—transaction was not approved; or Call Center—response pending more information, merchant must call the toll-free authorization phone number. The authorization response message may also include an authorization code, which may be a code that a credit card issuing bank returns in response to an authorization request message in an electronic message (either directly or through the transaction processing network) to the merchant computer that indicates approval of the transaction. The code may serve as proof of authorization. As noted above, in some embodiments, a transaction processing network may generate or forward the authorization response message to the merchant.

A “communication device” may be a device that includes one or more electronic components (e.g., an integrated chip) that can communicate with another device or entity. For example, a communication device can be a computing device that includes at least one processor coupled to a memory that stores instructions or code for execution by the processor, and may include a communication interface that allows the communication device to interact with other entities. A communication device can be a portable communication device that can be transported and operated by a user, and may include one or more electronic components (e.g., an integrated chip). A portable communication device may provide remote communication capabilities to a network. The portable communication device can be configured to transmit and receive data or communications to and from other devices. A portable communication device may be in the form of a client device such as a mobile phone (e.g., smart phone, cellular phone, etc.), tablets, portable media player, personal digital assistant devices (PDAs), wearable device (e.g., watch, health monitoring device such as a fitness tracker, etc.), electronic reader device, etc., or in the form of a card (e.g., smart card) or a fob, etc. Examples of portable communication devices may also include portable computing devices (e.g., laptops, netbooks, ultrabooks, etc.). A portable communication device may also be in the form of a vehicle (e.g., an automobile), or be integrated as part of a vehicle (e.g., an infosystem of a vehicle). Other examples of communication device may include IOT devices, smart appliances and electronics, etc.

A “facilitator” may be any entity capable of authenticating a user of a client device. A facilitator may include a client-side application (e.g., a facilitator application) as well as a backend server (e.g., a facilitator server) capable of supporting the client-side application. In some cases, a facilitator application may be executed upon receiving instructions from a facilitator server to authenticate a user of the client device. The facilitator application may cause the client device upon which it is installed to obtain user-specific data. This user-specific data may then be compared to expected user-specific data, either by the facilitator application on the client device or by the facilitator server, to determine whether the obtained user-specific data matches the expected user-specific data. In some embodiments, a facilitator may be an electronic wallet provider (e.g., Apple Pay). It should be noted that the facilitator may be unaffiliated with the SRT Platform and/or the initiator.

An “initiator” may be any entity capable of facilitating communication between a resource provider and one or more SRT platforms. An initiator may operate a number of servers which provide at least a portion of the functionality described herein. In some cases, an initiator may obtain approval and/or accreditation from one or more SRT platforms in order to operate in conjunction with those SRT platforms. A resource provider may enroll with the initiator in order to obtain access to at least a portion of the processes described herein. An initiator may provide each resource provider that enrolls with it a link to embed within a checkout element. The link, when activated by a user wishing to transact with the resource provider, may initiate the processes described herein in order to facilitate a transaction between the user and the resource provider. It should be noted that the initiator may be unaffiliated with the SRT Platform and/or the facilitator.

An “issuer” may typically refer to a business entity (e.g., a bank) that maintains an account for a user that is associated with a portable communication device such as an account enrolled in a mobile application installed on a portable communication device. An issuer may also issue account parameters associated with the account to a portable communication device. An issuer may be associated with a host system that performs some or all of the functions of the issuer on behalf of the issuer.

A “key” may refer to a piece of information that is used in a cryptographic algorithm to transform input data into another representation. A cryptographic algorithm can be an encryption algorithm that transforms original data into an alternate representation, or a decryption algorithm that transforms encrypted information back to the original data. Examples of cryptographic algorithms may include triple data encryption standard (TDES), data encryption standard (DES), advanced encryption standard (AES), etc.

A “merchant” may typically be an entity that engages in transactions and can sell goods or services, or provide access to goods or services.

A “real account identifier” may refer to an original account identifier associated with an account. For example, a real account identifier may be a primary account number (PAN) issued by an issuer for a card account (e.g., credit card, debit card, etc.). For instance, in some embodiments, a real account identifier may include a sixteen digit numerical value such as “4147 0900 0000 1234.” The first six digits of the real account identifier (e.g., “414709”), may represent a real issuer identifier (BIN) that may identify an issuer associated with the real account identifier.

The term “resource” generally refers to any asset that may be used or consumed. For example, the resource may be computer resource (e.g., stored data or a networked computer account), a physical resource (e.g., a tangible object or a physical location), or other electronic resource or communication between computers (e.g., a communication signal corresponding to an account for performing a transaction). Some non-limiting examples of a resource may be a good or service, a physical building, a computer account or file, or a payment account. In some embodiments, a resource may refer to a financial product, such as a loan or line of credit.

A “resource provider” may be an entity that can provide a resource such as goods, services, information, and/or access to such a resource. Examples of a resource provider include merchants, online or other electronic retailers, access devices, secure data access points, etc. A “merchant” may typically be an entity that engages in transactions and can sell goods or services, or provide access to goods or services. A “resource provider computer” may be any computing device operated by a resource provider.

A “secure remote transaction (SRT) platform” may be any entity capable of facilitating a transaction in the manners described. A SRT platform may be capable of communicating with an initiator, a facilitator, and a transaction processing network. In some embodiments, a SRT platform may include a SRT server, a token provider, and a transaction processing network. An SRT platform may be configured to perform one or more processes that include: receive a request for a transaction from an initiator, identify an account associated with the transaction, determine an appropriate facilitator for the account, cause the determined facilitator to authenticate a user associated with the account, generate a token to be used in the transaction, and provide the token to the initiator to complete the transaction.

A “server computer” may include a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a Web server. The server computer may be coupled to a database and may include any hardware, software, other logic, or combination of the preceding for servicing the requests from one or more client computers. The server computer may comprise one or more computational apparatuses and may use any of a variety of computing structures, arrangements, and compilations for servicing the requests from one or more client computers.

A “token” may refer to a substitute identifier for some information. For example, a transaction token may include an identifier for a transaction account that is a substitute for an account identifier, such as a primary account number (PAN). For instance, a token may include a series of alphanumeric characters that may be used as a substitute for an original account identifier. For example, a token “4900 0000 0000 0001” may be used in place of a PAN “4147 0900 0000 1234.” In some embodiments, a token may be “format preserving” and may have a numeric format that conforms to the account identifiers used in existing transaction processing networks (e.g., ISO 8583 financial transaction message format). In some embodiments, a token may be a random string of characters. In some embodiments, a token may be used in place of a PAN to initiate, authorize, settle or resolve a transaction. The token may also be used to represent the original credential in other systems where the original credential would typically be provided. In some embodiments, a token value may be generated such that the recovery of the original PAN or other account identifier from the token value may not be computationally derived. Further, in some embodiments, the token format may be configured to allow the entity receiving the token to identify it as a token and recognize the entity that issued the token.

“Tokenization” may refer to a process by which data is replaced with substitute data. For example, an account identifier (e.g., a primary account number (PAN)) may be tokenized by replacing the account identifier with a substitute number (e.g., a token) that is associated with the account identifier. Further, tokenization may be applied to other information which may be replaced with a substitute value. Tokenization may be used to enhance transaction efficiency, improve transaction security, increase service transparency, or to provide a method for third-party enablement.

A “token service provider” may refer to an entity including one or more server computers that generates, processes, and/or maintains tokens. A token service provider may include or be in communication with a token vault where the generated tokens are stored. Specifically, the token vault may maintain one-to-one mapping between a token and the data (e.g., a real account identifier) represented by the token. A token service provider may provide reports or data output to reporting tools regarding approved, pending, and/or declined token requests. The token service provider may provide data output related to token-based transactions to reporting tools and applications and present the token and/or the data substituted by the token (e.g., real account identifiers) as appropriate in the reporting output.

A “token vault” may refer to a repository that maintains established token-to-PAN mappings. According to various embodiments, the token vault may also maintain other attributes of the token requestor that may be determined at the time of registration and that may be used by the token SRT server to apply domain restrictions or other controls during transaction processing. The token vault may be a part of the token service system. In some embodiments, the token vault may be provided as a part of the token SRT server. Alternatively, the token vault may be a remote repository accessible by the token SRT server. Token vaults, due to the sensitive nature of the data mappings that are stored and managed in them, may be protected by strong underlying physical and logical security.

A “transaction” may be any interaction or exchange between two or more parties. For example, a transaction may include a first entity requesting resources from a second entity. In this example, the transaction is completed when the resources are either provided to the first entity or the transaction is declined.

A “transaction processing network,” or “processing network,” may refer to an electronic payment system used to accept, transmit, or process transactions made by payment devices for money, goods, or services. The processing network may transfer information and funds among authorization entities (e.g., issuers), acquirers, merchants, and payment device users.

FIG. 1 depicts a number of components that may be involved in a system used to implement at least some embodiments of the disclosure. In FIG. 1, a client device 102 may be in communication with a number of remote entities via a network connection (either wireless or physical). For example, the client device 102 may be used to access a website maintained by a resource provider server 104 or an authorization entity server 106 (e.g., via a browser application). In this example, the website may have embedded a checkout element configured to cause the client device 102 to initiate communication with a initiator server 108. The initiator server 108 may, in turn, be in communication with a secure remote transaction (SRT) platform 110.

In some embodiments, the client device 102 may have installed on it a number of facilitator applications 112. The facilitator applications may be configured to cause the client device 102 to communicate with a number of facilitator application servers 114 in order to authenticate a user of the client device 102. In some embodiments, the client device 102 may store, in its memory, one or more cryptographic keys to be associated with facilitators installed on the client device 102 and/or the client device 102 itself.

In some embodiments of the invention, the client device 102 may be a mobile device (e.g. a mobile phone). The mobile device may be capable of communicating with cell towers (e.g., via cellular communications such as GSM, LTE, 4G) and wireless routers (e.g., via WiFi). The mobile device may store the user's account credentials, such as a PAN (primary account number), a token, a name, an address, a CVV, an expiration date, and any other suitable information. The mobile device may also store one or more private cryptographic keys associated with the mobile device itself or applications installed upon the mobile device. Such data may be securely stored via hardware (e.g., a secure element) or software.

In some embodiments, the resource provider server 104 may be affiliated with an online retailer or another suitable resource provider having an electronic catalog. The resource provider server 104 may serve one or more pages of a resource provider website to a browser installed on the client device 102. In some embodiments, the website served to the browser application may contain a portal or link that, when accessed using the browser application, initiates communication with the initiator server 108.

In some embodiments of the invention, the authorization entity server 106 may be any computing device configured to determine whether or not to approve a transaction to be conducted by a particular user. The authorization entity server 106 may maintain a number of accounts, one or more of which are associated with particular users. Each account may be associated with some amount of a resource (e.g., a balance) upon which authorization for a transaction may be based. However, while an authorization entity server 106 may be capable of determining whether or not to authorize a transaction for a user, the authorization entity server 106 may not be capable of authenticating a user as it is located remote to that user. Hence, the authorization entity server 106 may be configured to use embodiments of the system described herein to authenticate a user. In some embodiments, upon successful enrollment of a user into the system described herein, the authorization entity server 106 may generate a token to be associated with the user and may provide the token to the SRT platform 110 to be bound to a client device 102 along with a pair of cryptographic keys.

The initiator server 108 may be any suitable computing device configured to identify a user, identify accounts for that user, receive a selection of one of those accounts, communicate the selected account to an SRT platform 110 associated with that account, and complete a transaction using the selected account. In some embodiments, the initiator server 108 may be further configured to verify signed data received from the client device 102. For example, the initiator server may, upon receiving data from the client device 102, verify that data using a public cryptographic key associated with the client device 102 or an application installed upon the client device 102.

In some embodiments, the system may be implemented across one or more SRT platforms 110. The SRT platforms may each be associated with a transaction processing network. Each SRT platform may include some combination of an SRT server (or servers) 110(A), token data 110(B), and a processing network 110(C). Multiple accounts may be associated with a single SRT platform. For example, a user may be associated with two different accounts which are each associated with different authentication entities, while both accounts are able to be processed using a single SRT platform. The SRT server 110(A), may be configured to identify one or more facilitator applications 112 associated with an account and cause the user to be authenticated using one of those facilitator applications 112. This may involve communicating a request for authentication to a facilitator application server 114 associated with a particular facilitator application 112.

Additionally, once the user has been authenticated, either the client device 102 or the SRT server 110(A) may be configured to generate cryptographic keys and/or a token to be bound (or otherwise associated) with a particular client device 102 which is stored in the respective token data 110(B) so that data received from that client device 102 may be verified using a stored public key. The token and cryptographic keys may be bound to the client device 102 upon receiving an indication that the client device 102 has been verified by an authorization entity server 106. In some embodiments, the SRT server 110(A) may pass a public key associated with the client device 102 to the initiator server 208, which may verify data received from the client device 102 and generate transaction information that includes the token to be used for a transaction. A mapping between the token and the transaction may be maintained by the SRT server 110(A) in its respective token data. In some embodiments, the SRT server 110(A) may receive a number of files from various authorization entities, each of which may include mappings between email addresses and various PANs. In this way, the SRT server 110(A) may maintain a mapping between user identifier information and accounts.

The facilitator applications 112 may be any suitable set of computer-executable instructions installed on the client device 102 that, when executed, causes the client device 102 to perform an authentication process. In some embodiments, the authentication process may involve the collection of biometric information associated with a user of the client device 102. For example, the facilitator application 112 may obtain voiceprint or fingerprint data to be used to authenticate the user. The facilitator application may be tied to hardware installed on the client device 102. Examples of facilitator applications 112 may include fingerprint, retinal, or voice scanning applications. The hardware associated with those applications may include fingerprint, retinal, or voice scanning hardware such as fingerprint, retinal, or voice sensors. Other types of facilitator applications 112 may also include PIN and password facilitator applications. In some embodiments, a facilitator application 112 may be a wallet SRT server.

The facilitator application server 114 may be any suitable computing device that provides support for a facilitator application 112. In some embodiments, the facilitator application server 114 may perform authentication processing on behalf of the facilitator application 112. For example, the facilitator application 112 may cause the client device 102 to obtain authentication data from a user of the client device 102. Once obtained, the authentication data may be transmitted to the facilitator application server 114 that corresponds to the facilitator application used to collect the authentication data. The authentication data may then be compared to authentication data on record for that user by the facilitator application server 114. Once a user has been authenticated, the facilitator application server 114 and/or facilitator application 112 may generate an authentication result indicating that the user has been authenticated. The client device 102 may sign the received the authentication result using a private key specific to the client device 102 and stored by the client device 102.

For an illustrative example of at least some embodiments of the disclosure, consider a scenario in which a user wishes to enroll into the system described herein and conduct a transaction. In this scenario, the user may request enrollment with a particular authorization entity server 106. The request may be made in relation to a particular account maintained by that authorization entity server 106 (e.g., a credit card account maintained by a banking institution). The authorization entity server 106 may reference account data stored in association with the particular account in order to identify contact information. Once identified, the authorization entity server 106 may transmit a verification message to the user via the stored contact information. In some embodiments, the verification message may include a one-time password (OTP) or other dynamic verification data, which the user may be required to enter via the client device 102 to be verified. Once verified, the authorization entity server 106 may provide an indication of the client device 102 to the SRT platform 110. A token and cryptographic keys may be generated for the client device 102 either by the authorization entity server 106, the client device 102, or the SRT platform 110. Once generated, the token and at least a private cryptographic key of a cryptographic key pair may be transmitted to the client device 102.

Once the client device 102 has been enrolled using the illustrative scenario above, the user may access a merchant (resource provider 104) website to complete a transaction (e.g., make a purchase). In this scenario, the user may, upon selecting a number of items for the transaction, be served a checkout page for the merchant website. The checkout page may include a list of the items, prices, quantities, or any other suitable transaction-related information. In addition, the checkout page may include a checkout element that may be selected to initiate a transaction. Once the checkout element has been selected, the user may be given the ability to select an account associated with the authorization entity server 106 to be used to complete the transaction.

Upon receiving a selection of account associated with the authorization entity server 106 to be used to complete the transaction, the SRT platform 110 may cause a facilitator application 112 to be executed in order to authenticate the user. The facilitator application 112 may then execute an authentication process and, upon completion of the authentication process, may return an authentication indicator that indicates whether or not the user is authenticated to the client device 102. In this scenario, the client device 102 may then sign the authentication indicator by performing a cryptographic algorithm on the authentication indicator using the private cryptographic key of the cryptographic key pair. The signed authentication indicator may be provided to the SRT platform 110 via the initiator application server 108.

Upon verifying the authentication indicator and confirming that the user is authenticated, the SRT platform 110 may provide the token associated with the clinet device 102 back to the initiator application server 108. The initiator server 108 may subsequently use the received token to complete the requested transaction.

For clarity, a certain number of components are shown in FIG. 1. It is understood, however, that embodiments of the invention may include more than one of each component. In addition, some embodiments of the invention may include fewer than or greater than all of the components shown in FIG. 1. In addition, the components in FIG. 1 may communicate via any suitable communication medium (including the internet), using any suitable communication protocol.

FIG. 2 depicts an example system architecture that may be implemented to provide secure remote transaction in accordance with embodiments of the disclosure. In FIG. 2, a SRT server 202 may be in communication with a number of client devices 204 and authorization entity servers 206 via a network connection 208. The network connection 208 may include at least a transaction processing network. In some embodiments, the SRT server 202 may be an example SRT server 110 of FIG. 1.

In at least some embodiments, the SRT server 202 may include at least one memory 214 and one or more processing units (or processor(s)) 216. The processor(s) 216 may be implemented as appropriate in hardware, computer-executable instructions, firmware or combinations thereof. Computer-executable instruction or firmware embodiments of the processor(s) 216 may include computer-executable or machine executable instructions written in any suitable programming language to perform the various functions described.

The memory 214 may store program instructions that are loadable and executable on the processor(s) 216, as well as data generated during the execution of these programs. Depending on the configuration and type of SRT server 202, the memory 214 may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.). The SRT server 202 may also include additional storage 218, such as either removable storage or non-removable storage including, but not limited to, magnetic storage, optical disks, and/or tape storage. The disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the SRT server 202. In some embodiments, the memory 214 may include multiple different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM) or ROM.

Turning to the contents of the memory 214 in more detail, the memory 214 may include an operating system and one or more application programs or services for implementing the features disclosed herein including at least a module for binding accounts to tokens and/or cryptographic keys (account binding module 220). The memory 214 may also include account data 222, which provides data stored in association with a user account, cryptographic ley data 224, which provides at least a list of public cryptographic keys stored in association with client devices 204, and/or token data 220, which provides a mapping between a generated token and a transaction or account.

In some embodiments, the account binding module 220 may, in conjunction with the processor 216, be configured to receive an indication from an authorization entity server 206 that a client device 204 is to be enrolled with respect to a particular account. In some embodiments, the indication may include a device identifier for the client device 204 (e.g., a phone number) as well as an account number (e.g., a primary account number (PAN)). In some embodiments, upon receiving the indication, the account binding module 220 may generate a token to be associated with the client device 204. The token may be stored by the SRT server 202 within a token vault (e.g., token data 226) in relation to the client device 204. Additionally, the account binding module 220 may generate a cryptographic key pair to be associated with the client device 204 and the account number. One of the keys of the cryptographic key pair may be assigned as a private key 234 and the other may be assigned as a public key 238. The cryptographic key assigned as the private key 234 may be conveyed to the client device 204 using known secure key delivery protocols. In some embodiments, the private key 234 may be provisioned onto the client device 204 via a message transmitted to the client device 204 by the SRT server 202 (e.g., via the received device identifier). In some embodiments, the private key 234 may be provisioned onto the client device 204 via a message transmitted to the client device 204 by the authorization entity server 206. In some embodiments, the public key 238 may be transmitted to the authorization entity server 206. In some embodiments, the account binding module 220 may be configured to verify the authenticity of an authentication indicator which has been signed by a client device 204 using the private key 234.

In some embodiments, the account binding module 220 may be further configured to generate a token upon receiving an indication that an authentication indicator received from a client device 204 has been verified. In some embodiments, the token may be a one-time use token which is only authorized for use with the specific transaction at issue. In some embodiments, the token may be specific to both the client device 204 and the resource provider, in that the token may be used multiple times by the resource provider for that client device 204 (e.g., a “card on file” token). For example, upon conducting with a particular client device 204 for the first time, the resource provider may receive a token generated in the manner described herein. The resource provider may then store the token in memory for use with the client device 204 until an expiration date (or some other suitable expiration condition) associated with that token. The account mapping module 220 may store the generated token in a token vault (e.g., token data 226) with a mapping to the account for which the token was generated. Upon receiving an authorization request message that includes the token, the SRT server 202 may query the token vault to identify the account associated with the token. The SRT server 202 may then proceed with the transaction of the authorization request message using the identified account information.

The SRT server 202 may also contain communications interface(s) 228 that enable the SRT server 202 to communicate with a stored database, another computing device or server, one or more remote devices, other application servers, and/or any other suitable electronic devices. In some embodiments, the communication interface 228 may enable the SRT server 202 to communicate with other electronic devices on a network (e.g., on a private network). The SRT server 202 may also include input/output (I/O) device(s) and/or ports 230, such as for enabling connection with a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, speakers, a printer, etc.

The client device 204 may be any electronic device capable of communicating with other electronic devices. For example, the client device 204 may be a mobile phone capable of wirelessly communicating with a number of other electronic devices. In some embodiments, the client device 204 may be an example of client device 102 depicted in FIG. 1. The client device 204 may have installed upon it a number of software modules, including an authentication application 231 and at least one facilitator application 232. In some embodiments, the client device may also include, in its memory, at least one private key 234. In some embodiments, the authentication application 231 may include computer executable instructions that cause the client device 204 to perform at least a portion of the functionality described herein. For example, in some embodiments, the authentication application 231 of the client device 204 may be configured to generate the private key 234 (and the related public key 238) in response to verifying that received authentication data.

In some embodiments, the facilitator application 232 may be a mobile application installed upon, and executed from, the client device 204. In accordance with at least some embodiments, the facilitator application 232 may be configured to authenticate the user and generate an authentication indicator that indicates whether or not the user is authenticated. The authentication application 231 of the client device 204 may then be configured to sign the authentication indicator by performing a cryptographic algorithm on the authentication indicator using the private cryptographic key 234 which has been provided to the client device by the account binding module 220 as described above. It should be noted that there are a number of techniques for signing data in this manner that would be known to one skilled in the art. In some embodiments, the client device 204 may store a token generated by the account binding module 220 described above. However, it should be noted that the client device need not be provided the token in at least some embodiments.

In some embodiments, the authorization entity 206 may be an example of authorization entity server 106 depicted in FIG. 1, which may be configured to determine whether a particular transaction should be authorized. The authorization entity 206 may maintain a number of accounts, at least one of which may be associated with a client device 204. In some embodiments, the authorization entity 206 may maintain a number of tokens 236 which are mapped to accounts that are maintained by the authorization entity. In some embodiments, the authorization entity 206 may maintain one or more public keys 238 associated with particular client devices 204. It should be noted that in some embodiments, the authorization entity 206 may not store token data 236 or public keys 238 (e.g., the data may be stored on the SRT server 202).

FIG. 3 illustrates a registration process for an authentication system 300, according to some embodiments. Authentication system 300 may include a communication device operated by a user such as client device 310, and a secure remote server 320. In some embodiments in which system 300 is used to authenticate a user to conduct transactions, system 300 may also include an issuer 330 (an example of an authorization entity) associated with an account of the user. Client device 310 may have an authentication application installed therein. The authentication application can be, for example, downloaded from an application store or be pre-installed on client device 310. In some embodiments, the authentication application can be compatible with multiple service providers, and can be used to authenticate the user with different service providers. Secure remote server 320 may securely store credentials associated with a user's account, and can be configured to release the user's credentials upon successful authentication of client device 310 to secure remote server 320. In some embodiments, secure remote sever 320 can be associated with or be operated by a token service provider.

The registration process may begin by the user launching the authentication application on client device 310. The user may select a biometric facilitator to register with the authentication application. Examples of a biometric facilitator may include a facilitator application configured to cause the client device 310 to obtain fingerprint, retina scan, facial recognition, voice recognition, or other unique human characteristics that can be detected by client device 310. In some embodiments, the presence of a secondary device coupled or in proximity to client device 310 can be used as an alternative facilitator. The user may register multiple types of facilitators with the authentication application, and may only need to register each particular facilitator once. The registered facilitator(s) can then be selected for use to authenticate the user to one or more compatible service providers.

Next, the user may select a compatible service provider and configure which facilitator will be used to authenticate the user to the service provider. One or more facilitators can be selected for a particular service provider. In some embodiments, different facilitators or different combination of facilitators can be used for different service providers. When multiple facilitators are selected for a particular service provider, the user can be authenticated when all of the multiple facilitators are verified, or when one of the multiple facilitators is verified. In some embodiments, the facilitators can be prioritized such that a higher priority facilitator is requested first, and after a predetermined number of unsuccessful attempts, a lesser priority facilitator can be requested. In some embodiments, the user may also optionally register the phone number or other device identifier of client device 310 with the service provider.

Upon linking the selected facilitator(s) to a particular service provider, the authentication application may generate a public/private key pair and associate the public/private key pair with the service provider. The public key may then be sent to the secure remote server 320 associated with the service provider for storage. In some embodiments, the public key can also be optionally sent to an issuer 330, and issuer 330 may generate a one-time passcode (OTP) and send the OTP to client device 310 for verification. Client device 310 may send the OTP back to secure remote server 320 to verify that client device 320 is a valid device of the user, and issuer 330 and/or secure remote server 320 may then provision a token for the user's account, and associate the token with the selected facilitator(s) and public key. In some embodiments, the token is not required to be stored on client device 310. Instead, the token can be stored at secure remote server 320 and is released by secure remote server 320 upon authentication of the user and client device 310 to secure remote server 320. This may enhance the security of the system because the token is not resident on client device 310, and thus cannot be compromised by malware on client device 310.

In this example provisioning process, the user may provide an indication of one or more accounts with which he or she is associated to the SRT platform. In some embodiments, the SRT platform may identify and contact an authorization entity (e.g., an issuer) associated with the indicated account. For example, the SRT platform may identify an authorization entity associated with a particular account indicated by the user based on an indicator within the provided account information. The SRT server may, in turn, communicate with that authorization entity to verify the account. An authorization entity associated with the account may then verify that the user is associated with the account. An authentication process may then be performed as described herein.

In some embodiments, this process may involve requiring a user to provide at least one account number via an input field 402 at 404. The SRT platform may then determine, based on the account number provided, a transaction processing network and/or an authorization entity associated with the account. It should be noted that at least some account identifiers may include a banking identification number (BIN) that can be used to identify both the transaction processing network and the authorization entity as a portion of the account number. The SRT platform may then communicate with the identified authorization entity associated with the identified transaction processing network.

In some embodiments, the identified authorization entity associated with the identified transaction processing network may identify one or more communication channels associated with the user of the account. For example, the user may be associated with a particular communication channel upon opening an account with the authorization entity. The one or more communication channels, or at least an obfuscated version of those communication channels, may be presented to the user at 406 to enable the user to verify his or her ownership of the account via those communication channels. In some embodiments, multiple communication channels may be presented to the user for his or her selection. In some embodiments, a default communication channel may be selected over which to communicate with the user.

Once an appropriate communication channel has been identified, the authorization entity or the SRT platform may transmit verification details to the user via the identified communication channel. In some embodiments, the verification details may include a code or pin. The user may then be required to provide those verification details back at 408 in order to verify that the user at least has access to the communication channel.

In some embodiments, once a user has been verified as being an owner of the account using the techniques depicted in FIG. 4, a private cryptographic key may be provisioned onto the client device from which the process was initiated. The private cryptographic key may be generated by the SRT server and may be used by the client device to sign an authentication indicator in the future.

By way of illustrated example, as depicted in FIG. 4, a user may be prompted to enter an account to be linked to himself or herself at 404. In this example, the authorization entity, once contacted, may initiate a verification process. For example, the authorization entity may provide verification details (e.g., a one-time code) to a communication channel known to be associated with the user. To do this, the authorization entity may provide the user with a choice of communication channel to which the verification details will be transmitted at 406. The user may then be asked to retrieve the verification details in order to verify that the user is authentic at 408. If the verification details provided by the user match those sent via the selected communication channel, then the account may be verified as being associated with the user at 410 and a private key may be provisioned onto the client device. It should be noted that the verification process described herein may be separate from the authentication process described elsewhere. In some embodiments, even though the user has verified his or her ownership of an account in the manner depicted in FIG. 4, the user may still be authenticated using the other techniques described herein. Upon being authenticated using the techniques described herein, an authentication indicator generated as a result of that authentication may be signed using the provisioned private key.

FIG. 5 illustrates a process for authenticating the user with a service provider using the authentication system, according to some embodiments. When the user intends to access an account, service, or function associated with a service provider, the user may launch an application associated with the service provider on client device 510. The application can be the same authentication application that was used to register the user's facilitators, a dedicated application provided by or associated with the service provider (e.g., mobile wallet, mobile payment application, merchant application, etc.), or can be a web browser via which the user can access a web page or login page of the service provider. The application may determine one or more facilitators previously linked to the service provider that the user is attempting to access, and request the user to provide the one or more facilitators associated with the service provider. In some embodiments, the application may request the user to provide all of the facilitators if a combination of facilitators are used, or may request the facilitators according to a prioritized order. The user may then provide the facilitator to client device 510. Upon verifying that the facilitator(s) provided by the user match the previously registered facilitator(s), client device 510 may sign an authentication indicator using the private key linked to the user's account with the service provider.

An access request including the signed authentication indicator is then sent to secure remote server 520 to indicate to secure remote server 520 that the user has successfully been authenticated to client device 510. In some embodiments, the access request may include data representing the facilitator, or an indicator indicating which facilitator(s) were provided by the user. Secure remote server 520 may then verify the signature by using the stored public key linked to the user's account associated with the service provider. Upon verifying the signature, the secure remote server 520 may grant the user access to the service provider.

In embodiments in which the secure remote server 520 is associated with a token service provider, secure remote server 520 may release a token associated with the user's account to a merchant 540 to enable the user to conduct a transaction with merchant 540. In some embodiments, the access request may also include transaction details of the transaction, and secure remote server 520 may generate a transaction authentication verification value and provide the transaction authentication verification value with the token. For example, the transaction authentication verification value can be a cryptogram generated based on the transaction details and/or the token. Merchant 540 can then provide the token or the token together with the transaction authentication verification value in an authorization request message to request authorization for the transaction.

In some scenarios, the user may access the service provider using a different device than the communication device that was used for registering the user's facilitators. As such, the device that the user is using to access the service provider may not have the previously stored facilitators or sensor hardware necessary to authenticate the user. For example, the user may access a merchant's website using a desktop computer instead of the user's client device, and the desktop computer may not have a fingerprint reader or access to the user's previously stored fingerprint data to properly authenticate the user. In such scenarios, a cross-device authentication scheme can be employed.

FIG. 6 illustrates a process for authenticating the user with a service provider using multiple devices, according to some embodiments. When the user attempts to access a service provider from a different device, such as visiting the service provider's web site using a web browser on device 650 that does not have the previously stored facilitators, the user may enter a device identifier such as a phone number or an IP address associated with the communication device 610 that does have the device identifiers. Device 650 may then push an authentication request to communication device 610. In response, communication device 610 may request the user to provide the facilitator(s) associated with the service provider. The user may then provide the facilitator to client device 610. Upon verifying that the facilitator(s) provided by the user match the previously registered facilitator(s), communication device 310 may sign an authentication indicator using the private key linked to the user's account with the service provider.

An access request including the signed authentication indicator is then sent to secure remote server 620 to indicate to secure remote server 620 that the user has successfully been authenticated to communication device 610. In some embodiments, the access request may include data representing the facilitator, or an indicator indicating which facilitator(s) were provided by the user. Secure remote server 320 may then verify the signature by using the stored public key linked to the user's account associated with the service provider. Upon verifying the signature, the secure remote server 620 may grant the user access to the service provider.

In embodiments in which the secure remote server 620 is associated with a token service provider, secure remote server 620 may release a token associated with the user's account to a merchant 640 whose website the user is accessing on device 350 to enable the user to conduct a transaction with merchant 640. In some embodiments, the access request may also include transaction details of the transaction, and secure remote server 620 may generate a transaction authentication verification value and provide the transaction authentication verification value with the token. For example, the transaction authentication verification value can be a cryptogram generated based on the transaction details and/or the token. The transaction authentication verification value can accompany a token in an authorization request message and can serve as proof that the token is being used in an appropriate corresponding transaction channel or mode (e.g., physical point of sale vs. e-commerce). Merchant 640 can then provide the token or the token together with the transaction authentication verification value in an authorization request message to request authorization for the transaction.

FIG. 7 illustrates a flow diagram of a process 700 for performing authentication of users in accordance with at least some embodiments. Process 700 can be performed on a secure remote transaction server 202 depicted in FIG. 2.

Process 700 may begin at 702, when a request is received to enroll an account with the system described herein. In some embodiments, the request may be submitted by a user of a client device via a mobile application installed upon the mobile device. In some embodiments, the request may be conveyed to a secure remote transaction server from an authorization entity. For example, upon submission of a request to enroll an account into the system described by a user, the request may be transmitted to an authorization entity. The authorization entity may then forward the request to the secure remote transaction server. In this example, the authorization entity may determine whether the user of the client device is authorized to access the account before or after the request has been forwarded to the secure remote transaction server.

At 704, the process may involve determining that the user is authorized to access the account. In some embodiments, this may involve either the secure remote transaction server or the authorization entity associated with the account contacting the user via a communication channel stored in relation to the account. For example, upon creation of the account, the user may be required to provide a communication channel (e.g., an email address or phone number) that will be associated with the account via a know-your-customer (e.g., KYC) process. In this example, the user may be contacted via the communication channel provided during the creation of the account. In some embodiments, determining that the user is authorized to access the account may involve transmitting a one-time passcode to the user via the communication channel and causing the client device to prompt the user to enter the one-time passcode. In these embodiments, the user may be determined to be authorized to access the account upon determining that the one-time passcode entered by the user matches the transmitted one-time passcode.

At 706, a cryptographic key pair may be generated in relation to the account. At least the public key of the cryptographic key pair may be stored upon the secure remote transaction server. At least the private key of the cryptographic key pair may be stored upon the client device. In some embodiments, the cryptographic key pair may be generated by the client device. For example, the client device may generate a cryptographic key pair and may subsequently transmit the public key to the secure remote transaction server. In some embodiments, the secure remote transaction server may generate the cryptographic key pair. For example, the secure remote transaction server may generate a cryptographic key pair and may subsequently transmit the private key to the client device. In some embodiments, in addition to storing the public key, the secure remote transaction server may forward the public key to an authorization entity associated with the account being enrolled.

At 708, the process may involve generating a token to be associated with the account. In some embodiments, the token may be generated by the secure remote transaction server. In some embodiments, the token may be generated by an authorization entity server and transmitted to the secure remote transaction server. The generated token may then be stored in association with the account.

At 710, the process may involve receiving a request to complete a transaction. In some embodiments, the request may be received at a secure remote transaction server from an access device that manages access to one or more resources. The request may include various details related to the requested transaction along with a signed authentication indicator. For example, upon initiation of the requested transaction, the user may be prompted to provide one or more biometric samples. The biometric samples provided by the user may be processed by a facilitator application on the client device to determine the authenticity of the user. Once determined, the facilitator application may generate an authentication indicator that indicates a likelihood that the user requesting the transaction is the user enrolled into the account. The client device may then sign this authentication indicator by performing a cryptographic operation on the authentication indicator using the private key generated and stored on the client device at 706. The signed authentication indicator may be provided to the secure remote transaction server within the request received at 710.

At 712, upon receiving the signed authentication indicator, the secure remote transaction server may verify the signed authentication indicator by performing a second cryptographic operation on the signed authentication indicator using the public key generated at 706 and stored at the secure remote transaction server. In this process, the second cryptographic operation may result in the creation of an unsigned version of the authentication indicator, which may then be processed to determine whether the user is authenticated. In some embodiments, the unsigned version of the authentication indicator may be compared to an expected authentication indicator result. In some embodiments, a likelihood value in the unsigned version of the authentication indicator may be compared to an acceptable risk threshold value to determine whether the transaction should be conducted. For example, a generated unsigned version of the authentication indicator may include a likelihood that the user requesting the transaction is the user enrolled into the account. In this example, the likelihood may be compared to a predetermined threshold value. If the likelihood is greater than the predetermined threshold value, then the signed authentication indicator may be verified. Upon verification of the signed authentication indicator, the process may involve initiating the requested transaction at 714. This may involve providing the token stored in association with the account at 708 to the access device from which the request was received at 710.

FIG. 8 illustrates a flow diagram of a process 800 for registering authentication data in accordance with at least some embodiments. Process 800 can be performed on a communication device operated by a user, which may be an example of a client device 102 depicted in FIG. 1.

Process 800 may begin at block 802 by receiving a request to register authentication data for an account associated with a service provider. In some embodiments, a user may indicate an account or accounts to register. For example, the user may select one or more credit card numbers or banking account numbers to enroll into the system.

At block 804, the user may be prompted to provide the authentication data. In some embodiments, the user may select what type of authentication data to provide as well as an application to authenticate the user (e.g., a biometric facilitator). In some embodiments, an application may be automatically selected by the system to authenticate the user. It should be noted that the application that performs the authentication (e.g., the facilitator application) may be different from the application used to request to register with the system.

At bock 806, the authentication data is received from the user, for example, via a sensor on the communication device. For example, the user may provide a biometric sample to the client device that includes fingerprint, voiceprint, facial images, or other suitable biometric information. At block 808, the received authentication data may be registered and stored onto the communication device or onto a remote sever that supports a facilitator application installed upon the communication device (e.g., a facilitator application server). The authentication data may then be processed to authenticate a user of the communication device. For example, a facilitator application may generate an authentication indicator indicating whether or not the user has been authenticated.

At block 810, a public and private key pair may obtained by the communication device. In some embodiments, at least a private key may be received by the communication device from a secure remote server (e.g., an SRT server). For example, the communication device may send an authentication indicator to the secure remote server, along with enrollment data, and may receive a private key generated by the secure remote server. In some embodiments, the public and private key pair of the cryptographic key pair may be generated by the communication device. In some embodiments, the cryptographic key pair may be generated using information obtained from the secure remote server and/or information related to the communication device. For example, the communication device may receive a base key pair from the secure remote server and may generate the cryptographic key pair using some algorithm for modifying the base key pair using information from the communication device. At block 812, the private key is associated with the account and the authentication data and stored on the communication device.

At block 814, the generated public key is sent to a secure remote server, and the secure remote server links the public key to a token associated with the account. In some embodiments, the token can be used by the user to access services associated with the account, and may act as a substitute for a real account identifier of the account.

FIG. 9 illustrates a flow diagram of a process 900 for accessing an account, according to some embodiments. In accordance with at least some embodiments, process 900 may be performed on a communication device, which may be an example of a client device 102 depicted in FIG. 1.

Process 900 may begin at block 902 by receiving a request to access an account from the user's communication device. At block 904, the user may be prompted to provide the authentication data previously registered for the account. In some embodiments, the user may be prompted to provide authentication data via a mobile application (e.g., a facilitator application) installed upon the communication device which is separate from a mobile application via which the user has requested access to the account.

At block 906, the authentication data is received from the user, for example, via a sensor on communication device. At block 908, the received authentication data is compared with the registered authentication data. At block 910, the received authentication data is determined to match the registered authentication data. In some embodiments, the registered authentication data may be stored on a remote server that supports a biometric facilitator application and this step may involve providing the received authentication data to that remote server for verification. In some embodiments, the registered authentication data may be stored on, and verified upon, the communication device.

At block 912, in response to determining a match, an authentication indicator is generated to indicate that the user has been verified. At block 914, the generated authentication indicator may be signed using the private key stored on the communication device in relation to the account.

At block 916, the signed authentication indicator may be sent to the secure remote server within an access request. The secure remote server may verify the signed authentication indicator using the public key associated the account, and in response to determining that the authentication indicator is verified, releases the token associated with the account to the service provider to grant the user access to the account. In some embodiments, verification of the authentication indicator may involve performing a cryptographic operation on the signed authentication indicator using the public key that results in generation of an unsigned version of the authentication indicator. The unsigned version of the authentication indicator may then be compared to an expected unsigned version of the authentication indicator.

Embodiments of the disclosure provide for a number of technical advantages over conventional systems. For example, embodiments of the disclosure enable authentication of a user by leveraging existing facilitator applications on a mobile device, while enabling an SRT platform and authorization entity to be assured that the authentication was performed by a legitimate client device. As authorization entities are not currently able to receive this assurance in conventional systems, this represents a technical improvement over such systems (as those systems do not include the technical means to provide this functionality). Further, as indicated by the above-described process flows, embodiments of the invention can be used to securely authenticate a device and a user of that device when conducting a remote transaction, without requiring a user to enter a PIN or password. Further, since tokens and transaction authentication verification values are used in embodiments of the invention, sensitive data such as account numbers, PII (personal identifiable information), etc., can be protected in transit.

Although some of the examples described above are described in the context of secure remote commerce transactions, it is understood that embodiments of the invention can be used in other contexts in which authentication and data security issues are present. For example, embodiments of the invention can be used to obtain access to secure data (e.g., medical records, personal data such as tax records, etc.) or can be used in situations where a user may wish to obtain access to a secure location such as a building or a transit station.

A computer system will now be described that may be used to implement any of the entities or components described herein. Subsystems in the computer system are interconnected via a system bus. Additional subsystems include a printer, a keyboard, a fixed disk, and a monitor which can be coupled to a display adapter. Peripherals and input/output (I/O) devices, which can couple to an I/O controller, can be connected to the computer system by any number of means known in the art, such as a serial port. For example, a serial port or external interface 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 allows the central processor to communicate with each subsystem and to control the execution of instructions from system memory or the fixed disk, as well as the exchange of information between subsystems. The system memory and/or the fixed disk may embody a computer-readable medium.

The techniques described herein may involve implementing one or more functions, processes, operations or method steps. In some embodiments, the functions, processes, operations or method steps may be implemented as a result of the execution of a set of instructions or software code by a suitably-programmed computing device, microprocessor, data processor, or the like. The set of instructions or software code may be stored in a memory or other form of data storage element which is accessed by the computing device, microprocessor, etc. In other embodiments, the functions, processes, operations or method steps may be implemented by firmware or a dedicated processor, integrated circuit, etc.

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.

While certain exemplary embodiments have been described in detail and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not intended to be restrictive of the broad invention, and that this invention is not to be limited to the specific arrangements and constructions shown and described, since various other modifications may occur to those with ordinary skill in the art.

As used herein, the use of “a,” “an,” or “the” is intended to mean “at least one,” unless specifically indicated to the contrary.

Claims

1. A computer-implemented method comprising: receiving, by a secure remote transaction server from an access device, a request to complete a transaction in association with an account, the request including a signed authentication indicator, wherein an authentication indicator is signed by an authentication application using a private key of a cryptographic key pair to form the signed authentication indicator, after one or more of multiple facilitators authenticate a user of a client device according to a prioritized order of the multiple facilitators, wherein the multiple facilitators are prioritized such that a higher priority facilitator is requested first, and after a predetermined number of unsuccessful attempts, a lesser priority facilitator is requested;verifying, by the secure remote transaction server, the signed authentication indicator using a public key of the cryptographic key pair stored in the secure remote transaction server and associated with the account; andupon verifying the signed authentication indicator, providing a token to the access device.
2. The computer-implemented method of claim 1, wherein the signed authentication indicator has been generated by the client device by performing a first cryptographic operation using the private key.
3. The computer-implemented method of claim 1, wherein verifying the signed authentication indicator using the public key comprises performing a second cryptographic operation on the signed authentication indicator using the public key.
4. The computer-implemented method of claim 1, wherein the method further comprises: identifying, by the secure remote transaction server, an authorization entity associated with the account based on information in the request; andverifying, by the secure remote transaction server, an authenticity of the account with the authorization entity associated with the account.
5. The computer-implemented method of claim 4, wherein the authenticity of the account is determined by the authorization entity using a one-time passcode.
6. The computer-implemented method of claim 5, wherein the authorization entity transmits the one-time passcode to the client device via a communication channel stored in relation to the account.
7. The computer-implemented method of claim 1, wherein the cryptographic key pair is generated on the client device and the public key is received by the secure remote transaction server from the client device.
8. The computer-implemented method of claim 1, wherein the cryptographic key pair is generated on the secure remote transaction server and the method further comprises transmitting the private key to the client device.
9. The computer-implemented method of claim 1, wherein the public key is forwarded to an authorization entity associated with the account.
10. A secure remote transaction server comprising: a processor; anda memory including instructions that, when executed with the processor, cause the secure remote transaction server to, at least:receiving, by the secure remote transaction server from an access device, a request to complete a transaction in association with an account, the request including a signed authentication indicator, wherein an authentication indicator is signed by an authentication application using a private key of a cryptographic key pair to form the signed authentication indicator after one or more of multiple facilitators authenticate a user of a client device according to a prioritized order of multiple facilitators, wherein the multiple facilitators are prioritized such that a higher priority facilitator is requested first, and after a predetermined number of unsuccessful attempts, a lesser priority facilitator is requested;verifying, by the secure remote transaction server, the authentication indicator using a public key of the cryptographic key pair stored in the secure remote transaction server and associated with the account; andupon verifying the authentication indicator, providing a token to the access device.
11. The secure remote transaction server of claim 10, wherein the authentication indicator indicates that the user is authenticated by the one or more of the multiple facilitators.
12. The secure remote transaction server of claim 10, wherein verifying the authentication indicator using the public key comprises generating an unsigned version of the signed authentication indicator and assessing the unsigned version of the signed authentication indicator.
13. The secure remote transaction server of claim 12, wherein assessing the unsigned version of the signed authentication indicator comprises comparing the unsigned version of the signed authentication indicator to an expected result.
14. The secure remote transaction server of claim 12, wherein assessing the unsigned version of the signed authentication indicator comprises determining whether a likelihood value in the unsigned version of the signed authentication indicator exceeds a threshold value.
15. The secure remote transaction server of claim 10, wherein the token is subsequently used by the access device to complete the transaction.
16. The secure remote transaction server of claim 10, wherein the one or more of the multiple facilitators uses biometric verification to authenticate the user.
17. The secure remote transaction server of claim 10, wherein generating the token to be associated with the account comprises receiving the token from an authorization entity associated with the account.
18. A computer-implemented method comprising: receiving, by a communication device, a request to access an account;prompting, by a facilitator of multiple facilitators of the communication device, a user to provide authentication data, wherein the multiple facilitators are prioritized such that a higher priority facilitator is requested first, and after a predetermined number of unsuccessful attempts, a lesser priority facilitator is requested;receiving, by the facilitator of the multiple facilitators of the communication device, the authentication data from the user;comparing, by the facilitator of the multiple facilitators of the communication device, the received authentication data with registered authentication data;determining, by the facilitator of the multiple facilitators of the communication device, that the received authentication data matches the registered authentication data;generating, by the facilitator of the multiple facilitators of the communication device, an authentication indicator indicating a match of the received authentication data to the registered authentication data;signing, by the communication device, the authentication indicator using a private key of a cryptographic key pair to form a signed authentication indicator; andsending, by the communication device, the signed authentication indicator to a secure remote server in an access request, wherein the secure remote server releases a token to grant the user access to the account in response to verifying the signed authentication indicator using a public key of the cryptographic key pair.
19. The communication device of claim 18, wherein the token is released to a service provider computer.
20. The communication device of claim 18, wherein the one or more of the multiple facilitators uses biometric verification to authenticate the user.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation application of U.S. patent application Ser. No. 16/977,645, which is a National Stage of International Application No. PCT/I132018/056173, International Filing Date Aug. 16, 2018, which claims the benefit of and priority to U.S. Provisional Patent Application No. 62/639,652, entitled, “SECURE REMOTE TOKEN RELEASE WITH ONLINE AUTHENTICATION,” filed Mar. 7, 2018, which are all fully incorporated by reference herein.

US Referenced Citations (615)

Number	Name	Date	Kind
5280527	Gullman et al.	Jan 1994	A
5613012	Hoffman et al.	Mar 1997	A
5781438	Lee et al.	Jul 1998	A
5850442	Muftic	Dec 1998	A
5883810	Franklin et al.	Mar 1999	A
5930767	Reber et al.	Jul 1999	A
5953710	Fleming	Sep 1999	A
5956699	Wong et al.	Sep 1999	A
6000832	Franklin et al.	Dec 1999	A
6014635	Harris et al.	Jan 2000	A
6044360	Picciallo	Mar 2000	A
6163771	Walker et al.	Dec 2000	A
6227447	Campisano	May 2001	B1
6236981	Hill	May 2001	B1
6267292	Walker et al.	Jul 2001	B1
6327578	Linehan	Dec 2001	B1
6341724	Campisano	Jan 2002	B2
6385596	Wiser et al.	May 2002	B1
6422462	Cohen	Jul 2002	B1
6425523	Shem-Ur et al.	Jul 2002	B1
6453301	Niwa	Sep 2002	B1
6592044	Wong et al.	Jul 2003	B1
6636833	Flitcroft et al.	Oct 2003	B1
6748367	Lee	Jun 2004	B1
6805287	Bishop et al.	Oct 2004	B2
6879965	Fung et al.	Apr 2005	B2
6891953	DeMello et al.	May 2005	B1
6901387	Wells et al.	May 2005	B2
6931382	Laage et al.	Aug 2005	B2
6938019	Uzo	Aug 2005	B1
6941285	Sarcanin	Sep 2005	B2
6980670	Hoffman et al.	Dec 2005	B1
6990470	Hogan et al.	Jan 2006	B2
6991157	Bishop et al.	Jan 2006	B2
7051929	Li	May 2006	B2
7069249	Stolfo et al.	Jun 2006	B2
7103576	Mann, III et al.	Sep 2006	B2
7113930	Eccles et al.	Sep 2006	B2
7136835	Flitcroft et al.	Nov 2006	B1
7177835	Walker et al.	Feb 2007	B1
7177848	Hogan et al.	Feb 2007	B2
7194437	Britto et al.	Mar 2007	B1
7209561	Shankar et al.	Apr 2007	B1
7264154	Harris	Sep 2007	B2
7287692	Patel et al.	Oct 2007	B1
7292999	Hobson et al.	Nov 2007	B2
7350230	Forrest	Mar 2008	B2
7353382	Labrou et al.	Apr 2008	B2
7379919	Hogan et al.	May 2008	B2
RE40444	Linehan	Jul 2008	E
7415443	Hobson et al.	Aug 2008	B2
7444676	Asghari-Kamrani et al.	Oct 2008	B1
7469151	Khan et al.	Dec 2008	B2
7548889	Bhambri et al.	Jun 2009	B2
7567934	Flitcroft et al.	Jul 2009	B2
7567936	Peckover et al.	Jul 2009	B1
7571139	Giordano et al.	Aug 2009	B1
7571142	Flitcroft et al.	Aug 2009	B1
7580898	Brown et al.	Aug 2009	B2
7584153	Brown et al.	Sep 2009	B2
7593896	Flitcroft et al.	Sep 2009	B1
7606560	Labrou	Oct 2009	B2
7627531	Breck et al.	Dec 2009	B2
7627895	Gifford et al.	Dec 2009	B2
7650314	Saunders	Jan 2010	B1
7685037	Reiners et al.	Mar 2010	B2
7702578	Fung et al.	Apr 2010	B2
7707120	Dominguez et al.	Apr 2010	B2
7712655	Wong	May 2010	B2
7734527	Uzo	Jun 2010	B2
7753265	Harris	Jul 2010	B2
7770789	Oder, II et al.	Aug 2010	B2
7784685	Hopkins, III	Aug 2010	B1
7793851	Mullen	Sep 2010	B2
7801826	Labrou et al.	Sep 2010	B2
7805376	Smith	Sep 2010	B2
7805378	Berardi et al.	Sep 2010	B2
7818264	Hammad	Oct 2010	B2
7828220	Mullen	Nov 2010	B2
7835960	Breck et al.	Nov 2010	B2
7841523	Oder, II et al.	Nov 2010	B2
7841539	Hewton	Nov 2010	B2
7844550	Walker et al.	Nov 2010	B2
7848980	Carlson	Dec 2010	B2
7849020	Johnson	Dec 2010	B2
7853529	Walker et al.	Dec 2010	B1
7853995	Chow et al.	Dec 2010	B2
7865414	Fung et al.	Jan 2011	B2
7873579	Hobson et al.	Jan 2011	B2
7873580	Hobson et al.	Jan 2011	B2
7890393	Talbert et al.	Feb 2011	B2
7891563	Oder, II et al.	Feb 2011	B2
7896238	Fein et al.	Mar 2011	B2
7908216	Davis et al.	Mar 2011	B1
7922082	Muscato	Apr 2011	B2
7931195	Mullen	Apr 2011	B2
7937324	Patterson	May 2011	B2
7938318	Fein et al.	May 2011	B2
7954705	Mullen	Jun 2011	B2
7959076	Hopkins, III	Jun 2011	B1
7996288	Stolfo	Aug 2011	B1
8025223	Saunders et al.	Sep 2011	B2
8046256	Chien et al.	Oct 2011	B2
8060448	Jones	Nov 2011	B2
8060449	Zhu	Nov 2011	B1
8074877	Mullen et al.	Dec 2011	B2
8074879	Harris	Dec 2011	B2
8082210	Hansen et al.	Dec 2011	B2
8095113	Kean et al.	Jan 2012	B2
8104679	Brown	Jan 2012	B2
RE43157	Bishop et al.	Feb 2012	E
8109436	Hopkins, III	Feb 2012	B1
8121942	Carlson et al.	Feb 2012	B2
8121956	Carlson et al.	Feb 2012	B2
8126449	Beenau et al.	Feb 2012	B2
8132723	Hogg et al.	Mar 2012	B2
8171525	Pelly et al.	May 2012	B1
8175973	Davis et al.	May 2012	B2
8190523	Patterson	May 2012	B2
8196813	Vadhri	Jun 2012	B2
8205791	Randazza et al.	Jun 2012	B2
8219489	Patterson	Jul 2012	B2
8224702	Mengerink et al.	Jul 2012	B2
8225385	Chow et al.	Jul 2012	B2
8229852	Carlson	Jul 2012	B2
8265993	Chien et al.	Sep 2012	B2
8280777	Mengerink et al.	Oct 2012	B2
8281991	Wentker et al.	Oct 2012	B2
8328095	Oder, II et al.	Dec 2012	B2
8336088	Raj et al.	Dec 2012	B2
8346666	Lindelsee et al.	Jan 2013	B2
8376225	Hopkins, III	Feb 2013	B1
8380177	Laracey	Feb 2013	B2
8387873	Saunders et al.	Mar 2013	B2
8401539	Beenau et al.	Mar 2013	B2
8401898	Chien et al.	Mar 2013	B2
8402555	Grecia	Mar 2013	B2
8403211	Brooks et al.	Mar 2013	B2
8412623	Moon et al.	Apr 2013	B2
8412837	Emigh et al.	Apr 2013	B1
8417642	Oren	Apr 2013	B2
8447699	Batada et al.	May 2013	B2
8453223	Svigals et al.	May 2013	B2
8453925	Fisher et al.	Jun 2013	B2
8458487	Palgon et al.	Jun 2013	B1
8484134	Hobson et al.	Jul 2013	B2
8485437	Mullen et al.	Jul 2013	B2
8494959	Hathaway et al.	Jul 2013	B2
8498908	Mengerink et al.	Jul 2013	B2
8504475	Brand et al.	Aug 2013	B2
8504478	Saunders et al.	Aug 2013	B2
8510816	Quach et al.	Aug 2013	B2
8528067	Hurry et al.	Sep 2013	B2
8533116	Davis et al.	Sep 2013	B2
8533860	Grecia	Sep 2013	B1
8538845	Liberty	Sep 2013	B2
8555079	Shablygin et al.	Oct 2013	B2
8566168	Bierbaum et al.	Oct 2013	B1
8567670	Stanfield et al.	Oct 2013	B2
8571939	Lindsey et al.	Oct 2013	B2
8577336	Mechaley, Jr.	Nov 2013	B2
8577803	Chatterjee et al.	Nov 2013	B2
8577813	Weiss	Nov 2013	B2
8578176	Mattsson	Nov 2013	B2
8583494	Fisher	Nov 2013	B2
8584251	McGuire et al.	Nov 2013	B2
8589237	Fisher	Nov 2013	B2
8589271	Evans	Nov 2013	B2
8589291	Carlson et al.	Nov 2013	B2
8595098	Starai et al.	Nov 2013	B2
8595812	Bomar et al.	Nov 2013	B2
8595850	Spies et al.	Nov 2013	B2
8606638	Dragt	Dec 2013	B2
8606700	Carlson et al.	Dec 2013	B2
8606720	Baker et al.	Dec 2013	B1
8615468	Varadarajan	Dec 2013	B2
8620754	Fisher	Dec 2013	B2
8635157	Smith et al.	Jan 2014	B2
8646059	von Behren et al.	Feb 2014	B1
8651374	Brabson et al.	Feb 2014	B2
8656180	Shablygin et al.	Feb 2014	B2
8751391	Freund	Jun 2014	B2
8751642	Vargas et al.	Jun 2014	B2
8762263	Gauthier et al.	Jun 2014	B2
8793186	Patterson	Jul 2014	B2
8838982	Carlson et al.	Sep 2014	B2
8856539	Weiss	Oct 2014	B2
8887308	Grecia	Nov 2014	B2
9065643	Hurry et al.	Jun 2015	B2
9070129	Sheets et al.	Jun 2015	B2
9100826	Weiss	Aug 2015	B2
9160741	Wentker et al.	Oct 2015	B2
9229964	Stevelinck	Jan 2016	B2
9245267	Singh	Jan 2016	B2
9249241	Dai et al.	Feb 2016	B2
9256871	Anderson et al.	Feb 2016	B2
9280765	Hammad	Mar 2016	B2
9519901	Dorogusker	Dec 2016	B1
9530137	Weiss	Dec 2016	B2
9646303	Karpenko et al.	May 2017	B2
9680942	Dimmick	Jun 2017	B2
9780950	Dundas et al.	Oct 2017	B1
20010029485	Brody et al.	Oct 2001	A1
20010034720	Armes	Oct 2001	A1
20010054003	Chien et al.	Dec 2001	A1
20020007320	Hogan et al.	Jan 2002	A1
20020016749	Borecki et al.	Feb 2002	A1
20020029193	Ranjan et al.	Mar 2002	A1
20020035548	Hogan et al.	Mar 2002	A1
20020056043	Glass	May 2002	A1
20020073045	Rubin et al.	Jun 2002	A1
20020116341	Hogan et al.	Aug 2002	A1
20020133467	Hobson et al.	Sep 2002	A1
20020147913	Lun Yip	Oct 2002	A1
20030028481	Flitcroft et al.	Feb 2003	A1
20030130955	Hawthorne	Jul 2003	A1
20030191709	Elston et al.	Oct 2003	A1
20030191945	Keech	Oct 2003	A1
20040010462	Moon et al.	Jan 2004	A1
20040044739	Ziegler	Mar 2004	A1
20040050928	Bishop et al.	Mar 2004	A1
20040059682	Hasumi et al.	Mar 2004	A1
20040093281	Silverstein et al.	May 2004	A1
20040139008	Mascavage, III	Jul 2004	A1
20040143532	Lee	Jul 2004	A1
20040158532	Breck et al.	Aug 2004	A1
20040210449	Breck et al.	Oct 2004	A1
20040210498	Freund	Oct 2004	A1
20040232225	Bishop et al.	Nov 2004	A1
20040236632	Maritzen et al.	Nov 2004	A1
20040260646	Berardi et al.	Dec 2004	A1
20050037735	Coutts	Feb 2005	A1
20050080730	Sorrentino	Apr 2005	A1
20050108178	York	May 2005	A1
20050199709	Linlor	Sep 2005	A1
20050246293	Ong	Nov 2005	A1
20050269401	Spitzer et al.	Dec 2005	A1
20050269402	Spitzer et al.	Dec 2005	A1
20060235795	Johnson et al.	Oct 2006	A1
20060237528	Bishop et al.	Oct 2006	A1
20060278704	Saunders et al.	Dec 2006	A1
20070107044	Yuen et al.	May 2007	A1
20070129955	Dalmia et al.	Jun 2007	A1
20070136193	Starr	Jun 2007	A1
20070136211	Brown et al.	Jun 2007	A1
20070170247	Friedman	Jul 2007	A1
20070179885	Bird et al.	Aug 2007	A1
20070198432	Pitroda et al.	Aug 2007	A1
20070208671	Brown et al.	Sep 2007	A1
20070245414	Chan et al.	Oct 2007	A1
20070288377	Shaked	Dec 2007	A1
20070291995	Rivera	Dec 2007	A1
20080015988	Brown et al.	Jan 2008	A1
20080029607	Mullen	Feb 2008	A1
20080035738	Mullen	Feb 2008	A1
20080052226	Agarwal et al.	Feb 2008	A1
20080054068	Mullen	Mar 2008	A1
20080054079	Mullen	Mar 2008	A1
20080054081	Mullen	Mar 2008	A1
20080065554	Hogan et al.	Mar 2008	A1
20080065555	Mullen	Mar 2008	A1
20080201264	Brown et al.	Aug 2008	A1
20080201265	Hewton	Aug 2008	A1
20080228646	Myers et al.	Sep 2008	A1
20080243702	Hart et al.	Oct 2008	A1
20080245855	Fein et al.	Oct 2008	A1
20080245861	Fein et al.	Oct 2008	A1
20080283591	Oder, II et al.	Nov 2008	A1
20080302869	Mullen	Dec 2008	A1
20080302876	Mullen	Dec 2008	A1
20080313264	Pestoni	Dec 2008	A1
20090006262	Brown et al.	Jan 2009	A1
20090010488	Matsuoka et al.	Jan 2009	A1
20090037333	Flitcroft et al.	Feb 2009	A1
20090037388	Cooper et al.	Feb 2009	A1
20090043702	Bennett	Feb 2009	A1
20090048971	Hathaway et al.	Feb 2009	A1
20090106112	Dalmia et al.	Apr 2009	A1
20090106160	Skowronek	Apr 2009	A1
20090134217	Flitcroft et al.	May 2009	A1
20090157555	Biffle et al.	Jun 2009	A1
20090159673	Mullen et al.	Jun 2009	A1
20090159700	Mullen et al.	Jun 2009	A1
20090159707	Mullen et al.	Jun 2009	A1
20090173782	Muscato	Jul 2009	A1
20090200371	Kean et al.	Aug 2009	A1
20090248583	Chhabra	Oct 2009	A1
20090276347	Kargman	Nov 2009	A1
20090281948	Carlson	Nov 2009	A1
20090294527	Brabson et al.	Dec 2009	A1
20090307139	Mardikar et al.	Dec 2009	A1
20090308921	Mullen	Dec 2009	A1
20090327131	Beenau et al.	Dec 2009	A1
20100008535	Abulafia et al.	Jan 2010	A1
20100042848	Rosener	Feb 2010	A1
20100088237	Wankmueller	Apr 2010	A1
20100094755	Kloster	Apr 2010	A1
20100106644	Annan et al.	Apr 2010	A1
20100120408	Beenau et al.	May 2010	A1
20100133334	Vadhri	Jun 2010	A1
20100138347	Chen	Jun 2010	A1
20100145860	Pelegero	Jun 2010	A1
20100161433	White	Jun 2010	A1
20100185545	Royyuru et al.	Jul 2010	A1
20100211505	Saunders et al.	Aug 2010	A1
20100223186	Hogan et al.	Sep 2010	A1
20100228668	Hogan et al.	Sep 2010	A1
20100235284	Moore	Sep 2010	A1
20100258620	Torreyson et al.	Oct 2010	A1
20100291904	Musfeldt et al.	Nov 2010	A1
20100299267	Faith et al.	Nov 2010	A1
20100306076	Taveau et al.	Dec 2010	A1
20100325041	Berardi et al.	Dec 2010	A1
20110010292	Giordano et al.	Jan 2011	A1
20110016047	Wu et al.	Jan 2011	A1
20110016320	Bergsten et al.	Jan 2011	A1
20110040640	Erikson	Feb 2011	A1
20110047076	Carlson et al.	Feb 2011	A1
20110083018	Kesanupalli et al.	Apr 2011	A1
20110087596	Dorsey	Apr 2011	A1
20110093397	Carlson et al.	Apr 2011	A1
20110119155	Hammad et al.	May 2011	A1
20110125597	Oder, II et al.	May 2011	A1
20110153437	Archer et al.	Jun 2011	A1
20110153498	Makhotin et al.	Jun 2011	A1
20110154466	Harper et al.	Jun 2011	A1
20110161233	Tieken	Jun 2011	A1
20110178926	Lindelsee et al.	Jul 2011	A1
20110191244	Dai	Aug 2011	A1
20110238511	Park et al.	Sep 2011	A1
20110238573	Varadarajan	Sep 2011	A1
20110246317	Coppinger	Oct 2011	A1
20110258111	Raj et al.	Oct 2011	A1
20110272471	Mullen	Nov 2011	A1
20110272478	Mullen	Nov 2011	A1
20110276380	Mullen et al.	Nov 2011	A1
20110276381	Mullen et al.	Nov 2011	A1
20110276424	Mullen	Nov 2011	A1
20110276425	Mullen	Nov 2011	A1
20110295745	White et al.	Dec 2011	A1
20110302081	Saunders et al.	Dec 2011	A1
20120023567	Hammad	Jan 2012	A1
20120028609	Hruska	Feb 2012	A1
20120030047	Fuentes et al.	Feb 2012	A1
20120035998	Chien et al.	Feb 2012	A1
20120041881	Basu et al.	Feb 2012	A1
20120047237	Arvidsson et al.	Feb 2012	A1
20120066078	Kingston et al.	Mar 2012	A1
20120072350	Goldthwaite et al.	Mar 2012	A1
20120078735	Bauer et al.	Mar 2012	A1
20120078798	Downing et al.	Mar 2012	A1
20120078799	Jackson et al.	Mar 2012	A1
20120095852	Bauer et al.	Apr 2012	A1
20120095865	Doherty et al.	Apr 2012	A1
20120116902	Cardina et al.	May 2012	A1
20120123882	Carlson et al.	May 2012	A1
20120123940	Killian et al.	May 2012	A1
20120129514	Beenau et al.	May 2012	A1
20120143754	Patel	Jun 2012	A1
20120143767	Abadir	Jun 2012	A1
20120143772	Abadir	Jun 2012	A1
20120158580	Eram et al.	Jun 2012	A1
20120158593	Garfinkle et al.	Jun 2012	A1
20120173431	Ritchie et al.	Jul 2012	A1
20120185386	Salama et al.	Jul 2012	A1
20120197807	Schlesser et al.	Aug 2012	A1
20120203664	Torossian et al.	Aug 2012	A1
20120203666	Torossian et al.	Aug 2012	A1
20120215688	Musser et al.	Aug 2012	A1
20120215696	Salonen	Aug 2012	A1
20120221421	Hammad	Aug 2012	A1
20120226582	Hammad	Sep 2012	A1
20120231844	Coppinger	Sep 2012	A1
20120233004	Bercaw	Sep 2012	A1
20120246070	Vadhri	Sep 2012	A1
20120246071	Jain et al.	Sep 2012	A1
20120246079	Wilson et al.	Sep 2012	A1
20120265631	Cronic et al.	Oct 2012	A1
20120271770	Harris et al.	Oct 2012	A1
20120297446	Webb et al.	Nov 2012	A1
20120300932	Cambridge et al.	Nov 2012	A1
20120303503	Cambridge et al.	Nov 2012	A1
20120303961	Kean et al.	Nov 2012	A1
20120304273	Bailey et al.	Nov 2012	A1
20120310725	Chien et al.	Dec 2012	A1
20120310831	Harris et al.	Dec 2012	A1
20120316992	Oborne	Dec 2012	A1
20120317035	Royyuru et al.	Dec 2012	A1
20120317036	Bower et al.	Dec 2012	A1
20130017784	Fisher	Jan 2013	A1
20130018757	Anderson et al.	Jan 2013	A1
20130019098	Gupta et al.	Jan 2013	A1
20130031006	McCullagh et al.	Jan 2013	A1
20130054337	Brendell et al.	Feb 2013	A1
20130054466	Muscato	Feb 2013	A1
20130054474	Yeager	Feb 2013	A1
20130081122	Svigals et al.	Mar 2013	A1
20130091028	Oder, II et al.	Apr 2013	A1
20130110658	Lyman et al.	May 2013	A1
20130111599	Gargiulo	May 2013	A1
20130117185	Collison et al.	May 2013	A1
20130124290	Fisher	May 2013	A1
20130124291	Fisher	May 2013	A1
20130124364	Mittal	May 2013	A1
20130138525	Bercaw	May 2013	A1
20130144888	Faith et al.	Jun 2013	A1
20130145148	Shablygin et al.	Jun 2013	A1
20130145172	Shablygin et al.	Jun 2013	A1
20130159178	Colon et al.	Jun 2013	A1
20130159184	Thaw	Jun 2013	A1
20130166402	Parento et al.	Jun 2013	A1
20130166456	Zhang et al.	Jun 2013	A1
20130173736	Krzeminski et al.	Jul 2013	A1
20130185202	Goldthwaite et al.	Jul 2013	A1
20130191227	Pasa et al.	Jul 2013	A1
20130191286	Cronic et al.	Jul 2013	A1
20130191289	Cronic et al.	Jul 2013	A1
20130198071	Jurss	Aug 2013	A1
20130198080	Anderson et al.	Aug 2013	A1
20130200146	Moghadam	Aug 2013	A1
20130204787	Dubois	Aug 2013	A1
20130204793	Kerridge et al.	Aug 2013	A1
20130212007	Mattsson et al.	Aug 2013	A1
20130212017	Bangia	Aug 2013	A1
20130212019	Mattsson et al.	Aug 2013	A1
20130212024	Mattsson et al.	Aug 2013	A1
20130212026	Powell et al.	Aug 2013	A1
20130212666	Mattsson et al.	Aug 2013	A1
20130218698	Moon et al.	Aug 2013	A1
20130218769	Pourfallah et al.	Aug 2013	A1
20130226799	Raj	Aug 2013	A1
20130226802	Hammad et al.	Aug 2013	A1
20130226813	Voltz	Aug 2013	A1
20130246199	Carlson	Sep 2013	A1
20130246202	Tobin	Sep 2013	A1
20130246203	Laracey	Sep 2013	A1
20130246258	Dessert	Sep 2013	A1
20130246259	Dessert	Sep 2013	A1
20130246261	Purves et al.	Sep 2013	A1
20130246267	Tobin	Sep 2013	A1
20130254028	Salci	Sep 2013	A1
20130254052	Royyuru et al.	Sep 2013	A1
20130254102	Royyuru	Sep 2013	A1
20130254117	von Mueller et al.	Sep 2013	A1
20130262296	Thomas et al.	Oct 2013	A1
20130262302	Lettow et al.	Oct 2013	A1
20130262315	Hruska	Oct 2013	A1
20130262316	Hruska	Oct 2013	A1
20130262317	Collinge et al.	Oct 2013	A1
20130275300	Killian et al.	Oct 2013	A1
20130275307	Khan	Oct 2013	A1
20130275308	Paraskeva et al.	Oct 2013	A1
20130282502	Jooste	Oct 2013	A1
20130282575	Mullen et al.	Oct 2013	A1
20130282588	Hruska	Oct 2013	A1
20130297501	Monk et al.	Nov 2013	A1
20130297504	Nwokolo et al.	Nov 2013	A1
20130297508	Belamant	Nov 2013	A1
20130304649	Cronic et al.	Nov 2013	A1
20130308778	Fosmark et al.	Nov 2013	A1
20130311382	Fosmark et al.	Nov 2013	A1
20130317982	Mengerink et al.	Nov 2013	A1
20130332344	Weber	Dec 2013	A1
20130339253	Sincai	Dec 2013	A1
20130346305	Mendes	Dec 2013	A1
20130346314	Mogollon et al.	Dec 2013	A1
20140007213	Sanin et al.	Jan 2014	A1
20140013106	Redpath	Jan 2014	A1
20140013114	Redpath	Jan 2014	A1
20140013452	Aissi et al.	Jan 2014	A1
20140019352	Shrivastava	Jan 2014	A1
20140025581	Calman	Jan 2014	A1
20140025585	Calman	Jan 2014	A1
20140025958	Calman	Jan 2014	A1
20140032417	Mattsson	Jan 2014	A1
20140032418	Weber	Jan 2014	A1
20140040137	Carlson et al.	Feb 2014	A1
20140040139	Brudnicki et al.	Feb 2014	A1
20140040144	Plomske et al.	Feb 2014	A1
20140040145	Ozvat et al.	Feb 2014	A1
20140040148	Ozvat et al.	Feb 2014	A1
20140040628	Fort et al.	Feb 2014	A1
20140041018	Bomar et al.	Feb 2014	A1
20140046853	Spies et al.	Feb 2014	A1
20140047551	Nagasundaram et al.	Feb 2014	A1
20140052532	Tsai et al.	Feb 2014	A1
20140052620	Rogers et al.	Feb 2014	A1
20140052637	Jooste et al.	Feb 2014	A1
20140068706	Aissi	Mar 2014	A1
20140074637	Hammad	Mar 2014	A1
20140108172	Weber et al.	Apr 2014	A1
20140114857	Griggs et al.	Apr 2014	A1
20140143137	Carlson	May 2014	A1
20140164243	Aabye et al.	Jun 2014	A1
20140188586	Carpenter et al.	Jul 2014	A1
20140189350	Baghdasaryan	Jul 2014	A1
20140249945	Gauthier et al.	Sep 2014	A1
20140289528	Baghdasaryan	Sep 2014	A1
20140289833	Briceno	Sep 2014	A1
20140294701	Dai et al.	Oct 2014	A1
20140297534	Patterson	Oct 2014	A1
20140310183	Weber	Oct 2014	A1
20140324690	Allen et al.	Oct 2014	A1
20140330721	Wang	Nov 2014	A1
20140330722	Laxminarayanan et al.	Nov 2014	A1
20140331265	Mozell et al.	Nov 2014	A1
20140337236	Wong et al.	Nov 2014	A1
20140344153	Raj et al.	Nov 2014	A1
20140372308	Sheets	Dec 2014	A1
20150019443	Sheets et al.	Jan 2015	A1
20150032625	Dill et al.	Jan 2015	A1
20150032626	Dill et al.	Jan 2015	A1
20150032627	Dill et al.	Jan 2015	A1
20150046338	Laxminarayanan et al.	Feb 2015	A1
20150046339	Wong et al.	Feb 2015	A1
20150052064	Karpenko et al.	Feb 2015	A1
20150081544	Schulz et al.	Mar 2015	A1
20150088756	Makhotin et al.	Mar 2015	A1
20150106239	Gaddam et al.	Apr 2015	A1
20150112870	Nagasundaram et al.	Apr 2015	A1
20150112871	Kumnick	Apr 2015	A1
20150120472	Aabye et al.	Apr 2015	A1
20150127529	Makhotin et al.	May 2015	A1
20150127547	Powell et al.	May 2015	A1
20150140960	Powell et al.	May 2015	A1
20150142673	Nelsen et al.	May 2015	A1
20150161597	Subramanian et al.	Jun 2015	A1
20150178724	Ngo et al.	Jun 2015	A1
20150180836	Wong et al.	Jun 2015	A1
20150186864	Jones	Jul 2015	A1
20150193222	Pirzadeh et al.	Jul 2015	A1
20150195133	Sheets et al.	Jul 2015	A1
20150199679	Palanisamy et al.	Jul 2015	A1
20150199689	Kumnick et al.	Jul 2015	A1
20150220917	Aabye et al.	Aug 2015	A1
20150269566	Gaddam et al.	Sep 2015	A1
20150269578	Subramanian	Sep 2015	A1
20150278799	Palanisamy	Oct 2015	A1
20150287037	Salmon et al.	Oct 2015	A1
20150312038	Palanisamy	Oct 2015	A1
20150319158	Kumnick	Nov 2015	A1
20150324736	Sheets et al.	Nov 2015	A1
20150326559	Kuang	Nov 2015	A1
20150332262	Lingappa	Nov 2015	A1
20150356560	Shastry et al.	Dec 2015	A1
20150363775	Li	Dec 2015	A1
20150363781	Badenhorst	Dec 2015	A1
20160028550	Gaddam et al.	Jan 2016	A1
20160036790	Shastry et al.	Feb 2016	A1
20160042263	Gaddam et al.	Feb 2016	A1
20160065370	Le Saint et al.	Mar 2016	A1
20160092696	Guglani et al.	Mar 2016	A1
20160092872	Prakash et al.	Mar 2016	A1
20160092874	O'Regan et al.	Mar 2016	A1
20160103675	Aabye et al.	Apr 2016	A1
20160119296	Laxminarayanan et al.	Apr 2016	A1
20160132878	O'Regan et al.	May 2016	A1
20160140545	Flurscheim et al.	May 2016	A1
20160148197	Dimmick	May 2016	A1
20160148212	Dimmick	May 2016	A1
20160171479	Prakash et al.	Jun 2016	A1
20160173483	Wong et al.	Jun 2016	A1
20160197725	Hammad	Jul 2016	A1
20160210628	McGuire	Jul 2016	A1
20160217461	Gaddam et al.	Jul 2016	A1
20160218875	Le Saint et al.	Jul 2016	A1
20160224976	Basu et al.	Aug 2016	A1
20160224977	Sabba et al.	Aug 2016	A1
20160232527	Patterson	Aug 2016	A1
20160239842	Cash et al.	Aug 2016	A1
20160269391	Gaddam et al.	Sep 2016	A1
20160308995	Youdale et al.	Oct 2016	A1
20160350748	Pruthi et al.	Dec 2016	A1
20170046696	Powell et al.	Feb 2017	A1
20170076288	Awasthi	Mar 2017	A1
20170103387	Weber	Apr 2017	A1
20170109745	Al-Bedaiwi et al.	Apr 2017	A1
20170109751	Dunkelberger	Apr 2017	A1
20170148013	Rajurkar et al.	May 2017	A1
20170163617	Laxminarayanan et al.	Jun 2017	A1
20170163629	Law et al.	Jun 2017	A1
20170186001	Reed et al.	Jun 2017	A1
20170200156	Karpenko et al.	Jul 2017	A1
20170200165	Laxminarayanan et al.	Jul 2017	A1
20170201520	Chandoor et al.	Jul 2017	A1
20170220818	Nagasundaram et al.	Aug 2017	A1
20170221054	Flurscheim et al.	Aug 2017	A1
20170221056	Karpenko et al.	Aug 2017	A1
20170228723	Taylor et al.	Aug 2017	A1
20170228728	Sullivan	Aug 2017	A1
20170236113	Chitalia et al.	Aug 2017	A1
20170293914	Girish et al.	Oct 2017	A1
20170295155	Wong	Oct 2017	A1
20170337549	Wong	Nov 2017	A1
20170344732	Kohli	Nov 2017	A1
20170364903	Lopez	Dec 2017	A1
20170364914	Howard	Dec 2017	A1
20170373852	Cassin et al.	Dec 2017	A1
20180006821	Kinagi	Jan 2018	A1
20180047023	Bouda	Feb 2018	A1
20180075081	Chipman	Mar 2018	A1
20180247303	Raj et al.	Aug 2018	A1
20180262334	Hammad	Sep 2018	A1
20180268399	Spector et al.	Sep 2018	A1
20180268405	Lopez	Sep 2018	A1
20180285875	Law et al.	Oct 2018	A1
20180324184	Kaja et al.	Nov 2018	A1
20180324584	Lopez	Nov 2018	A1
20190020478	Girish et al.	Jan 2019	A1
20190066069	Faith et al.	Feb 2019	A1
20190147439	Wang et al.	May 2019	A1
20190356489	Palanisamy	Nov 2019	A1
20190384896	Jones	Dec 2019	A1
20190392431	Chitalia et al.	Dec 2019	A1
20200267153	Kang et al.	Aug 2020	A1

Foreign Referenced Citations (19)

Number	Date	Country
1028401	Aug 2000	EP
2156397	Feb 2010	EP
0014648	Mar 2000	WO
0135304	May 2001	WO
0135304	May 2002	WO
2004042536	May 2004	WO
2004051585	Jun 2004	WO
2005001751	Jan 2005	WO
2006113834	Oct 2006	WO
2009032523	Mar 2009	WO
2010078522	Jul 2010	WO
2012068078	May 2012	WO
2012098556	Jul 2012	WO
2012142370	Oct 2012	WO
2012167941	Dec 2012	WO
2013048538	Apr 2013	WO
2013056104	Apr 2013	WO
2013119914	Aug 2013	WO
2013179271	Dec 2013	WO

Non-Patent Literature Citations (7)

Entry
“Petition for Inter Partes Review of U.S. Pat. No. 8,533,860 Challenging Claims 1-30 Under 35 U.S.C. § 312 and 37 C.F.R. § 42.104”, USPTO Patent Trial and Appeal Board, IPR 2016-00600, Feb. 17, 2016, 65 pages.
U.S. Appl. No. 16/311,144, filed Dec. 18, 2018, 83 pages.
U.S. Appl. No. 16/977,645 , “Non-Final Office Action”, dated Oct. 4, 2021, 24 pages.
U.S. Appl. No. 16/977,645 , “Notice of Allowance”, dated Feb. 2, 2022, 17 pages.
EP18909101.0 , “Extended European Search Report”, dated Mar. 18, 2021, 9 pages.
PCT/IB2018/056173 , “International Preliminary Report on Patentability”, dated Sep. 17, 2020, 9 pages.
PCT/IB2018/056173 , “International Search Report and Written Opinion”, dated Dec. 10, 2018, 14 pages.

Related Publications (1)

	Number	Date	Country
	20220255741 A1	Aug 2022	US

Provisional Applications (1)

	Number	Date	Country
	62639652	Mar 2018	US

Continuations (1)

	Number	Date	Country
Parent	16977645		US
Child	17734443		US

Secure remote token release with online authentication

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract