Intelligent Card Unlock

Abstract

Various examples are provided that are generally directed to unlocking a locked contactless card for use in payment in card-present transactions. The contactless card is a payment card associated with a payment account. An application executing on a mobile device may be operable to enable unlocking the locked contactless card and to receive an indication that the contactless card associated with the mobile device has been unlocked for use in card-present transactions. The application may present information related to authorized uses of the unlocked contactless card via a graphical user interface. The authorized uses of the unlocked contactless card may be changed via the graphical user interface.

Description

[Technical Field]

[0001] This application claims priority to U.S. Non-provisional Application No. 16 / 863,179, entitled "Unlocking an Intelligent Card," filed April 30, 2020. The contents of the aforementioned application are incorporated herein by reference in their entirety.

[0002] Examples herein relate generally to computing platforms and, more particularly, to intelligently unlocking payment cards, including contactless cards, used in transactions. [Background technology]

[0003] The payment card lock feature currently allows a user to lock a payment card so that it cannot be used when the user does not have the card, i.e., when the card is lost, stolen, or misplaced. Locking the card prevents it from being used for any transactions. The card lock feature allows a user to determine if a card is simply misplaced and not stolen without having to go through all the actions required to report a card as lost or stolen. The actions of reporting a card as lost or stolen may include placing a hold on the account associated with the card, sending a new physical card via mail service, and other inconveniences. The payment card lock feature was developed to eliminate the actions and inconvenience required for such card replacement.

[0004] It would be beneficial and advantageous in terms of fraud prevention and user security if payment cards could be locked at all times and easily unlocked at the user's request or when it is determined that the user is in a convenient time or location where they are likely to be located. Summary of the Invention

[0005] Examples disclosed herein provide systems, methods, articles of manufacture, and computer-readable media that enable unlocking of contactless cards for use in card-present transactions. According to one embodiment, the apparatus may include a display device, a processor circuit, a transceiver, a card reader circuit, and a memory. The processor circuit may be operable to display a graphical user interface on the display device. The transceiver may be connected to the processor circuit and operable to communicate with an external device. The card reader circuit may be connected to the processor circuit and operable to transmit and receive signals within a signal field. The memory may be connected to the processor circuit and operable to store an unlock-lock application. The unlock-lock application may have instructions that, when executed by the processor circuit, cause the processor circuit to receive encrypted data from the contactless card via the card reader circuit. The contactless card may be locked to prevent its use in card-present transactions, and the encrypted data may be generated based on a cryptographic algorithm and a diversified key. The unlock-lock application executed by the processor circuit may transmit the encrypted data to an authentication server for authentication and unlocking of the contactless card. An indication may be received indicating that the contactless card has been unlocked and unlocked for use in card-present transactions. The unlocked indication indicates that the contactless card has been authenticated. User preferences for use of the contactless card in payment card transactions when unlocked may be identified, and a representation of the identified user preferences for the contactless card may be presented in a graphical user interface displayed on the display device.

[0006] Another example discloses a system including a contactless card and a mobile device. The contactless card may include a processor, a memory, and a communication interface operable to support at least one of near field communication, Bluetooth, or Wi-Fi communication protocols. The mobile device may include a mobile device processor, a mobile device memory, a transceiver, a display device, and a card reading circuit. The card reading circuit is operable to communicate with the contactless card via the communication interface, and the mobile device memory stores programming code including an instance of an unlock-lock application. The processor of the contactless card may be operable to generate encrypted data using a cryptographic algorithm and a diversified key and to transmit, via the communication interface, a signal including the encrypted data usable to authenticate the contactless card. When executed by the mobile device processor, the programming code causes the mobile device processor to perform functions including receiving, from the card reading circuit, a signal including the encrypted data transmitted from the contactless card. The encrypted data may be transferred via the transceiver for authenticating and unlocking the contactless card. The mobile device processor may receive an unlock indication indicating that the contactless card has been unlocked. User preferences may be identified that permit limited use of the contactless card when unlocked for use in card-present transactions, and a representation of the identified user preferences for the contactless card when unlocked may be displayed in a graphical user interface displayed on a display device.

[0007] An example of a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium may be embodied with computer-readable program code. The computer-readable program code is executable by a processor circuit and causes the processor circuit to receive encrypted data from a communication interface of a contactless card via a card reading circuit. The contactless card may be locked from use in a card-present transaction, and the encrypted data may be generated based on a cryptographic algorithm and a diversified key. The encrypted data may be transmitted to an authentication server to enable unlocking of the contactless card. An unlock indication may be received indicating that the contactless card has been unlocked for use in a card-present transaction. The unlock indication is proof of the encrypted data. Authorized contactless card usage restrictions regarding the ability of the contactless card to complete payment card transactions may be identified. An indication of the unlocked-for-use status and the authorized contactless card usage restrictions may be presented in a graphical user interface presented on a display device. [Brief explanation of the drawings]

[0008] [Figure 1A] 1A and 1B show an example of a system for locking and unlocking cards used in transactions. [Figure 1B] 1A and 1B show an example of a system for locking and unlocking cards used in transactions.

[0009] [Figure 2A] 2A and 2B show an example of locking and unlocking a card for use in a transaction. [Figure 2B] 2A and 2B show an example of locking and unlocking a card for use in a transaction.

[0010] [Figure 3A] 3A-3C show an example of locking and unlocking a card for use in a transaction. [Figure 3B]3A-3C show an example of locking and unlocking a card for use in a transaction. [Figure 3C] 3A-3C show an example of locking and unlocking a card for use in a transaction.

[0011] [Figure 4A] 4A and 4B show an example of a contactless card suitable for use in the example of FIGS. 1-2B. [Figure 4B] 4A and 4B show an example of a contactless card suitable for use in the example of FIGS. 1-2B.

[0012] [Figure 5] FIG. 5 illustrates an example of a mobile device suitable for implementing the examples of FIGS.

[0013] [Figure 6] FIG. 6 illustrates an example of a computing architecture suitable for implementing the examples of FIGS. DETAILED DESCRIPTION OF THE INVENTION

[0014] An example disclosed herein provides a secure technique for locking and unlocking a payment card for use in card-present transactions. Generally, payment cards are unlockable and operable to complete card-present transactions with a merchant. Even though a card can be locked if the user is unaware that it is lost, there is still an opportunity for the lost card to be used for fraudulent activities. The foregoing example advantageously provides an easy-to-use and easy-to-implement solution that reduces the likelihood of credit fraud.

[0015] In the above example, an unauthenticated contactless card locks the contactless card from being used in card-present transactions, whereas authentication of the contactless card indicates that the contactless card is valid (e.g., authenticated and assigned to an authorized user and payment account) and unlocks the contactless card so that it can be used in card-present transactions.

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

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

[0018] Referring to the drawings, like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding. It will be apparent, however, that the novel examples may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form to facilitate explanation. It is intended to cover all modifications, equivalents, and alternatives falling within the scope of the claims.

[0019] FIG. 1A illustrates a schematic diagram of an example system 100 consistent with examples of the disclosure.

[0020] In the example of FIG. 1A , mobile device 110 may include processor circuitry 147, communication interface 146, touchscreen display 149, and memory 141. Memory 141 may be operable to store account authentication application 143, unlock-lock application 144, and other applications 145, such as messaging applications, banking applications, location data applications, and phone applications. Each application 143-145 may include computer-readable programming code executable by a processor or processor circuitry. Account authentication application 143 may provide functions and features in response to a request from unlock-lock application 144. Examples of functions and features provided in response to a request are described with reference to FIGS. 2A and 2B .

[0021] The touchscreen display 149 may be coupled to the processor circuitry 147, for example, and operable to present a graphical user interface (shown in another example) in response to signals from the processor circuitry 147. The communication interface 146 may be operable to communicate with external devices, such as the server 120, via multiple transceivers (not shown in this example). For example, the mobile device 110 may be a smartphone (shown in another example) equipped with a cellular transceiver and a Wi-Fi transceiver (e.g., an 802.11 family of transceivers). The card reader 148 may include near-field communication (NFC) circuitry operable to transmit and receive signals within the signal field of the mobile device 110 (e.g., a short-range area of ​​approximately 2-10 cm). As shown, the memory 141 of the mobile device 110 includes an instance of an operating system (OS) 142. Examples of operating systems 142 include the Android® OS, iOS®, Linux®, and Windows® operating systems. As shown, OS 142 includes an account authentication application 143, an unlock-lock application 144, and one or more other applications 145. Account authentication application 143 allows a user to perform various account-related operations, such as viewing account balances, purchasing items, and processing payments. A user must initially authenticate using authentication information to access account authentication application 143. For example, authentication information may include a username and password, biometric information, etc.

[0022] The executed account authentication application causes the processor circuitry 147 to perform functions related to authenticating contactless cards such as 101. For example, when a locked contactless card 101 is placed within the signal field of a card reader 148 of the mobile device 110, the contactless card 101 establishes a communication path with the mobile device 110 and provides encrypted data 190 to the account authentication application 143 of the mobile device 110. The account authentication application 143 can then transmit the encrypted data 190 over the network 130 to the server 120, which authenticates and unlocks the contactless card 101 for use in card-present transactions. The server 120 may provide an indication to the account authentication application 143 via a message over the network 130 indicating the successful authentication and unlocking of the contactless card 101. The account authentication application 143 may provide instructions or otherwise notify an unlock-lock application 144, which, when executed, causes the processor circuitry 147 to perform functions related to restricting the operation of the unlocked contactless card. Processor circuitry 147 causes processor circuitry to perform functions when account authentication application 143 is executed. When account authentication application 143 and unlock-lock application 144 are operational, the content of the graphical user interface may be generated or provided by account authentication application 143 and unlock-lock application 144 executed by processor circuitry 147.

[0023] The foregoing operational examples provide context for the functionality of each disclosed example, and it may be helpful to describe the components of system 100 in more detail with reference to the functions performed by each component.

[0024] As shown, system 100 includes one or more contactless cards 101, one or more mobile devices 110, and a server 120. Contactless card 101 may be any type of payment card, such as a credit card, debit card, ATM card, or gift card. Contactless card 101 may include one or more chips (not shown), such as a radio frequency identification (RFID) chip, operable to communicate with mobile device 110 via NFC, the EMV® standard, or other short-range protocols over wireless communication. While NFC is used as an example communication protocol, the present disclosure is equally applicable to other types of wireless communication, such as the EMV® standard, Bluetooth®, and / or Wi-Fi. Mobile device 110 may be any type of network-enabled computing device, such as a smartphone, tablet computer, wearable device, laptop, portable gaming device, or the like. Server 120, which includes one or more processors 121, may be any type of computing device, such as a server, workstation, computer cluster, cloud computing platform, virtualized computing system, or the like.

[0025] The contactless card 101 may include a processor 115 and a communication interface 116. As described with reference to the examples of Figures 4A and 4B, the processor 115 may be circuitry operable to perform logical functions, and the communication interface 116 may be circuitry operable to exchange signals with other devices, such as the mobile device 110.

[0026] As shown, the contactless card's memory 102 includes a data store for card data 103, a counter 104, a master key 105, a diversified key 106, a unique customer identifier 107, and an account number 108. The card data 103 generally includes account-related information, such as information used to process payments using the contactless card 101. For example, the card data 103 may include an account number, an expiration date, a billing address, or a security code (CVV). The account number may be any type of account number, such as a primary account number (PAN), a virtual account number, and / or a token generated based on a PAN. Other types of account numbers are contemplated, and the use of an account number or other types of card data 103 should not be considered limiting of this disclosure. The card data 103 may further include a name, a billing address, a shipping address, and other account-related information. The account number 108 stores a single-use virtual account number with an associated expiration date and CVV value. For example, the account number 108 may include multiple single-use virtual account numbers, expiration dates, and CVV values.

[0027] As shown, server 120 includes a data store of account data 124 and memory 122. The account data 124 includes account-related data for multiple users and / or accounts. The account data 124 may include at least a master key 105, a counter 104, a customer identifier 107, an associated contactless card 101, the account holder's name, a billing address for the account, one or more shipping addresses, one or more virtual card numbers, and biographical information for each account. Memory 122 may include a management application 123, which may include one or more of an instance of card data 103 for the account, an instance of counter 104, an instance of master key 105, and an instance of diversified key 106 from the account data 124.

[0028] The system 100 is operable to implement key diversification to protect data, which may be referred to herein as a key diversification technique. Generally, the server 120 (or other computing device) and the contactless card 101 may be provisioned to use the same master key 105 (also referred to as a master symmetric key). More specifically, each contactless card 101 is programmed with an individual master key 105 that has a corresponding pair with the server 120. For example, when the contactless card 101 is manufactured, a unique master key 105 may be programmed into the memory 102 of the contactless card 101. Similarly, the unique master key 105 may be stored in the account data 124 of the server 120, in the customer record associated with the contactless card 101 (and / or in another secure location). The master key may be kept secret from anyone other than the contactless card 101 and the server 120, thereby improving the security of the system 100.

[0029] The master key 105 may be used in conjunction with a counter 104 to enhance security through key diversification. The counter 104 includes a value that is synchronized between the contactless card 101 and the server 120. The value of the counter 104 may include a numerical value that changes each time data is exchanged between the contactless card 101 and the server 120 (and / or between the contactless card 101 and the mobile device 110). To enable NFC data transfer between the contactless card 101 and the mobile device 110, the account authentication application 143 may communicate with the contactless card 101 when the contactless card 101 is sufficiently close to a card reader 148 of the mobile device 110. The card reader 148 may be operable to read from and / or communicate with the contactless card 101 (e.g., via NFC, Bluetooth, RFID, Wi-Fi, etc.). Accordingly, an exemplary card reader 148 includes an NFC communication module, a Bluetooth communication module, and / or an RFID communication module.

[0030] After the account authentication application 143 and / or the unlock-lock application 144 are launched or opened, the loaded application may prompt the user to tap the contactless card 101 against the mobile device 110. For example, the user may tap the contactless card 101 against the mobile device 110, thereby bringing the contactless card 101 close enough to the card reader 148 of the mobile device 110 to enable NFC data transfer between the contactless card 101 and the card reader 148 of the mobile device 110. In some examples, the mobile device 110 may trigger the card reader 148 via an API call or the like. Additionally and / or alternatively, the mobile device 110 may trigger the card reader 148 by periodically polling the card reader 148. More generally, the mobile device 110 may trigger the card reader 148 to engage in communication using any feasible method. When the contactless card 101 is tapped to the mobile device 110 (e.g., brought within NFC range of the card reader 148), the account authentication application 143, on its own initiative or in response to a signal from the unlock-lock application 144, may generate encrypted data 190 and send instructions to the contactless card 101, as depicted in FIG. 1A.

[0031] In response, contactless card 101 increments the value of counter 104 and provides master key 105 and the value of counter 104 as inputs to a cryptographic algorithm to generate diversified key 106 as output. Contactless card 101 may then encrypt customer identifier 107 using diversified key 106 to generate encrypted data 190. Contactless card 101 may then transmit (e.g., via an NFC connection, a Bluetooth connection, etc.) encrypted data 190 to account authentication application 143 on mobile device 110. Account authentication application 143 on mobile device 110 may then transmit encrypted data 190 to server 120 over network 130. In at least one example, contactless card 101 transmits the value of counter 104 along with encrypted data 190.

[0032] After communication is established between the mobile device 110 and the contactless card 101, the contactless card 101 may generate a message authentication code (MAC) cipher. In particular, this may occur upon reading, such as an NFC read, of a Near Field Communication Data Exchange (NDEF) tag, which may be generated according to the NFC data exchange format. For example, the account authentication application 143 and / or a reader, such as the card reader 148, may send a message, such as an applet selection message, that includes the applet ID of the NDEF generation applet. At this time, the value of the counter 104 maintained by the contactless card 101 may be updated or incremented. At this point, a message may be generated that includes a header and a shared secret. A session key may then be generated. A MAC cipher may be generated from the message, which may include the header and the shared secret. The MAC cipher may then be concatenated with one or more blocks of random data, and the MAC cipher and random number (RND) may be encrypted with the session key. The cipher and header may then be concatenated, encoded as ASCII hexadecimal, and returned in the form of an NDEF message (e.g., indicating the answer to another message). In some examples, the MAC code may be transmitted as an NDEF tag, and in other examples, the MAC code may be included with a uniform resource indicator (URI) (e.g., as a formatted string). Contactless card 101 may transmit the MAC code to mobile device 110, which may forward the MAC code to server 120 for verification, as described below. However, in some examples, mobile device 110 may verify the MAC code.

[0033] More generally, when preparing to transmit data (e.g., to server 120 and / or mobile device 110), contactless card 101 may increment the value of counter 104. Contactless card 101 may then provide master key 105 and the value of counter 104 as input to a cryptographic algorithm that generates diversified key 106 as output. The cryptographic algorithm may include an encryption algorithm, a hash-based message authentication code (HMAC) algorithm, a cipher-based message authentication code (CMAC) algorithm, etc. Non-limiting examples of cryptographic algorithms may include symmetric encryption algorithms such as 3DES or AES128, symmetric HMAC algorithms such as HMAC-SHA-256, symmetric CMAC algorithms such as AES-CMAC, etc. Contactless card 101 may then encrypt data (e.g., customer identifier 107 and other data) using diversified key 106. The contactless card 101 may then transmit the encrypted data (e.g., encrypted data 190) to the account authentication application 143 of the mobile device 110 (e.g., via an NFC connection, a Bluetooth connection, etc.). For example, the contactless card 101 may be operable to transmit the encrypted data via the tap 174 and receive a signal when the contactless card is within the signal field of the card reader 148. Similarly, the card reader 148 may also be operable to transmit and receive a signal. More particularly, the card reader 148 may receive the encrypted data 190 via the tap 174 while the contactless card 101 is locked. The account authentication application 143 of the mobile device 110 may then transmit the encrypted data to the server 120 via the network 130. In at least one example, the contactless card 101 transmits the value of the counter 104 along with the encrypted data. In such an example, contactless card 101 may transmit either the encrypted value of counter 104 or the unencrypted value of counter 104.

[0034] Upon receiving the encrypted data 190 from the mobile device 110, the management application 123 of the server 120 may be operable to validate the encrypted data 190 with key diversification. The key diversification performed by the management application 123 of the server 120 may include performing the same symmetric encryption (by the contactless card's processor 115) using the value of the counter 104 as input for the encryption and the master key 105 as the key for the encryption. As mentioned above, the value of the counter 104 may be determined by the data received with the encrypted data 190 from the mobile device 110, or by a value of the counter 104 maintained by the server 120 to perform the variance of the contactless card's 101 key, as previously described. The output of the encryption may be the same as the value of the diversified key 106 generated by the contactless card 101. The management application 123 may then use the diversified key 106 to decrypt the encrypted data 190 received over the network 130, and the encrypted data 190 may reveal the data transmitted by the contactless card 101 (e.g., at least the customer identifier 107). In doing so, the management application 123 may authenticate the data transmitted from the contactless card 101 via the mobile device 110, such as by comparing the decrypted customer identifier 107 with a customer ID in the account data 124 for the account and validating the encrypted data received from the contactless card 101 if the customer ID values ​​match.

[0035] While the counter 104 is shown as an example, other data may be used to secure communications between the contactless card 101, the mobile device 110, and / or the server 120. For example, the counter 104 may be exchanged with a random nonce generated each time a new diversified key 106 is needed, the full counter value transmitted by the contactless card 101 and the server 120, a portion of the counter value transmitted by the contactless card 101 and the server 120, a counter maintained independently by but not transmitted between the contactless card 101 and the server 120, a one-time passcode exchanged between the contactless card 101 and the server 120, a cryptographic hash of data, etc. In some examples, one or more portions of the diversified key 106 may be used by a party to create multiple diversified keys 106.

[0036] As shown, server 120 may include one or more hardware security modules (HSMs) 125. For example, one or more HSMs 125 may be operable to perform one or more cryptographic operations as disclosed herein. In some examples, one or more HSMs 125 may be configured as special-purpose security devices operable to perform one or more cryptographic operations. HSMs 125 may be configured such that keys are never revealed outside of HSMs 125 but instead are maintained within HSMs 125. For example, one or more HSMs 125 may be operable to perform at least one of key derivation, decryption, and MAC operations. One or more HSMs 125 may be included within server 120 or may be in data communication with server 120.

[0037] After authenticating the locked contactless card 101 and subsequently unlocking the contactless card for use in a card-present transaction, the components of the system 100 can operate according to the example system shown in FIG. 1B and the accompanying discussion.

[0038] 1B , in addition to the mobile device 110, network 130, and server 120 that perform the same functions, the system 184 further includes an unlock server 129, a server 160 that hosts a payment account component 163, a point-of-sale device (POS device) 170 at a merchant 180, and a network 191 that connects the POS device 170 to the payment account component 163 of the server 160. The unlock server 129 may include a processor and a memory having programming code or instructions and may be operable to manage, via an instance of an unlock-lock application 144″, the number of unlocked contactless cards belonging to other users, as well as user preference settings that limit the use of the unlocked contactless cards 101′.

[0039] Returning to the exemplary operation, in response to transmitting encrypted data 190 to server 120, processor circuitry 147 executing account authentication application 143 may receive an indication from server 120 that contactless card 101 has been unlocked based on authentication of encrypted data 190. Account authentication application 143 may also output an indication to unlock-lock application 144 that the contactless card has been unlocked.

[0040] In another example, the unlock server 129 may be operable to receive from the mobile device 110 user preference settings that are indicated as selected for permitted uses of the contactless card in card-present transactions when the contactless card is unlocked. The unlock server 129 may further be operable to obtain from the mobile device 110 a determined location of the mobile device via a location data application running as one of the other applications 145. The location of the mobile device 110 may be used by an instance of the unlock-lock application 144'' to generate a list of merchants that satisfy the user-preferred limited card uses.

[0041] The unlock server 129 may be operable to manage user preferences for an unlock-lock application executing on the mobile device processor (i.e., processor circuitry 147) of the mobile device 110. In a more detailed example, the unlock server 129 may be operable to receive user preference settings from the mobile device indicating selected, permitted uses of an unlocked contactless card in a card-present transaction. The unlock server may be operable to derive a maximum transaction amount threshold from the user preference settings. For example, for a transaction at a restaurant, the user preference may be set to $50. The unlock server 129 may forward the maximum transaction amount threshold derived from the user preference settings to the payment account component 163 of the server 160 via either the communication link 188 or the network 130. The communication link 188 may be a direct communication connection between the unlock server 129 and the server 160. The maximum transaction amount threshold may also be forwarded to the mobile device 110 for presentation in a graphical user interface presented on the touchscreen display 149.

[0042] 1A , once the management application 123 of the server 120 verifies the data 190 encrypted using key diversification, the management application 123 may send an authentication indication to the account authentication application 143 of the mobile device 110, and in one example, may establish a connection to the application programming interface (API) of the unlock-lock application 144 to provide the authentication indication to the unlock-lock application 144. When the unlock-lock application 144 receives the authentication indication, which it interprets as indicating that the contactless card 101′ has been unlocked, the unlock-lock application 144 may send a request to the unlock server 129 regarding usage restrictions for the unlocked contactless card 101′. The restricted uses (described in more detail with reference to other examples) may include a list of merchants within a region that are whitelisted for card-present transactions using the unlocked contactless card 101′. The merchant 180 may be on a list of whitelisted merchants. The unlocked contactless card 101' has the functionality of the contactless card 101, the only difference being that the unlocked contactless card 101' has been unlocked and is now capable of participating in certain card-present transactions, subject to the limited uses disclosed herein. For example, the unlocked contactless card 101' may be operable to communicate with a card reader 148 via a wireless connection 175. The unlocked contactless card 101' may be presented for a card-present transaction, and transaction data 166 may be transmitted from the contactless card 101' to a POS device 170 at a merchant 180 via a wireless connection 177. The transaction data 166 may be, for example, information used to complete the transaction, such as a card number, an account number, or some other identifying information that may be used to authenticate whether the contactless card 101' is connected to an authorized payment account. Of course, if the contactless card 101' is equipped with an identification chip or magnetic strip, the information required for the transaction can be transmitted by inserting the identification chip into the POS device 170 or swiping the magnetic strip and providing the transaction data 166.The POS device 170 of the merchant 180 may be operable to transmit the transaction data 166 over the network 191 to the payment account component 163 for verification processing.

[0043] Server 160 may be operable to receive transaction data 166 and determine whether the transaction can be completed based on a verification process performed by payment account component 163. For example, payment account component 163 may use transaction data 166 to process financial aspects of the transaction, such as, for example, that the transaction is a card-present transaction, that the user's payment account associated with the unlocked contactless card 101′ is valid and has sufficient credit or funds, that contactless card 101′ is unlocked for the card-present transaction, that user preference settings provided by unlock-lock application 144 are satisfied, etc. Transaction response data 167 of server 160 may be an indication of the results of the verification process performed by payment account component 163 and may be sent back to POS device 170 via network 191.

[0044] The payment account component 163 may include additional functionality beyond enabling card-present transaction completion. The payment account component may include query logic or machine learning that can be applied to past transactions to identify patterns or trends and whitelist those transactions deemed low risk. For example, patterns or trends can reveal frequent visits to particular merchants, dollar thresholds that a user does not frequently exceed, and / or location patterns, such as consistently purchasing meals within one mile of the user's office or home and / or at particular times of the day. These patterns and trends can be used to identify new user preferences or modify existing user preferences. For example, in situations where a new restaurant or coffee shop opens within a set radius, the user preferences can be modified to generate a list of any lunch locations with a particular merchant category code to allow card-present transaction completion. For example, the user preferences can also be modified to allow purchases at restaurants within one mile of the user's office that cost less than $25.

[0045] The example of FIG. 1B illustrates how management application 123 of server 120 verifies encrypted data 190 of FIG. 1A before transmitting card data 103 from server 120 to mobile device 110. In at least one example, management application 123 may encrypt card data 103 before transmitting to account authentication application 143. As mentioned, card data 103 may include the account number, CVV, and / or expiration date of contactless card 101. Card data 103 may further include the account holder's first name, last name, shipping address, and billing address. In one example, the account number of card data 103 may be a virtual card number generated after verification of encrypted data 190 by management application 123. In another example, the account number of card data 103 is a record from account number 108. In one example, the account authentication application 143 (or another element of the OS) stores the first name and last name. The account authentication application 143 may provide an indication of the authentication of the card data 103 and / or encrypted data 190 to the API of the unlock-lock application 144. The unlock-lock application 144 may use the interpretation information provided by the account authentication application 143 to determine whether the contactless card is unlocked for card-present transactions, and if so, implement user preferences as described with reference to this example and the examples of Figures 2A-3C.

[0046] In one example, the card data 103 sent from the server 120 to the mobile device 110 includes all relevant information needed to make a purchase using the account associated with the contactless card 101 (e.g., account number, expiration date, CVV, billing address, shipping address, first name, last name, etc.).

[0047] In one example, network 130 may connect to other servers in addition to server 120. For example, mobile device processor circuitry 147 may be operable to obtain location preference settings from multiple user preference settings stored in memory 141. Mobile device processor circuitry 147 may obtain location data from location application and other applications 145. The location data may include a location, a timestamp, and a speed. The obtained location preference settings and the obtained location data may be transmitted to unlock server 129. In response, mobile device processor circuitry 147 may receive a list of affiliated stores that satisfy the obtained location preference settings based on the obtained location data. The processor circuitry may present the list of affiliated stores in a graphical user interface on a display device, such as touchscreen display 149.

[0048] The mobile device processor circuit 147 may be further operable to determine, based on the location data provided by the location application, that a card unlock operation is required to satisfy the impending card-present transaction. The processor circuit may generate instructions to generate a notification indicating that a card unlock operation is requested. A notification activation signal may be output operable to activate an output device or a display device in accordance with the generated instructions. Example output devices and display devices are shown in the example of FIG. 6.

[0049] FIG. 2A is a flowchart illustrating an example of a process utilizing the example system of FIG. 1. Process 200 may be executed by mobile device 110 of FIG. 1A or 1B. Through execution of the unlock-lock application and the authentication application, processor circuitry 147 of mobile device 110 may be operable to receive encrypted data from a contactless card via card-reading circuitry at 210. For example, the contactless card may be locked to prevent its use in card-present transactions, and the encrypted data may be generated based on a cryptographic algorithm and a diversified key generated by the contactless card. At 220, the encrypted data may be forwarded to an authentication server to authenticate and unlock the contactless card. For example, the authentication server may be operable to decrypt the encrypted data, verify the decrypted data, and authenticate the contactless card. If the verification is successful and authenticated, the contactless card may be unlocked for card-present transactions. The authentication server may be operable to generate an unlock instruction indicating that the contactless card has been unlocked based on verification of the decrypted data, and forward the unlock instruction to the mobile device. The processor of the mobile device may receive an unlock indication indicating that the contactless card has been unlocked and can now be used in card-present transactions (230). Additionally, the unlock indication may indicate that the contactless card has been authenticated and unlocked. The processor may further be operable to determine 240 user preferences regarding use of the contactless card when unlocked for use in payment card transactions.User preferences can include, for example, keeping the card unlocked for a set number of card-present transactions (e.g., the next 10 transactions, or 20 transactions), allowing re-locking via manual tap on a phone, a location (an area from your commute to your office, a specific business district, a shopping mall, a travel destination, etc.), a spending amount (e.g., $100 total for all transactions, a $50 limit for an individual transaction, etc.), a time increment (e.g., the next 6 hours, 1 hour, 45 minutes, commute or trip time), or a re-lock setting that re-locks the card (or transitions to a default state (e.g., full or partial locking for one transaction) after an unlock duration, after a user preference time setting as described above, after a default time setting, after a number of transactions, or other setting, etc.). Alternatively, a server such as 120 or 129 in FIG. 1 may automatically re-lock the card so that card-present transactions are no longer possible without a subsequent unlock, for example, according to a default setting or a user preference. At 250, the processor may present a representation of the identified user preferences for the contactless card in a graphical user interface presented on a display device, which may be a touchscreen display.

[0050] FIG. 2B illustrates another example of a process that can be implemented during execution of the unlock-lock application 144 to enable unlocking of a contactless card. Process 201 may be implemented as a mobile computing application that can provide authorized use of an unlocked contactless card. A mobile computing application, such as the unlock-lock application 143 of FIG. 1, may be stored in memory as a non-transitory computer-readable medium or implemented by a processor or processing circuitry. In exemplary process 201, the processor may receive encrypted data from a communication interface of the contactless card via card-reading circuitry (211). For example, the contactless card may be locked from use in card-present transactions, and the encrypted data may be generated based on a cryptographic algorithm and a diversified key implemented and stored on the contactless card. The processor may then transmit the encrypted data to an authentication server to enable unlocking of the contactless card (221). At 231, a processor executing the unlock-lock application on the mobile device may receive an unlock instruction that the contactless card has been unlocked for use in card-present transactions. Further, the instruction may be used as confirmation by the server that the encrypted data was provided by an authorized user of the card. The unlock-lock application executed by the processor may identify permitted contactless card usage restrictions regarding the contactless card's ability to complete payment card transactions (241). For example, a merchant whitelist may be stored in a database maintained by the server, such as unlock-lock application data 126 in FIG. 1A. In response to verifying that the encrypted data was provided by an authorized user of the card, the server may deliver some or all of the merchant whitelist to the unlock-lock application on the mobile device. The unlocked contactless card may only be usable (i.e., authorized for use) for card-present transactions at merchants included in the merchant whitelist.For example, the server may receive user preference settings from the unlock-lock application on the mobile device. The user preference settings may indicate a time setting, e.g., a user's preferred time and area setting, such as allowing card-present transactions at 9:00 AM within five square blocks or a half mile of the user's location, the user's office or home location, an area setting, and a merchant code setting (e.g., coffee shops, restaurants, and drug stores only). Other settings may be based on geographic location, geofenced area, merchant name, price threshold, time threshold, day of the week, time range within a day, zip code, area code, merchant category, product category, etc. The time threshold may be a default timer, such as 30 minutes from the time the contactless card is unlocked. As an example, geofencing is a feature of a computer program that allows a developer or administrator to define geographic boundaries using mobile device location data services, such as Global Positioning System (GPS) or Radio Frequency Identification (RFID) tags (if permitted by the mobile device user), or Wi-Fi or cellular data that can be used to determine location. The geofenced area may be, for example, an area surrounded by a radius, or an area established by a zip code, or a government boundary such as a city or county designation, etc. In one example, a merchant whitelist may be based on a user selecting a merchant code to restrict use of an unlocked contactless card at merchants assigned the merchant code.

[0051] At 251, the mobile device may present, in a graphical user interface presented on the display device, an indication of the unlock status for use (e.g., unlocked, open lock icon, etc.) and a representation of the identified authorized contactless card usage restrictions. For example, the representation may be part of a distribution of a whitelist of merchants, a map of a specified area setting, etc. In one example, the processor may present, via the graphical user interface, multiple contactless card usage restrictions in response to a user preference selection for setting contactless card usage restrictions. The usage restrictions may include one or more of a geographic location, a geofenced area, a merchant name, a price threshold, a time threshold, a day of the week, a time range within a day, a postal code, an area code, a merchant category, a product category, etc.

[0052] The processor circuit may further be operable to receive, via a graphical user interface, a selection of user preferences that set usage limits for the contactless card. Location information may not be available until the user opens an application; for example, a user requesting card unlocking (at 211 in the example of FIG. 2B ) may launch an unlock-lock application, which may obtain permission to access or obtain location information from a location application or service, such as GPS, Wi-Fi location services, etc. For example, the location data application may be operable to determine the location of the device. In one example, the memory may be operable to store multiple user preference settings and further instructions for the unlock-lock application when executed by the processor circuit. The processor circuit may be operable to determine, based on the location provided by the location data application, that a card unlock operation is necessary to satisfy an impending card-present transaction. The processor circuit may be operable to generate instructions for generating a notification indicating that a card unlock operation is necessary and to output a notification activation signal operable to activate an output or display device in accordance with the generated instructions. For example, the processor circuit may present a prompt in the graphical user interface indicating the locked status of the contactless card.

[0053] In an operational example, in response to the indication of authentication, the unlock-lock application 144 may generate a list of card usage restrictions in a graphical user interface based on user preferences maintained by the unlock-lock application 144 and present the generated list of card usage restrictions (as shown in other examples).

[0054] The processor circuitry may be operable to present a menu of user preference settings on the graphical user interface for selection by the user. The user preference settings may permit use of an unlocked contactless card in a card-present transaction, and selection thereof may allow the user to customize use of the contactless card when unlocked. For example, as shown in FIG. 3A, the menu of the graphical user interface 313 may include several user preferences 301-305. The user may select one or more of the presented user preferences 301-305. As shown in FIG. 3A, user preference #1 301 and user preference #3 303 are shown in bold, indicating that these user preferences have been selected by the user.

[0055] The processor circuitry may be operable to receive an indication of one or more selections of user preference settings presented in the menu. FIG. 3B illustrates an example of a graphical user interface showing a selection of user preference settings. For example, the mobile device 310 may present a graphical user interface 314 on the display device 320. The unlock-lock application may present selections via touch on the graphical user interface 314 if the display device is a touchscreen. Examples of user preference settings to select include a location selection, such as location #1 317, a time range selection, such as time range #3 311, an area selection, such as radius #6, and a merchant category code selection, such as MCC#X 315. In one example, the time range selection may specify a time range during which the contactless card remains unlocked. The area selection may specify an area within which the contactless card may be used for card-present transactions when unlocked. For example, the area may be defined by a radius from the user's location, an area within square blocks or square miles or feet, or other methods of indicating an area, such as a zip code or other postal code. For example, the radius selection may specify a distance from a user's location within which contactless is permitted to be used for card-present transactions. The merchant category code selection specifies a category of goods or services offered by a merchant with a merchant category code assigned to each good or service offered by the merchant.

[0056] The processor circuit may obtain the location preference setting from a plurality of user preference settings stored in memory (e.g., see Location #1 setting 317 in FIG. 3B). An unlock-lock application executed by the processor circuit may be operable to obtain location data from a location data application also executing on the processor circuit. The unlock-lock application may be operable to cause the processor circuit to transmit the obtained location preference setting and the obtained location data to an unlock server. The unlock server may be able to identify the number of merchants that satisfy the obtained location preference setting. For example, the unlock server may be operable to have access to other user preference settings as well as information about merchants that satisfy each location preference setting. The unlock-lock application may receive a list of merchants that satisfy the obtained location preference setting or other settings based on the obtained location data.

[0057] Returning to the example of Figure 2A, the processor circuitry may be operable to communicate, via the unlock-lock application, with a server, such as 120 of Figure 1, operable to manage user preferences for the unlock-lock application. In one example, the processor circuitry may be operable to provide the user preference settings indicated as selected to authorize use of the unlocked contactless card in a card-present transaction.

[0058] In one example, the merchant name or merchant category code (e.g., grocery store, professional services, etc. (Merchant Category Code (MCC) per IRS Revised Procedure 2004-43)) is a classification code assigned to the merchant / payee by the payment card institution. The payment card institution assigns a specific code to a merchant based on the merchant's primary business activity. The merchant category code allows a user to make card-present purchases in an area that is new to the user, such as a new restaurant where the user has not made a card-present purchase or a restaurant that is not established in the map application used for location data services.

[0059] 3A is an example of a graphical user interface (GUI) for the unlock-lock application 144 on the mobile device 110. For example, the processor may be operable to drive a display device, such as a touchscreen display of the mobile device, to present a graphical user interface with multiple user preferences for setting contactless card usage limits. Each user preference 301-305 may include settings based on geographic location, geofenced area, merchant name, price threshold, time threshold, day of the week, time range within a day, zip code, area code, merchant category, product category, etc.

[0060] When contactless card 101 is tapped to mobile device 110, account authentication application 143 sends instructions to contactless card 101 via card reader 148 (e.g., via NFC, Bluetooth, RFID, and / or EMV protocols, etc.). In one example, the instructions may specify encryption using key diversification, as depicted in FIG. 1A, in which case account authentication application 143 receives card data 103 from server 120. In another example, the instructions may specify sending card data 103 to account authentication application 143 in an NDEF file (e.g., via NFC, Bluetooth, RFID, etc.), in which case account authentication application 143 receives card data 103 in the NDEF file directly from contactless card 101 via card reader 148. In another example, the instructions may specify that card data 103 be sent to account authentication application 143 via the EMV protocol, in which case account authentication application 143 receives card data 103 directly from contactless card 101 via the EMV protocol. However, as described, in examples where the EMV protocol is used, the CVV value is received from contactless card 101 in an NDEF file and / or from management application 123. In another example, the instructions may specify that account number 108 be encrypted and sent to account authentication application 143 using key diversification as depicted in FIG. 1A, in which case account authentication application 143 receives a record of account number 108 from contactless card 101 (which is used following verification of encrypted data 190 by server 120).

[0061] 3B is a diagram of a mobile device 310 presenting a graphical user interface 314 including a selection of user preference settings 311-317. The mobile device may be operable to transmit the selected user preference settings 311-317 to a server. For example, the server may receive the user preference settings from an unlock-lock application on the mobile device. The user preference settings 311-317 may indicate, for example, a time setting, a user's preferred time and area setting, such as allowing card-present transactions to occur at 9:00 AM within five square blocks or one-half square mile of the user's location, office, or home location, an area setting, a merchant code setting (e.g., coffee shops, restaurants, and drug stores only), and so forth.

[0062] As shown in FIG. 3C , the unlock-lock application may be operable to present a list of merchants 321-327 in a graphical user interface 314 on a display device 320 (e.g., a touchscreen display) of the mobile device 310. For example, as described above, the mobile device 110 may provide the mobile device's location to the unlock server 129. More specifically, the unlock server 129 may obtain a location setting from a user preference setting provided via the graphical user interface 313 of FIG. 3A . In one example, the location setting may be a radius from a predetermined location (e.g., radius #6 in the graphical user interface 314 of FIG. 3B ). The predetermined location may be, for example, the location of the mobile device, the user's office, home, a friend's house, a favorite restaurant, a gym, etc. The unlock server 129 may access a merchant location service, such as 149, based on the user preference setting. From the merchant location service 149, an instance of the unlock-lock application 144″ can obtain a list of merchants, such as merchants #1-#X, based on the obtained location setting and the determined location. The instance of the unlock-lock application 144'' may be operable to generate a list of affiliated merchants based on the obtained location settings and the determined location of the mobile device. The generated list of affiliated merchants may be transferred to the mobile device 110, for example, via the network 130. In the example of FIG. 3C, the mobile device 310 may be operable to present the list of affiliated merchants 321-327 in a graphical user interface 324 on a display device 320 of the mobile device 310.

[0063] FIG. 4A illustrates a contactless card 101 / 101′, which may include a payment card such as a credit card, debit card, and / or gift card. As shown, the contactless card 101 / 101′ may be issued by a service provider 405, with the information displayed on the front or back of the card 101 / 101′. In some examples, the contactless card 101 / 101′ may be unrelated to a payment card and may include, but is not limited to, an identification card. In some examples, the payment card may include a dual-interface contactless card. The contactless card 101 / 101′ may include a substrate 410, which may include a single layer or one or more laminates 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, contactless card 101 / 101' may have physical characteristics that conform to the ID-1 format of the ISO / IEC 7810 standard, and contactless cards may otherwise conform to the ISO / IEC 14443 standard. However, it will be understood that contactless cards 101 / 101' according to the present disclosure may have different characteristics, and the present disclosure does not require that the contactless card be implemented as a payment card.

[0064] The contactless card 101 / 101′ may also include identification information 415 displayed on the front and / or back of the card, as well as a contact pad 420. The contact pad 420 may be operable to establish contact with another communication device, such as the mobile device 110, a user device, a smartphone, a laptop, desktop, or tablet computer. The contactless card 101 may also include processor circuitry, an antenna, and other components not shown in the example of FIG. 4A . These components may be located behind the contact pad 420 or elsewhere on the substrate 410. The contactless card 101 / 101′ may also include a magnetic strip or tape, which may be located on the back of the card (not shown in FIG. 4A ).

[0065] 4B, contact pad 420 of contactless card 101 / 101′ may include processor circuitry 425 for storing and processing information, including microprocessor 430, communication interface 431, and memory 420. It will be understood that processor circuitry 425 may include additional components necessary to perform the functions described herein, such as processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and tamper-proof hardware.

[0066] The memory 420 may be read-only memory, write-once-read-many-time memory, or read / write memory, such as RAM, ROM, or EEPROM, and the contactless card 101 / 101′ may include one or more of these memories. Read-only memory may be factory programmable as read-only, or may be one-time programmable. One-time programmable provides the opportunity to write once and read many times. Write-once-read-many-time memory can be programmed at any time after the memory chip leaves the factory. Once programmed, memory cannot be rewritten but can be read any number of times. Read / write memory can be programmed and reprogrammed any number of times after leaving the factory. Read / write memory can also be read many times after leaving the factory.

[0067] The memory 420 may be operable to store one or more applets 440, one or more counters 404, a customer identifier 407, and a virtual account number 408. The one or more applets 440 may include one or more software applications operable to run on one or more contactless cards, such as a JavaCard applet. However, it will be understood that the applet 440 is not limited to a JavaCard applet and may instead be any software application operable on a contactless card or other device having limited memory. The one or more counters 404 may include a numeric counter sufficient to store an integer. The customer identifier 407 may include a unique alphanumeric identifier assigned to a user of the contactless card 101 / 101′, and the customer identifier 407 may distinguish a user of the contactless card 101 / 101′ from users of other contactless cards. In some examples, the customer identifier 407 may identify both the customer and the account assigned to the customer and may further identify the contactless card associated with the customer's account. As previously mentioned, the account numbers 408 may include thousands of one-time use virtual account numbers associated with the contactless cards 101 / 101'.

[0068] Although the processor and memory elements of the foregoing exemplary embodiments are described with reference to contact pads 420, the present disclosure is not limited thereto. It is understood that these elements may be implemented external to, completely separate from, or as additional elements in addition to the microprocessor 430 and memory 402 elements located within contact pads 420.

[0069] In some examples, contactless card 101 / 101′ may include one or more antennas 455. The one or more antennas 455 may be disposed internal to contactless card 101 / 101′ and around processor circuit 425 of contact pad 420. For example, one or more antennas 455 may be integral with processor circuit 425, or one or more antennas 455 may be used in conjunction with an external booster coil to provide communication interface 431. As another example, one or more antennas 455 may be external to contact pad 420 and processor circuit 425.

[0070] As an example, the coil of the contactless card 101 / 101′ may function as the secondary of an air-core transformer. A terminal, such as the card reader 148 of the mobile device 110 of FIG. 1, may communicate with the contactless card 101 / 101′ by cutting power or performing amplitude modulation. The contactless card 101 / 101′ may collect data transmitted from a POS terminal (not shown in this example) or card reader 148 using a gap in the contactless card's power connection, which may be maintained functionally via one or more capacitors. The contactless card 101 / 101′ may return communication by switching a load on the contactless card's coil via detectable load modulation. The load modulation may be detected at the terminal's coil. More generally, using information stored in the antenna 455, processor circuit 425, and / or memory 420, the contactless card 101 / 101′ provides a communication interface 431 that communicates via NFC, Bluetooth, and / or Wi-Fi communication protocols, respectively. If contactless card 101 / 101' is equipped to provide Bluetooth and Wi-Fi communication, then Bluetooth and Wi-Fi communication may be provided via transceiver 435.

[0071] As described above, contactless card 101 / 101′ may be built on a software platform operable on a smart card or other device with limited memory, such as JavaCard, on which one or more applications or applets may be securely executed. Applet 440 may be added to the contactless card to provide one-time passwords (OTPs) for multi-factor authentication (MFA) in various mobile application-based use cases. Applet 440 may be operable to respond to one or more requests, such as a near-field data exchange request, from a reader, such as a mobile NFC reader (e.g., in mobile device 110), and generate an NDEF message including the cryptographically secure OTP encoded as an NDEF text tag.

[0072] An example of an NDEF OTP is the NDEF short-record layout (SR=1). In such an example, one or more applets 440 may be operable to encode the OTP as a text tag of the well-known type NDEF Type 4. In some examples, an NDEF message may include one or more records. The applet 440 may be operable to add one or more static tag records in addition to the OTP record.

[0073] In some examples, one or more applets 440 may be operable to emulate a radio frequency identification (RFID) tag. The RFID tag may include one or more polymorphic tags. In some examples, each time the tag is read, different cryptographic data is presented that can indicate the authenticity of the contactless card. Based on one or more applications, an NFC read of the RFID tag may be processed, the data may be transmitted to a server, such as server 120, and the data may be verified at the server.

[0074] In some examples, the contactless card 101 / 101′ and the server 120 may contain specific data so that the card can be properly identified. The contactless card 101 / 101′ may include one or more unique identifiers (not shown). Each time a read operation is performed, the counter 404 may be operable to increment. In some examples, each time data from the contactless card 101 / 101′ is read (e.g., by the mobile device 110), the counter 404 is sent to the server for verification, and (as part of the verification) it is determined whether the counter values ​​404 are equal.

[0075] One or more counters 404 may be operable to prevent replay attacks. For example, if a ciphertext is captured and replayed, the ciphertext is immediately rejected if the counter 404 is read, used, or passed over. If the counter 404 is not being used, it may be replayed. In some examples, the counter incremented on the card is different from the counter incremented for the transaction. The contactless card 101 / 101′ cannot determine the application transaction counter 404 because there is no communication between the applets 440 on the contactless card 101 / 101′. In some examples, the contactless card 101 / 101′ may include a first applet, which may be a transaction applet, and a second applet. Each of the first applet and the second applet may include a respective counter 404.

[0076] In some examples, counter 404 may be asynchronous with a server such as 120 in Figure 1. In some examples, counter 404 may increment to account for accidental reads, such as tilted reads, when initiating a transaction, but the application does not process counter 404. In some examples, when mobile device 110 is woken, card reader 148 (acting as an NFC device in this example) is enabled and mobile device 110 may be operable to read an available tag, but no action is taken in response to the read.

[0077] To keep the counter 404 synchronized, an application may be executed, such as a background application operable to detect when the mobile device 110 wakes up and synchronize with the server 120, where the resulting reading indicates the next time the counter 404 should be incremented. In another example, a hashed one-time password may be utilized to accommodate a window of mis-synchronization. For example, if within a threshold of 10, the counter 404 may be operable to advance. However, if within a different threshold, such as 10 or 10,000, a request to perform a re-synchronization may be processed, requesting via one or more applications that the user tap, gesture, or otherwise indicate via the user's device one or more times. If the counter 404 increments in the proper order, the user may know that they have done so.

[0078] 1A and 1B, such as counter 104, master key 105, and diversified key 106, is one example of an encrypted and / or decrypted key diversification technique. This exemplary key diversification technique should not be considered limiting of this disclosure, as this disclosure is equally applicable to other types of key diversification techniques.

[0079] During the contactless card 101 / 101' creation process, two cryptographic keys may be uniquely assigned to each card. The cryptographic keys may include symmetric keys that can be used to both encrypt and decrypt data. The Triple DES (3DES) algorithm may be used for EMV and is implemented in hardware on the contactless card 101 / 101'. A key diversification process may be used to derive one or more keys from a master key based on uniquely identifiable information for each entity needing a key.

[0080] In some examples, to overcome deficiencies in the 3DES algorithm, which is susceptible to vulnerabilities, a session key may be derived (such as a unique key per session), but rather than using a master key, a unique key and counter from the card may be used as diversification data. For example, each time the contactless card 101 / 101' is used in operation, a different key may be used to create the message authentication code (MAC) and perform the encryption. This results in triple encryption. Session keys may be generated by one or more applets and may be generated by using the application transaction counter 404 in one or more algorithms (as defined in EMV 4.3 Book 2 a1.3.1 Common Session Key Derivation).

[0081] Additionally, the counter increment for each card 101 / 101′ may be unique, assigned by personalization, or algorithmically assigned by some identifying information. For example, contactless cards 101 / 101′ ending in odd numbers may be operable to increment the counter by 2, while contactless cards 101 / 101′ ending in even numbers may increment the counter by 5. In some examples, the increments may also vary with sequential readings, such that one card cycles through the counter as 1, 3, 5, 2, 2, and so on. The specific sequence or algorithmic sequence may be defined at the time of issuance or another personalization, or may be defined from one or more processes derived from a unique identifier. Using a specific sequence or algorithmic sequence can make it difficult for a replay attacker to generalize from a small number of card instances.

[0082] The authentication message may be delivered as the contents of a text NDEF record in hexadecimal ASCII format. Alternatively, the NDEF record may be encoded in hexadecimal format.

[0083] When the contactless card 101 is tapped against a device running Apple's iOS operating system, such as an iPhone, iPod, or iPad, the contactless card can recognize the iOS operating system and transmit appropriate data to communicate with the device. For example, the terminating contactless card 101 / 101' can provide encrypted identification information necessary to authenticate the card using an NDEF tag, e.g., via NFC. Similarly, when the contactless card tap is directed against a mobile device 110 running the Android operating system, such as an Android smartphone or tablet, the terminating contactless card 101 / 101' can recognize the Android operating system and transmit appropriate data (e.g., encrypted identification information necessary for authentication according to the methods described herein) to communicate with the device.

[0084] 5 illustrates an example of an exemplary computing architecture 500 including a computing system 502 that may be suitable for implementing various embodiments as described above. In various examples, the computing architecture 500 may include or be implemented as part of an electronic device. In some examples, the computing architecture 500 may be representative of a system that implements one or more components of the system 100, for example. In some examples, the computing system 502 may be representative of the mobile device 110 and the server 120 of the system 100, for example. In this context, the embodiments are not limited. More generally, the computing architecture 500 is operable to implement all of the logic, applications, systems, methods, apparatus, and functionality described herein with reference to FIGS. 1-6 .

[0085] As used herein, the terms “system,” “component,” and “module” are intended to refer to computer-related entities, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by exemplary computing architecture 500. For example, a component may be, but is not limited to, a process running on a computer processor, a computer processor, a hard disk drive, multiple storage drives (optical and / or magnetic storage media), an object, an executable file, a thread of execution, a program, and / or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and / or thread of execution, and components can be localized on one computer and / or distributed among two or more computers. Furthermore, components can be communicatively coupled to each other by various types of communication media to coordinate operations. Coordination can include unidirectional or bidirectional information exchange. For example, components may communicate information in the form of signals communicated over the communication media. Information can be implemented as signals assigned to various signal lines. In such assignments, each message is a signal. However, further embodiments may alternatively employ data messages. Such data messages may be transmitted across a variety of connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

[0086] Computing system 502 may include various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input / output (I / O) components, power supplies, etc. However, embodiments are not limited to implementation by computing system 502.

[0087] 5, computing system 502 includes a processor 504, a system memory 506, and a system bus 508. Processor 504 can be any of a variety of commercially available computer processors, such as AMD® Athlon®, Duron®, and Opteron® processors, ARM® application, embedded, and secure processors, IBM® and Motorola® DragonBall® and PowerPC® processors, IBM and Sony® Cell processors, Intel® Celeron®, Core®, Core(2) Duo®, Itanium®, Pentium®, Xeon®, and XScale® processors, and similar processors. Dual microprocessors, multi-core processors, and other multiprocessor architectures can also be employed as processor 504.

[0088] The system bus 508 provides an interface for connecting system components, including but not limited to the system memory 506, to the processor 504. The system bus 508 may further be any of several types of bus structures that may interconnect a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. Interface adapters may connect to the system bus 508 through a slot architecture. Exemplary slot architectures include, but are not limited to, Accelerated Graphics Port (AGP), CardBus, (Extended) Industry Standard Architecture ((E)ISA), MicroChannel Architecture (MCA), NuBus, Peripheral Component Interconnect (Expansion) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), etc.

[0089] The system memory 506 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 (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory (e.g., one or more flash arrays), polymer memory such as ferroelectric polymer memory, ovonic memory, phase-change or ferroelectric memory, silicon oxide-silicon nitride-silicon oxide (SONOS) memory, magnetic or optical cards, device arrays such as RAID drives, solid-state memory (e.g., USB memory, solid-state drives (SSDs), and any other type of storage medium suitable for storing information. In the illustrated example shown in FIG. 5 , the system memory 506 may include non-volatile memory 510 and / or volatile memory 512. A basic input / output system (BIOS) may be stored in the non-volatile memory 510.

[0090] Computing system 502 may include various types of computer-readable storage media in the form of one or more low-speed memory units, such as an internal (or external) hard disk drive (HDD) 514, a magnetic floppy disk drive (FDD) 516 that reads from or writes to a removable magnetic disk 518, and an optical disk drive 520 that reads from or writes to a removable optical disk 522 (e.g., a CD-ROM or DVD). HDD 514, FDD 516, and optical disk drive 520 may be connected to system bus 508 by HDD interface 524, FDD interface 526, and optical drive interface 528, respectively. HDD interface 524 for external drive implementations may include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. Computing system 502 is generally operable to implement all of the logic, systems, methods, devices, and functions described herein with reference to Figures 1-7.

[0091] The drives and associated computer-readable media provide volatile and / or nonvolatile storage of data, data structures, computer-executable instructions, etc. For example, the drives and memory units 510, 512 may store a number of program modules including an operating system 530, one or more application programs 532, other program modules 534, and program data 536. In one example, the one or more application programs 532, other program modules 534, and program data 536 may include, for example, various applications and / or components of system 100, such as operating system 142, account authentication application 143, unlock-lock application 144, other applications 145, and management application 123.

[0092] A user can enter commands and information into the computing system 502 through one or more wired / wireless input devices, such as a keyboard 538 and a pointing device such as a mouse 540. Other input devices may include a microphone, infrared (IR) remote control, radio frequency (RF) remote control, game pad, stylus pen, card reader, dongle, fingerprint reader, gloves, graphics tablet, joystick, keyboard, retina reader, touch screen (e.g., capacitive, resistive, etc.), trackball, track pad, sensor, stylus, etc. These and other input devices are often connected to the processor 504 through an input device interface 542 connected to the system bus 508, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.

[0093] A monitor 544 or other type of display device is also connected to the system bus 508 via an interface, such as a video adapter 546. The monitor 544 can be internal or external to the computing system 502. In addition to the monitor 544, computers typically include other peripheral output devices, such as speakers, printers, etc.

[0094] Computing system 502 can operate in a networked environment using wired and / or wireless communication logical connections to one or more remote computers, such as remote computer 548. The remote computer 548 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 common network node, and typically includes many or all of the elements described above relative to computing system 502, although for simplicity, only memory / storage device 550 is illustrated. The depicted logical connections include wired and / or wireless connections to a local area network (LAN) 552 and / or larger networks, e.g., a wide area network (WAN) 554. Such LAN and WAN networking environments are commonplace in offices and businesses and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet. In an embodiment, network 130 of FIG. 1 is one or more of LAN 552 and WAN 554.

[0095] When used in a LAN networking environment, the computing system 502 is connected to the LAN 552 through a wired and / or wireless communication network interface or adapter 556. The adapter 556 can facilitate wired and / or wireless communication to the LAN 552 and can also include a wireless access point disposed thereon for communicating with the wireless capabilities of the adapter 556.

[0096] When used in a WAN networking environment, the computing system 502 may include a modem 558, or may be connected to a communications server on the WAN 554, or have other means for establishing communications over the WAN 554, such as via the Internet. The modem 558, which may be internal or external and a wired and / or wireless device, connects to the system bus 508 via the input device interface 542. In a networked environment, program modules depicted relative to the computing system 502, or portions thereof, may be stored in the remote memory / storage device 550. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between computers may be used.

[0097] The computing system 502 is operable to communicate with wired and wireless devices or entities using the IEEE 802 family of standards, such as wireless devices operatively arranged for wireless communication (e.g., modulation techniques according to IEEE 802.16 wireless communications). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth® wireless technologies. Thus, communication may be in a predefined structure, such as a traditional network, or simply ad-hoc communication between at least two devices. Wi-Fi networks use wireless technologies known as IEEE 802.11x (a, b, g, n, etc.) to provide secure, reliable, and high-speed wireless connectivity. Wi-Fi networks can be used to connect computers to each other, to the Internet, and to wired networks (using IEEE 802.3 related media and functions).

[0098] FIG. 6 illustrates an example of a mobile device that can be used to implement the techniques and processes described with reference to the examples of FIGS. 1-5.

[0099] The mobile device 611 may be a smartphone that includes a display device such as a touchscreen display 620. The touchscreen display 620 may be connected to the processor 612 and operable to present screen content and receive input via a touch sensor 622. Examples of touchscreen mobile devices such as the mobile device 611 may include (but are not limited to) a smartphone, a personal digital assistant (PDA), a tablet computer, a smartwatch, or another portable device. However, the structure and operation of the mobile device 611 utilizing a touchscreen is provided by way of example, and the subject technology described herein is not intended to be limited thereto. For purposes of this discussion, FIG. 6 illustrates an example of a mobile device 611 having a touchscreen display for displaying content and receiving user input as (or as part of) a user interface.

[0100] There are various ways in which the mobile device 611 may operate to obtain information regarding the device's current location. In our example, the mobile device 611 includes a Global Positioning System (GPS) receiver 632 and associated antenna 634. GPS is a space-based satellite navigation system that provides location data and time information virtually anywhere on Earth. A rechargeable battery 629 may provide sufficient power to power the various components of the mobile device 611.

[0101] Mobile devices supporting the sale alert applications and techniques described herein may include a variety of different types of user interface elements. For purposes of discussion, in the smartphone example of a mobile device shown in FIG. 6 , the user interface elements of the mobile device 611 include a touchscreen display 620 (also referred to herein as “touchscreen 620” or “display 620”). For output purposes, the touchscreen 620 includes a display screen such as a liquid crystal display (LCD). For input purposes, the touchscreen display 620 includes a plurality of touch sensors 622. Other interface elements may include a keypad including one or more keys 630. For example, the keypad may be implemented in hardware as a T9 or QWERTY keyboard on the mobile device 611, and the keys 630 may correspond to the physical keys of such a keyboard. Alternatively, the keys 630 (and keyboard) on the mobile device 611 may be implemented as “soft keys” of a virtual keyboard that is graphically represented in an appropriate arrangement via the touchscreen display 620. Soft keys presented on the touchscreen display 620 may enable a user of the mobile device 611 to invoke the same user interface functions as physical hardware keys. In some implementations, the microphone 602 and speaker 604 may be used as additional user interface elements for audio input and output, as well as for some functions related to processing associated with interfacing with the sales alerts application 647, as described herein. In a further example, the sales alerts application 647, in response to accessing contacts stored in the mobile device memory 614, may present a prompt in a user interface, such as 425 in FIG. 4B , to send a request to one or more of the contacts to join an affinity reward group.

[0102] For output, touchscreen display 620 is a display device used to present information (e.g., text, video, graphics, or other visual content) to a user of mobile device 611. Processor 612 controls the visual display output on an LCD or other display element of touchscreen display 620 via display driver 624 to present various visual outputs to the device user. Additionally, output devices may include, for example, speaker 604, vibrating mechanism 631, touchscreen display 620, etc.

[0103] Generally, the touchscreen display 620 and touch sensor 622 (and, if included, one or more keys 630) are used to provide a textual and graphical user interface for the mobile device 611. In one example, the touchscreen display 620 provides displayable content to a user on the mobile device 611. The touchscreen display 620 also allows a user to directly interact with displayable content provided in a content display area by touching the surface of the screen, typically with an instrument such as a finger or stylus.

[0104] 6, the mobile device 611 also includes touch detection circuitry 628 coupled to the touch sensor 622 to detect the occurrence and relative position / location of each touch with respect to the content display area of ​​the touchscreen display 620. In this example, the touch detection circuitry 628 is operable to provide touch location information to the processor 612 based on user input received via the touch sensor 622. In some implementations, the processor 612 is operable to associate the touch location information with particular content being displayed within the content display area of ​​the touchscreen display 620. The touch location information captured by the touch detection circuitry 628 and provided to the processor 612 may include, but is not limited to, coordinates identifying the location of each detected touch with respect to the display area of ​​the touchscreen display 620 and a timestamp corresponding to each detected touch location.

[0105] 6, mobile device 611 includes a microphone 602 for inputting audio signals and a speaker 604 for outputting audio signals. Microphone 602 and speaker 604 are communicatively connected to a voice or speech encoder / decoder (vocoder) 606. In the case of voice telephony, for example, vocoder 606 provides bidirectional conversion between analog audio signals representing voice or other sounds and digital samples at a compressed bit rate compatible with the digital protocols of wireless telephone network communications or voice over packet (e.g., Internet Protocol) communications. The vocoder, speaker, and microphone may also be used as elements of the user interface during other operations of the device, including certain transaction communications.

[0106] Also shown in FIG. 6 , the mobile device 611 includes at least one transceiver (XCVR) 608, which may be a digital transceiver for digital wireless communication over a wide-area wireless mobile communication network, although the mobile device 611 may also include additional digital or analog transceivers (not shown). The transceiver 608 conforms to one or more of the various digital wireless communication standards utilized by modern mobile networks. Examples of such transceivers include, but are not limited to, transceivers capable of operating in accordance with Code Division Multiple Access (CDMA) and 3GPP® (Third Generation Partnership Project) network technologies, including, but not limited to, 3GPP® Type 2 (or 3GPP® 2) and 3GPP® Long Term Evolution (LTE), sometimes referred to as “4G.” For example, the transceiver 608 provides two-way wireless communication of information, including digitized voice signals, still images and / or video signals, web page information for display and web-related input, and various types of mobile messaging to and from the mobile device 611. The transceiver 608 connects to an antenna 609 via a radio frequency (RF) transmit / receive amplifier (not shown separately). The transceiver 608 may also support various types of mobile messaging services, such as Short Message Service (SMS), Enhanced Message Service (EMS), and / or Multimedia Messaging Service (MMS).

[0107] In one example, the transceiver 608 may be coupled to and operable to exchange communications with the processor 612. The processor 612 of the mobile device 611 may be further operable to perform additional functions, including using the transceiver to establish a connection and exchange communications with a server, such as the affinity exchange server 45 of FIG. 1. Through the connection with the server, the mobile device 611 may be able to obtain various information, such as affinity reward exchange rates, neutral affinity reward values, affinity aggregation account related information, etc. The processor in executing the sales notification application 647 may implement embodiments such as those described above with reference to FIGS. 1-5.

[0108] The mobile device 611 may also include a Wi-Fi transceiver 610 and associated antenna 633. Although Wi-Fi is used here as an example, the transceiver 610 may take the form of any available two-way wireless local area network receiver of a type compatible with one or more standard protocols for communication implemented in wireless local area networks, such as one of the Wi-Fi standards under IEEE 802.11 and / or WiMAX.

[0109] The mobile device 611 further includes a processor 612, which functions as a programmable controller of the mobile device 611 by, for example, configuring the mobile device 611 to perform various operations according to instructions or programming executable by the processor 612. For example, such operations may include various general operations of the mobile device 611 and operations related to adjusting screen brightness as described herein. The flash memory 614 may be used, for example, to store programming or instructions for execution by the processor 612. Depending on the type of device, the mobile device 611 stores and executes an operating system through which certain applications may run on the device. Examples of operating systems include Android, Apple iOS, Microsoft Windows OS, Bada, Tizen, Symbian OS, Blackberry OS, etc. The flash memory 614 may also be used to store mobile configuration settings for different mobile applications or services executable on the mobile device 611 (using the processor 612). The mobile device 611 may also include a non-volatile random access memory (RAM) 616 for working data processing memory. The RAM memory 616 or storage device 637 may be coupled to the processor 612 and operable to store programming code executable by the processor 612 .

[0110] Alternatively, or additionally, the application may be stored in storage 637, which may be solid-state memory storage or other memory device suitable for storing applications. In one example, storage 637 may be a separate chip including tamper-resistant storage and execution memory and operable to communicate with an operating system. Storage 637 may store an instance of a sales notification application 647, for example, for processing receipt data, communicating with one or more services or servers, and processing as described with reference to the examples of FIGS. 1-3. Other applications, such as 642 and 644, may also be stored in storage 637.

[0111] Logic implemented by the processor 612 of the mobile device 611 configures the processor 612 to control various functions implemented by the mobile device 611. Although the processor logic may be implemented in a variety of ways, in the example provided, the processor logic is implemented by programming for execution by the processor 612.

[0112] Various examples may be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include a processor, a microprocessor, a circuit, a circuit element (e.g., a transistor, a resistor, a capacitor, an inductor, etc.), an integrated circuit, an application specific integrated circuit (ASIC), a programmable logic device (PLD), a digital signal processor (DSP), a field programmable gate array (FPGA), a logic gate, a register, a semiconductor device, a chip, a microchip, a chipset, etc. Examples of software may include a software element, a program, an application, a computer program, an application program, a system program, a machine program, an operating system software, a middleware, firmware, a software module, a routine, a subroutine, a function, a method, a procedure, a software interface, an application program interface (API), an instruction set, computational code, computer code, a code segment, a computer code segment, a word, a value, a symbol, or any combination thereof. The decision of whether an embodiment is implemented using hardware and / or software elements may vary according to any number of factors, such as desired computational speed, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints.

[0113] One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium that represent various logic within a processor and, when read by a machine, cause the machine to produce logic for performing the techniques described herein. Such expressions, known 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 produce the logic or processors. Some examples may be implemented using, for example, a machine-readable medium or article that may store instructions or sets of instructions that, when executed by a machine, cause the machine to perform a method and / or operation in accordance with an example. 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. A machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage medium and / or storage device, 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 rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of digital versatile disks (DVDs), tape, cassette, 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.

[0114] The description of the foregoing 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. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the disclosure be limited not by this detailed description, but rather by the claims appended hereto. Future applications claiming priority to this application may claim the disclosed subject matter differently and may generally include any set of one or more limitations variously disclosed or otherwise set forth herein.

Claims

1. A display device; a processor circuit capable of causing the display device to display a graphical user interface; a transceiver connected to the processor circuit and capable of communicating with an external device; a card reader circuit connected to the processor circuit and capable of transmitting and receiving signals within a signal field; a memory coupled to the processor circuit and capable of storing an unlock-lock application; An apparatus comprising: The unlock-lock application, when executed by the processor circuit, causes the processor circuit to: receiving, via said card reading circuitry, encrypted data generated based on an encryption algorithm and a diversified key from a contactless card that is locked to prevent use of the presented transaction; forwarding the encrypted data to an authentication server for authenticating and unlocking the contactless card; receiving an unlock instruction indicating that the contactless card has been unlocked for use in the current transaction and including that the contactless card has been authenticated; When unlocked, identifying user preferences regarding use of said contactless card in payment card transactions; and presenting, in a graphical user interface displayed on said display device, a representation of preferences of the identified user of said contactless card; A device containing instructions to perform

2. The memory capable of storing the instructions, when executed by the processor circuit, causes the processor circuit to: operating a display device to present a graphical user interface including a plurality of user preferences for setting usage limits for said contactless card; The apparatus of claim 1 , further comprising instructions to cause the apparatus to execute:

3. The memory, when executed by the processor circuit, causes the processor circuit to: presenting, via the graphical user interface, a plurality of usage restrictions for the contactless card in response to a user's preference selection for setting usage restrictions for the contactless card; 10. The apparatus of claim 1, capable of storing instructions to cause a

4. The plurality of use restrictions are: including one or more of a geographic location, a geofenced area, a merchant name, a price threshold, a time threshold, a day of the week, a time range within a day, a postal code, an area code, a merchant category, or a product category; 4. The apparatus of claim 3.

5. The memory, when executed by the processor circuit, causes the processor circuit to: receiving, via the graphical user interface, a user preference selection for setting usage limits for the contactless card; 4. The apparatus of claim 3, capable of storing instructions for causing the execution of:

6. a location application capable of determining a location of the device; The memory includes: setting preferences for a plurality of users of the unlock-lock application; When executed by the processor circuit, the processor circuit: obtaining location preference settings from the plurality of user preference settings stored in the memory; obtaining location data from the location application executing on the processor circuit; transmitting the obtained location preference settings and the obtained location data to an unlock server; receiving a list of merchants that satisfy the acquired location preference settings based on the acquired location data; and presenting the list of merchants in the graphical user interface on the display device; 10. The apparatus of claim 1, further comprising:

7. an output device connected to the processor circuit and capable of generating sound or vibration; a location application executable by the processor circuitry, the location application capable of determining a location of the device; The memory is capable of storing a plurality of user preference settings for the unlock-lock application, the memory being configured to, when executed by the processor circuit, cause the processor circuit to: determining that a card unlock operation is required when a card-present transaction is imminent based on the location provided by the location application; and generating a notification via the output device or the display device indicating a request for the card unlock operation; can store additional instructions that cause 10. The apparatus of claim 1.

8. The memory includes: setting preferences for a plurality of users of the unlock-lock application; When executed by the processor circuit, the processor circuit: presenting, in the graphical user interface, for selection by a user, a menu of user preference settings that, when unlocked, set permissions for use of the contactless card in card-present transactions; receiving an indication of a selection of one or more of the user preference settings presented in the menu; and providing an indication of the user preference setting to a server capable of managing user preferences for the unlock-lock application as an authorization selection for the unlocked contactless card in a card-present transaction; and It is possible to store 10. The apparatus of claim 1.

9. The indication of one or more selections of the user preference settings includes: a time range selection specifying a time range during which the contactless card is unlocked; A radius selection that specifies the distance from the user's location within which contactless use is permitted for card-present transactions; or a merchant code selection that identifies a category of goods or services offered by the merchant to which the selected merchant code is assigned; 9. The apparatus of claim 8, comprising:

10. a contactless card including a processor, a memory, and a communication interface operable to support at least one of near field communication, Bluetooth, or Wi-Fi communication protocols; a mobile device including a mobile device processor, a mobile device memory, a transceiver, a display device, and card reader circuitry; A system comprising: The processor: generating encrypted data using a cryptographic algorithm and a diversified key; Operable to transmit, via the communications interface, a signal including encrypted data usable to authenticate the contactless card; the card reader circuitry is operable to communicate with the contactless card via the communication interface; The mobile device memory stores programming code including an instance of an unlock-lock application, the programming code, when executed by the mobile device processor, receiving a signal containing encrypted data emitted from the contactless card from the card reader circuit; transmitting the encrypted data via a transceiver for authenticating and unlocking the contactless card; receiving an unlock instruction indicating that the contactless card has been unlocked; Identifying user preferences for permitting limited use of the contactless card when unlocked for use in card-present transactions; displaying a representation of the preferences of the identified user of the unlocked contactless card in a graphical user interface displayed on a display device; causing the mobile device processor to perform a function system.

11. The processor of the contactless card further comprises: Operable to generate a diversified key using a master key and a counter value stored in a memory of the contactless card; The counter value is a count of either the number of times the contactless card has been used in a card-present transaction or the number of times the contactless card has been authenticated. The system of claim 10.

12. further comprising an authentication server coupled to the memory storing the cryptographic algorithm and the diversified key, the authentication server operable to execute programming code; When the programming code is executed, receiving encrypted data from a mobile device that is authorized to communicate with the authentication server; decrypting the encrypted data; verifying the decrypted data to authenticate the contactless card; generating an unlock instruction indicating unlocking of the contactless card based on verification of the decrypted data; outputting the unlock instruction to the mobile device; It is possible to operate as The system of claim 10.

13. an unlock-lock server hosting an instance of the unlock application operable to manage user settings of the unlock application; the user preferences are provided by execution by a mobile device processor of the instance of the unlock application stored in a mobile device memory; a location application stored in a memory of the mobile device operable to determine a location of said mobile device; the mobile device processor: determining a location of the mobile device; Operable to provide the determined location of the mobile device to the unlock-lock server; The unlock-lock server receiving a user preference setting from the mobile device as a selection indicating that the contactless card is authorized for use in the card-present transaction when the contactless card is unlocked; obtaining the determined location of the mobile device from the mobile device; obtaining a location setting from the user's preference setting, the location setting being a radius from a predetermined location; accessing merchant location services based on said user preference settings; retrieving a list of merchants from the merchant location service based on the retrieved location settings and the determined location; generating a list of affiliated merchants based on the obtained location settings and the determined location of the mobile device; and operable to transfer the generated list of merchants to the mobile device. The system of claim 10.

14. a payment account component operable to authorize purchases involving a contactless card and to maintain a maximum transaction amount threshold used to authorize or deny purchases involving said contactless card; an unlock-lock server operable to manage user preferences for an unlock-lock application executing on said mobile device processor; Furthermore, The unlock-lock server receiving a user preference setting from the mobile device indicating that authorization to use the unlocked contactless card is selected for the card-present transaction; Deriving a maximum transaction amount threshold from the user preference settings; forwarding a maximum transaction amount threshold derived from said user preference setting to a payment account component; transmitting a maximum transaction amount threshold to the mobile device for display on a graphical user interface; It is possible to operate as The system of claim 10.

15. When unauthenticated, the contactless card is locked and cannot be used for card-present transactions; the authenticated contactless card is valid and unlocked for use in card-present transactions; The system of claim 10.

16. A non-transitory computer-readable storage medium having computer-readable program code embodied thereon, The computer readable program code is executable by a processor circuit, and causes the processor circuit to: receiving, via a card reader circuit, encrypted data generated based on a cryptographic algorithm and a diversified key from a communication interface of a contactless card that is locked from use in card-present transactions; transmitting the encrypted data to an authentication server to enable unlocking of the contactless card; receiving an unlock instruction, the unlock instruction being an encrypted data confirmation indicating that the contactless card has been unlocked for use in a card-present transaction; Identifying permitted contactless card usage restrictions related to the ability of said contactless card to complete payment card transactions; causing a graphical user interface displayed on the display device to display an indication of the unlocked status for use and the usage limitations of the identified authorized contactless card. A non-transitory computer-readable storage medium.

17. further comprising computer readable program code executable by said processor circuitry; The processor circuitry includes: driving a display device to present a graphical user interface having a plurality of user preferences for setting usage limits for the contactless card; 17. The non-transitory computer-readable storage medium of claim 16.

18. further comprising computer readable program code executable by said processor circuitry; The processor circuitry includes: presenting, via a graphical user interface, a plurality of usage restrictions of the contactless card for selection of a user's preferences for the contactless card when unlocked; receiving, via the graphical user interface, a selection of at least one of the plurality of usage restrictions; when unlocked, storing said selection as a preference of the user of said contactless card; the plurality of usage restrictions include one or more of a geographic location, a geofenced area, a merchant name, a price threshold, a time threshold, a day of the week, a time range within a day, a zip code, an area code, a merchant category, or a product category; 17. The non-transitory computer-readable storage medium of claim 16.

19. further comprising computer readable program code executable by said processor circuitry; The processor circuitry includes: Obtaining location preference settings from preference settings of a plurality of users; Obtaining location data from a location application, the location data including a location, a timestamp, and a velocity; transmitting the acquired location preference settings and the acquired location data to an Unlock-Lock server; receiving a list of merchants that meet the acquired location preference settings based on the acquired location data; causing a graphical user interface of the display device to display a list of affiliated stores; 17. The non-transitory computer-readable storage medium of claim 16.

20. further comprising computer readable program code executable by said processor circuitry; The processor circuitry includes: determining, based on the location data provided by the location application, that a card unlock operation is requested if a card-present transaction is imminent; generating instructions to generate a notification indicating a request for a card unlock operation; executing, in accordance with the generated instructions, to output a notification activation signal operable to activate an output device or a display device; 20. The non-transitory computer-readable storage medium of claim 19.

Images