Patent Description:
One-time passcodes may be used as a second form of authentication. However, one-time passcodes are susceptible to many security risks. For example, if a user leaves their smartphone unlocked in a public place, passersby may have access to any passcodes sent to the device. Similarly, if a malicious user gains access to the device and/or the account where the passcodes are sent, the malicious user may have access to the passcodes. Doing so may allow the malicious user to access account data and other sensitive information.

<CIT> describes using on-demand applications to generate virtual numbers for a contactless card to securely autofill form fields.

The invention is defined by claims <NUM>, <NUM> and <NUM>.

Systems, methods, apparatuses, and computer-readable media for secure generation of one-time passcodes using a contactless card. An operating system (OS) executing on a processor of a device receives a uniform resource locator (URL) and a cryptogram from a contactless card associated with an account. The OS launches an application associated with the contactless card. The application transmits the cryptogram to an authentication server. The application receives a decryption result from the authentication server indicating the authentication server decrypted the cryptogram. Based on the decryption result, the application transmits a request for a one-time passcode (OTP) comprising an identifier to the URL. The processor receives an OTP from an OTP generator at the URL. The application receives an input value and compares the input value to a copy of the OTP received from the OTP generator. The application determines that the comparison results in a match, and displays, based on the determination that the comparison results in the match, one or more attributes of the account on the device.

Embodiments disclosed herein provide techniques to securely generate a one-time passcode (OTP) that may be used as a second form of authentication. Generally, a user may desire to authenticate into an account, complete a purchase, or perform any operation that requires multi-factor authentication (MFA). In one example, the user may tap a contactless card to a computing device to initiate the authentication. In response to coming into communications range with the device, the contactless card may generate a data package comprising a cryptogram and a uniform resource locator (URL). An operating system of the device may read the data package and/or the URL and launch an account application on the device that is associated with the URL. In one example, the account application is associated with an issuer of the contactless card. The account application may transmit an OTP request to an OTP generator at the URL. The OTP request may include the cryptogram.

The OTP generator and/or a server associated with the OTP generator may then attempt to decrypt the cryptogram as described in greater detail herein. If the decryption is successful, the OTP generator may identify contact information for the associated account, such as a phone number, email, etc. The OTP generator may generate an OTP and transmit the OTP to the identified contact information. The user may then receive the OTP from the OTP generator and provide the received OTP as input to the account application. The account application may compare the input to an instance of the OTP received from the OTP generator. If the comparison results in a match, the account application may validate the OTP, and permit the requested operation, e.g., viewing account details, making a purchase, etc. If the comparison does not result in a match, the verification may fail, and the account application may reject or otherwise restrict performance of the requested operation.

Advantageously, embodiments disclosed herein provide secure techniques for generating an OTP for multi-factor authentication using a contactless card. By leveraging cryptograms generated by contactless cards, embodiments of the disclosure may securely verify the identity of the user requesting to perform an operation with minimal risk of fraudulent activity. Furthermore, doing so ensures that OTP codes are only generated when the user has access to a contactless card as well as a computing device with a secure application for facilitating the cryptogram verification with the server. Furthermore, by providing a simplified OTP generation process, more requests may be handled by the server, thereby improving system performance.

With general reference to notations and nomenclature used herein, one or more portions of the detailed description which follows may be presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substances of their work to others skilled in the art. A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities.

Further, these manipulations are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. However, no such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein that form part of one or more embodiments. Rather, these operations are machine operations. Useful machines for performing operations of various embodiments include digital computers as selectively activated or configured by a computer program stored within that is written in accordance with the teachings herein, and/or include apparatus specially constructed for the required purpose or a digital computer. Various embodiments also relate to apparatus or systems for performing these operations. These apparatuses may be specially constructed for the required purpose. The required structure for a variety of these machines will be apparent from the description given.

Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. The intention is to cover all modification, equivalents, and alternatives within the scope of the claims.

<FIG> depicts an exemplary computing architecture <NUM>, also referred to as a system, consistent with disclosed embodiments. Although the computing architecture <NUM> shown in <FIG> has a limited number of elements in a certain topology, it may be appreciated that the computing architecture <NUM> may include more or less elements in alternate topologies as desired for a given implementation.

The computing architecture <NUM> comprises a computing device <NUM>, a server <NUM>, and a contactless card <NUM>. The contactless card <NUM> is representative of any type of payment card, such as a credit card, debit card, ATM card, gift card, and the like. The contactless card <NUM> may comprise one or more communications interfaces <NUM>, such as a radio frequency identification (RFID) chip, configured to communicate with a communications interface <NUM> (also referred to herein as a "card reader", a "wireless card reader", and/or a "wireless communications interface") of the computing devices <NUM> via NFC, the EMV standard, or other short-range protocols in wireless communication. Although NFC is used as an example communications protocol herein, the disclosure is equally applicable to other types of wireless communications, such as the EMV standard, Bluetooth, and/or Wi-Fi.

The computing device <NUM> is representative of any number and type of computing device, such as smartphones, tablet computers, wearable devices, laptops, portable gaming devices, virtualized computing system, merchant terminals, point-of-sale systems, servers, desktop computers, and the like. A mobile device is used as an example of the computing device <NUM>, but should not be considered limiting of the disclosure. The server <NUM> is representative of any type of computing device, such as a server, workstation, compute cluster, cloud computing platform, virtualized computing system, and the like. Although not depicted for the sake of clarity, the computing device <NUM>, contactless card <NUM>, and server <NUM> each include one or more processor circuits to execute programs, code, and/or instructions.

As shown, a memory <NUM> of the contactless card <NUM> includes an applet <NUM>, a counter <NUM>, a master key <NUM>, a diversified key <NUM>, and a unique customer identifier (ID) <NUM>. The applet <NUM> is executable code configured to perform the operations described herein. The counter <NUM>, master key <NUM>, diversified key <NUM>, and customer ID <NUM> are used to provide security in the system <NUM> as described in greater detail below.

As shown, a memory <NUM> of the mobile device <NUM> includes an instance of an operating system (OS) <NUM>. Example operating systems <NUM> include the Android® OS, iOS®, macOS®, Linux®, and Windows® operating systems. As shown, the OS <NUM> includes an account application <NUM> and a web browser <NUM>. The account application <NUM> allows users to perform various account-related operations, such as activating payment cards, viewing account balances, purchasing items, processing payments, and the like. In some embodiments, a user may authenticate using authentication credentials to access certain features of the account application <NUM>. For example, the authentication credentials may include a username (or login) and password, biometric credentials (e.g., fingerprints, Face ID, etc.), and the like. The web browser <NUM> is an application that allows the device <NUM> to access information via the network <NUM> (e.g., via the Internet).

As shown, a memory <NUM> of the server <NUM> includes an authentication application <NUM>, which includes an OTP generator <NUM>. Although depicted as integrated components of the server <NUM>, in some embodiments, the authentication application <NUM> and the OTP generator <NUM> may be separated into distinct components. Furthermore, the authentication application <NUM> and/or the OTP generator <NUM> may be implemented in hardware, software, and/or a combination of hardware and software.

In some embodiments, to secure the account application <NUM> and/or associated data, e.g., details of the user's account in the account database <NUM>, the system <NUM> may provide for secure generation of OTPs using the contactless card <NUM>. For example, a user may provide authentication credentials to the account application <NUM>, such as a username/password that are validated by the account application <NUM> (e.g., using a local instance of the account database <NUM> and/or transmitting the credentials to the server <NUM> for validation). Once validated, the account application <NUM> may instruct the user to tap the contactless card <NUM> to the computing device <NUM>.

In the embodiment depicted in <FIG>, the user may tap the contactless card <NUM> to the computing device <NUM> (or otherwise bring the contactless card <NUM> within communications range of the card reader <NUM> of the device <NUM>). The applet <NUM> of the contactless card <NUM> may then generate a URL <NUM> that is directed to a resource, such as the server <NUM>, the authentication application <NUM>, and/or the OTP generator <NUM>. In some embodiments, the applet <NUM> constructs the URL <NUM> according to one or more rules. In some embodiments, the contactless card <NUM> stores a plurality of URLs <NUM> and the applet <NUM> selects the URL <NUM> from the plurality of URLs <NUM> based on one or more rules. In some embodiments, the applet <NUM> may generate the URL <NUM> by selecting a URLs <NUM> and adding dynamic data, such as a cryptogram <NUM>, as one or more parameters of the URL.

The cryptogram <NUM> may be based on the customer ID <NUM> of the contactless card <NUM>. The cryptogram <NUM> may be generated based on any suitable cryptographic technique. In some embodiments, the applet <NUM> may include the URL <NUM>, the cryptogram <NUM>, and an unencrypted identifier (e.g., the customer ID <NUM>, an identifier of the contactless card <NUM>, and/or any other unique identifier) as part of a data package. In at least one embodiment, the data package is an NDEF file.

As stated, the computing architecture <NUM> is configured to implement key diversification to secure data, which may be referred to as a key diversification technique herein. Generally, the server <NUM> (or another computing device) and the contactless card <NUM> may be provisioned with the same master key <NUM> (also referred to as a master symmetric key). More specifically, each contactless card <NUM> is programmed with a distinct master key <NUM> that has a corresponding pair in the server <NUM>. For example, when a contactless card <NUM> is manufactured, a unique master key <NUM> may be programmed into the memory <NUM> of the contactless card <NUM>. Similarly, the unique master key <NUM> may be stored in a record of a customer associated with the contactless card <NUM> in the account database <NUM> of the server <NUM> (and/or stored in a different secure location, such as the hardware security module (HSM) <NUM>). The master key <NUM> may be kept secret from all parties other than the contactless card <NUM> and server <NUM>, thereby enhancing security of the system <NUM>. In some embodiments, the applet <NUM> of the contactless card <NUM> may encrypt and/or decrypt data (e.g., the customer ID <NUM>) using the master key <NUM> and the data as input a cryptographic algorithm. For example, encrypting the customer ID <NUM> with the master key <NUM> may result in the cryptogram <NUM>. Similarly, the server <NUM> may encrypt and/or decrypt data associated with the contactless card <NUM> using the corresponding master key <NUM>.

In other embodiments, the master keys <NUM> of the contactless card <NUM> and server <NUM> may be used in conjunction with the counters <NUM> to enhance security using key diversification. The counters <NUM> comprise values that are synchronized between the contactless card <NUM> and server <NUM>. The counter <NUM> may comprise a number that changes each time data is exchanged between the contactless card <NUM> and the server <NUM> (and/or the contactless card <NUM> and the computing device <NUM>). When preparing to send data (e.g., to the server <NUM> and/or the device <NUM>), the applet <NUM> of the contactless card <NUM> may increment the counter <NUM>. The applet <NUM> of the contactless card <NUM> may then provide the master key <NUM> and counter <NUM> as input to a cryptographic algorithm, which produces a diversified key <NUM> as output. The cryptographic algorithm may include encryption algorithms, hash-based message authentication code (HMAC) algorithms, cipher-based message authentication code (CMAC) algorithms, and the like. Nonlimiting examples of the cryptographic algorithm may include a symmetric encryption algorithm such as 3DES or AES <NUM>; a symmetric HMAC algorithm, such as HMAC-SHA-<NUM>; and a symmetric CMAC algorithm such as AES-CMAC. Examples of key diversification techniques are described in greater detail in <CIT>.

Continuing with the key diversification example, the applet <NUM> may then encrypt the data (e.g., the customer ID <NUM> and/or any other data) using the diversified key <NUM> and the data as input to the cryptographic algorithm. For example, encrypting the customer ID <NUM> with the diversified key <NUM> may result in an encrypted customer ID (e.g., a cryptogram <NUM>). In some embodiments, the cryptogram <NUM> is included in as a parameter of the URL <NUM>. In other embodiments, the cryptogram <NUM> is not a parameter of the URL <NUM>, but is transmitted with the URL <NUM> in a data package such as an NDEF file. The operating system <NUM> may then read the data package including the URL <NUM> and cryptogram <NUM> via the communications interface <NUM> of the computing device <NUM>.

As stated, the cryptogram <NUM> may be a parameter of the URL <NUM>. For example, the URL <NUM> may be "http://www. com/OTPgenerator?param=ABC123". In such an example, the cryptogram <NUM> may correspond to the parameter "ABC123". However, if the cryptogram <NUM> is not a parameter of the URL <NUM>, the URL <NUM> may be "http://www. com/OTPgenerator. " Regardless of whether the URL <NUM> includes the cryptogram <NUM> as a parameter, the URL <NUM> may be registered with the account application <NUM>, which causes the operating system <NUM> to launch the account application <NUM>, and provide the URL <NUM> and cryptogram <NUM> to the account application <NUM> as input.

The account application <NUM> may then transmit the cryptogram <NUM> to the server <NUM> with a request to generate an OTP. In embodiments where the URL <NUM> includes the cryptogram <NUM> as a parameter, the account application <NUM> extracts the cryptogram <NUM> from the URL <NUM> and transmits the request with cryptogram <NUM> to an address associated with the OTP generator <NUM>, e.g., at least a portion of the URL <NUM>. In some embodiments, the <NUM> makes an application programming interface (API) call to the OTP generator <NUM>. Further still, the account application <NUM> may include another identifier, such as the unencrypted customer ID <NUM> provided by the applet <NUM> in the data package. In some embodiments, the another identifier may be an identifier of the contactless card <NUM>, an account identifier, and the like. In such embodiments, the account application <NUM> may include an instance of one or more portions of the account database <NUM> to determine the another identifier.

<FIG> depicts an embodiment where the account application <NUM> transmits an OTP request <NUM> comprising the cryptogram <NUM> and the unencrypted identifier to the server <NUM>. Once received, the server <NUM> may attempt to authenticate the cryptogram <NUM>. For example, the authentication application <NUM> may attempt to decrypt the cryptogram <NUM> using a copy of the master key <NUM> stored by the server <NUM>. In some embodiments, the authentication application <NUM> may identify the master key <NUM> and counter <NUM> using the unencrypted customer ID <NUM> (or other identifier) provided by the account application <NUM> to the server <NUM>. In some examples, the authentication application <NUM> may provide the master key <NUM> and counter <NUM> as input to the cryptographic algorithm, which produces a diversified key <NUM> as output. The resulting diversified key <NUM> may correspond to the diversified key <NUM> of the contactless card <NUM>, which may be used to decrypt the cryptogram <NUM>.

Regardless of the decryption technique used, the authentication application <NUM> may successfully decrypt the cryptogram <NUM>, thereby verifying or authenticating the cryptogram <NUM> in the OTP request <NUM> (e.g., by comparing the customer ID <NUM> that is produced by decrypting the cryptogram <NUM> to a known customer ID stored in the account database <NUM>, and/or based on an indication that the decryption using the master key <NUM> and/or diversified key <NUM> was successful). Although the keys <NUM>, <NUM> are depicted as being stored in the memory <NUM>, the keys may be stored elsewhere, such as in a secure element and/or the HSM <NUM>. In such embodiments, the secure element and/or the HSM <NUM> may decrypt the cryptogram <NUM> using the master key <NUM> and/or diversified key <NUM> and a cryptographic function. Similarly, the secure element and/or HSM <NUM> may generate the diversified key <NUM> based on the master key <NUM> and counter <NUM> as described above. If the decryption is successful, the authentication application <NUM> may identify contact information for the user, e.g., an email address, phone number, a device identifier registered to the instance of the account application <NUM>, a device identifier of the computing device <NUM>, etc., stored in the account database <NUM>. The authentication application <NUM> may identify the contact information based on the unencrypted identifier included in the OTP request <NUM>. The authentication application <NUM> may then instruct the OTP generator <NUM> to generate an OTP and transmit the OTP to the identified contact information.

If, however, the authentication application <NUM> is unable to decrypt the cryptogram <NUM> to yield the expected result (e.g., the customer ID <NUM> of the account associated with the contactless card <NUM>), the authentication application <NUM> does not validate the cryptogram <NUM>. In such an example, the authentication application <NUM> determines to refrain from generating an OTP. The authentication application <NUM> may transmit an indication of the failed decryption to the account application <NUM>.

<FIG> depicts an embodiment where the authentication application <NUM> transmits a decryption result <NUM> to the account application <NUM>. The decryption result <NUM> generally indicates whether the server <NUM> decrypted the cryptogram <NUM> or did not decrypt the cryptogram <NUM>. In the example depicted in <FIG>, the decryption result <NUM> indicates that the server <NUM> decrypted the cryptogram <NUM>. The account application <NUM> may use the decryption result <NUM> to determine whether the cryptogram <NUM> was decrypted. Based on the successful decryption, the OTP generator <NUM> may generate and transmit an OTP <NUM> to the computing device <NUM> based on the determined contact information. The OTP <NUM> may be any alphanumeric string of any length. If the contact information is a phone number, the OTP generator <NUM> may transmit the OTP <NUM> via a short message service (SMS) message. If the contact information is an email address, the OTP generator <NUM> may transmit the OTP <NUM> via email. If the contact information is a device identifier, the OTP generator <NUM> may transmit the OTP <NUM> as part of a push notification directed to the computing device <NUM>.

The user may then provide the received OTP as input to the account application <NUM> via a user interface. The account application <NUM> may then compare the input provided by the user to an instance of the OTP <NUM> received from the OTP generator <NUM>. In another embodiment, the account application <NUM> may transmit the user input to the OTP generator <NUM>, which performs the comparison. If the OTP generator <NUM> performs the comparison, the OTP generator <NUM> transmits a comparison result to the account application <NUM>. In some embodiments, the user may provide the input to another application, such as the web browser <NUM> that has loaded a page associated with the OTP generator <NUM>. The web page may then perform the comparison. If the comparison results in a match, the multi-factor authentication may be completed, and the user may be able to perform one or more requested operations. For example, the user may view account attributes, perform an operation associated with the account, make a payment, transfer funds, view balances, etc..

<FIG> is a schematic 200a illustrating an embodiment where a contactless card <NUM> is tapped to a computing device <NUM>. While the computing device <NUM> is depicted as outputting a screen (e.g., a home screen) of the operating system <NUM>, the computing device <NUM> may generally be in any state. For example, the user may be using another application, such as the web browser <NUM>, when tapping the contactless card <NUM> to the computing device <NUM>.

As stated, when the contactless card <NUM> is tapped to the computing device <NUM>, the applet <NUM> may generate a cryptogram <NUM> and URL <NUM>. In some embodiments, the cryptogram <NUM> is a parameter of the URL <NUM>. The applet <NUM> may further include an identifier, such as an unencrypted customer ID <NUM>, an identifier of the contactless card <NUM>, and the like. If the cryptogram <NUM> is a parameter of the URL <NUM>, the unencrypted identifier may also be a parameter of the URL <NUM>. Regardless of whether the cryptogram <NUM> and/or unencrypted identifier are parameters of the URL <NUM>, the cryptogram <NUM>, unencrypted identifier, and the URL <NUM> may be included in a data package, such as an NDEF file, that is read by the computing device <NUM>. As shown, responsive to receiving the data package, the operating system <NUM> may launch the account application <NUM>, as the URL <NUM> (or a portion thereof) may be registered with the account application <NUM> in the operating system <NUM>.

<FIG> is a schematic 200b illustrating an embodiment where the account application <NUM> is opened responsive to the operating system <NUM> reading the URL <NUM> received from the contactless card <NUM>. As shown, the account application <NUM> instructs the user to provide a first authentication factor, which may be biometric credentials. The account application <NUM> may verify the biometric credentials, and based on the verification, generate an OTP request <NUM> for an OTP <NUM> from the OTP generator <NUM>. As stated, the account application <NUM> may transmit the cryptogram <NUM> and an unencrypted identifier to the OTP generator <NUM>. In some embodiments, the OTP request <NUM> may be an API call.

The authentication application <NUM> may then attempt to decrypt the cryptogram <NUM> as described in greater detail above. If the decryption is successful, the authentication application <NUM> may identify contact information for the user's account in the account database <NUM>. In some embodiments, the contact information is identified based on the unencrypted identifier, e.g., the unencrypted customer ID <NUM>, a device ID, and the like. The authentication application <NUM> may then instruct the OTP generator <NUM> to generate an OTP <NUM> and transmit the OTP <NUM> to the contact information. The authentication application <NUM> may also transmit a decryption result <NUM> to the account application <NUM>.

<FIG> is a schematic 200c illustrating an embodiment where the OTP <NUM> is sent to the computing device <NUM> as a push notification <NUM>. The user may be instructed to enter the OTP <NUM> in the input field <NUM>. As shown, the push notification <NUM> allows the user to select the push notification <NUM> to autofill the OTP <NUM> to the field <NUM>. For example, when selected, an autofill service (not pictured) of the operating system <NUM> may copy the OTP <NUM> and fill the OTP <NUM> into the field <NUM>. In another example, the OTP <NUM> may be copied to a clipboard (not pictured) of the operating system <NUM>. Doing so allows the user to paste the OTP <NUM> from the clipboard to the field <NUM>.

As shown, the OTP <NUM> may be entered as input to field <NUM>. The account application <NUM> may then verify the OTP <NUM> entered into field <NUM>, e.g., by comparing the input to an instance of the OTP <NUM> received from the OTP generator <NUM>. In another example, the account application <NUM> provides the input entered into field <NUM> to the OTP generator <NUM>, which performs the comparison, and returns a result of the comparison to the account application <NUM>. If the comparison results in a match, the account application <NUM> may determine the multi-factor authentication is complete.

<FIG> is a schematic 200d illustrating an embodiment where the input provided in field <NUM> matches the OTP <NUM>. Based on the match and the decryption of the cryptogram <NUM>, the user may be logged into their account in the account application <NUM>. As shown, the account application <NUM> displays various account attributes, e.g., account balances. Embodiments are not limited in this context, as the MFA using the OTP <NUM> may be used to authorize any requested operation.

Operations for the disclosed embodiments may be further described with reference to the following figures. Some of the figures may include a logic flow. Although such figures presented herein may include a particular logic flow, it can be appreciated that the logic flow merely provides an example of how the general functionality as described herein can be implemented. Further, a given logic flow does not necessarily have to be executed in the order presented unless otherwise indicated. Moreover, not all acts illustrated in a logic flow may be required in some embodiments. In addition, the given logic flow may be implemented by a hardware element, a software element executed by a processor, or any combination thereof.

<FIG> illustrates an embodiment of a logic flow, or routine, <NUM>. The logic flow <NUM> may be representative of some or all of the operations executed by one or more embodiments described herein. For example, the logic flow <NUM> may include some or all of the operations to enable secure generation of an OTP using a contactless card. Embodiments are not limited in this context.

In block <NUM>, routine <NUM> receives, by an operating system <NUM> executing on a processor of a computing device <NUM>, a uniform resource locator (URL) <NUM> and a cryptogram <NUM> from a contactless card <NUM> associated with an account. In block <NUM>, routine <NUM> launches, by the operating system <NUM> responsive to receiving the URL <NUM>, the account application <NUM> associated with the contactless card <NUM>. In some embodiments, however, the account application <NUM> is executing in the foreground of the operating system <NUM> and need not be launched. In such embodiments, the user may request to perform an operation, such as viewing an account balance, transferring funds, etc..

In block <NUM>, routine <NUM> transmits, by the account application <NUM>, the cryptogram <NUM> to an authentication server <NUM>. The account application <NUM> may further include an unencrypted identifier, e.g., the customer ID <NUM> and/or a device identifier to the authentication application <NUM>. In block <NUM>, routine <NUM> receives, by the account application <NUM>, a decryption result <NUM> from the server <NUM> indicating the authentication server <NUM> decrypted the cryptogram <NUM>.

In block <NUM>, routine <NUM> transmits, by the account application <NUM> based on the decryption result, a request for a one-time passcode (OTP) comprising an identifier to the server <NUM>. The identifier may be the unencrypted customer ID <NUM>, the device identifier, and/or an identifier of the contactless card <NUM>. In block <NUM>, routine <NUM> determines, by the server <NUM> based on the identifier, contact information in an account database <NUM>. The contact information may include, but is not limited to, a phone number, email address, device identifier, etc. In block <NUM>, routine <NUM> receives, by the computing device <NUM> at the determined contact information, the OTP <NUM> from the OTP generator <NUM>. In block <NUM>, routine <NUM> receives, by the account application <NUM>, an input value from the user. In block <NUM>, routine <NUM> compares, by the account application <NUM>, the input value to a copy of the OTP received from the OTP generator <NUM>. In block <NUM>, routine <NUM> determines, by the account application <NUM>, that the comparison results in a match. In block <NUM>, routine <NUM> displays, by the account application <NUM> based on the decryption result <NUM> and the determination that the comparison results in the match, one or more attributes of the account on the device. Additionally and/or alternatively, the account application <NUM> may authorize performance of an operation requested by the user based on the determination that the comparison results in a match and the decryption result <NUM>.

In block <NUM>, routine <NUM> receives, by an operating system <NUM> executing on a processor of a computing device <NUM>, a uniform resource locator (URL) <NUM> and a cryptogram <NUM> from a contactless card <NUM> associated with an account. The applet <NUM> may generate the cryptogram <NUM> as described in greater detail herein. The applet <NUM> may further transmit an unencrypted identifier, e.g., customer ID <NUM> to the computing device <NUM>. In block <NUM>, routine <NUM> launches, by the operating system <NUM> responsive to receiving the URL <NUM>, an account application <NUM> associated with the contactless card <NUM>. In block <NUM>, routine <NUM> transmits, by the account application <NUM>, the cryptogram <NUM> to an authentication server <NUM>. The account application <NUM> may further transmit the unencrypted identifier to the server <NUM>.

In block <NUM>, routine <NUM> receives, by the account application <NUM>, a decryption result <NUM> from the authentication server <NUM> indicating the authentication server <NUM> decrypted the cryptogram <NUM>. In block <NUM>, routine <NUM> transmits, by the account application <NUM> based on the decryption result <NUM>, a request for a one-time passcode (OTP) comprising an identifier to the URL. The identifier may be the unencrypted customer ID <NUM>, the device identifier, and/or an identifier of the contactless card <NUM>. In block <NUM>, routine <NUM> determines, by the server <NUM> based on the identifier, contact information in an account database <NUM>. The contact information may include, but is not limited to, a phone number, email address, device identifier, etc. In block <NUM>, routine <NUM> receives, by the computing device <NUM> at the determined contact information, the OTP <NUM> from an OTP generator <NUM> at the URL <NUM>. In block <NUM>, routine <NUM> receives, by the account application <NUM>, an input value. In block <NUM>, routine <NUM> compares, by the account application <NUM>, the input value to a copy of the OTP <NUM> received from the OTP generator <NUM>. In block <NUM>, routine <NUM> determines, by the application, that the comparison results in a match. In block <NUM>, routine <NUM> displays, by the account application <NUM> based on the determination that the comparison results in the match and based on the decryption result <NUM>, one or more attributes of the account on the device.

<FIG> is a schematic <NUM> illustrating an example configuration of a contactless card <NUM>, which may include a payment card, such as a credit card, debit card, or gift card, issued by a service provider as displayed as service provider indicia <NUM> on the front or back of the contactless card <NUM>. In some examples, the contactless card <NUM> is not related to a payment card, and may include, without limitation, an identification card. In some examples, the transaction card may include a dual interface contactless payment card, a rewards card, and so forth. The contactless card <NUM> may include a substrate <NUM>, which may include a single layer or one or more laminated layers composed of plastics, metals, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyesters, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card <NUM> may have physical characteristics compliant with the ID-<NUM> format of the ISO/IEC <NUM> standard, and the transaction card may otherwise be compliant with the ISO/IEC <NUM> standard. However, it is understood that the contactless card <NUM> according to the present disclosure may have different characteristics, and the present disclosure does not require a transaction card to be implemented in a payment card.

The contactless card <NUM> may also include identification information <NUM> displayed on the front and/or back of the card, and a contact pad <NUM>. The contact pad <NUM> may include one or more pads and be configured to establish contact with another client device, such as an ATM, a user device, smartphone, laptop, desktop, or tablet computer via transaction cards. The contact pad may be designed in accordance with one or more standards, such as ISO/IEC <NUM> standard, and enable communication in accordance with the EMV protocol. The contactless card <NUM> may also include processing circuitry, antenna and other components as will be further discussed in <FIG>. These components may be located behind the contact pad <NUM> or elsewhere on the substrate <NUM>, e.g. within a different layer of the substrate <NUM>, and may electrically and physically coupled with the contact pad <NUM>. The contactless card <NUM> may also include a magnetic strip or tape, which may be located on the back of the card (not shown in <FIG>). The contactless card <NUM> may also include a Near-Field Communication (NFC) device coupled with an antenna capable of communicating via the NFC protocol. Embodiments are not limited in this manner.

As illustrated in <FIG>, the contact pad <NUM> of contactless card <NUM> may include processing circuitry <NUM> for storing, processing, and communicating information, including a processor <NUM>, a memory <NUM>, and one or more communications interface <NUM>. It is understood that the processing circuitry <NUM> may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary to perform the functions described herein.

The memory <NUM> may be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM, and EEPROM, and the contactless card <NUM> may include one or more of these memories. A read-only memory may be factory programmable as read-only or one-time programmable. One-time programmability provides the opportunity to write once then read many times. A write once/read-multiple memory may be programmed at a point in time after the memory chip has left the factory. Once the memory is programmed, it may not be rewritten, but it may be read many times. A read/write memory may be programmed and re-programed many times after leaving the factory. A read/write memory may also be read many times after leaving the factory. In some instances, the memory <NUM> may be encrypted memory utilizing an encryption algorithm executed by the processor <NUM> to encrypted data.

The memory <NUM> may be configured to store one or more applets <NUM>, one or more counters <NUM>, a customer ID <NUM>, the master key <NUM>, diversified key <NUM>, and URLs <NUM>. The one or more applets <NUM> may comprise one or more software applications configured to execute on one or more contactless cards, such as a Java® Card applet. However, it is understood that applet <NUM> are not limited to Java Card applets, and instead may be any software application operable on contactless cards or other devices having limited memory. The one or more counter <NUM> may comprise a numeric counter sufficient to store an integer. The customer ID <NUM> may comprise a unique alphanumeric identifier assigned to a user of the contactless card <NUM>, and the identifier may distinguish the user of the contactless card from other contactless card users. In some examples, the customer ID <NUM> may identify both a customer and an account assigned to that customer and may further identify the contactless card <NUM> associated with the customer's account.

The processor <NUM> and memory elements of the foregoing exemplary embodiments are described with reference to the contact pad <NUM>, but the present disclosure is not limited thereto. It is understood that these elements may be implemented outside of the contact pad <NUM> or entirely separate from it, or as further elements in addition to processor <NUM> and memory <NUM> elements located within the contact pad <NUM>.

In some examples, the contactless card <NUM> may comprise one or more antenna(s) <NUM>. The one or more antenna(s) <NUM> may be placed within the contactless card <NUM> and around the processing circuitry <NUM> of the contact pad <NUM>. For example, the one or more antenna(s) <NUM> may be integral with the processing circuitry <NUM> and the one or more antenna(s) <NUM> may be used with an external booster coil. As another example, the one or more antenna(s) <NUM> may be external to the contact pad <NUM> and the processing circuitry <NUM>.

In an embodiment, the coil of contactless card <NUM> may act as the secondary of an air core transformer. The terminal may communicate with the contactless card <NUM> by cutting power or amplitude modulation. The contactless card <NUM> may infer the data transmitted from the terminal using the gaps in the power connection of the contactless card <NUM>, which may be functionally maintained through one or more capacitors. The contactless card <NUM> may communicate back by switching a load on the coil of the contactless card <NUM> or load modulation. Load modulation may be detected in the terminal's coil through interference. More generally, using the antenna(s) <NUM>, processor <NUM>, and/or the memory <NUM>, the contactless card <NUM> provides a communications interface to communicate via NFC, Bluetooth, and/or Wi-Fi communications.

As explained above, contactless card <NUM> may be built on a software platform operable on smart cards or other devices having limited memory, such as JavaCard, and one or more or more applications or applets may be securely executed. Applet <NUM> may be added to contactless cards to provide a one-time password (OTP) for multifactor authentication (MFA) in various mobile application-based use cases. Applet <NUM> may be configured to respond to one or more requests, such as near field data exchange requests, from a reader, such as a mobile NFC reader (e.g., of a mobile computing device <NUM> or point-of-sale terminal), and produce an NDEF message that comprises a cryptographically secure OTP encoded as an NDEF text tag. The NDEF message may include the URL <NUM>, the cryptogram <NUM>, and any other data.

One example of an NDEF OTP is an NDEF short-record layout (SR=<NUM>). In such an example, one or more applets <NUM> may be configured to encode the OTP as an NDEF type <NUM> well known type text tag. In some examples, NDEF messages may comprise one or more records. The applet <NUM> may be configured to add one or more static tag records in addition to the OTP record.

In some examples, the one or more applets <NUM> may be configured to emulate an RFID tag. The RFID tag may include one or more polymorphic tags. In some examples, each time the tag is read, different cryptographic data is presented that may indicate the authenticity of the contactless card. Based on the one or more applets <NUM>, an NFC read of the tag may be processed, the data may be transmitted to a server, such as a server of a banking system, and the data may be validated at the server.

In some examples, the contactless card <NUM> and server may include certain data such that the card may be properly identified. The contactless card <NUM> may include one or more unique identifiers (not pictured). Each time a read operation takes place, the counter <NUM> may be configured to increment. In some examples, each time data from the contactless card <NUM> is read (e.g., by a mobile device), the counter <NUM> is transmitted to the server for validation and determines whether the counter <NUM> are equal (as part of the validation) to a counter of the server.

The one or more counter <NUM> may be configured to prevent a replay attack. For example, if a cryptogram has been obtained and replayed, that cryptogram is immediately rejected if the counter <NUM> has been read or used or otherwise passed over. If the counter <NUM> has not been used, it may be replayed. In some examples, the counter that is incremented on the contactless card <NUM> is different from the counter that is incremented for transactions. The contactless card <NUM> is unable to determine the application transaction counter <NUM> since there is no communication between applets <NUM> on the contactless card <NUM>. In some examples, the contactless card <NUM> may comprise a first applet <NUM>-<NUM>, which may be a transaction applet, and a second applet <NUM>-<NUM>. Each applet <NUM>-<NUM> and <NUM>-<NUM> may comprise a respective counter <NUM>.

In some examples, the counter <NUM> may get out of sync. In some examples, to account for accidental reads that initiate transactions, such as reading at an angle, the counter <NUM> may increment but the application does not process the counter <NUM>. In some examples, when the mobile device <NUM> is woken up, NFC may be enabled and the device <NUM> may be configured to read available tags, but no action is taken responsive to the reads.

To keep the counter <NUM> in sync, an application, such as a background application, may be executed that would be configured to detect when the mobile device <NUM> wakes up and synchronize with the server of a banking system indicating that a read that occurred due to detection to then move the counter <NUM> forward. In other examples, Hashed One Time Password may be utilized such that a window of mis-synchronization may be accepted. For example, if within a threshold of <NUM>, the counter <NUM> may be configured to move forward. But if within a different threshold number, for example within <NUM> or <NUM>, a request for performing re-synchronization may be processed which requests via one or more applications that the user tap, gesture, or otherwise indicate one or more times via the user's device. If the counter <NUM> increases in the appropriate sequence, then it possible to know that the user has done so.

The key diversification technique described herein with reference to the counter <NUM>, master key, and diversified key, is one example of encryption and/or decryption a key diversification technique. This example key diversification technique should not be considered limiting of the disclosure, as the disclosure is equally applicable to other types of key diversification techniques.

During the creation process of the contactless card <NUM>, two cryptographic keys may be assigned uniquely per card. The cryptographic keys may comprise symmetric keys which may be used in both encryption and decryption of data. Triple DES (3DES) algorithm may be used by EMV and it is implemented by hardware in the contactless card <NUM>. By using the key diversification process, one or more keys may be derived from a master key based upon uniquely identifiable information for each entity that requires a key.

In some examples, to overcome deficiencies of 3DES algorithms, which may be susceptible to vulnerabilities, a session key may be derived (such as a unique key per session) but rather than using the master key, the unique card-derived keys and the counter may be used as diversification data. For example, each time the contactless card <NUM> is used in operation, a different key may be used for creating the message authentication code (MAC) and for performing the encryption. This results in a triple layer of cryptography. The session keys may be generated by the one or more applets and derived by using the application transaction counter with one or more algorithms (as defined in EMV <NUM> Book <NUM> A1. <NUM> Common Session Key Derivation).

Further, the increment for each card may be unique, and assigned either by personalization, or algorithmically assigned by some identifying information. For example, odd numbered cards may increment by <NUM> and even numbered cards may increment by <NUM>. In some examples, the increment may also vary in sequential reads, such that one card may increment in sequence by <NUM>, <NUM>, <NUM>, <NUM>, <NUM>,. The specific sequence or algorithmic sequence may be defined at personalization time, or from one or more processes derived from unique identifiers. This can make it harder for a replay attacker to generalize from a small number of card instances.

The authentication message may be delivered as the content of a text NDEF record in hexadecimal ASCII format. In another example, the NDEF record may be encoded in hexadecimal format.

<FIG> illustrates an NDEF short-record layout (SR=<NUM>) data structure <NUM> according to an example embodiment. One or more applets may be configured to encode the OTP as an NDEF type <NUM> well known type text tag. In some examples, NDEF messages may comprise one or more records. The applets may be configured to add one or more static tag records in addition to the OTP record. Exemplary tags include, without limitation, Tag type: well known type, text, encoding English (en); Applet ID: D2760000850101; Capabilities: read-only access; Encoding: the authentication message may be encoded as ASCII hex; type-length-value (TLV) data may be provided as a personalization parameter that may be used to generate the NDEF message. In an embodiment, the authentication template may comprise the first record, with a well-known index for providing the actual dynamic authentication data. The data structure <NUM> may include the URL <NUM>, the cryptogram <NUM>, and any other data provided by the applet <NUM>.

<FIG> illustrates an embodiment of an exemplary computer architecture <NUM> suitable for implementing various embodiments as previously described. In one embodiment, the computer architecture <NUM> may include or be implemented as part of computing architecture <NUM>.

As used in this application, the terms "system" and "component" are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing computer architecture <NUM>. For example, a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Further, components may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the unidirectional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

The computer architecture <NUM> includes various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components, power supplies, and so forth.

As shown in <FIG>, the computer architecture <NUM> includes a processor <NUM>, a system memory <NUM> and a system bus <NUM>. The processor <NUM> can be any of various commercially available processors.

The system bus <NUM> provides an interface for system components including, but not limited to, the system memory <NUM> to the processor <NUM>. Interface adapters may connect to the system bus <NUM> via slot architecture.

The computer architecture <NUM> may include or implement various articles of manufacture. An article of manufacture may include a computer-readable storage medium to store logic. Examples of a computer-readable storage medium may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of logic may include executable computer program instructions implemented using any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. Embodiments may also be at least partly implemented as instructions contained in or on a non-transitory computer-readable medium, which may be read and executed by one or more processors to enable performance of the operations described herein.

In the illustrated embodiment shown in <FIG>, the system memory <NUM> can include non-volatile <NUM> and/or volatile <NUM>. A basic input/output system (BIOS) can be stored in the non-volatile <NUM>.

The computer <NUM> may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive <NUM>, a magnetic disk drive <NUM> to read from or write to a removable magnetic disk <NUM>, and an optical disk drive <NUM> to read from or write to a removable optical disk <NUM> (e.g., a CD-ROM or DVD). The hard disk drive <NUM>, magnetic disk drive <NUM> and optical disk drive <NUM> can be connected to system bus <NUM> the by an HDD interface <NUM>, and FDD interface <NUM> and an optical disk drive interface <NUM>, respectively. The HDD interface <NUM> for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE <NUM> interface technologies.

The drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For example, a number of program modules can be stored in the drives and non-volatile <NUM>, and volatile <NUM>, including an operating system <NUM>, one or more applications <NUM>, other program modules <NUM>, and program data <NUM>. In one embodiment, the one or more applications <NUM>, other program modules <NUM>, and program data <NUM> can include, for example, the various applications and/or components of the system <NUM>.

A user can enter commands and information into the computer <NUM> through one or more wire/wireless input devices, for example, a keyboard <NUM> and a pointing device, such as a mouse <NUM>. Other input devices may include microphones, infra-red (IR) remote controls, radio-frequency (RF) remote controls, game pads, stylus pens, card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, track pads, sensors, styluses, and the like. These and other input devices are often connected to the processor <NUM> through an input device interface <NUM> that is coupled to the system bus <NUM> but can be connected by other interfaces such as a parallel port, IEEE <NUM> serial port, a game port, a USB port, an IR interface, and so forth.

A monitor <NUM> or other type of display device is also connected to the system bus <NUM> via an interface, such as a video adapter <NUM>.

The computer <NUM> may operate in a networked environment using logical connections via wire and/or wireless communications to one or more remote computers, such as a remote computer(s) <NUM>. The remote computer(s) <NUM> can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all the elements described relative to the computer <NUM>, although, for purposes of brevity, only a memory and/or storage device <NUM> is illustrated. The logical connections depicted include wire/wireless connectivity to a local area network <NUM> and/or larger networks, for example, a wide area network <NUM>.

When used in a local area network <NUM> networking environment, the computer <NUM> is connected to the local area network <NUM> through a wire and/or wireless communication network interface or network adapter <NUM>. The network adapter <NUM> can facilitate wire and/or wireless communications to the local area network <NUM>, which may also include a wireless access point disposed thereon for communicating with the wireless functionality of the network adapter <NUM>.

When used in a wide area network <NUM> networking environment, the computer <NUM> can include a modem <NUM>, or is connected to a communications server on the wide area network <NUM> or has other means for establishing communications over the wide area network <NUM>, such as by way of the Internet. The modem <NUM>, which can be internal or external and a wire and/or wireless device, connects to the system bus <NUM> via the input device interface <NUM>. In a networked environment, program modules depicted relative to the computer <NUM>, or portions thereof, can be stored in the remote memory and/or storage device <NUM>. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

The computer <NUM> is operable to communicate with wire and wireless devices or entities using the IEEE <NUM> family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE <NUM> over-the-air modulation techniques). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wireless technologies, among others. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices. Wi-Fi networks use radio technologies called IEEE <NUM> (a, b, g, n, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE <NUM>-related media and functions).

The various elements of the devices as previously described with reference to <FIG> may include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processors, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. However, determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given implementation.

Such representations, known as "IP cores" may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that make the logic or processor. Some embodiments may be implemented, for example, using a machine-readable medium or article which may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform a method and/or operations in accordance with the embodiments. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software. The machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory, removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, and the like, implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.

Claim 1:
A method, comprising:
receiving, by an operating system, OS, executing on a processor of a device, a uniform resource locator, URL and a cryptogram from a contactless card associated with an account (<NUM>);
launching, by the operating system responsive to receiving the URL, an application (<NUM>) associated with the contactless card (<NUM>);
transmitting, by the application (<NUM>), the cryptogram to an authentication server (<NUM>);
receiving, by the application (<NUM>), a decryption result from the authentication server indicating the authentication server decrypted the cryptogram (<NUM>);
characterised by
transmitting, by the application based on the decryption result, a request for a one-time passcode, OTP comprising an identifier to the URL (<NUM>);
receiving, by the device (<NUM>), the OTP from an OTP generator at the URL;
receiving, by the application (<NUM>), an input value (<NUM>);
comparing, by the application (<NUM>), the input value to a copy of the OTP received from the OTP generator (<NUM>);
determining, by the application (<NUM>), that the comparison results in a match (<NUM>); and
displaying, by the application based on the determination that the comparison results in the match, one or more attributes of the account on the device (<NUM>).