Method, computing device, and storage medium for securely generating one-time passwords using contactless cards.

By generating a one-time password through communication between a contactless card and a computing device, and combining key diversification technology, the vulnerability of OTP to security risks is solved, and secure and efficient user authentication is achieved.

CN116848833BActive Publication Date: 2026-11-10CAPITAL ONE SERVICES LLC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202180094058.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-01-04
Filing Date
2021-12-14
Publication Date
2026-11-10
Estimated Expiration
2041-12-14

AI Technical Summary

Technical Problem

One-time passwords are vulnerable to security risks, especially when devices are not locked in public places or when malicious users gain access to devices, leading to the leakage of account data.

Method used

One-time passwords are generated using contactless cards, which communicate with computing devices to generate and verify passwords. Security is ensured by combining key diversification technology, and OTPs are generated only when the user holds the card and the device is secure.

Benefits of technology

It improves the security of user authentication, reduces the risk of fraudulent activities, simplifies the OTP generation process, and improves system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116848833B_ABST
    Figure CN116848833B_ABST
Patent Text Reader

Abstract

Systems, methods, apparatuses, and computer-readable media for securely generating one-time passwords using contactless cards are disclosed. In one example, the device's operating system (OS) can receive a Uniform Resource Locator (URL) and a password from the contactless card. The OS can launch an application associated with the URL. The application can transmit the password to an authentication server. The application can receive a decryption result from the authentication server, instructing the authentication server to decrypt the password. Based on the decryption result, the application can request an OTP. A processor can receive the OTP from an OTP generator. The application can receive an input value and compare the input value with a copy of the OTP. The application can determine if the comparison matches and, based on the determination of a match, display one or more attributes of the account.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related applications

[0002] This application claims priority to U.S. Patent Application Serial No. 17 / 140,698, filed January 4, 2021, entitled "Secure Generation of One-Time Passwords Using a Contactless Card". The contents of the foregoing application are incorporated herein by reference in their entirety. Technical Field

[0003] The embodiments disclosed herein relate to computing systems. More specifically, the embodiments disclosed herein relate to computing systems for providing secure generation of one-time passwords using contactless cards. Background Technology

[0004] One-time passwords can be used as a second form of authentication. However, one-time passwords are vulnerable to many security risks. For example, if a user does not lock their smartphone in a public place, a passerby could access any password sent to the device. Similarly, if a malicious user gains access to the device and / or account that sent the password, the malicious user could access the password. Doing so could allow a malicious user to access account data or other sensitive information. Summary of the Invention

[0005] Systems, methods, apparatuses, and computer-readable media for securely generating one-time passwords using contactless cards are disclosed. In one example, an operating system (OS) executing on a device's processor can receive a Uniform Resource Locator (URL) and a password from a contactless card associated with an account. The OS can launch an application associated with the contactless card. The application can transmit the password to an authentication server. The application can receive a decryption result from the authentication server, instructing the authentication server to decrypt the password. Based on the decryption result, the application can transmit a request for a one-time password (OTP), including an identifier, to the URL. The processor can receive the OTP from an OTP generator at the URL. The application can receive an input value and compare it with a copy of the OTP received from the OTP generator. The application can determine that the comparison matches and, based on the determination of a match, display one or more attributes of the account on the device. Attached Figure Description

[0006] Figure 1A One aspect of the subject matter is shown according to one embodiment.

[0007] Figure 1B One aspect of the subject matter is shown according to one embodiment.

[0008] Figure 1C One aspect of the subject matter is shown according to one embodiment.

[0009] Figure 2A One aspect of the subject matter is shown according to one embodiment.

[0010] Figure 2B One aspect of the subject matter is shown according to one embodiment.

[0011] Figure 2C One aspect of the subject matter is shown according to one embodiment.

[0012] Figure 2D One aspect of the subject matter is shown according to one embodiment.

[0013] Figure 3 A routine 300 according to one embodiment is shown.

[0014] Figure 4 A routine 400 according to one embodiment is shown.

[0015] Figure 5A A contactless card according to one embodiment is shown.

[0016] Figure 5B A contactless card 136 according to one embodiment is shown.

[0017] Figure 6 A data structure 600 according to one embodiment is shown.

[0018] Figure 7 A computer architecture 700 according to one embodiment is shown. Detailed Implementation

[0019] The embodiments disclosed herein provide techniques for securely generating one-time passcodes (OTPs) that can be used as a second form of authentication. Generally, users may expect to authenticate to an account, complete a purchase, or perform any operation requiring multi-factor authentication (MFA). In one example, a user may tap a contactless card against a computing device to initiate authentication. In response to entering communication range with the device, the contactless card may generate a data packet including a password and a uniform resource locator (URL). The device's operating system may read the data packet and / or the URL and launch an account application associated with the URL on the device. In one example, this account application is associated with the issuer of the contactless card. The account application may forward an OTP request to an OTP generator at the URL. This OTP request may include the password.

[0020] The OTP generator and / or the server associated with it can then attempt to decrypt the password, as described in more detail herein. If decryption is successful, the OTP generator can identify contact information for the associated account, such as a phone number, email address, etc. The OTP generator can then generate an OTP and send it to the identified contact information. The user can then receive the OTP from the OTP generator and provide it as input to the account application. The account application can compare this input with an instance of the OTP received from the OTP generator. If the comparison matches, the account application can verify the OTP and allow the requested action, such as viewing account details, making a purchase, etc. If the comparison does not match, verification may fail, and the account application can refuse or otherwise restrict the execution of the requested action.

[0021] Advantageously, the embodiments disclosed herein provide a security technique for generating OTPs for multi-factor authentication using contactless cards. By utilizing the PIN generated from the contactless card, embodiments of this disclosure can securely verify the identity of a user requesting to perform an operation with minimal risk of fraudulent activity. Furthermore, this ensures that the OTP code is generated only when the user has access to the contactless card and to access the computing device for secure applications facilitating PIN verification with the server. Additionally, by providing a simplified OTP generation process, more requests can be processed by the server, thereby improving system performance.

[0022] Referring generally to the symbols and nomenclature used herein, one or more parts of the following detailed description can be presented in terms of a program procedure that can be executed on a computer or computer network. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. A process herein is generally conceived as a self-consistent sequence of operations that leads to a desired result. These operations are those that require physical manipulation of physical quantities. Typically, though not strictly necessary, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transmitted, combined, compared, and otherwise manipulated. Primarily for the sake of convention, these signals are sometimes referred to as bits, values, elements, symbols, characters, items, numbers, etc., as proven convenient. However, it should be noted that all these and similar terms are to be associated with appropriate physical quantities and are merely convenient notations applied to those quantities.

[0023] Furthermore, these manipulations are often referred to using terms such as addition or comparison, which are generally associated with mental operations performed by a human operator. However, in any of the operations described herein that form part of one or more examples, such an ability of a human operator is not necessary, or in most cases not desirable. Instead, these operations are machine operations. Useful machines for performing the operations of the various embodiments include digital computers selectively activated or configured by computer programs stored therein, written in accordance with the teachings herein, and / or including devices or digital computers specifically constructed for the desired purpose. The various embodiments also relate to devices or systems for performing these operations. These devices can be specifically constructed for the desired purpose. The necessary structures for the various such machines will be apparent from the given description.

[0024] Referring now to the accompanying drawings, wherein the same reference numerals are used throughout to refer to the same elements. In the following description, numerous specific details are set forth for purposes of explanation in order to provide a thorough understanding thereof. However, it will be apparent that novel embodiments may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form to facilitate the description thereto. All modifications, equivalents, and substitutions are intended to cover within the scope of the claims.

[0025] Figure 1A An exemplary computing architecture 100, also referred to as a system, consistent with the disclosed embodiments is depicted. Although Figure 1A-1C The computing architecture 100 shown has a limited number of elements in a particular topology, but it can be appreciated that the computing architecture 100 may include more or fewer elements in alternative topologies desired according to a given implementation.

[0026] The computing architecture 100 includes a computing device 102, a server 104, and a contactless card 136. The contactless card 136 represents any type of payment card, such as a credit card, debit card, ATM card, gift card, etc. The contactless card 136 may include one or more communication interfaces 122, such as a radio frequency identification (RFID) chip, configured to communicate wirelessly with the computing device 102 (also referred to herein as a "card reader," "wireless card reader," and / or "wireless communication interface") via NFC, EMV standards, or other short-range protocols. While NFC is used herein as an example communication protocol, this disclosure is equally applicable to other types of wireless communication, such as EMV standards, Bluetooth, and / or Wi-Fi.

[0027] Computing device 102 represents any number and type of computing devices, such as smartphones, tablets, wearable devices, laptops, portable gaming devices, virtualized computing systems, merchant terminals, point-of-sale systems, servers, desktop computers, etc. Mobile devices are used as examples of computing device 102, but should not be considered as limiting this disclosure. Server 104 represents any type of computing device, such as servers, workstations, computing clusters, cloud computing platforms, virtualized computing systems, etc. Although not depicted for clarity, computing device 102, contactless card 136, and server 104 each include one or more processor circuits to execute programs, code, and / or instructions.

[0028] As shown in the figure, the memory 106 of the contactless card 136 includes an applet 108, a counter 110, a master key 112, a diversity key 114, and a unique customer identifier (ID) 116. The applet 108 is executable code configured to perform the operations described herein. The counter 110, master key 112, diversity key 114, and customer ID 116 are used to provide security in system 100, as described in more detail below.

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

[0030] As shown in the figure, the memory 128 of server 104 includes an authentication application 123, which includes an OTP generator 142. Although depicted as an integrated component of server 104, in some embodiments, the authentication application 123 and the OTP generator 142 may be separate components. Furthermore, the authentication application 123 and / or the OTP generator 142 may be implemented in hardware, software, and / or a combination of hardware and software.

[0031] In some embodiments, to protect account application 118 and / or associated data, such as details of user accounts in account database 130, system 100 can provide secure generation of an OTP for using contactless card 136. For example, a user can provide authentication credentials to account application 118, such as a username / password verified by account application 118 (e.g., by using a local instance of account database 130 and / or transmitting credentials to server 104 for verification). Once verified, account application 118 can instruct the user to tap contactless card 136 onto computing device 102.

[0032] exist Figure 1AIn the depicted embodiments, a user can tap the contactless card 136 onto the computing device 102 (or otherwise bring the contactless card 136 into the communication range of the card reader 122 of the device 102). An applet 108 of the contactless card 136 can then generate a URL 120 that is directed to resources such as server 104, authentication application 126, and / or OTP generator 142. In some embodiments, the applet 108 constructs the URL 120 according to one or more rules. In some embodiments, the contactless card 136 stores multiple URLs 120, and the applet 108 selects a URL 120 from the multiple URLs 120 based on one or more rules. In some embodiments, the applet 108 can generate the URL 120 by selecting the URL 120 and adding dynamic data such as a password 134 as one or more parameters of the URL.

[0033] Password 134 may be based on customer ID 116 of contactless card 136. Password 134 may be generated based on any suitable cryptographic technique. In some embodiments, applet 108 may include URL 120, password 134, and unencrypted identifiers (e.g., customer ID 116, identifier of contactless card 136, and / or any other unique identifier) ​​as part of a data packet. In at least some embodiments, the data packet is an NDEF file.

[0034] As described above, the computing architecture 100 is configured to implement key diversification to protect data, which may be referred to herein as key diversification technology. Generally, the server 104 (or another computing device) and the contactless card 136 may be equipped with the same master key 112 (also referred to as the master symmetric key). More specifically, each contactless card 136 is programmed with a different master key 112, which has a corresponding pair within the server 104. For example, when manufacturing the contactless card 136, a unique master key 112 may be programmed into the memory 106 of the contactless card 136. Similarly, the unique master key 112 may be stored in the account data 130 of the server 104 in the records of customers associated with the contactless card 136 (and / or stored in a different secure location, such as in a hardware security module (HSM) 132). The master key 112 can be kept confidential from parties other than the contactless card 136 and the server 104, thereby enhancing the security of the system 100. In some embodiments, the applet 108 of the contactless card 136 can use the master key 112 to encrypt and / or decrypt data (e.g., customer ID 116), and this data serves as input to a cryptographic algorithm. For example, encrypting the customer ID 116 using the master key 112 can generate a password 134. Similarly, the server 104 can use the corresponding master key 112 to encrypt and / or decrypt data associated with the contactless card 136.

[0035] In other embodiments, the master key 112 of the contactless card 136 and server 104 can be used in conjunction with a counter 110 to enhance security through key diversification. The counter 110 includes a value synchronized between the contactless card 136 and server 104. The counter 110 can include a number that changes each time data is exchanged between the contactless card 136 and server 104 (and / or the contactless card 136 and computing device 102). When ready to send data (e.g., to server 104 and / or device 102), the applet 108 of the contactless card 136 can increment the counter 110. The applet 108 of the contactless card 136 can then provide the master key 112 and the counter 110 as input to a cryptographic algorithm that produces a diversification key 114 as output. This cryptographic algorithm can include encryption algorithms, hash-based message authentication code (HMAC) algorithms, cipher-based message authentication code (CMAC) algorithms, etc. Non-limiting examples of cryptographic algorithms may include symmetric encryption algorithms such as 3DES or AES107; symmetric HMAC algorithms such as HMAC-SHA-256; and symmetric CMAC algorithms such as AES-CMAC. Examples of key diversification techniques are described in more detail in U.S. Patent Application 16 / 205,119, filed November 29, 2018. The aforementioned patent application is incorporated herein by reference in its entirety.

[0036] Continuing with the key diversification example, applet 108 can then use the diversification key 114 and data as input to a cryptographic algorithm to encrypt data (e.g., customer ID 116 and / or any other data). For example, encrypting customer ID 116 using the diversification key 114 can produce an encrypted customer ID (e.g., password 134). In some embodiments, password 134 is included as a parameter of URL 120. In other embodiments, password 134 is not a parameter of URL 120, but is transmitted using a data packet such as URL 120 in an NDEF file. Operating system 138 can then read the data packet including URL 120 and password 134 via communication interface 122 of computing device 102.

[0037] As previously mentioned, password 134 can be a parameter of URL 120. For example, URL 120 could be "http: / / www.example.com / OTPgenerator?param=ABC123". In such an example, password 134 could correspond to the parameter "ABC123". However, if password 134 is not a parameter of URL 120, then URL 120 could be "http: / / www.example.com / OTPgenerator". Regardless of whether URL 120 includes password 134 as a parameter, URL 120 can register with account application 118, causing operating system 138 to launch account application 118 and provide URL 120 and password 134 as input to account application 118.

[0038] Account application 118 can then transmit password 134 along with a request to generate an OTP to server 104. In embodiments where URL 120 includes password 134 as a parameter, account application 118 extracts password 134 from URL 120 and transmits a request with password 134 to an address associated with OTP generator 142, such as at least a portion of URL 120. In some embodiments, account application 118 makes an application programming interface (API) call to OTP generator 142. Furthermore, account application 118 may include another identifier, such as an unencrypted customer ID 116 provided in a data packet by applet 108. In some embodiments, the other identifier may be an identifier for contactless card 136, an account identifier, etc. In such embodiments, account application 118 may include instances of one or more portions of account database 130 to determine the other identifier.

[0039] Figure 1BAn embodiment is depicted in which an account application transmits an OTP request 146, including a password 134 and an unencrypted identifier, to a server 104. Once received, the server 104 can attempt to authenticate the password 134. For example, authentication application 126 can attempt to decrypt the password 134 using a copy of the master key 112 stored by the server 104. In some embodiments, authentication application 126 can use an unencrypted customer ID 116 (or other identifier) ​​provided to the server 104 by account application 118 to identify the master key 112 and counter 110. In some examples, authentication application 126 can provide the master key 112 and counter 110 as input to a cryptographic algorithm that produces a diversification key 114 as output. The resulting diversification key 114 can correspond to the diversification key 114 of the contactless card 136, which can be used to decrypt the password 134.

[0040] Regardless of the decryption technique used, authentication application 126 can successfully decrypt password 134, thereby verifying or authenticating password 134 in OTP request 146 (e.g., by comparing the customer ID 116 resulting from decrypting password 134 with a known customer ID stored in account database 130, and / or based on an indication of successful decryption using master key 112 and / or diversification key 114). Although keys 112 and 114 are depicted as being stored in memory 128, these keys can be stored elsewhere, such as in the secure element and / or HSM 132. In such an embodiment, the secure element and / or HSM 132 can decrypt password 134 using master key 112 and / or diversification key 114 along with a cryptographic function. Similarly, as described above, the secure element and / or HSM 132 can generate diversification key 114 based on master key 112 and counter 110. If decryption is successful, authentication application 126 can identify user contact information stored in account database 130, such as email address, phone number, device identifier of the instance registered to account application 118, device identifier of computing device 102, etc. Authentication application 126 can identify the contact information based on the unencrypted identifier included in OTP request 146. Authentication application 126 can then instruct OTP generator 142 to generate an OTP and transmit the OTP to the identified contact information.

[0041] However, if authentication application 126 cannot decrypt password 134 to produce the expected result (e.g., customer ID 116 of the account associated with contactless card 136), then authentication application 126 does not verify password 134. In such an example, authentication application 126 determines to suppress the generation of OTP. Authentication application 126 can transmit an indication of decryption failure to account application 118.

[0042] Figure 1C An embodiment is depicted in which authentication application 126 transmits decryption result 148 to account application 118. This decryption result 148 typically indicates to server 104 whether password 134 has been decrypted or not. Figure 1C In the depicted example, decryption result 148 indicates that server 104 has decrypted password 134. Account application 118 can use decryption result 148 to determine whether password 134 has been decrypted. Based on successful decryption, OTP generator 142 can generate OTP 150 and send it to computing device 102 based on the determined contact information. OTP 150 can be any alphanumeric string of any length. If the contact information is a phone number, OTP generator 142 can send OTP 150 via a short message service (SMS) message. If the contact information is an email address, OTP generator 142 can send OTP 150 via email. If the contact information is a device identifier, OTP generator 142 can send OTP 150 as part of a push notification directed to computing device 102.

[0043] The user can then provide the received OTP as input to the account application 118 via a user interface. The account application 118 can then compare the user-provided input with an instance of OTP 150 received from the OTP generator 142. In another embodiment, the account application 118 can transmit the user input to the OTP generator 142, which performs the comparison. If the OTP generator 142 performs the comparison, it transmits the comparison result to the account application 118. In some embodiments, the user can provide input to another application, such as a web browser 140 that has loaded a page associated with the OTP generator 142. The web page can then perform the comparison. If the comparison result matches, multi-factor authentication can be completed, and the user can perform one or more requested actions. For example, the user can view account attributes, perform actions associated with the account, make payments, transfer funds, view the balance, etc.

[0044] Figure 2A This is a schematic diagram 200a illustrating an embodiment in which a contactless card 136 is tapped onto a computing device 102. Although the computing device 102 is depicted as a screen (e.g., a home screen) that outputs an operating system 138, the computing device 102 can typically be in any state. For example, when the contactless card 136 is tapped onto the computing device 102, the user may be using another application, such as a web browser 140.

[0045] As previously described, when the contactless card 136 is tapped against the computing device 102, the applet 108 can generate a password 134 and a URL 120. In some embodiments, the password 134 is a parameter of the URL 120. The applet 108 may further include identifiers, such as an unencrypted customer ID 116, an identifier for the contactless card 136, etc. If the password 134 is a parameter of the URL 120, the unencrypted identifier can also be a parameter of the URL 120. Regardless of whether the password 134 and / or the unencrypted identifier are parameters of the URL 120, the password 134, the unencrypted identifier, and the URL 120 can all be included in a data packet (such as an NDEF file) read by the computing device 102. As shown, in response to receiving the data packet, the operating system 138 can launch the account application 118 because the URL 120 (or a portion thereof) can register with the account application 118 in the operating system 138.

[0046] Figure 2B This is a schematic diagram 200b illustrating an embodiment in which an account application 118 is opened in response to the operating system 138 reading a URL 120 received from a contactless card 136. As shown, the account application 118 instructs the user to provide a first authentication factor, which may be a biometric credential. The account application 118 may verify the biometric credential and, based on this verification, generate an OTP request 146 for an OTP 150 from an OTP generator 142. As previously described, the account application 118 may transmit a password 134 and an unencrypted identifier to the OTP generator 142. In some embodiments, the OTP request 146 may be an API call.

[0047] The authentication application 126 can then attempt to decrypt the password 134, as described in more detail above. If decryption is successful, the authentication application 126 can identify the contact information for the user account in the account database 130. In some embodiments, the contact information is identified based on unencrypted identifiers, such as an unencrypted customer ID 116 and a device ID. The authentication application 126 can then instruct the OTP generator 142 to generate an OTP 150 and transmit the OTP 150 to the contact information. The authentication application 126 can also transmit the decryption result 148 to the account application 118.

[0048] Figure 2CThis is a schematic diagram 200c illustrating an embodiment in which OTP 150 is sent as a push notification 202 to computing device 102. A user can be instructed to type OTP 150 in input field 204. As shown, push notification 202 allows the user to select push notification 202 to automatically fill OTP 150 into field 204. For example, when selected, the autofill service (not shown) of operating system 138 can copy OTP 150 and fill OTP 150 into field 204. In another example, OTP 150 can be copied to the clipboard (not shown) of operating system 138. Doing so allows the user to paste OTP 150 from the clipboard into field 204.

[0049] As shown in the figure, OTP 150 can be entered as input into field 204. Account application 118 can then verify the OTP 150 entered into field 204, for example, by comparing this input with an instance of OTP 150 received from OTP generator 142. In another example, account application 118 provides the input entered into field 204 to OTP generator 142, which performs the comparison and returns the result to account application 118. If the comparison matches, account application 118 can determine that multi-factor authentication is complete.

[0050] Figure 2D This is a schematic diagram 200d illustrating an embodiment where the input provided in column 204 matches with OTP 150. Based on the match and decryption of password 134, the user can log in to their account in account application 118. As shown, account application 118 displays various account attributes, such as account balance. The embodiment is not limited to this context, as the MFA using OTP 150 can be used to authorize any requested operation.

[0051] Operations for the disclosed embodiments can be further described with reference to the following figures. Some figures may include logical flows. Although these figures presented herein may include specific logical flows, it will be appreciated that such logical flows provide only examples of how the general functionality described herein can be implemented. Furthermore, unless otherwise stated, a given logical flow does not necessarily have to be executed in the order presented. Additionally, not all actions shown in the logical flow may be necessary in some embodiments. Furthermore, a given logical flow may be implemented by hardware elements, software elements executed by a processor, or any combination thereof. The embodiments are not limited to this context.

[0052] Figure 3An embodiment of a logic flow or routine 300 is illustrated. Logic flow 300 may represent some or all of the operations performed by one or more embodiments described herein. For example, logic flow 300 may include some or all of the operations enabling the secure generation of an OTP using a contactless card. The embodiments are not limited to this context.

[0053] In block 302, routine 300 receives a Uniform Resource Locator (URL) 120 and a password 134 from a contactless card 136 associated with the account by operating system 138 executing on the processor of computing device 102. In block 304, in response to receiving the URL 120, routine 300 launches the account application 118 associated with the contactless card 136 by operating system 138. However, in some embodiments, account application 118 executes in the foreground of operating system 138 and does not need to be launched. In such embodiments, the user can request to perform operations such as checking account balances, transferring funds, etc.

[0054] In box 306, routine 300 transmits password 134 to authentication server 104 via account application 118. Account application 118 may also include unencrypted identifiers, such as customer ID 116 and / or device identifier for authentication application 126. In box 308, routine 300 receives decryption result 148 from server 104 via account application 118, which indicates that authentication server 104 has decrypted password 134.

[0055] In box 310, routine 300 sends a request for a one-time password (OTP) including an identifier to server 104 by account application 118 based on the decryption result. This identifier may be an unencrypted customer ID 116, a device identifier, and / or an identifier for contactless card 136. In box 312, routine 300 determines contact information in account database 130 by server 104 based on the identifier. This contact information may include, but is not limited to, a phone number, email address, device identifier, etc. In box 314, routine 300 receives an OTP 150 from OTP generator 142 at the determined contact information by computing device 102. In box 316, routine 300 receives input values ​​from the user by account application 118. In box 318, routine 300 compares the input values ​​with a copy of the OTP received from OTP generator 142 by account application 118. In box 320, routine 300 determines that the comparison result matches. In box 322, routine 300 displays one or more attributes of an account on the device based on the decryption result 148 and the determination of a match in the comparison result. Additionally and / or alternatively, account application 118 may authorize the execution of an operation requested by the user based on the determination of a match in the comparison result and the decryption result 148.

[0056] Figure 4 An embodiment of a logic flow or routine 400 is illustrated. Logic flow 400 may represent some or all of the operations performed by one or more embodiments described herein. For example, logic flow 400 may include some or all of the operations enabling the secure generation of an OTP using a contactless card. The embodiments are not limited to this context.

[0057] In box 402, routine 400 receives a Uniform Resource Locator (URL) 120 and a password 134 from a contactless card 136 associated with an account by an operating system 138 executing on a processor of computing device 102. As described in more detail herein, applet 108 can generate the password 134. Applet 108 can further transmit an unencrypted identifier (e.g., customer ID 116) to computing device 102. In box 404, in response to receiving the URL 120, routine 400 initiates an account application 118 associated with the contactless card 136 by operating system 138. In box 406, routine 400 transmits the password 134 to authentication server 104 by account application 118. Account application 118 can further transmit an unencrypted identifier to server 104.

[0058] In box 408, routine 400 receives a decryption result 148 from authentication server 104 by account application 118, which instructs authentication server 104 to decrypt password 134. In box 410, routine 400 sends a request for a one-time password (OTP) including an identifier to a URL based on the decryption result 148. This identifier could be an unencrypted customer ID 116, a device identifier, and / or an identifier for contactless card 136. In box 412, routine 400 determines contact information in account database 130 based on the identifier by server 104. This contact information may include, but is not limited to, a phone number, email address, device identifier, etc. In box 414, routine 400 receives an OTP 150 from OTP generator 142 at URL 120 at the determined contact information by computing device 102. In box 416, routine 400 receives an input value by account application 118. In box 418, routine 400 compares the input value with a copy of OTP 150 received from OTP generator 142 by account application 118. In box 420, routine 400 determines that the comparison result matches. In box 422, routine 400 displays one or more attributes of the account on the device based on the determination of the comparison result match and based on the decryption result 148.

[0059] Figure 5AThis is a schematic diagram 500 illustrating an example construction of a contactless card 136, which may include a payment card, such as a credit card, debit card, or gift card, issued by a service provider and displayed as a service provider mark 502 on the front or back of the contactless card 136. In some examples, the contactless card 136 is not a payment card and may include, but is not limited to, an identity card. In some examples, the contactless card may include a dual-interface contactless payment card, a rewards card, etc. The contactless card 136 may include a substrate 504, which may include a single layer or one or more laminates composed of plastics, metals, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyester, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card 136 may have physical characteristics conforming to the ID-1 format of the ISO / IEC 7816 standard, and the contactless card may additionally conform to the ISO / IEC 14443 standard. However, it is understood that the contactless card 136 according to this disclosure may have different characteristics, and this disclosure does not require the implementation of contactless cards in payment cards.

[0060] The contactless card 136 may also include identification information 506 displayed on the front and / or back of the card, and a contact pad 508. The contact pad 508 may include one or more pads and is configured to establish contact with another client device (such as an ATM, user equipment, smartphone, laptop, desktop computer, or tablet) via the transaction card. The contact pad may be designed according to one or more standards such as ISO / IEC 7816 and enable communication according to the EMV protocol. The contactless card 136 may also include processing circuitry, an antenna, and other components that will... Figure 5B Further discussion follows. These components may be located behind the contact pad 508 or elsewhere on the substrate 504, for example, within different layers of the substrate 504, and may be electrically and physically coupled to the contact pad 508. The contactless card 136 may also include a magnetic stripe or magnetic tape, which may be located on the back of the card. Figure 5A (Not shown in the image). The contactless card 136 may also include a near-field communication (NFC) device coupled to an antenna capable of communicating via the NFC protocol. Embodiments are not limited to this approach.

[0061] As shown in Figure 2, the contact pad 508 of the contactless card 136 may include processing circuitry 510 for storing, processing, and transmitting information, including a processor 512, a memory 106, and one or more communication interfaces 122. It is understood that the processing circuitry 510 may include additional components, including a processor, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and tamper-proof hardware, as necessary to perform the functions described herein.

[0062] Memory 106 may be a read-only memory, a write-once-read-many memory, or a read / write memory, such as RAM, ROM, and EEPROM, and the contactless card 136 may include one or more of these memories. Read-only memory can be programmed by the manufacturer to be read-only or programmable only once. One-time programmability provides the opportunity to write once and then read multiple times. Write-once / read-many memory can be programmed at some point after the memory chip has left the factory. Once the memory is programmed, it may not be rewritten but can be read multiple times. Read / write memory can be programmed and reprogrammed multiple times after leaving the factory. Read / write memory can also be read multiple times after leaving the factory. In some instances, memory 106 may be an encrypted memory that encrypts data using an encryption algorithm executed by processor 512.

[0063] Memory 106 can be configured to store one or more applets 108, one or more counters 110, customer ID 116, master key 112, diversity key 114, and URL 120. One or more applets 108 may include one or more software applications configured to execute on the contactless card, such as Java® card applets. However, it is understood that applet 108 is not limited to Java card applets, but can be any software application that can operate on the contactless card or other devices with limited memory. One or more counters 110 may include numeric counters sufficient to store integers. Customer ID 116 may include a unique alphanumeric identifier assigned to a user of contactless card 136, and this identifier can distinguish the user of the contactless card from other users of contactless cards. In some examples, customer ID 116 can identify both the customer and the account assigned to that customer, and can further identify the contactless card 136 associated with that customer's account.

[0064] The processor 512 and memory elements of the foregoing exemplary embodiments are described with reference to contact pad 508, but this disclosure is not limited thereto. It will be understood that these elements may be implemented outside of or completely separated from contact pad 508, or as further elements in addition to the processor 512 and memory 106 elements located within contact pad 508.

[0065] In some examples, the contactless card 136 may include one or more antennas 514. One or more antennas 514 may be placed within the contactless card 136 and around the processing circuitry 510 of the contact pad 508. For example, one or more antennas 514 may be integrated with the processing circuitry 510, and one or more antennas 514 may be used in conjunction with an external boost coil. Alternatively, one or more antennas 514 may be located outside the contact pad 508 and the processing circuitry 510.

[0066] In an embodiment, the coil of the contactless card 136 can act as the secondary winding of an air-core transformer. The terminal can communicate with the contactless card 136 by cutting off power or amplitude modulation. The contactless card 136 can infer data transmitted from the terminal using gaps in its power connection, which can be functionally maintained by one or more capacitors. The contactless card 136 can communicate back by switching the load or load modulation on its coil. Load modulation can be detected in the terminal coil by interference. More generally, using one or more antennas 514, a processor 512, and / or memory 106, the contactless card 136 provides a communication interface for communication via NFC, Bluetooth, and / or Wi-Fi.

[0067] As explained above, the contactless card 136 can be built on a software platform that operates on smart cards or other devices with limited memory, such as JavaCards, and one or more applications or applets can be securely executed. An applet 108 can be added to the contactless card to provide a one-time password (OTP) for multi-factor authentication (MFA) in various mobile application-based use cases. The applet 108 can 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., a mobile device or point-of-sale terminal), and generate an NDEF message that includes a password-secured OTP encoded as an NDEF text tag.

[0068] An example of NDEF OTP is the NDEF short record layout (SR=1). In such an example, one or more applets 108 can be configured to encode the OTP into text tags of the NDEF type 4 known type. In some examples, the NDEF message may include one or more records. In addition to the OTP record, the applet 108 can also be configured to add one or more static tag records.

[0069] In some examples, one or more applets 108 can be configured to emulate RFID tags. The RFID tag may include one or more polymorphic tags. In some examples, different cipher data is presented each time the tag is read, which can indicate the authenticity of the contactless card. Based on one or more applets 108, NFC readings of the tag can be processed, the data can be transmitted to a server such as a bank's server, and the data can be verified at the server.

[0070] In some examples, the contactless card 136 and the server may include data that allows the card to be correctly identified. The contactless card 136 may include one or more unique identifiers (not shown). Each time a read operation occurs, the counter 110 may be configured to increment. In some examples, each time data is read from the contactless card 136 (e.g., by a mobile device), the counter 110 is sent to the server for verification, and it is determined whether the counter 110 equals (as part of the verification) the server's counter.

[0071] One or more counters 110 can be configured to prevent replay attacks. For example, if a password has been obtained and replayed, the password is immediately rejected if it has been read, used, or otherwise ignored by counter 110. If counter 110 has not yet been used, it can be replayed. In some examples, the counter incremented on the contactless card 136 is different from the counter incremented for transactions. The contactless card 136 cannot determine the application of transaction counter 110 because there is no communication between applets 108 on the contactless card 136. In some examples, the contactless card 136 may include a first applet 440-1, which may be a transaction applet, and a second applet 440-2. Each applet 440-1 and 440-2 may include a corresponding counter 110.

[0072] In some examples, counter 110 may become out of sync. In some examples, counter 110 may increment to account for unexpected reads that initiate a transaction, such as reads at an angle, but the application will not process counter 110. In some examples, NFC may be enabled when mobile device 10 is woken up, and the device 102 may be configured to read available tags, but will not take any action in response to the read.

[0073] To keep counter 110 synchronized, an application, such as a background application, can be executed. This application would be configured to detect when mobile device 102 wakes up, synchronize with the bank's system server to indicate reads that have occurred due to the detection, and then move counter 110 forward. In other examples, a hashed one-time password could be used to allow for unsynchronized windows. For example, if within a threshold of 10, counter 110 could be configured to move forward. However, if within a different threshold number, such as 10 or 1000, requests for resynchronization could be processed, which would involve one or more applications requesting the user to tap, gesture, or otherwise indicate this once or multiple times via the user's device. If counter 110 increments in the appropriate order, it becomes possible to know that the user has done so.

[0074] The key diversification technique described herein with reference to counter 110, master key, and diversification key is an example of an encryption and / or decryption key diversification technique. This example key diversification technique should not be considered as a limitation of this disclosure, as this disclosure is equally applicable to other types of key diversification techniques.

[0075] During the creation process of the contactless card 136, two cryptographic keys can be uniquely assigned to each card. The cryptographic keys may include a symmetric key, which can be used for both encryption and decryption of data. The Triple DES (3DES) algorithm can be used by EMV, and it is implemented by hardware in the contactless card 136. Through a key diversification process, one or more keys can be derived from the master key based on uniquely identifiable information used by each entity requesting the key.

[0076] In some examples, to overcome the vulnerability of the 3DES algorithm, a session key (such as a unique key for each session) can be derived instead of using a master key. The key and counter derived from the unique card can be used as diversification data. For example, each time the contactless card 136 is used in operation, a different key can be used to create a message authentication code (MAC) and perform encryption. This results in a three-layer cipher. This session key can be generated by one or more applets and derived using an application transaction counter with one or more algorithms (as defined in EMV 4.3 Book 2 A1.3.1 Public Session Key Derivation).

[0077] Furthermore, the increment used for each card can be unique and assigned either through personalization or algorithmically based on some identifying information. For example, odd-numbered cards can increment by 2, and even-numbered cards by 5. In some examples, the increment can also vary in terms of sequential reading, allowing a card to increment in a repeating sequence of 1, 3, 5, 2, 2… The specific sequence or algorithmic sequence can be defined during personalization or defined in one or more processes derived from a unique identifier. This makes it more difficult for replay attackers to generalize from a small number of cards.

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

[0079] Figure 6 A short record layout (SR=1) data structure 600 for NDEF according to an example embodiment is shown. One or more applets can be configured to encode OTP as a text tag of a known type 4 NDEF type. In some examples, the NDEF message may include one or more records. The applet can be configured to add one or more static tag records in addition to the OTP record. Exemplary tags include, but are not limited to: Tag type: known type, text, encoding English (en); Applet ID: D2760000850101; Capability: read-only access; Encoding: the authentication message may be encoded as ASCII hexadecimal; Type-length-value (TLV) data may be provided as a personalized parameter that can be used to generate the NDEF message. In an embodiment, the authentication template may include a first record with a known index for providing the actual dynamic authentication data. The data structure 600 may include a URL 120, a password 134, and any other data provided by the applet 108.

[0080] Figure 7 An embodiment of an exemplary computer architecture 700 suitable for implementing the various embodiments described above is shown. In one embodiment, computer architecture 700 may include or be implemented as part of computing architecture 100, as discussed herein.

[0081] As used in this application, the terms "system" and "component" are intended to refer to computer-related entities, hardware, combinations of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing computer architecture 700. For example, a component can be, but is not limited to, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and / or magnetic storage media), an object, an executable file, an execution thread, a program, and / or a computer. For example, both an application running on a server and the server itself can be components. One or more components can reside within a process and / or an execution thread, and components can be located on a single computer and / or distributed across two or more computers. Furthermore, components can be communicatively coupled to each other via various types of communication media to coordinate their operation. This coordination can involve one-way or two-way information exchange. For example, components can transmit information in the form of signals transmitted through a communication medium. This information can be implemented as signals assigned to various signal lines. In such an assignment, each message is a signal. However, alternatively, further embodiments may employ data messages. Such data messages can be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

[0082] Computer architecture 700 includes various common computing elements, such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input / output (I / O) components, power supplies, etc. However, embodiments are not limited to those implemented by computing architecture 100.

[0083] like Figure 7 As shown, the computer architecture 700 includes a processor 702, a system memory 704, and a system bus 706. The processor 702 can be any of a variety of commercially available processors.

[0084] System bus 706 provides interfaces for system components, including but not limited to system memory 704 to processor 702. System bus 706 can be any of several types of bus architectures, which can further interconnect with memory buses (with or without memory controllers), peripheral buses, and local buses using any of a variety of commercially available bus architectures. Interface adapters can be connected to system bus 706 via slot architectures. Example slot architectures can include, but are not limited to, Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), Network User Bus (NuBus), Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, PCMCIA, etc.

[0085] Computer architecture 700 may include or implement various articles of manufacture. Articles of manufacture may include computer-readable storage media for storing logic. Examples of computer-readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, etc. 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, etc. Embodiments may also be implemented, at least in part, as instructions contained in or on a non-transitory computer-readable medium that can be read and executed by one or more processors to enable the operations described herein to be performed.

[0086] System memory 704 may include various types of computer-readable storage media in the form of one or more high-speed memory cells, such as read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), dual data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memories such as ferroelectric polymer memories, bidirectional memories, phase-change or ferroelectric memories, silicon-silicon oxide-silicon nitride-silicon oxide-silicon (SONOS) memories, magnetic cards or optical cards, device arrays such as redundant array of independent disk drives (RAID), solid-state storage devices (e.g., USB storage, solid-state drives (SSDs)), and any other type of storage media suitable for storing information. Figure 7In the illustrated embodiment, system memory 704 may include non-volatile memory 708 and / or volatile memory 710. The Basic Input / Output System (BIOS) may be stored in non-volatile memory 708.

[0087] Computer 712 may include various types of computer-readable storage media in the form of one or more low-speed memory units, including internal (or external) hard disk drive 714, disk drive 716 for reading from or writing to removable disk 718, and optical disc drive 720 for reading from or writing to removable optical disc 722 (e.g., CD-ROM or DVD). Hard disk drive 714, disk drive 716, and optical disc drive 720 may be connected to system bus 706 via HDD interface 724, FDD interface 726, and optical disc drive interface 728, respectively. HDD interface 724 for external drive implementations may include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies.

[0088] The drive and associated computer-readable media provide volatile and / or non-volatile storage for data, data structures, computer-executable instructions, etc. For example, numerous program modules may be stored in the drive and in non-volatile 708 and volatile 710, including operating system 730, one or more applications 732, other program modules 734, and program data 736. In one embodiment, one or more applications 732, other program modules 734, and program data 736 may include, for example, various applications and / or components of system 100.

[0089] Users can type commands and information into computer 712 using one or more wired / wireless input devices (e.g., keyboard 738 and pointing devices such as mouse 740). Other input devices may include microphones, infrared (IR) remote controls, radio-frequency (RF) remote controls, game pads, styluses, card readers, dongles, fingerprint readers, gloves, graphics tablets, joysticks, keyboards, retinal readers, touchscreens (e.g., capacitive, resistive, etc.), trackballs, touchpads, sensors, styluses, etc. These and other input devices are typically connected to processor 702 via input device interface 742, which is coupled to system bus 706, but may also be connected via other interfaces such as parallel ports, IEEE 1394 serial ports, game ports, USB ports, IR interfaces, etc.

[0090] A monitor 744 or other type of display device is also connected to the system bus 706 via an interface such as a video adapter 746. The monitor 744 can be internal or external to the computer 712. In addition to the monitor 744, the computer typically includes other peripheral output devices such as speakers, printers, etc.

[0091] Computer 712 can operate in a networked environment via logical connections to one or more remote computers, such as remote computer 748, through wired and / or wireless communications. Remote computer 748 can be a workstation, server computer, router, personal computer, laptop computer, microprocessor-based entertainment device, peer-to-peer device, or other public network node, and typically includes many or all of the elements described relative to computer 712, although only memory / storage device 750 is shown for the sake of brevity. The depicted logical connections include wired / wireless connections to local area networks 752 and / or larger networks such as wide area networks 754. Such LAN and WAN networking environments are common in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to global communication networks, such as the Internet.

[0092] When used in a local area network (LAN) 752 network environment, computer 712 is connected to LAN 752 via a wired and / or wireless communication network interface or network adapter 756. Network adapter 756 facilitates wired and / or wireless communication to LAN 752, which may also include a wireless access point configured thereon for communicating with the wireless functionality of network adapter 756.

[0093] When used in a wide area network (WAN) 754 networking environment, computer 712 may include a modem 758, or a communication server connected to WAN 754, or other means for establishing communication on WAN 754, such as via the Internet. Modem 758 may be a built-in or external wired and / or wireless device connected to system bus 706 via input device interface 742. In a networked environment, program modules or portions thereof depicted relative to computer 712 may be stored in remote memory / storage device 750. It will be appreciated that the network connections shown are exemplary, and other means for establishing communication links between computers may be used.

[0094] Computer 712 is operable to communicate with wired and wireless devices or entities (such as wireless devices operable in wireless communication, e.g., IEEE 802.11 air modulation technology) using the IEEE 802 family of standards. This includes, among other things, at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wireless technologies. Therefore, communication can be a predefined structure like a regular network, or simply ad hoc communication between at least two devices. Wi-Fi networks use radio technology known as IEEE 802.118 (a, b, g, n, etc.) to provide secure, reliable, and fast wireless connectivity. Wi-Fi networks can be used to connect computers to each other, connect to the Internet, and connect to wired networks (which use IEEE 802.3 related media and functions).

[0095] As previously referred to Figure 1A-6 The various elements of the described device can include a variety of hardware elements, software elements, or combinations of both. Examples of hardware elements can include devices, logic devices, components, processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application-specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field-programmable gate arrays (FPGAs), memory cells, logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. Examples of software elements can 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 programming interfaces (APIs), instruction sets, computational code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. However, determining whether an embodiment is implemented using hardware and / or software elements may vary depending on many factors, such as desired computing speed, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints expected according to a given implementation.

[0096] One or more aspects of at least one embodiment can be implemented by representative instructions stored on a machine-readable medium, representing various logic within a processor, which, when read by a machine, cause the machine to manufacture the logic to perform the techniques described herein. Such a representation, referred to as an "IP core," can be stored on a tangible machine-readable medium and supplied to various customers or manufacturing facilities for loading into manufacturing machines that manufacture logic or processors. Some embodiments can be implemented, for example, using a machine-readable medium or article that can store instructions or instruction sets that, if executed by a machine, cause the machine to perform the methods and / or operations according to the embodiments. Such a machine can include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and can be implemented using any suitable combination of hardware and / or software. Machine-readable media or articles 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, such as memory, removable or non-removable media, erasable or non-erasable media, writable or rewritable media, digital or analog media, hard disk, floppy disk, optical disc read-only memory (CD-ROM), recordable optical disc (CD-R), rewritable optical disc (CD-RW), optical disc, magnetic media, magneto-optical media, removable memory cards or discs, various types of digital universal discs (DVDs), magnetic tape, cassette tape, etc. Instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, etc., implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language.

[0097] The foregoing description of exemplary embodiments has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit this disclosure to the precise forms disclosed. Many modifications and variations are possible with respect to this disclosure. It is intended that the scope of this disclosure be limited not by this detailed description but by the appended claims. Future applications claiming priority to this application may claim the disclosed subject matter in different ways and may generally include any set of one or more limitations as disclosed herein or otherwise demonstrated.

Claims

1. A method for securely generating a one-time password using a contactless card, comprising: The operating system (OS) running on the device's processor receives a Uniform Resource Locator (URL) and password from a contactless card associated with the account. The application associated with the URL transmits the password to the authentication server; The application receives a decryption result from the authentication server, the decryption result indicating that the authentication server has decrypted the password; The application sends a request for a one-time password (OTP) including an identifier to the OTP generator based on the decryption result. The device receives the OTP from the OTP generator; The application receives the input value; as well as Based on the application's determination that the input value matches a copy of the OTP received from the OTP generator, the requested operation associated with the account is allowed to be performed on the device.

2. The method according to claim 1, further comprising: The OS launches the application in response to receiving the URL.

3. The method of claim 1, wherein the requested operation includes one or more of the following: (i) viewing one or more attributes of the account, (ii) transferring funds from the account, (iii) receiving funds, or (iv) processing a purchase using funds from the account.

4. The method according to claim 3, further comprising: The application receives a request to perform the operation.

5. The method according to claim 1, wherein, The URL is registered to launch the application in the OS, wherein the URL is directed to an application programming interface (API) endpoint for the OTP generator.

6. The method according to claim 1, further comprising: The application compares the input value with a copy of the OTP received from the OTP generator.

7. The method according to claim 1, further comprising: The OS provides the received OTP to the OS's autofill service; as well as The autofill service automatically fills the OTP into the form fields of the application.

8. A non-transitory computer-readable storage medium, the computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to: The operating system (OS) receives the Uniform Resource Locator (URL) and password from the contactless card associated with the account. The application associated with the URL transmits the password to the authentication server; The application receives a decryption result from the authentication server, the decryption result indicating that the authentication server has decrypted the password; The application sends a request for a one-time password (OTP) including an identifier to the OTP generator based on the decryption result. Receive the OTP from the OTP generator; The application receives the input value; as well as The application, based on a determination that the input value matches a copy of the OTP received from the OTP generator, allows the execution of the requested operation associated with the account.

9. The computer-readable storage medium of claim 8, wherein the instructions further cause the processor to: The OS launches the application in response to receiving the URL.

10. The computer-readable storage medium of claim 8, wherein the requested operation comprises one or more of the following: (i) viewing one or more attributes of the account, (ii) transferring funds from the account, (iii) receiving funds, or (iv) processing a purchase using funds from the account.

11. The computer-readable storage medium of claim 10, wherein the instructions further cause the processor to: The application receives a request to perform the operation.

12. The computer-readable storage medium according to claim 8, wherein, The URL is registered to launch the application in the OS, wherein the URL is directed to an application programming interface (API) endpoint for the OTP generator.

13. The computer-readable storage medium of claim 8, wherein the instructions further cause the processor to: The application compares the input value with a copy of the OTP received from the OTP generator.

14. The computer-readable storage medium of claim 8, wherein the instructions further cause the processor to: The OS provides the received OTP to the OS's autofill service; and The autofill service automatically fills the OTP into the form fields of the application.

15. A computing device for securely generating one-time passwords using contactless cards, comprising: processor; as well as A memory storing instructions that, when executed by the processor, cause the processor to: The operating system (OS) receives the Uniform Resource Locator (URL) and password from the contactless card associated with the account. The application associated with the URL transmits the password to the authentication server; The application receives a decryption result from the authentication server, the decryption result indicating that the authentication server has decrypted the password; The application sends a request for a one-time password (OTP) including an identifier to the OTP generator based on the decryption result. Receive the OTP from the OTP generator; The application receives the input value; as well as The application, based on a determination that the input value matches a copy of the OTP received from the OTP generator, allows the execution of the requested operation associated with the account.

16. The computing device of claim 15, wherein the instructions further cause the processor to: The OS launches the application in response to receiving the URL.

17. The computing device of claim 15, wherein the requested operation includes one or more of the following: (i) viewing one or more attributes of the account, (ii) transferring funds from the account, (iii) receiving funds, or (iv) processing a purchase using funds from the account.

18. The computing device of claim 17, wherein the instructions further cause the processor to: The application receives a request to perform the operation.

19. The computing device of claim 15, wherein the URL is registered to launch the application in the OS, wherein the URL is directed to an application programming interface (API) endpoint for the OTP generator.

20. The computing device of claim 15, wherein the instructions further cause the processor to: The OS provides the received OTP to the OS's autofill service; and The autofill service automatically fills the OTP into the form fields of the application.

Citation Information

Patent Citations

  • Systems and methods for cryptographic authentication of contactless cards

    US10581611B1

  • User-convenient authentication method and apparatus using a mobile authentication application

    CN104662864A

  • Secure password generation and management using NFC and contactless smart cards

    US10733283B1