Techniques for personal identification number management of contactless cards

Abstract

Embodiments disclosed herein provide techniques for secure PIN management for contactless cards using an application on a computing device, such as a mobile computing device. In some embodiments, a computing device may be installed with an application, enabling the computing device to act as a secure endpoint that enables communications between a contactless card and a backend server to facilitate PIN management. For example, the application may enable a mobile device to view and / or alter a PIN associated with a contactless card brought in proximity to the mobile device.

Description

Technical Field

[0001] Embodiments disclosed herein relate generally to computing platforms, and more particularly, to computing platforms for secure, personal identification number (PIN) management of contactless cards. Background Art

[0002] A personal identification number (PIN), or sometimes redundantly called a PIN number or PIN code, is a numeric (sometimes alphanumeric) password used in the process of authenticating a user to access a system. PINs have been the key to facilitating the exchange of private data between different data processing centers in computer networks used by financial institutions, governments, and businesses. Among other uses, PINs can be used to authenticate cardholders to banking systems, governments to citizens, businesses to employees, and computers to users. In everyday use, PINs are used for ATM or POS transactions, security access control (e.g., computer access, door access, car access, etc.), Internet transactions, or logging into restricted websites. Summary of the invention

[0003] This summary is not intended to identify only key features or essential features of the described subject matter, nor is it intended to be used alone to determine the scope of the described subject matter. The subject matter should be understood by reference to the entire specification of this patent, any or all drawings, and each claim.

[0004] In one aspect, the present disclosure relates to an apparatus comprising a processor and a memory, the memory comprising instructions that, when executed by the processor, cause the processor to perform one or more of the following: authenticating a user based on credentials received via a user interface; detecting a password received from a contactless card in proximity to the processor; determining that the contactless card is associated with the user based on authentication of the password; presenting a current personal identification number (PIN) associated with the contactless card via the user interface based on authentication of the user and authentication of the password; determining to change the current PIN associated with the contactless card to an updated PIN; identifying the updated PIN based on input received via the user interface; communicating the updated PIN to a server to associate the updated PIN with the contactless card; identifying a PIN script received from the server in response to communicating the updated PIN to the server; and communicating the PIN script to the contactless card to change the PIN stored on the contactless card from the current PIN to the updated PIN.

[0005] In some embodiments, the mobile device includes a processor and a memory, and the password is received from a contactless card via near field communication. In various embodiments, the instruction, when executed by the processor, also causes the processor to pass the password to the server and receive verification from the server to authenticate the password. In many embodiments, the instruction, when executed by the processor, also causes the processor to encrypt the updated PIN for delivery to the server. In many such embodiments, the instruction, when executed by the processor, also causes the processor to encrypt the updated PIN based on the unique identifier (uniqueidentifier, UID) received from the contactless card. In many other such embodiments, the instruction, when executed by the processor, also causes the processor to generate a session key using the UID to encrypt the updated PIN based on the UID. In multiple embodiments, the instruction, when executed by the processor, also causes the processor to authenticate the PIN script based on the message authentication code (message authentication code, MAC) received from the server. In multiple such embodiments, the instruction, when executed by the processor, also causes the processor to authenticate the PIN script based on the MAC received from the server using an integrated key.

[0006] In another aspect, the present disclosure relates to a non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed by a processor circuit, causes the processor circuit to perform one or more of the following: authenticating a user based on credentials received via a user interface; detecting a password received from a contactless card in proximity to the processor; determining that the contactless card is associated with the user based on authentication of the password; presenting a current personal identification number (PIN) associated with the contactless card via the user interface based on authentication of the user and authentication of the password; determining to change the current PIN associated with the contactless card to an updated PIN; identifying the updated PIN based on input received via the user interface; communicating the updated PIN to a server to associate the updated PIN with the contactless card; identifying a PIN script received from the server in response to communicating the updated PIN to the server; and communicating the PIN script to the contactless card to change the PIN stored on the contactless card from the current PIN to the updated PIN.

[0007] In some embodiments, the instruction set, in response to execution by the processor circuit, further causes the processor circuit to pass the password to the server and receive verification from the server to authenticate the password. In various embodiments, the instruction set, in response to execution by the processor circuit, further causes the processor circuit to encrypt the updated PIN for delivery to the server. In multiple embodiments, the instruction set, in response to execution by the processor circuit, further causes the processor circuit to encrypt the updated PIN based on a unique identifier (UID) received from a contactless card. In multiple such embodiments, the instruction set, in response to execution by the processor circuit, further causes the processor circuit to generate a session key using the UID to encrypt the updated PIN based on the UID. In many embodiments, the instruction set, in response to execution by the processor circuit, further causes the processor circuit to authenticate the PIN script based on a message authentication code (MAC) received from the server. In many such embodiments, the instruction set, in response to execution by the processor circuit, further causes the processor circuit to authenticate the PIN script using an integrated key based on the MAC received from the server.

[0008] In yet another aspect, the present disclosure relates to a computer-implemented method, which includes one or more of the following: authenticating a user based on credentials received via a user interface; detecting a password received from a contactless card; determining that the contactless card is associated with the user based on authentication of the password; presenting a current personal identification number (PIN) associated with the contactless card via the user interface based on authentication of the user and authentication of the password; determining to change the current PIN associated with the contactless card to an updated PIN; identifying the updated PIN based on input received via the user interface; communicating the updated PIN to a server to associate the updated PIN with the contactless card; identifying a PIN script received from the server in response to communicating the updated PIN to the server; and communicating the PIN script to the contactless card to change the PIN stored on the contactless card from the current PIN to the updated PIN.

[0009] Some embodiments include encrypting the updated PIN for delivery to the server. Some such embodiments include encrypting the updated PIN based on a unique identifier (UID) received from the contactless card. Some other such embodiments include generating a session key using the UID to encrypt the updated PIN based on the UID. Various embodiments include authenticating the PIN script based on a message authentication code received from the server. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 Various aspects of an exemplary system for PIN management according to one or more embodiments described herein are shown.

[0011] Figure 2 Aspects of an exemplary system for PIN management according to one or more embodiments described herein are shown.

[0012] Figure 3 An exemplary transaction card is shown according to one or more embodiments described herein.

[0013] Figure 4 Various aspects of a transaction card according to one or more embodiments described herein are shown.

[0014] Figure 5 A sequence flow 500 is shown according to one or more embodiments described herein.

[0015] Figure 6 A data structure 600 is shown in accordance with one or more embodiments described herein.

[0016] Figure 7 A logic flow is shown according to one or more embodiments described herein.

[0017] Figure 8 Routine 800 is shown according to an embodiment.

[0018] Fig. 9 A computer architecture 900 is shown according to one embodiment.

[0019] Fig.10 A communication architecture 1000 is shown according to one embodiment. DETAILED DESCRIPTION

[0020] Embodiments disclosed herein provide techniques for secure PIN management for contactless cards using an application on a computing device, such as a mobile computing device. In some embodiments, a computing device may have an application installed that enables the computing device to act as a secure endpoint that enables communication between a contactless card and a backend server to facilitate PIN management. For example, the application may enable a mobile device to be used to view and / or change a PIN associated with a contactless card brought into proximity with the mobile device. These and other embodiments are described and claimed.

[0021] In one embodiment, the user can install the application on the computing device. The user can then provide login credentials to access the application. Once logged in, the application can instruct the user to bring the contactless card to the vicinity of the computing device sufficient to enable near-field communication between the contactless card and the computing device. For example, the application can instruct the user to tap the contactless card on the device. Doing so can cause or instruct the contactless card to generate a password, which can be included as part of a data package, such as an NFC Forum data exchange format (NDEF) file. The data package can also include an unencrypted customer identifier (ID) or any other unique identifier. The application can read the data package via NFC and transmit the data package to the server for PIN management authorization. For PIN management authorization, the server can verify the contactless card, and the application is associated with a user authorized by the public. For example, the server can authenticate the password, such as using the received data package, and the server can confirm the login credentials for accessing the application corresponding to the same user associated with the contactless card seeking PIN management. If the server can authorize PIN management, the application can be used to view and / or edit the PIN associated with the contactless card.

[0022] Advantageously, embodiments disclosed herein provide techniques for securely performing PIN management operations from a computing device having an application installed. By leveraging a password generated by a contactless card associated with a user, combined with accessing the application by providing login credentials corresponding to the user, embodiments of the present disclosure may enable a computing device to act as a secure endpoint for PIN management operations associated with a contactless card with minimal risk of fraudulent activity. Additionally, the techniques described herein may enable a user to view a PIN without having to change or reset the PIN, thereby improving the customer experience. Furthermore, by using a computing device having an application installed, a user is not required to use a contactless card at a point-of-sale contact terminal to receive a PIN change script to change the PIN on the contactless card, thereby further improving the customer experience as well as system efficiency.

[0023] With general reference to the symbols and nomenclature used herein, one or more parts of the detailed description may be subsequently presented in terms of the program process executed on a computer or computer network. These procedural descriptions and representations are used by those skilled in the art to convey the essence of their work to other technicians in the field most effectively. Processes are generally conceived here as self-consistent sequences of operations that lead to desired results. These operations are those operations that require physical manipulation of physical quantities. Generally, although not necessarily, these quantities take the form of electrical signals, magnetic signals, or optical signals that can be stored, transmitted, combined, compared, and otherwise manipulated. Mainly for idiomatic reasons, sometimes these signals are referred to as bits, values, elements, symbols, characters, items, numbers, or the like, which have proven to be convenient. However, it should be noted that all of these and similar terms should be associated with appropriate physical quantities, and are merely convenient markers applied to those quantities.

[0024] Further, these manipulations are usually referred to with terms such as addition or comparison, which are usually associated with mental operations performed by a human operator. However, in any operation that constitutes part of one or more embodiments described herein, such ability of a human operator is not necessary, or is not desirable in most cases. On the contrary, these operations are machine operations. Useful machines for performing the operations of various embodiments include digital computers selectively activated or configured by computer programs stored therein written according to the teachings herein, and / or include devices or digital computers specially constructed for the desired purpose. Various embodiments also relate to devices or systems for performing these operations. These devices can be specially constructed for the desired purpose. The structure required for a variety of these machines will be apparent from the description given.

[0025] Reference is now made to the accompanying drawings, in which the same reference numerals are used to refer to the same elements throughout. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a thorough understanding thereof. However, novel embodiments may be practiced without these specific details. In other examples, structures and devices are shown in block diagram form to facilitate description thereof. It is intended to cover all modifications, equivalents, and substitutes consistent with the claimed subject matter.

[0026] In the various figures and accompanying descriptions, the designations "a" and "b" and "c" (and similar designators) are intended to be variables representing any positive integer. Thus, for example, if an embodiment sets the value to a=5, the complete set of components 123 shown as components 123-1 to 123-a (or 123a) may include components 123-1, 123-2, 123-3, 123-4, and 123-5. The embodiments are not limited in this context.

[0027] Figure 1 Various aspects of a PIN management system 102 are shown in accordance with one or more embodiments described herein. Generally, the PIN management system 102 may be used to enable a user to view and edit a PIN 144 associated with a contactless card 116 via a computing device 104. The illustrated embodiment includes a password 122 generated by the contactless card 116 and provided to the computing device 104. In various embodiments, the computing device 104 may send the password 122 to a backend server 124 (such as via an application 114) for authentication. In various such embodiments, PIN management functionality may be provided via the application 114 in response to a successful authentication of the password 122, which may be received by the computing device 104 as a verification 156.

[0028] PIN management system 102 includes computing device 104, contactless card 116, backend server 124, account data 128, key management service 130, and hardware security module 132. Contactless card 116 includes communication interface 120 and memory 118 with applet 134, master key 136, integration key 138, unique identifier 140, and PIN 144.

[0029] The computing device 104 is communicatively coupled to the backend server 124 via a network 142, and includes a memory 106, a user interface 110, and a communication interface 108. The memory 106 includes an operating system 112 with an application 114. The backend server 124 includes a memory 126 with a manager 152, a master key 146, an integration key 148, a unique identifier 150, and a login credential 154. It will be appreciated that one or more items in the memory 106, 118, 126 may be in an encrypted or unencrypted format without departing from the scope of the present disclosure. In addition, one or more items in the memory 106, 118, 126 may be transferred between different memories in the memory 106, 118, 126 in an encrypted or unencrypted format.

[0030] although Figure 1 The illustrated system 100 has a limited number of elements in a particular topology, but it can be appreciated that the PIN management system 102 can include more or fewer elements in alternative topologies as desired for a given implementation without departing from the scope of the present disclosure. For example, one or more of the account data 128, the key management service 130, and the hardware security module 132 can be incorporated into the backend server 124 without departing from the scope of the present disclosure. In another example, one or more operations can be performed by the computing device 104 rather than the backend server 124 or the contactless card 116 without departing from the scope of the present disclosure. The embodiments are not limited in this context.

[0031] In various embodiments, the illustrated embodiments involve various steps of authenticating a user's contactless card and a computing device to act as a secure endpoint to provide PIN management functionality for the contactless card. The contactless card 116 represents any type of payment card, such as a credit card, a debit card, an ATM card, a gift card, and similar payment cards. The contactless card 101 may include one or more communication interfaces 120, such as a radio frequency identification (RFID) chip, which is configured to communicate with a communication interface 108 (also referred to herein as a "card reader", "wireless card reader" and / or "wireless communication interface") of a computing device 104 via NFC, the EMV standard, or other short-range protocols in wireless communication. Although NFC is used as an example communication protocol herein, the present disclosure is equally applicable to other types of wireless communications, such as the EMV standard, Bluetooth, and / or Wi-Fi.

[0032] The computing device 104 represents any number and type of computing devices, such as smart phones, tablet computers, wearable devices, laptops, portable gaming devices, virtualized computing systems, desktop computers, and similar devices. The back-end server 124 represents any type of computing device, such as servers, workstations, computing clusters, cloud computing platforms, virtualized computing systems, and similar devices. Although not depicted for clarity, the computing device 104, the contactless card 116, and the back-end server 124 each include one or more processor circuits to execute programs, codes, and / or instructions.

[0033] As previously mentioned, the memory 118 of the contactless card 116 includes an applet 134, a master key 136, an integration key 138, a unique identifier 140, and a PIN 144. The applet 134 is executable code configured to perform the operations described herein. The master key 136, the integration key 138, the unique identifier 140, and the PIN 144 are used to provide security in the system 102, as described in more detail below. As previously mentioned, the memory 106 of the computing device 104 includes an instance of an operating system (OS) 112. The example operating system 112 includes OS, and Operating system. As shown, OS112 includes one or more applications, including application 114. Application 114 is software that allows computing device 104 to interact and communicate with contactless card 116 and back-end server 124 in a manner that provides PIN management functions. As mentioned above, the memory 126 of back-end server 124 includes manager 152, master key 146, integration key 148, unique identifier 150 and login credentials 154. As described in more detail herein, manager 152 is configured to interact with application 114 of computing device 104 to facilitate one or more back-end PIN management functions described herein. In at least one embodiment, the interaction between components can be provided via one or more application programming interfaces (APIs). In some embodiments, integration key 148 is used to calculate a message authentication code.

[0034] exist Figure 1 In the depicted embodiment, a user may log into the application 114 by providing login credentials via the user interface 110. The provided login credentials may be compared to the login credentials 154 associated with the user to enable the user to access the application 114. For example, the manager 152 may compare the provided login credentials to the login credentials 154. In another example, the manager 152 may use the key management service 130 or the hardware security module 132 to compare the provided login credentials to the login credentials 154. In some embodiments, the login credentials 154 or a portion thereof may be retrieved from the account data 128. In one embodiment, the login credentials 154 may be stored on the computing device 104. In such an embodiment, the application 114 may compare the provided login credentials to the login credentials 154.

[0035] Once the user logs into the application 114, the user may be instructed to tap the contactless card 116 to the computing device 104 (or otherwise bring the contactless card 101 within communication range of a card reader of the computing device 104). In some embodiments, the user is instructed to tap the contactless card 116 to the computing device 104 in response to selecting the PIN management option in the application 114.

[0036] Generally, once contactless card 116 is brought into the communication range of communication interface 108 of computing device 104, small application 134 of contactless card 116 can generate password 122. Password 122 can be based on one or more of master key 136, integration key 138, unique identifier 140 and PIN 144 of contactless card 116. For example, small application 134 can generate password 122 based on master key 136 and unique identifier 140. The password can be generated based on any suitable cryptographic technology. In some embodiments, small application 134 can include password 122 and customer ID (and / or any other unique identifier) ​​in data packet. In at least one embodiment, the data packet including password 122 and customer ID is NDEF file.

[0037] In an embodiment, computing device 104 may receive password 122 from contactless card 116. Computing device 104 may send password 122 to backend server 124, and in some embodiments, backend server 124 may determine that contactless card 116 is associated with the user based on password 122. For example, backend server 124 may verify information in password 122 against information stored on backend server 124.

[0038] The PIN management system 102 is configured to implement key diversification to protect data, which may be referred to herein as a key diversification technique. Generally, the backend server 124 (or another computing device) and the contactless card 116 may be provided with the same master key 136, 146 (also referred to as a master symmetric key). More particularly, each contactless card 116 is programmed with a different master key that has a corresponding pair in the backend server 124. For example, when the contactless card 116 is manufactured, a unique master key may be programmed into the memory 118 of the contactless card 116. Similarly, the unique master key may be stored in the record of the customer associated with the contactless card 116 in the account data 128 of the backend server 124 (and / or stored in a different secure location, such as a hardware security module (HSM) 132). The master key may be kept secret from all parties other than the contactless card 116 and the backend server 124, thereby enhancing the security of the system 102.

[0039] In some embodiments, the applet 134 of the contactless card 116 can encrypt and / or decrypt data (e.g., the unique identifier 140) using the master key 136 and the data as inputs to an encryption algorithm. For example, encrypting the unique identifier 140 using the master key 136 can generate the password 122. Similarly, the backend server 124 can encrypt and / or decrypt data associated with the contactless card 116 using the corresponding master key 146.

[0040] In some instances, the contactless card 116 and the backend server 124 can utilize their master keys to generate session keys, as discussed. The session key can be used to encrypt / decrypt data by the contactless card 116 and the backend server 124. For example, the master keys 136, 146 of the contactless card 116 and the backend server 124 can be used in combination with one or more counters to enhance security using key diversification. The counter can include a value synchronized between the contactless card 116 and the backend server 124. The counter value can include a number that changes each time data is exchanged between the contactless card 116 and the backend server 124 (and / or the contactless card 116 and the computing device 104). When preparing to send data (e.g., to the backend server 124 and / or the computing device 104), the small application 134 of the contactless card 116 can increment the counter value. Then, the small application 134 of the contactless card 116 can provide the master key 136 and the count value as input to a cryptographic algorithm, which produces a diversified key as output. Cryptographic algorithms may include encryption algorithms, hash-based message authentication code (HMAC) algorithms, ciphertext-based message authentication code (CMAC) algorithms, and similar algorithms. 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. U.S. patent application Ser. No. 16 / 205,119, filed on Nov. 29, 2018, describes examples of key diversification techniques in more detail. The aforementioned patent application is incorporated herein by reference in its entirety.

[0041] Continuing with the key diversification example, the contactless card 116 may then use the diversified key and the data as inputs to a cryptographic algorithm to encrypt data (e.g., the unique identifier 140 and / or any other data). For example, encrypting the unique identifier 140 using the diversified key may result in an encrypted customer ID (e.g., a password) included in a data packet communicated to the computing device 104. The application 114 may then read the data packet including the password 122 and the unencrypted customer ID via the communication interface 108.

[0042] Regardless of the encryption technique used, the application 114 may then transmit the data packet (including the password 122 and the unencrypted customer ID) to the backend server 124 via the network 142. The application 114 may also indicate to the backend server 124 that the data packet including the password 122 and the unencrypted customer ID was read from the contactless card 116 via the communication interface 108 of the computing device 104.

[0043] Once received, the manager 152 may attempt to authenticate the password 122. For example, the manager 152 may include an authentication application that attempts to decrypt the password 122 using a copy of the master key 146 stored by the backend server 124. In some embodiments, the manager 152 may use an unencrypted client ID included in the data packet to identify the master key 146 and the counter value. In some examples, the manager 152 may provide the master key 146 and the counter value as input to a cryptographic algorithm (e.g., in the key management server 130), which produces a diversified key as output. The resulting diversified key may correspond to a diversified key of the contactless card 116, which may be used to decrypt the password 122 in the data packet.

[0044] Manager 152 may successfully decrypt password 122, thereby verifying or authenticating password 122 in the data packet (e.g., by comparing unique identifier 140 generated by decrypting password 122 to known unique identifier 150 stored in account data 128, and / or based on an indication of successful decryption using a master key and / or a diversified key).

[0045] Although the one or more keys and / or identifiers are depicted as being stored in the memory 118, 126, the one or more keys and / or identifiers may be stored elsewhere, such as in the secure element and / or hardware security module 132. In such an embodiment, the secure element and / or hardware security module 132 may use the key and cryptographic function to decrypt the password. Similarly, as described above, the secure element and / or hardware security module 132 may generate a diversified key based on the master key 146 and the counter value. If the decryption is successful, the manager 152 may enable the PIN management functionality to be accessed and / or provided via the application 114 of the computing device 104, such as by sending a verification 156. As will be described in more detail below, such as with respect to Figure 2 As depicted, PIN management functions may include viewing and / or changing a PIN 144 in memory 118 that corresponds to a PIN 146 (deleted) in memory 126 .

[0046] However, if manager 152 cannot decrypt password 122 to produce the expected result (e.g., unique identifier 140 or customer ID of an account associated with contactless card 116), manager 152 does not verify password 122. In such an example, manager 152 determines to avoid enabling PIN management functionality via application 114 of computing device 104. Manager 152 can transmit an indication of the decryption failure to application 114 of computing device 104. Application 114 can then display an indication of the decryption failure to the user via user interface 110, and thus display a denial of access to the PIN management functionality to the user via user interface 110.

[0047] Figure 2 202 according to one or more embodiments described herein. In general, the PIN management system 202 can be used to enable a user to view and edit a PIN 244 associated with a contactless card 216 via a computing device 204. In some embodiments, Figure 2 The functionality described can be found in the Figure 1 The illustrated embodiment includes a request for an updated PIN 222 provided to a backend server 224 , such as based on input provided to the application 214 via the user interface 210 .

[0048] In various embodiments, the backend server 224 may generate a PIN script 258 based on the request for the updated PIN 222. In various such embodiments, the PIN script 258 may be passed by the computing device 204 to the contactless card 216 and used by the applet 234 to install the current PIN on the contactless card 216 and / or change to the updated PIN 244.

[0049] In various embodiments, PIN management system 202 can be the same as PIN management system 102. PIN management system 202 includes computing device 204, contactless card 216, backend server 224, account data 228, key management service 230, and hardware security module 232. Contactless card 216 includes communication interface 220 and memory 218 with applet 234, master key 236, integration key 238, unique identifier 240, and PIN 244. Computing device 204 is communicatively coupled to backend server 224 via network 242 and includes memory 206, user interface 210, and communication interface 208. Memory 206 includes operating system 212 with application 214. Backend server 224 includes memory 226 with manager 254, PIN 246, master key 248, integration key 250, unique identifier 252, PIN key 256, and PIN script 258. It will be appreciated that one or more items in the memories 206, 218, 226 may be in an encrypted or unencrypted format without departing from the scope of the present disclosure. Additionally, one or more items in the memories 206, 218, 226 may be transferred between different memories in the memories 206, 218, 226 in an encrypted or unencrypted format. Figure 2 The illustrated system 200 has a limited number of elements in a particular topology, but it can be appreciated that the PIN management system 202 can include more or fewer elements in alternative topologies, as desired for a given implementation, without departing from the scope of the present disclosure. For example, one or more of the account data 228, the key management service 230, and the hardware security module 232 can be incorporated into the backend server 224 without departing from the scope of the present disclosure. In another example, one or more operations can be performed by the computing device 204 instead of the backend server 224 or the contactless card 216 without departing from the scope of the present disclosure. The embodiments are not limited in this context.

[0050] In various embodiments, the illustrated embodiments relate to various aspects of PIN management functionality provided via computing device 204. In many embodiments, Figure 2 The described aspects of PIN management may occur after user authentication and password authentication, such as with respect to Figure 1One or more processes described. In some embodiments, the PIN management functionality may include presenting a current PIN (e.g., PIN 244) associated with the contactless card 216 via the user interface 110. A determination to change the current PIN associated with the contactless card 216 to an updated PIN may be made based on input provided to the application 214 via the user interface 210. The updated PIN may be identified based on input received via the user interface 210. For example, a user may select an option to change their PIN, and they may then be prompted to provide an updated PIN. The updated PIN 222 (including a request to update the PIN) may be passed to the backend server 224 to associate the updated PIN with the contactless card 216. In many embodiments, the updated PIN 222 request may be encrypted by the computing device 204 before being passed to the backend server 224. For example, the unique identifier 240 previously received from the contactless card 216 may be used to encrypt the updated PIN 222 before being transmitted to the backend server 224. In further examples, the computing device 204 may generate a session key using the unique identifier 240 and encrypt the updated PIN based on the unique identifier 240 .

[0051] In some embodiments, the updated PIN 222 may be stored in the account data 228 associated with the user. For example, the updated PIN 222 may be stored in the account data 228 as an encrypted PIN block. Further, the manager 254 of the backend server 224 may generate or directly generate a PIN script 258 to change the PIN on the contactless card 216. In various embodiments, the manager 254 may utilize one or more of the account data 228, the key management service 230, and the hardware security module 232 to generate the PIN script 258. For example, the hardware security module 232 may generate the PIN script 258. The PIN script 258 may include one or more instructions or operations that may be executed by the contactless card 204 to store the new PIN 222 in a secure memory. In some embodiments, the manager 254 may utilize a PIN key 256 to generate the PIN script 258. In one embodiment, the PIN key 256 may include a key common to a series of accounts. For example, the PIN key 256 may correspond to the first 6 or 8 digits of the account number.

[0052] The PIN script 258 may be delivered to the computing device 204 by the backend server 224 via the network 242. The PIN script 258 may then be delivered to the contactless card 216 by the computing device 204. In many embodiments, the computing device 204 may authenticate the PIN script 258 before delivering the PIN script 258 to the contactless card 216. For example, the computing device 204 may authenticate the PIN script 258 based on a message authentication code received from the backend server 224. In another example, the computing device 204 may use an integrated key to authenticate the PIN script 258 based on a MAC received from the backend server 224.

[0053] In various embodiments, NFC may be used to transfer the PIN script 258 to the contactless card 216. In some embodiments, the application 214 may prompt the user to tap the contactless card 216 to the computing device 204 (or bring it sufficiently close to the computing device 204) for the transmission of the PIN script 258. For example, in response to receiving the PIN script 258 from the backend server 224, the application 214 may utilize the user interface 210 to prompt the user to tap the contactless card 216 to the computing device 204. Once the contactless card 216 receives the PIN script 258, the processing circuit system may execute the PIN script 258 to change the PIN 244 from the current PIN to the updated PIN 222. In some embodiments, the applet 234 may utilize the PIN script 258 to update the PIN 244 in the memory of the contactless card 204.

[0054] In an embodiment, the PIN script 258 may be written in a scripting language such as Python, Ruby, JavaScript, etc. and the instructions may be human-readable. In other instances, the PIN script 258 may be executable and configured in a binary format. The embodiments are not limited in this manner.

[0055] Figure 3An example configuration of a transaction card 300 is shown, which may include a contactless card, a payment card, such as a credit card, debit card, or gift card, issued by a service provider as a service provider mark 302 displayed on the front or back of the transaction card 300. In many embodiments, the transaction card 300 may be the same or similar to the contactless card 116. In some examples, the transaction card 300 is not related to a payment card and may include, but is not limited to, an identification card. In some examples, the transaction card may include a dual interface contactless payment card, a rewards card, etc. The transaction card 300 may include a substrate 308, which may include a single layer or one or more laminated layers composed of plastic, metal, 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 transaction card 300 may have physical characteristics that conform to the ID-1 format of the ISO / IEC 7816 standard, and the transaction card may otherwise conform to the ISO / IEC 14443 standard. However, it should be understood that a transaction card 300 according to the present disclosure may have different characteristics, and the present disclosure does not require that the transaction card be implemented in a payment card. Figure 3 One or more components that are the same or similar to one or more other components of the present disclosure may be included. For example, the transaction card 300 may be the same or similar to the contactless card 116, 216. Further, without departing from the scope of the present disclosure, Figure 3 One or more components or aspects thereof may be incorporated into other embodiments of the present disclosure, or excluded from the described embodiments. Furthermore, one or more components or aspects thereof of other embodiments of the present disclosure may be incorporated into other embodiments of the present disclosure, or excluded from the described embodiments, without departing from the scope of the present disclosure. Figure 3 The embodiments are not limited in this context.

[0056] The transaction card 300 may also include identification information 306 displayed on the front and / or back of the card, and a contact pad 304. The contact pad 304 may include one or more pads and is configured to establish contact with another client device (such as an ATM, user device, smartphone, laptop, desktop or tablet computer) via the transaction card. The contact pad may be designed according to one or more standards such as the ISO / IEC 7816 standard and enable communication according to the EMV protocol. As will be described in Figure 4As discussed further in , the transaction card 300 may also include processing circuitry, an antenna, and other components. These components may be located behind the contact pads 304 or elsewhere on the substrate 308, such as in a different layer of the substrate 308, and may be electrically and physically coupled to the contact pads 304. The transaction card 300 may also include a magnetic stripe or tape that may be located on the back of the card ( Figure 3 Transaction card 300 may also include a near field communication (NFC) device coupled to the antenna that is capable of communicating via the NFC protocol. The embodiments are not limited in this manner.

[0057] like Figure 4 As shown, the contact pads 304 of the transaction card 300 may include a processing circuit system 416 for storing, processing, and communicating information, the processing circuit system including a processor 402, a memory 404, and one or more interfaces 406. It should be understood that the processing circuit system 416 may include additional components, including processors, memories, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware, as required to perform the functions described herein.

[0058] The memory 404 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 transaction card 300 may include one or more of these memories. Read-only memory may be programmable by the manufacturer to be read-only or one-time programmable. One-time programmability provides the opportunity to write once and then read many times. Write-once / read-many memory may be programmed at some point in time after the memory chip has been shipped from the factory. Once the memory is programmed, it cannot be rewritten, but may be read many times. Read / write memory may be programmed and reprogrammed many times after shipping from the factory. Read / write memory may also be read many times after shipping from the factory. In some instances, the memory 404 may be an encrypted memory, which utilizes an encryption algorithm executed by the processor 402 on the encrypted data.

[0059] The memory 404 may be configured to store one or more applets 408, one or more counters 410, a customer identifier 414, and an account number 412, which may be a virtual account number. The one or more applets 408 may include one or more software applications configured to execute on one or more contactless cards, such as Card applet. However, it should be understood that applet 408 is not limited to a Java Card applet, but can be any software application operable on a contactless card or other device with limited memory. One or more counters 410 may include a digital counter sufficient to store an integer. Customer identifier 414 may include a unique alphanumeric identifier assigned to a user of transaction card 300, and the identifier may distinguish the contactless card user from other contactless card users. In some examples, customer identifier 414 may identify both the customer and the account assigned to the customer, and may also identify the transaction card 300 associated with the customer account. As described above, account number 412 may include thousands of one-time use virtual account numbers associated with transaction card 300. Applet 408 of transaction card 300 may be configured to manage account numbers 412 (e.g., configured to select account numbers 412, mark the selected account numbers 412 as used), and transmit account numbers 412 to the mobile device for automatic filling by the auto-fill service.

[0060] The processor 402 and memory elements of the aforementioned exemplary embodiments are described with reference to the contact pad 304, but the present disclosure is not limited thereto. It should be understood that these elements may be implemented outside of the contact pad 304 or completely separated therefrom, or implemented as other elements other than the processor 402 and memory 404 elements located within the contact pad 304.

[0061] In some examples, the transaction card 300 may include one or more antennas 418. The one or more antennas 418 may be placed within the transaction card 300 and around the processing circuitry 416 of the contact pad 304. For example, the one or more antennas 418 may be integral with the processing circuitry 416, and the one or more antennas 418 may be used with an external booster coil. For another example, the one or more antennas 418 may be external to the contact pad 304 and the processing circuitry 416.

[0062] In an embodiment, the coil of the transaction card 300 may act as the secondary coil of an air core transformer. The terminal may communicate with the transaction card 300 by cutting power or amplitude modulation. The transaction card 300 (e.g., the contactless card 116) may use a gap in the power connection of the contactless card to infer data transmitted from the terminal, which gap may be functionally maintained by one or more capacitors. The transaction card 300 may communicate in the reverse direction by switching a load on the contactless card coil or load modulation. Load modulation may be detected in the coil of the terminal by interference. More generally, using the antenna 418, the processor 402, and / or the memory 404, the transaction card 300 provides a communication interface to communicate via NFC, Bluetooth, and / or Wi-Fi communications.

[0063] As explained above, the transaction card 300 may be built on a software platform operable on a smart card or other device with limited memory, such as JavaCard, and one or more applications or applets may be securely executed. An applet 408 may be added to a contactless card to provide a one-time password (OTP) for multifactor authentication (MFA) in various mobile application-based use cases. The applet 408 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 device or point-of-sale terminal)) and generate an NDEF message including a cryptographically secure OTP encoded as an NDEF text tag.

[0064] One example of an NDEF OTP is an NDEF short record layout (SR=1). In such an example, one or more applets 408 may be configured to encode the OTP as an NDEF Type 4 well-known type text tag. In some examples, an NDEF message may include one or more records. Applet 408 may be configured to add one or more static tag records in addition to the OTP record.

[0065] In some examples, one or more applets 408 can be configured to simulate an RFID tag. The RFID tag can include one or more polymorphic tags. In some examples, different cryptographic data is presented each time the tag is read, which can indicate the authenticity of the contactless card. Based on one or more applets 408, the NFC reading of the tag can be processed, the data can be transmitted to a server, such as a server of a banking system, and the data can be verified at the server.

[0066] In some examples, the transaction card 300 and the server may include specific data so that the card can be correctly identified. The transaction card 300 may include one or more unique identifiers (not shown). The counter 410 may be configured to increment each time a read operation occurs. In some examples, each time data is read from the transaction card 300 (e.g., by a mobile device), the counter 410 is transmitted to the server for verification, and a determination is made as to whether the counter 410 is equal to (as part of the verification) the server's counter.

[0067] One or more counters 410 may be configured to prevent replay attacks. For example, if a password has been obtained and replayed, the password is immediately rejected if the counter 410 has been read or used or otherwise ignored. If the counter 410 has not been used, it may be replayed. In some examples, the counter incremented on the card is different from the counter incremented for the transaction. The transaction card 300 cannot determine the application transaction counter 410 because there is no communication between the applets 408 on the transaction card 300. In some examples, the transaction card 300 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 410.

[0068] In some examples, counter 410 may become out of sync. In some examples, counter 410 may be incremented to handle unexpected reads that initiate a transaction, such as reading at an angle, but the application does not process counter 410. In some examples, NFC may be enabled when mobile device 10 is awake, and device 110 may be configured to read available tags, but not take action in response to the reads.

[0069] In order to keep the counter 410 synchronized, an application such as a background application can be executed, which will be configured to detect when the device (e.g., computing device 104) wakes up and synchronizes with the server of the banking system to indicate the reading that occurred due to the detection, and then moves the counter forward. In other examples, a hashed one-time password can be utilized so that an unsynchronized window can be accepted. For example, if within a threshold of 10, the counter 410 can be configured to move forward. But if within a different threshold number, such as within 10 or 1000, a request to perform a resynchronization can be processed, which requests the user to tap, gesture, or otherwise indicate one or more times via a user device via one or more applications. If the counter 410 increases in the appropriate order, it is possible to know that the user has done so.

[0070] The key diversification technique described herein with reference to counter 410, master key and diversification key is an example of encryption and / or decryption key diversification technique. This example key diversification technique should not be considered as limiting the present disclosure, as the present disclosure is equally applicable to other types of key diversification techniques.

[0071] During the creation process of the transaction card 300, two cryptographic keys may be uniquely assigned for each card. The cryptographic keys may include a symmetric key that may be used in both encryption and decryption of data. The Triple DES (3DES) algorithm may be used by EMV, and it is implemented by hardware in the transaction card 300. Using a key diversification process, one or more keys may be derived from a master key based on uniquely identifiable information for each entity that requires a key.

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

[0073] Further, the increment for each card may be unique and assigned by personalization, or algorithmically assigned by some identifying information. For example, odd cards may be incremented by 2, and even cards may be incremented by 5. In some examples, the increment may also vary in terms of sequential reading, such that a card may be incremented in a sequence of 1, 3, 5, 2, 2, ... repeatedly. The specific sequence or algorithmic sequence may be defined at personalization or in one or more processes derived from a unique identifier. This may make it more difficult for a replay attacker to generalize from a small number of card instances.

[0074] 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.

[0075] Figure 5 is a timing diagram illustrating an example sequence for providing authenticated access according to one or more embodiments of the present disclosure. The sequence flow 500 may include a transaction card 300 and a client device 502 , which may include an application 504 and a processor 506 .

[0076] At line 510, the application 504 communicates with the transaction card 300 (e.g., after being brought into proximity with the transaction card 300). The communication between the application 504 and the transaction card 300 may involve the transaction card 300 being brought into close proximity with a card reader (not shown) of the client device 502 to enable NFC data transfer between the application 504 and the transaction card 300.

[0077] At line 508, after communication has been established between the client device 502 and the transaction card 300, the transaction card 300 generates a message authentication code (MAC) password. In some examples, this may occur when the transaction card 300 is read by the application 504. Specifically, this may occur upon reading (such as an NFC read) a near field data exchange (NDEF) tag, which may be created according to the NFC data exchange format. For example, a reader application (such as the application 504) may transmit a message with an applet ID of an NDEF generating applet, such as an applet selection message. Upon confirmation of the selection, a sequence of a select file message followed by a read file message may be transmitted. For example, the sequence may include "select capability file", "read capability file", and "select NDEF file". At this time, a counter value maintained by the transaction card 300 may be updated or incremented, which may be followed by "read NDEF file". At this time, a message may be generated, which may include a header and a shared secret. A session key may then be generated. A MAC password may be created from the message, which may include a header and a shared secret. The MAC password may then be concatenated with one or more random data blocks, and the MAC password and random number (RND) may be encrypted using the session key. Thereafter, the password and header may be concatenated and encoded as ASCII hexadecimal and returned in the NDEF message format (in response to the "Read NDEF File" message).

[0078] In some examples, the MAC password may be transmitted as an NDEF tag, and in other examples, the MAC password may be included with a uniform resource indicator (e.g., as a formatted string). In some examples, the application 504 may be configured to transmit a request to the transaction card 300, the request including instructions for generating a MAC password.

[0079] At line 512, the transaction card 300 sends the MAC password to the application 504. In some examples, the transmission of the MAC password occurs via NFC, however, the present disclosure is not limited thereto. In other examples, such communication may occur via Bluetooth, Wi-Fi, or other wireless data communication means. At line 514, the application 504 passes the MAC password to the processor 506.

[0080] At line 516, processor 506 verifies the MAC password according to instructions from application 122. For example, the MAC password can be verified as explained below. In some examples, verifying the MAC password can be performed by a device other than client device 502 (such as a server of a banking system that performs data communication with client device 502). For example, processor 506 can output the MAC password for transmission to the server of the banking system, which can verify the MAC password. In some examples, for the purpose of verification, the MAC password can act as a digital signature. Other digital signature algorithms, such as public key asymmetric algorithms (e.g., digital signature algorithms and RSA algorithms) or zero-knowledge protocols, can be used to perform the verification.

[0081] Figure 6 An NDEF short record layout (SR=1) data structure 600 is shown according to an example embodiment. One or more applets may be configured to encode the OTP as a text tag of a well-known type of NDEF type 4. In some examples, the NDEF message may include one or more records. The applet may 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: well-known type, text, encoding English (en); Applet ID: D2760000850101; Capabilities: read-only access; Encoding: The authentication message may be encoded as ASCII hexadecimal; Type-length-value (TLV) data may be provided as personalized parameters that can be used to generate an NDEF message. In an embodiment, the authentication template may include a first record with a well-known index for providing actual dynamic authentication data.

[0082] Figure 7 One embodiment of a logic flow 700 is shown, which can represent operations performed in various embodiments in conjunction with the techniques disclosed herein. The logic flow 700 can represent some or all operations performed by one or more components / devices / environments described herein (such as one or more of the contactless card 116, 216, the computing device 104, 204, the backend server 124, 224, the key management service 130, 230, and the hardware security module 132, 232).

[0083] In the illustrated embodiment, the logic flow 700 may start at box 702. At box 702, a user may authenticate based on credentials received via a user interface. For example, a user may authenticate based on credentials received via a user interface 110 of a computing device 104. Continuing to box 704, the logic flow 700 includes: receiving a password from a contactless card near the computing device. For example, the password 122 received from the contactless card 116 may be detected by an application 114 executed on a computing device or a mobile device. Continuing to box 706, the logic flow 700 includes: determining that the contactless card is associated with the user based on the authentication of the password. For example, the backend server 124 may determine that the contactless card 116 is associated with the user logged into the application 114 based on the authentication of the password 122. In some embodiments, the association may be passed from the backend server 124 to the computing device 104 in the verification 156.

[0084] At block 708, the logic flow 700 includes presenting a current personal identification number (PIN) associated with the contactless card via the user interface based on the authentication of the user and the authentication of the password. The current PIN associated with the contactless card can be presented via the user interface based on the authentication of the user and the authentication of the password. For example, the current PIN can be presented via the user interface 110 of the computing device 104 based on the authentication of the user based on the login credentials 154 and the authentication of the password 122.

[0085] At block 710, logic flow 700 includes determining to change a current PIN associated with the contactless card to a new PIN or a PIN different from the current PIN associated with the contactless card. For example, application 214 may determine to change PIN 244 associated with contactless card 216 to an updated PIN based on input received via user interface 210. At block 712, logic flow 700 includes identifying an updated PIN based on input received via the user interface, wherein the updated PIN may be identified based on input received via the user interface. For example, updated PIN 222 may be determined based on input received via user interface 210.

[0086] At block 714, the logic flow 700 includes communicating the updated PIN to the server to associate the updated PIN with the contactless card, wherein the updated PIN may be communicated to the server to associate the updated PIN with the contactless card. For example, the computing device 204 may communicate the updated PIN 222 to the backend server 224 via the network 242 to associate the updated PIN 222 with the contactless card 216.

[0087] At block 716, the logic flow 700 includes identifying the PIN script received from the server in response to passing the updated PIN to the server, wherein the PIN script received from the server can be identified in response to passing the updated PIN to the server. For example, the PIN script 258 can be identified by the application 214 in response to passing the updated PIN 222 to the backend server 224. As will be appreciated, the updated PIN 222 can be received as part of a larger data packet sent from the computing device 204 to the backend server 224. Continuing to block 718, the logic flow 700 includes passing the PIN script to the contactless card to change the PIN stored on the contactless card from the current PIN to the updated PIN. The PIN script can be passed to the contactless card to change the PIN stored on the contactless card from the current PIN to the updated PIN. For example, the computing device 204 can pass the PIN script 258 to the contactless card 216 to change the PIN 244 stored in the memory 218 of the contactless card 216 from the current PIN to the updated PIN 222.

[0088] Figure 8 An example routine 800 is shown that may be performed by a contactless card according to embodiments discussed herein.

[0089] In block 802, the routine 800 includes receiving, by a contactless card, a request for identification information from a computing device. For example, the contactless card may receive a request for authentication from a computing device (such as a mobile device) as part of an NFC exchange. The identification information may include a customer identifier or token, which may be configured to uniquely identify the contactless card (and an associated user), as discussed herein.

[0090] In block 804, routine 800 includes: generating a password including identification information by the contactless card. As discussed herein, the password can be generated to include identification information and encrypted by applying a cryptographic algorithm. In some instances, the cryptographic algorithm can utilize a session key generated based on at least a master key and a count value of the contactless card. Further and in block 806, routine 800 includes: transmitting the password to the computing device by the contactless card.

[0091] The computing device may receive the password and send the password to one or more backend servers to authenticate the identification information and the contactless card. If authenticated and the user successfully logs into the application on the computing device, the user may be allowed to perform one or more operations, including updating the contactless PIN. In response to the user selecting to update the PIN, the computing device may communicate and perform one or more operations to update the current PIN with the new PIN on the backend server, as discussed herein.

[0092] In an embodiment, the back-end server can generate a script or a set of instructions or operations, which can then be passed to the contactless card. The script can cause the contactless card to update the PIN. For example, the script can include information such as a new PIN and one or more instructions to cause the contactless card to write the new PIN into a memory associated with the current PIN. Embodiments are not limited to this approach. For example, the instruction can include an authentication instruction that can be used by the contactless card to authenticate the script. The back-end server can send the script (PIN script) to a computing device to further pass it to the contactless card. In some instances, the back-end server can encrypt the script using an encryption algorithm. In one example, the back-end server can utilize a session key for an authentication password.

[0093] In block 808, the routine 800 includes receiving, by the contactless card, a PIN script from a computing device. As discussed, the PIN script may include one or more instructions configured to cause the contactless card to change a current PIN to a new PIN. In some instances, the contactless card may first decrypt the PIN script by using a session key used to generate the password.

[0094] In block 810, routine 800 includes causing, by the contactless card, the current PIN to be changed to a new PIN based on the PIN script. For example, the PIN script may cause the new PIN to be written to a memory location for storing PINs, such as a memory location associated with the current PIN.

[0095] Fig. 9 An embodiment of an exemplary computer architecture 900 suitable for implementing various embodiments as previously described is shown. In one embodiment, the computer architecture 900 may include or be implemented as part of one or more systems or devices discussed herein, such as a computing device or backend server.

[0096] As used in this application, the terms "system" and "component" are intended to refer to computer-related entities: hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing computer architecture 900. For example, a component can be, but is not limited to, a process running on a processor, a processor, a hard drive, multiple storage drives (optical and / or magnetic storage media), an object, an executable file, an execution thread, a program, and / or a computer. By way of example, both an application running on a server and a server can be components. One or more components can reside in a process and / or an execution thread, and a component can be located on a computer and / or distributed between two or more computers. Further, components can be communicatively coupled to each other by various types of communication media to coordinate operations. The coordination can involve unidirectional or bidirectional information exchange. For example, a component can transmit information in the form of a signal transmitted through a communication medium. Information can be implemented as a signal assigned to various signal lines. In such an assignment, each message is a signal. However, a further example can alternatively adopt a data message. Such a data message can be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

[0097] The computing architecture 100 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, the embodiments are not limited to implementation by the computing architecture 100.

[0098] like Fig. 9 As shown, computing architecture 100 includes processor 912, system memory 904, and system bus 906. Processor 912 may be any of a variety of commercially available computer processors.

[0099] The system bus 906 provides an interface for system components, including but not limited to the system memory 904 to the processor 912. The system bus 906 can be any of a variety of types of bus structures, which can also use any of a variety of commercially available bus architectures to interconnect with a memory bus (whether or not having a memory controller), a peripheral bus, and a local bus. An interface adapter can be connected to the system bus 608 via a slot architecture. 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), NuBus, peripheral component interconnect (PCI), PCI (extended) (PCI (X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA) and similar architectures.

[0100] The computing architecture 100 may include or implement various articles of manufacture. Articles of manufacture may include a computer-readable storage medium 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, which may be read and executed by one or more processors to enable the operations described herein to be performed.

[0101] The system memory 904 may include various types of computer-readable storage media in the form of one or more high-speed memory units, such as read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double 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 memory such as ferroelectric polymer memory, Austenite memory, phase change or ferroelectric memory, silicon-silicon oxide-silicon nitride-silicon oxide-silicon (SONOS) memory, magnetic or optical cards, device arrays such as redundant array of independent disks (RAID) drives, solid-state storage devices (e.g., USB memory, solid-state drive (SSD)), and any other type of storage medium suitable for storing information. Fig. 9 In the illustrative embodiment shown, system memory 904 may include non-volatile 908 and / or volatile 910. A basic input / output system (BIOS) may be stored in non-volatile 908.

[0102] The computer 902 may include various types of computer-readable storage media in the form of one or more low-speed memory units, including an internal (or external) hard disk drive 930, a magnetic disk drive 916 that reads from or writes to a removable magnetic disk 920, and an optical disk drive 928 that reads from or writes to a removable optical disk 932 (e.g., a CD-ROM or DVD). The hard disk drive 930, magnetic disk drive 916, and optical disk drive 928 may be connected to the system bus 906 via a HDD interface 914, an FDD interface 918, and an optical drive interface 934, respectively. The HDD interface 914 for external drive implementations may include at least one or both of a universal serial bus (USB) and IEEE 1394 interface technologies.

[0103] The drives and associated computer-readable media provide volatile and / or nonvolatile storage of data, data structures, computer-executable instructions, etc. For example, a number of program modules may be stored in the drives and nonvolatile 908 and volatile 910, including an operating system 922, one or more applications 942, other program modules 924, and program data 926. In one embodiment, one or more applications 942, other program modules 924, and program data 926 may include, for example, various applications and / or components of the systems discussed herein.

[0104] A user may enter commands and information into the computer 902 through one or more wired / wireless input devices, such as a keyboard 950 and a pointing device such as a mouse 952. Other input devices may include a microphone, an infrared (IR) remote control, a radio-frequency (RF) remote control, a game pad, a stylus, a card reader, a dongle, a fingerprint reader, a glove, a graphics tablet, a joystick, a keyboard, a retina reader, a touch screen (e.g., capacitive, resistive, etc.), a trackball, a trackpad, a sensor, a stylus, and the like. These and other input devices are often connected to the processor 912 through an input device interface 936 coupled to the system bus 906 but may also be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, and the like.

[0105] A monitor 944 or other type of display device is also connected to the system bus 906 via an interface, such as a video adapter 946. The monitor 944 may be internal or external to the computer 902. In addition to the monitor 944, computers typically include other peripheral output devices such as speakers, printers, and the like.

[0106] The computer 902 can operate in a networked environment using logical connections via wired and / or wireless communications with one or more remote computers, such as a remote computer 948. The remote computer 948 can be a workstation, a server computer, a router, a personal computer, a portable computer, a microprocessor-based entertainment appliance, a peer device, or other public network node, and typically includes many or all of the elements described with respect to the computer 902, although only a memory / storage device 958 is shown for purposes of simplicity. The depicted logical connections include wired / wireless connections to a local area network 956 and / or a larger network, such as a wide area network 954. 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 be connected to a global communication network, such as the Internet.

[0107] When used in a LAN 956 networking environment, the computer 902 is connected to the LAN 956 through a wired and / or wireless communication network interface or network adapter 938. The network adapter 938 may facilitate wired and / or wireless communications to the LAN 956, which may also include a wireless access point disposed thereon for communicating with the wireless functionality of the network adapter 938.

[0108] When used in a wide area network 954 networking environment, the computer 902 may include a modem 940 or be connected to a communication server on the wide area network 954, or have other means for establishing communications on the wide area network 954, such as by way of the Internet. The modem 940 may be an internal or external wired and / or wireless device, connected to the system bus 906 via the input device interface 936. In a networked environment, program modules depicted with respect to the computer 902, or portions thereof, may be stored in a remote memory / storage device 958. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

[0109] The computer 902 is operable to communicate with wired and wireless devices or entities using the IEEE 802 family of standards, such as wireless devices operatively arranged in wireless communications (e.g., IEEE 802.11 over-the-air modulation techniques). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth, among others. TM Wireless technology. Therefore, the communication can be a predefined structure like a conventional network, or just an ad hoc communication between at least two devices. Wi-Fi networks use radio technology called IEEE 802.11 (a, b, g, n, etc.) to provide secure, reliable, and fast wireless connections. Wi-Fi networks can be used to connect computers to each other, to the Internet, and to wired networks (which use IEEE 802.3 related media and functions).

[0110] Various elements of the device as previously described herein may include various hardware elements, software elements, or a combination of the two. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processors, 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 may include software components, programs, applications, computer programs, applications, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, 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 can vary depending on any number of factors, such as desired computing rates, power levels, thermal tolerances, processing cycle budgets, input data rates, output data rates, memory resources, data bus speeds, and other design or performance constraints, as desired for a given implementation.

[0111] The components and features of the devices described above may be implemented using any combination of discrete circuit systems, application specific integrated circuits (ASICs), logic gates, and / or single chip architectures. Further, where appropriate, features of the devices may be implemented using microcontrollers, programmable logic arrays, and / or microprocessors, or any combination of the foregoing. It should be noted that hardware, firmware, and / or software elements may be collectively or individually referred to herein as "logic" or "circuitry."

[0112] Fig.10 1 is a block diagram depicting an exemplary communication architecture 1000 suitable for implementing various embodiments as described above. The communication architecture 1000 includes various common communication elements, such as transmitters, receivers, radios, network interfaces, baseband processors, antennas, amplifiers, filters, power supplies, etc. However, the embodiments are not limited to implementation by the communication architecture 1000, which can be consistent with the systems and devices discussed herein.

[0113] like Fig.10As shown, the communication architecture 1000 includes one or more clients 1002 and servers 1004. The server 1004 can implement one or more functions and embodiments discussed herein. The client 1002 and the server 1004 are operably connected to one or more corresponding client data stores 1006 and server data stores 1008, which can be used to store local information of the corresponding client 1002 and server 1004, such as Cookies and / or associated context information.

[0114] The client 1002 and the server 1004 can communicate information to each other using a communication framework 1010. The communication framework 1010 can implement any well-known communication technologies and protocols. The communication framework 1010 can be implemented as a packet-switched network (e.g., a public network such as the Internet, a private network such as an intranet, etc.), a circuit-switched network (e.g., a public switched telephone network), or a combination of a packet-switched network and a circuit-switched network (with appropriate gateways and converters).

[0115] The communication framework 1010 can implement various network interfaces, which are arranged to receive, transmit and connect to the communication network. The network interface can be regarded as a special form of input / output (I / O) interface. The network interface can adopt a connection protocol, including but not limited to direct connection, Ethernet (such as thick, thin, twisted pair 10 / 100 / 1000Base T and the like), token ring, wireless network interface, cellular network interface, IEEE 802.7ax network interface, IEEE802.16 network interface, IEEE 802.20 network interface and the like. Further, multiple network interfaces can be used to participate in various communication network types. For example, multiple network interfaces can be used to allow communication through broadcast, multicast and unicast networks. If the processing requirements specify a greater speed and capacity, a distributed network controller architecture can be similarly adopted to aggregate, load balance, and otherwise increase the communication bandwidth required by the client 1002 and the server 1004. The communication network can be any type and combination of wired and / or wireless networks, including but not limited to direct interconnection, secure customized connection, private network (such as corporate intranet), public network (such as Internet), personal area network (PAN), local area network (LAN), metropolitan area network (MAN), mission operating as a node on the Internet (OMNI), wide area network (WAN), wireless network, cellular network and other communication networks.

[0116] As previously referenced Figures 1 to 8The various elements of the described devices may include various hardware elements, software elements, or a combination of the two. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processors, 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 may include software components, programs, applications, computer programs, applications, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, 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 can vary depending on any number of factors, such as desired computing rates, power levels, thermal tolerances, processing cycle budgets, input data rates, output data rates, memory resources, data bus speeds, and other design or performance constraints, as desired for a given implementation.

[0117] One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium representing various logics within a processor, which, when read by a machine, causes the machine to manufacture logic to perform the techniques described herein. Such representations, referred to as "IP cores," may be stored on tangible machine-readable media and supplied to various customers or manufacturing facilities to be loaded into manufacturing machines that manufacture logic or processors. Some embodiments may be implemented, for example, using a machine-readable medium or article, which may store instructions or instruction sets, which, if executed by a machine, may cause the machine to perform methods and / or operations according to an embodiment. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., 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, 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, compact disk read only memory (CD-ROM), compact disk recordable (CD-R), compact disk rewritable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of digital versatile disks (DVDs), magnetic tapes and cassettes, etc. 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, etc., implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language.

[0118] The foregoing description of example embodiments has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. In light of this disclosure, many modifications and variations are possible. It is intended that the scope of the disclosure is not limited by this detailed description, but rather by the appended claims. Applications filed in the future claiming priority to the present 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 presented.

Claims

1. A device comprising: processor; and a memory comprising instructions that, when executed by the processor, cause the processor to: authenticating the user based on credentials received via the user interface; detecting a code received from a contactless card in proximity to the processor; determining that the contactless card is associated with the user based on authentication of the password; presenting, via the user interface, a current personal identification number (PIN) associated with the contactless card based on authentication of the user and authentication of the password; determining to change a current PIN associated with the contactless card to an updated PIN; identifying the updated PIN based on input received via the user interface; communicating the updated PIN to a server to associate the updated PIN with the contactless card; identifying a PIN script received from the server in response to communicating the updated PIN to the server; as well as The PIN script is passed to the contactless card to change the PIN stored on the contactless card from the current PIN to the updated PIN.

2. The device according to claim 1, wherein: The mobile device includes the processor and the memory, and the password is received from the contactless card via near field communication.

3. The device according to claim 1, wherein: The instructions, when executed by the processor, further cause the processor to communicate the password to the server and receive verification from the server to authenticate the password.

4. The device according to claim 1, wherein: The instructions, when executed by the processor, further cause the processor to encrypt the updated PIN for communication to the server.

5. The device according to claim 4, wherein: The instructions, when executed by the processor, further cause the processor to encrypt the updated PIN based on a unique identifier (UID) received from the contactless card.

6. The device according to claim 5, wherein: The instructions, when executed by the processor, further cause the processor to generate a session key using the UID to encrypt the updated PIN based on the UID.

7. The device according to claim 1, wherein: The instructions, when executed by the processor, further cause the processor to authenticate the PIN script based on a message authentication code (MAC) received from the server.

8. The device according to claim 7, wherein: The instructions, when executed by the processor, further cause the processor to authenticate the PIN script using an integration key based on the MAC received from the server.

9. At least one non-transitory computer-readable medium comprising a set of instructions that, in response to being executed by a processor circuit, cause the processor circuit to: authenticating the user based on credentials received via the user interface; detecting a password received from a contactless card in proximity to a processor; determining that the contactless card is associated with the user based on authentication of the password; presenting, via the user interface, a current personal identification number (PIN) associated with the contactless card based on authentication of the user and authentication of the password; determining to change a current PIN associated with the contactless card to an updated PIN; identifying the updated PIN based on input received via the user interface; communicating the updated PIN to a server to associate the updated PIN with the contactless card; identifying a PIN script received from the server in response to communicating the updated PIN to the server; as well as The PIN script is passed to the contactless card to change the PIN stored on the contactless card from the current PIN to the updated PIN.

10. The at least one non-transitory computer-readable medium of claim 9, wherein: The set of instructions, in response to execution by the processor circuit, further cause the processor circuit to communicate the password to the server and receive verification from the server to authenticate the password.

11. The at least one non-transitory computer-readable medium of claim 9, wherein: The set of instructions, in response to execution by the processor circuit, further cause the processor circuit to encrypt the updated PIN for communication to the server.

12. The at least one non-transitory computer readable medium of claim 11, wherein: The set of instructions, in response to execution by the processor circuit, further cause the processor circuit to encrypt the updated PIN based on a unique identifier (UID) received from the contactless card.

13. The at least one non-transitory computer-readable medium of claim 12, wherein: The set of instructions, in response to execution by the processor circuit, further cause the processor circuit to generate a session key using the UID to encrypt the updated PIN based on the UID.

14. The at least one non-transitory computer-readable medium of claim 9, wherein: The set of instructions, in response to execution by the processor circuit, further cause the processor circuit to authenticate the PIN script based on a message authentication code (MAC) received from the server.

15. The at least one non-transitory computer readable medium of claim 14, wherein: The set of instructions, in response to execution by the processor circuit, further cause the processor circuit to authenticate the PIN script using an integrated key based on the MAC received from the server.

16. A computer-implemented method comprising: authenticating the user based on credentials received via the user interface; Detecting a PIN received from a contactless card; determining that the contactless card is associated with the user based on authentication of the password; presenting, via the user interface, a current personal identification number (PIN) associated with the contactless card based on authentication of the user and authentication of the password; determining to change a current PIN associated with the contactless card to an updated PIN; identifying the updated PIN based on input received via the user interface; communicating the updated PIN to a server to associate the updated PIN with the contactless card; identifying a PIN script received from the server in response to communicating the updated PIN to the server; as well as The PIN script is passed to the contactless card to change the PIN stored on the contactless card from the current PIN to the updated PIN.

17. The computer-implemented method of claim 16, comprising: The updated PIN is encrypted for communication to the server.

18. The computer-implemented method of claim 17, comprising: The updated PIN is encrypted based on a unique identifier (UID) received from the contactless card.

19. The computer-implemented method of claim 18, comprising: A session key is generated using the UID to encrypt the updated PIN based on the UID.

20. The computer-implemented method of claim 16, comprising: The PIN script is authenticated based on a message authentication code received from the server.

Images