US11210656B2 - Determining specific terms for contactless card activation - Google Patents

Abstract

Systems, methods, articles of manufacture, and computer-readable media for determining specific terms to activate a contactless card. An application executing on a server may receive a request from a device specifying a uniform resource locator comprising encrypted data, the encrypted data based at least in part on a private key assigned to a contactless card. The application may decrypt the encrypted data and determine a type of the contactless card. The application may determine a plurality of terms associated with the type of the contactless card and transmit the terms to a web browser on the device. The application may receive, from the web browser, an indication specifying acceptance of the plurality of terms. The application may store, based on the decryption of the encrypted data and the received indication specifying acceptance of the terms, an indication in a database specifying the contactless card is activated for use.

Description

TECHNICAL FIELD

Embodiments herein generally relate to computing platforms, and more specifically, to computing platforms to determine specific terms for contactless card activation.

BACKGROUND

Payment cards may be mailed to a customer in an inactive state such that the cards cannot be used for purchases or other transactions prior to activation. There are significant security risks involved in the card activation process. Furthermore, different requirements may be imposed on the activation of specific types of cards. While some solutions have attempted to move the activation process to online platforms, these solutions do not offer the flexibility and security required to scale to the ever increasing number of card types.

SUMMARY

Embodiments disclosed herein provide systems, methods, articles of manufacture, and computer-readable media for determining specific terms to activate a contactless card. In one example, an application executing on a server may receive a request from a device specifying a uniform resource locator comprising encrypted data, the encrypted data based at least in part on a private key assigned to a contactless card. The application may decrypt the encrypted data and determine a type of the contactless card. The application may determine a plurality of terms associated with the type of the contactless card and transmit the terms to a web browser on the device. The application may receive, from the web browser, an indication specifying acceptance of the plurality of terms. The application may store, based on the decryption of the encrypted data and the received indication specifying acceptance of the terms, an indication in a database specifying the contactless card is activated for use.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C illustrate embodiments of a system for determining specific terms for contactless card activation.

FIGS. 2A-2C illustrate embodiments of a system for determining specific terms for contactless card activation.

FIGS. 3A-3D illustrate embodiments of determining specific terms for contactless card activation.

FIGS. 4A-4D illustrate embodiments of determining specific terms for contactless card activation.

FIGS. 5A-5B illustrate an example contactless card.

FIG. 6 illustrates an embodiment of a first logic flow.

FIG. 7 illustrates an embodiment of a second logic flow.

FIG. 8 illustrates an embodiment of a third logic flow.

FIG. 9 illustrates an embodiment of a fourth logic flow.

FIG. 10 illustrates an embodiment of a computing system.

DETAILED DESCRIPTION

Embodiments disclosed herein provide techniques for secure activation of contactless cards with disclosure of card-specific terms and/or customer-specific terms. Generally, a user may receive a contactless card in an inactive state that must be activated to be used. In some embodiments, the user may tap the contactless card to a computing device, such as a smartphone, to initiate the activation process. Tapping the contactless card to the smartphone (or otherwise brining the contactless card within wireless data communications range of the smartphone) may cause the contactless card to generate encrypted data. The encrypted data may be transmitted to the smartphone.

In some embodiments, the encrypted data generated by the contactless card may be part of a uniform resource locator (URL) directed to a server. Once received, an operating system (OS) of the smartphone may cause a web browser to access the URL. When accessed, the server may receive the encrypted data, and decrypt the encrypted data to verify the authenticity of the contactless card. The server may then determine a type of the contactless card and determine a plurality of terms and conditions associated with the card. The terms and conditions may be transmitted to the web browser on the smartphone, where the user may then accept and/or decline the terms and conditions. If the user accepts, an indication of the acceptance is transmitted to the server, which may activate the contactless card, e.g., by storing an indication that the contactless card is active in a database. The user may then use the contactless card for any desired payment transaction.

Advantageously, embodiments disclosed herein improve the security of all devices and associated data. For example, by requiring validation of encrypted data generated by the contactless card to activate the contactless card, the security of the contactless card is improved. As another example, by presenting terms and conditions specific to a type of the contactless card and/or other user attributes, user privacy and compliance with applicable laws and regulations is improved. Furthermore, doing so removes the need of the card issuer to mail the terms and condition in paper format, thereby conserving resources.

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

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

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

FIG. 1A depicts a schematic of anexemplary system100, consistent with disclosed embodiments. As shown, thesystem100 includes one or morecontactless cards101, one or moremobile computing devices110, and anauthentication server120. Thecontactless cards101 are representative of any type of payment cards, such as a credit card, debit card, ATM card, gift card, and the like. Thecontactless cards101 may comprise one ormore communications interfaces109, such as a radio frequency identification (RFID) chip, configured to communicate with thecomputing devices110 via NFC, the EMV standard, or other short-range protocols in wireless communication. Although NFC is used as an example communications protocol, the disclosure is equally applicable to other types of communications, such as the EMV standard, Bluetooth, and/or Wi-Fi. Themobile devices110 are representative of any type of network-enabled computing devices, such as smartphones, tablet computers, wearable devices, laptops, portable gaming devices, and the like. Theauthentication server120 is representative of any type of computing device, such as a server, workstation, compute cluster, cloud computing platform, virtualized computing system, and the like.

As shown, amemory102 of the contactless card includes anapplet103, acounter104, aprivate key105, adiversified key106, and a unique customer identifier (ID)107. Theapplet103 is executable code configured to perform the operations described herein. Thecounter104,private key105,diversified key106, andcustomer ID107 are used to provide security in thesystem100 as described in greater detail below.

As shown, amemory111 of themobile device110 includes an instance of an operating system (OS)112.Example operating systems112 include the Android® OS, iOS®, macOS®, Linux®, and Windows® operating systems. As shown, theOS112 includes anaccount application113. Theaccount application113 allows users to perform various account-related operations, such as activating one or morecontactless cards101, viewing account balances, purchasing items, processing payments, and the like. Theaccount application113 may further control access permissions to different functions provided by theaccount application113. In some embodiments, a user may authenticate using authentication credentials to access certain features of theaccount application113. For example, the authentication credentials may include a username (or login) and password, biometric credentials (e.g., fingerprints, Face ID, etc.), and the like.

As stated, thecontactless cards101 may need to be activated before thecontactless cards101 may be used to provide payment data for transactions. To activate acontactless card101, the user may tap thecontactless card101 to thedevice110. Generally, once thecontactless card101 is brought within communications range of thecommunications interface118 of thedevice110, theapplet103 of thecontactless card101 may generate encrypted data as part of the authentication process required to activate thecontactless card101. For example, in some embodiments, theapplet103 may generate a URL withencrypted data108 as part of the authentication process required to activate thecontactless card101. To enable NFC data transfer between thecontactless card101 and themobile device110, theaccount application113 may communicate with thecontactless card101 when thecontactless card101 is sufficiently close to thecommunications interface118 of themobile device110. Thecommunications interface118 may be configured to read from and/or communicate with thecommunications interface109 of the contactless card101 (e.g., via NFC, Bluetooth, RFID, etc.). Therefore,example communications interfaces118 include NFC communication modules, Bluetooth communication modules, and/or RFID communication modules.

As stated, thesystem100 is configured to implement key diversification to secure data, which may be referred to as a key diversification technique herein. Generally, the server120 (or another computing device) and thecontactless card101 may be provisioned with the same private key105 (also referred to as a master key, or master symmetric key). More specifically, eachcontactless card101 is programmed with a uniqueprivate key105 that has a corresponding pair in (or managed by) theserver120. For example, when acontactless card101 is manufactured, a uniqueprivate key105 may be stored in thememory102 of thecontactless card101. Similarly, the uniqueprivate key105 may be stored in a record (or profile) of a customer associated with thecontactless card101 in theaccount data124 of the server120 (and/or stored in a different secure location, such as the hardware security module (HSM)125). Theprivate key105 may be kept secret from all parties other than thecontactless card101 andserver120, thereby enhancing security of thesystem100. In some embodiments, theapplet103 of thecontactless card101 may encrypt and/or decrypt data (e.g., the customer ID107) using theprivate key105 and the data as input a cryptographic algorithm. For example, encrypting thecustomer ID107 with theprivate key105 may result in an encrypted customer ID. Similarly, theauthentication server120 may encrypt and/or decrypt data associated with thecontactless card101 using the correspondingprivate key105.

In some embodiments, thecounters104 and/orprivate keys105 of thecontactless card101 andserver120 may be used in conjunction with thecounters104 to enhance security using key diversification. Thecounters104 comprise values that are synchronized between a givencontactless card101 andserver120. Thecounter value104 may comprise a number that changes each time data is exchanged between thecontactless card101 and the server120 (and/or thecontactless card101 and the mobile device110). When preparing to send data (e.g., to theserver120 and/or the mobile device110), theapplet103 of thecontactless card101 may increment thecounter value104. Thecontactless card101 may then provide theprivate key105 andcounter value104 as input to a cryptographic algorithm, which produces adiversified key106 as output. The cryptographic algorithm may include encryption algorithms, hash-based message authentication code (HMAC) algorithms, cipher-based message authentication code (CMAC) algorithms, and the like. Non-limiting examples of the cryptographic algorithm may include a symmetric encryption algorithm such as 3DES or AES128; a symmetric HMAC algorithm, such as HMAC-SHA-256; and a symmetric CMAC algorithm such as AES-CMAC. Examples of key diversification techniques are described in greater detail in U.S. patent application Ser. No. 16/205,119, filed Nov. 29, 2018. The aforementioned patent application is incorporated by reference herein in its entirety. Theapplet103 of thecontactless card101 may include the cryptographic payload as a parameter of the URL withencrypted data108.

Continuing with the key diversification example, thecontactless card101 may then encrypt the data (e.g., thecustomer ID107 and/or any other data) using thediversified key106 and the data as input to the cryptographic algorithm. For example, encrypting thecustomer ID107 with thediversified key106 may result in an encrypted customer ID. In some embodiments, the encrypted data generated by thecontactless card101 may include a URL. The URL may be directed to theauthentication server120, or some other URL associated with an entity issuing thecontactless card101. In other embodiments, the URL may further be a universal link URL that opens a local resource (e.g., a specific page of theaccount application113, such as a card activation page). The URL may further include data (e.g., parameters) used by theauthentication server120 to validate the data generated by thecontactless card101.

For example, if the URL to the authentication server120 (and/or the URL to the account application113) is “http://www.example.com/accountapp” and the encrypted data generated based on the aforementioned encryption operations is “ABC123”, the URL withencrypted data108 may be “http://www.example.com/accountapp?data=ABC123”. In some embodiments, theapplet103 may encode the encrypted data according to an encoding format compatible with URLs prior to including the encrypted data as a parameter of theURL108. For example, the encrypted data may be a string of binary data (e.g., zeroes and ones), which may not be compatible with URLs. Therefore, theapplet103 may encode the encrypted data to the American Standard Code for Information Interchange (ASCII) base64 encoding format. Doing so represents the binary encrypted data in an ASCII string format by translating it into a radix-64 representation (e.g., “ABC123” in the previous example). Further still, in embodiments where the URL is directed to a local resource, such as theaccount application113, theURL108 may include an indication of which page of theaccount application113 to open. Continuing with the previous example, a page identifier of “1” (or other page identifier, such as a page name, etc.) may be added as a parameter to the URL, and the URL withencrypted data108 may be “http://www.example.com/accountapp?data=ABC123&p=1”.

Once generated, theapplet103 may transmit the URL withencrypted data108 to themobile device110, e.g., via NFC. In one embodiment, when received by theOS112, theOS112 causes theweb browser115 to access the URL withencrypted data108. Doing so causes information describing themobile device110 to be sent with the request to access the URL withencrypted data108. For example, the information may include attributes of themobile device110, such as operating system version, hardware capabilities, and software capabilities.

In the embodiment depicted inFIG. 1A, the URL withencrypted data108 is directed to theserver120, which may include a hypertext transfer protocol (HTTP) server. In one embodiment, theauthentication application123 provides the HTTP server and/or associated functionality. Therefore, theweb browser115 accessing the URL withencrypted data108 causes theserver120 to receive the URL withencrypted data108, e.g., in an HTTP request. Theauthentication application123 may receive the URL withencrypted data108 and extract the encrypted data, which may include the encrypted customer ID (e.g., the “ABC123” from the previous example, etc.). Theauthentication application123 may convert the encrypted data to the original encoding format (e.g., from ASCII base64 to binary). Theaccount application113 may similarly perform conversions, e.g., from ASCII base 64 to binary, and vice versa.

Theauthentication application123 may then attempt to authenticate the encrypted data. For example, theauthentication application123 may attempt to decrypt the encrypted data using a copy of theprivate key105 stored by theserver120. In another example, theauthentication application123 may provide theprivate key105 andcounter value104 as input to the cryptographic algorithm, which produces adiversified key106 as output. The resultingdiversified key106 may correspond to thediversified key106 of thecontactless card101, which may be used to decrypt theencrypted customer ID107. Therefore, theauthentication application123 may successfully decrypt the encrypted data, thereby verifying the encrypted data. For example, as stated, acustomer ID107 may be used to generate the encrypted data included in the URL withencrypted data108. In such an example, theauthentication application123 may decrypt the encrypted data using theprivate key105 of theauthentication server120. If the result of the decryption yields thecustomer ID107 associated with the account in theaccount data124, theauthentication application123 verifies the encrypted data. If theauthentication application123 is unable to decrypt the encrypted data to yield the expected result (e.g., thecustomer ID107 of the account associated with the contactless card101), theauthentication application123 does not verify (or validate or authenticate) the encrypted data. Due to the failed verification, theauthentication application123 may return an error to theweb browser115 and/or otherwise reject the attempted activation of thecontactless card101.

Regardless of the decryption technique used, theauthentication application123 may successfully decrypt theencrypted customer ID107, thereby verifying the encrypted customer ID107 (e.g., by comparing the resultingcustomer ID107 to a customer ID stored in theaccount data124, and/or based on an indication that the decryption using the key105 and/or106 was successful). Although thekeys105,106 are depicted as being stored in thememory122, thekeys105,106 may be stored elsewhere, such as in a secure element and/or theHSM125. In such embodiments, the secure element and/or theHSM125 may decrypt theencrypted customer ID107 using thekeys105 and/or106 and a cryptographic function. Similarly, the secure element and/orHSM125 may generate thediversified key106 based on theprivate key105 andcounter value104 as described above.

If theauthentication application123 verifies theencrypted customer ID107 in the URL withencrypted data108, theauthentication application123 may return a corresponding indication of verification to theweb browser115. Theauthentication application123 may then determine a type of thecontactless card101 being activated, e.g., based on a type specified in theaccount data124 and/or thecard data126. For example, each card may be associated with a unique identifier that is associated with at least one type of card, of a plurality of card types. Theauthentication application123 may further receive data describing attributes of the customer associated with thecontactless card101 being activated, e.g., the customer's address, date of birth, etc. Using the card type and/or the customer attributes, theauthentication application123 may determine a plurality ofterms127 from thecard data126 applicable to the card type and/or the customer data. Theterms127 may generally include terms, conditions, card member agreements, disclosures regarding the use of personal information, legal disclosures, privacy notices, and the like, which may collectively be referred to as “terms” herein. For example, a first card type may have a first plurality of terms (e.g., interest rates, disclosures, etc.), while a second card type may have a second plurality of terms, which may be the same and/or different than the first plurality of terms. Similarly, a customer located in a first state (e.g., based on the customer's address) may be required to receive additional and/or different terms relative to a customer located in a second state. Therefore, based on the customer attributes and/or the card type, theauthentication application123 dynamically determines a specific set of terms required to activate thecontactless card101.

In some embodiments, theauthentication application123 may determine that thecontactless card101 is a replacement for a previously active contactless card. In such embodiments, the user may have previously accepted the custom terms for the previous card, and a reduced set ofterms128 may be determined to activate the contactless card. For example, eachcontactless card101 may be associated with an issue and/or manufacture date. Theauthentication application123 may determine the dates of thereplacement card101 and the previous card and determine theterms127 based on the dates. In one embodiment, theauthentication application123 computes a difference of the different terms to determine the reduced set of terms (also referred to as a subset of terms). Theauthentication application123 may therefore determine the reduced set of terms that have changed, been added, and/or been removed based on the dates of each card. Doing so allows theauthentication application123 to transmit the reduced set of terms as thecustom terms128 to theweb browser115. However, the full set of terms may be included with the reduced set of terms. The user may then accept the reduced set of terms as part of the activation process of thereplacement card101. In some embodiments, theauthentication application123 may modify the format of thecustom terms128 to reflect which terms have changed for the replacement card. For example, if a new disclosure is added to thecustom terms128 of the replacement card that were not present in theterms127 of the original card, theauthentication application123 may highlight, bold, italicize, enlarge the font, or otherwise modify the new disclosure such that the user can easily detect the new terms.

FIG. 1B illustrates an embodiment where theauthentication application123 has decrypted the encrypted customer ID, thereby verifying (or authenticating) the encrypted data in the URL withencrypted data108, and determined a set ofcustom terms128 applicable to the activation of thecontactless card101. As shown, theauthentication application123 transmits thecustom terms128 to theweb browser115, where thecustom terms128 may further indicate that theauthentication application123 successfully decrypted the encrypted customer ID.

Responsive to receiving thecustom terms128, theweb browser115 may output an interface displaying thecustom terms128 for activation of thecontactless card101. The user may then read thecustom terms128 and determine to accept thecustom terms128 to activate thecontactless card101. For example, the user may click a checkbox indicating acceptance of thecustom terms128, provide a signature, etc.

FIG. 1C depicts an embodiment where the user has accepted thecustom terms128 via theweb browser115. As shown, theweb browser115 then transmits an indication ofacceptance129 to theserver120. Theauthentication application123 may then receive theacceptance129, and determine to activate thecontactless card101 based on the successful decryption of the encrypted data included in the URL withencrypted data108 and the user's acceptance of the custom terms128. In one embodiment, theauthentication application123 may store an indication in a user profile in theaccount data124 and/or thecard data126 indicating thecontactless card101 has been activated. Doing so allows the customer to use thecontactless card101 to provide payment data for transactions and/or provide the card number, expiration date, and/or CVV of thecontactless card101 in virtual interfaces to provide the payment data for transactions.

FIG. 2A is a schematic200 depicting an embodiment where theaccount application113 is used to activate thecontactless card101. As shown, the user taps thecontactless card101 to themobile device110 to proceed with the card activation. In some embodiments, the user may provide authentication credentials to access the account associated with thecontactless card101 prior to tapping thecontactless card101 to thedevice110. However, in other embodiments, the user need not be logged in to their account to activate thecontactless card101.

In response to the tap of thecontactless card101, theapplet103 encrypts thecustomer ID107, which is transmitted to theaccount application113 as at least a portion ofencrypted data208. Generally, the encrypted customer ID included in theencrypted data208 is generated by theapplet103 as described above with respect to the generation of the URL with encrypted data108 (e.g., by encrypting thecustomer ID107 with theprivate key105 and/or thediversified key106, where thediversified key106 is generated based on theprivate key105 and the counter value104).

Responsive to receiving the encrypted customer ID in theencrypted data208, theaccount application113 may transmit theencrypted data208 to theauthentication server120. Once received, theauthentication application123 may attempt to decrypt theencrypted customer ID208 using theprivate key105 and/or thediversified key106 as described above. If the attempted decryption yields thecustomer ID107 associated with the account, theauthentication application123 may transmit an indication of successful validation to theaccount application113. Otherwise, if the attempted decryption of theencrypted customer ID208 is not successful, theauthentication application123 may transmit an indication of the failed decryption to theaccount application113, which may reject activation of thecontactless card101. As another example, theauthentication application123 may reject activation of thecontactless card101.

FIG. 2B reflects an embodiment where theauthentication application123 verified the encrypted customer ID included in theencrypted data208. As stated, theauthentication application123 may determine a type of thecard101, a date of thecard101, or any other attribute of thecard101. Theauthentication application123 may further determine one or more attributes of the associated account holder (e.g., name, address, age, etc.). Theauthentication application123 may then use the attributes of thecard101 and/or the attributes of the account holder to determine a plurality ofcustom terms228 for thecontactless card101. Theauthentication application123 may then transmit thecustom terms228 to theaccount application113. Theaccount application113 may then output thecustom terms228 for display on themobile device110. As stated, in some embodiments (e.g., where thecontactless card101 is a replacement card), theterms228 may be a reduced set of terms. In such embodiments, theauthentication application123 and/or theaccount application113 may modify the reduced set of terms to improve readability thereof.

Theaccount application113 may provide one or more graphical user interface (GUI) elements allowing the user to accept theterms228.FIG. 2C depicts an embodiment where the user has accepted theterms228. In the depicted embodiment, theaccount application113 transmits an indication ofacceptance229 to theauthentication application123. Once theauthentication application123 receives theacceptance229, theauthentication application123 may activate thecontactless card101 based on the acceptance of the terms and the verification of theencrypted customer ID208. For example, theauthentication application123 may store an indication in theaccount data124 and/or thecard data126 indicating thecontactless card101 has been activated.

As previously stated, a URL may be directed to theaccount application113. Therefore, in such embodiments, theencrypted data208 generated inFIG. 2A may include a URL directed to a card activation page of theaccount application113. In such embodiments, theaccount application113 may extract theencrypted customer ID107 from the URL, optionally decode theencrypted customer ID107, and transmit the encoded and/or decodedcustomer ID107 to the to theserver120 via thenetwork130. Theauthentication application123 may then decrypt theencrypted customer ID107 to verify the encrypted data.

By requiring validation of encrypted data generated by thecontactless card101 to activate thecontactless card101, embodiments disclosed herein improve the security of thecontactless card101. Furthermore, by presenting terms specific to a type of the contactless card and/or specific to user attributes (e.g. country of residence, state of residence, city of residence, age, legal status, etc.), user privacy and compliance with applicable laws and regulations is improved. Furthermore, doing so removes the need of the card issuer to mail the terms and condition in paper format, thereby conserving resources.

FIG. 3A is a schematic300 depicting an example embodiment of tapping thecontactless card101 to provide secure activation using custom terms for thecontactless card101. Once the user taps thecontactless card101 to themobile device110, theapplet103 of thecontactless card101 encrypts thecustomer ID107 to generate the URL withencrypted data108. Theapplet103 may then transmit the URL withencrypted data108 to themobile device110, e.g., via NFC. Once received, theOS112 may cause thedevice110 to access the URL withencrypted data108. Because no application is in the foreground of the device110 (e.g., the device displays a home screen of the OS112), the NFC data transfer may be a background NFC read from the perspective of thedevice110. The background NFC read may cause theOS112 to open an application (e.g. theweb browser115 and/or the account application113).

In the embodiment depicted inFIG. 3A, the URL withencrypted data108 may be directed to theserver120 and/or theauthentication application123. As shown in the schematic310 ofFIG. 3B, theOS112 may launch theweb browser115 and cause theweb browser115 to access the URL withencrypted data108. As shown, theweb browser115 provides the user with indications specifying that the activation process has been initiated. Theauthentication application123 may then attempt to decrypt theencrypted customer ID107 using theprivate key105 and/or thediversified key106 assigned to thecontactless card101. If theauthentication application123 is unable to decrypt theencrypted customer ID107 to yield an expected result (e.g., thecustomer ID107 of the account, etc.), theauthentication application123 does not verify theencrypted customer ID107. If theauthentication application123 successfully decrypts theencrypted customer ID107 to yield an expected result (e.g., thecustomer ID107 of the account, etc.), theauthentication application123 verifies theencrypted customer ID107. As shown inFIG. 3B, theauthentication application123 successfully decrypts the encrypted customer ID, and theauthentication application123 transmits an indication of the verification to theweb browser115. Theauthentication application123 may then determine the custom terms for thecontactless card101 based on one or more attributes of thecard101 and/or one or more attributes of the account holder(s).

FIG. 3C is a schematic320 illustrating a simplified portion of thecustom terms127 determined by theauthentication application123 for thecontactless card101 being activated. More specifically,FIG. 3C depicts an embodiment where thecontactless card101 being activated is a replacement of a previouscontactless card101. Therefore, theweb browser115 may output some terms, such as theterms321, in a modified format, such as bold and italicized font. Doing so may allow the user to easily view the terms. Furthermore, as shown, the web browser may provide alink322 to the complete terms specific to the account holder and thecard101. Once accessed, thelink322 may cause theweb browser115 to display all relevant terms. The user may select the accept button to accept the terms, which causes theweb browser115 to transmit an indication of acceptance to theauthentication application123.FIG. 3D is a schematic330 illustrating an embodiment where theauthentication application123 has activated thecard101 for use, and returns a success page to theweb browser115.

FIG. 4A is a schematic400 depicting an example embodiment of tapping thecontactless card101 to provide secure activation using custom terms for thecontactless card101. As shown, theaccount application113 may be executing on themobile device110, and instruct the user to tap thecontactless card101 for activation. Once the user taps thecontactless card101 to themobile device110, theapplet103 of thecontactless card101 encrypts thecustomer ID107. Theapplet103 may then transmit theencrypted customer ID107 to themobile device110, e.g., via NFC.

FIG. 4B is a schematic410 illustrating an embodiment where theaccount application113 receives theencrypted customer ID107 from thecontactless card101. Theaccount application113 may then transmit theencrypted customer ID107 to theauthentication application123 for verification. Theauthentication application123 may then attempt to decrypt theencrypted customer ID107 using theprivate key105 and/or thediversified key106 assigned to thecontactless card101. If theauthentication application123 is unable to decrypt theencrypted customer ID107 to yield an expected result (e.g., thecustomer ID107 of the account, etc.), theauthentication application123 does not verify theencrypted customer ID107. If theauthentication application123 successfully decrypts theencrypted customer ID107 to yield an expected result (e.g., thecustomer ID107 of the account, etc.), theauthentication application123 verifies theencrypted customer ID107. As shown inFIG. 4B, theauthentication application123 successfully decrypts the encrypted customer ID, and theauthentication application123 transmits an indication of the verification to theweb browser115. Theauthentication application123 may then determine the custom terms for thecontactless card101 based on one or more attributes of thecard101 and/or one or more attributes of the account holder(s).

FIG. 4C is a schematic420 illustrating a simplified portion of thecustom terms127 determined by theauthentication application123 for thecontactless card101 being activated. More specifically,FIG. 4C depicts an embodiment where thecontactless card101 being activated is not a replacement of a previouscontactless card101. Therefore, theaccount application113 may output all terms received from theauthentication application123. While not depicted inFIG. 4C (orFIG. 3C) for the sake of clarity, the complete set of terms may be displayed on thedevice110. The user may select the accept button to accept the terms, which causes theaccount application113 to transmit an indication of acceptance to theauthentication application123.FIG. 4D is a schematic430 illustrating an embodiment where theauthentication application123 has activated thecard101 for use, and returns a success page to theaccount application113.

FIG. 5A illustrates acontactless card101, which may comprise a payment card, such as a credit card, debit card, and/or a gift card. As shown, thecontactless card101 may be issued by aservice provider502 displayed on the front or back of thecard101. In some examples, thecontactless card101 is not related to a payment card, and may comprise, without limitation, an identification card. In some examples, the payment card may comprise a dual interface contactless payment card. Thecontactless card101 may comprise asubstrate510, which may include a single layer or one or more laminated layers composed of plastics, metals, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyesters, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, thecontactless card101 may have physical characteristics compliant with the ID-1 format of the ISO/IEC 7810 standard, and the contactless card may otherwise be compliant with the ISO/IEC 14443 standard. However, it is understood that thecontactless card101 according to the present disclosure may have different characteristics, and the present disclosure does not require a contactless card to be implemented in a payment card.

Thecontactless card101 may also include identification information515 displayed on the front and/or back of the card, and acontact pad520. Thecontact pad520 may be configured to establish contact with another communication device, such as themobile devices110, a user device, smart phone, laptop, desktop, or tablet computer. Thecontactless card101 may also include processing circuitry, antenna and other components not shown inFIG. 5A. These components may be located behind thecontact pad520 or elsewhere on thesubstrate510. Thecontactless card101 may also include a magnetic strip or tape, which may be located on the back of the card (not shown inFIG. 5A).

As illustrated inFIG. 5B, thecontact pad520 ofcontactless card101 may include processingcircuitry525 for storing and processing information, including amicroprocessor530 and thememory102. It is understood that theprocessing circuitry525 may contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives and tamper proofing hardware, as necessary to perform the functions described herein.

Thememory102 may be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM, and EEPROM, and thecontactless card101 may include one or more of these memories. A read-only memory may be factory programmable as read-only or one-time programmable. One-time programmability provides the opportunity to write once then read many times. A write once/read-multiple memory may be programmed at a point in time after the memory chip has left the factory. Once the memory is programmed, it may not be rewritten, but it may be read many times. A read/write memory may be programmed and re-programed many times after leaving the factory. A read/write memory may also be read many times after leaving the factory.

Thememory102 may be configured to store one ormore applets103, thecounter value104,private key105, thediversified key106, and one or more customer (or user)IDs107. The one ormore applets103 may comprise one or more software applications configured to execute on one or more contactless cards, such as a Java® Card applet. However, it is understood thatapplets103 are not limited to Java Card applets, and instead may be any software application operable on contactless cards or other devices having limited memory. Thecustomer ID107 may comprise a unique alphanumeric identifier assigned to a user of thecontactless card101, and the identifier may distinguish the user of the contactless card from other contactless card users. In some examples, thecustomer ID107 may identify both a customer and an account assigned to that customer and may further identify the contactless card associated with the customer's account. In some embodiments, theapplet103 may use thecustomer ID107 as input to a cryptographic algorithm with thekeys105 and/or106 to encrypt thecustomer ID107. Similarly, theapplet103 may construct a URL that includes theencrypted customer ID107 as a parameter. The URL may be directed to theserver120 and/or theaccount application113.

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

In some examples, thecontactless card101 may comprise one ormore antennas555. The one ormore antennas555 may be placed within thecontactless card101 and around theprocessing circuitry525 of thecontact pad520. For example, the one ormore antennas555 may be integral with theprocessing circuitry525 and the one ormore antennas555 may be used with an external booster coil. As another example, the one ormore antennas555 may be external to thecontact pad520 and theprocessing circuitry525.

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

As explained above,contactless cards101 may be built on a software platform operable on smart cards or other devices having limited memory, such as JavaCard, and one or more or more applications or applets may be securely executed. Applets may be added to contactless cards to provide a one-time password (OTP) for multifactor authentication (MFA) in various mobile application-based use cases. Applets may be configured to respond to one or more requests, such as near field data exchange requests, from a reader, such as a mobile NFC reader (e.g., thecommunications interface118 of the device110), and produce an NDEF message that comprises a cryptographically secure OTP (e.g., an encrypted customer ID) encoded as an NDEF text tag.

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

FIG. 6 illustrates an embodiment of alogic flow600. Thelogic flow600 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, thelogic flow600 may include some or all of the operations to activate acontactless card101 using terms specific to the contactless card and the account holder. Embodiments are not limited in this context.

As shown, thelogic flow600 begins atblock605, where a user taps thecontactless card101 to themobile device110 to cause theapplet103 of thecontactless card101 to generate encrypted data. Atblock610, theapplet103 generates thecustomer ID107 as part of a URL with encrypted data. Atblock615, the applet transmits the URL with encrypted data to themobile device110. Atblock620, theOS112 may launch theweb browser115 to access the URL with encrypted data, which may be directed to theserver120 and/or theauthentication application123. Theserver120 may attempt to decrypt the encrypted customer ID included in the URL as described herein. Atblock625, theweb browser115 receives an indication from theserver120 that theencrypted customer ID107 was verified by decrypting theencrypted customer ID107. Doing so may cause theserver120 to determine the terms that are specific to the account holder and thecontactless card101.

Atblock630, theweb browser115 receives the plurality of terms from theserver120 and outputs the terms for display. Atblock635, theweb browser115 receives acceptance of the terms from the user. Atblock640, theweb browser115 transmits an indication of the acceptance to theserver120. Doing so may cause theserver120 to activate thecontactless card101. Atblock645, theweb browser115 may receive and output an indication from the server specifying that thecontactless card101 has been activated.

FIG. 7 illustrates an embodiment of alogic flow700. Thelogic flow700 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, thelogic flow700 may include some or all of the operations to activate acontactless card101 using terms specific to the contactless card and the account holder. Embodiments are not limited in this context.

As shown, thelogic flow700 begins atblock705, where a user taps thecontactless card101 to themobile device110 to cause theapplet103 of thecontactless card101 to generate encrypted data. Atblock710, theapplet103 generates theencrypted customer ID107, which may be part of a URL with encrypted data, where the URL is directed to an activation page of theaccount application113. Atblock715, the applet transmits the URL with encrypted data to themobile device110. Atblock720, theOS112 may launch theaccount application113 and open the card activation page responsive to receiving the URL withencrypted data108. Atblock725, theaccount application113 transmits the received encrypted data (e.g., the encrypted customer ID107) to theserver120. In one embodiment, the account application extracts the encrypted data (e.g., the encrypted customer ID107) from theURL108 before transmitting the encrypted data to the server. In another embodiment, theaccount application113 transmits the URL withencrypted data108 to theserver120. Theserver120 may then attempt to decrypt the encrypted data as described herein. Doing so may cause theserver120 to determine the terms that are specific to the account holder and thecontactless card101.

Atblock730, theaccount application113 receives an indication from theserver120 that theencrypted customer ID107 was verified by decrypting theencrypted customer ID107 and the determined plurality of terms. Atblock735, theaccount application113 receives acceptance of the terms from the user. Atblock740, theaccount application113 transmits an indication of the acceptance to theserver120. Doing so may cause theserver120 to activate thecontactless card101. Atblock745, theaccount application113 may receive and output an indication from the server specifying that thecontactless card101 has been activated.

FIG. 8 illustrates an embodiment of alogic flow800. Thelogic flow800 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, thelogic flow800 may include some or all of the operations to activate acontactless card101 using terms specific to the contactless card and the account holder. Embodiments are not limited in this context.

As shown, thelogic flow800 begins atblock805, where theserver120 receives a URL comprising encrypted data from aweb browser115 executing on amobile device110. The URL with encrypted data may be generated by theapplet103 of thecontactless card101 based at least in part on the private key assigned to thecontactless card101. Atblock810, theserver120 may decrypt the encrypted data based on an instance of the private key maintained by theserver120. Atblock815, theserver120 determines a type of thecontactless card101. For example, a unique identifier of thecontactless card101 may be stored in theaccount data124 and/or thecard data126. The unique identifier may be used to determine a type of the card, e.g., in thecard data126. Thecard data126 may specify the type of the card, a date the card was issued, and anyrelated terms127 for the card. Atblock820, theserver120 determines the plurality of terms for the card and/or terms based on user attributes, such as age, residence, credit limits, etc.

Atblock825, theserver120 may optionally identify any changed terms for the card, e.g., when the card is a replacement for a previous card held by the account holder. Theserver120 may modify the changed terms (e.g., highlight, bold, increase font size, etc.) of the changed terms to improve readability on the user's device. Atblock830, theserver120 transmits an indication to theweb browser115 that theserver120 decrypted the encrypted data, thereby verifying the encrypted data. Theserver120 may further transmit the terms determined atblock820, which may be outputted for display by theweb browser115. Atblock835, theserver120 receives an indication from theweb browser115 specifying that the user accepted the terms. Atblock840, theserver120 stores an indication (e.g., in the account data124) indicating that the card has been activated for use based on the acceptance of the terms and the decryption of the encrypted data. Atblock845, theserver120 transmits an indication to theweb browser115 indicating the card has been activated. Theweb browser115 may display the indication on a display.

FIG. 9 illustrates an embodiment of alogic flow900. Thelogic flow900 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, thelogic flow900 may include some or all of the operations to activate acontactless card101 using terms specific to the contactless card and the account holder. Embodiments are not limited in this context.

As shown, thelogic flow900 begins atblock905, where theserver120 receives encrypted data from anaccount application113 executing on amobile device110. The encrypted data may be generated by theapplet103 of thecontactless card101 based at least in part on the private key assigned to thecontactless card101. In some embodiments, theapplet103 includes the encrypted data as a parameter of a URL with encrypted data. Atblock910, theserver120 may decrypt the encrypted data based on an instance of the private key maintained by theserver120. Atblock915, theserver120 determines a type of thecontactless card101. For example, a unique identifier of thecontactless card101 may be stored in theaccount data124 and/or thecard data126. The unique identifier may be used to determine a type of the card, e.g., in thecard data126. Thecard data126 may specify the type of the card, a date the card was issued, and anyrelated terms127 for the card. Atblock920, theserver120 determines the plurality of terms for the card and/or terms based on user attributes, such as age, residence, credit limits, etc.

Atblock925, theserver120 may optionally identify any changed terms for the card, e.g., when the card is a replacement for a previous card held by the account holder. Theserver120 may modify the changed terms (e.g., highlight, bold, increase font size, etc.) of the changed terms to improve readability on the user's device. Atblock930, theserver120 transmits an indication to theaccount application113 that theserver120 decrypted the encrypted data, thereby verifying the encrypted data. Theserver120 may further transmit the terms determined atblock920, which may be outputted for display by theaccount application113. Atblock935, theserver120 receives an indication from theaccount application113 specifying that the user accepted the terms. Atblock940, theserver120 stores an indication (e.g., in the account data124) indicating that the card has been activated for use based on the acceptance of the terms and the decryption of the encrypted data. Atblock945, theserver120 transmits an indication to theaccount application113 indicating the card has been activated. Theaccount application113 may display the indication on a display.

FIG. 10 illustrates an embodiment of anexemplary computing architecture1000 comprising acomputing system1002 that may be suitable for implementing various embodiments as previously described. In various embodiments, thecomputing architecture1000 may comprise or be implemented as part of an electronic device. In some embodiments, thecomputing architecture1000 may be representative, for example, of a system that implements one or more components of thesystem100. In some embodiments,computing system1002 may be representative, for example, of thecontactless card101,mobile devices110, andauthentication server120 of thesystem100. The embodiments are not limited in this context. More generally, thecomputing architecture1000 is configured to implement all logic, applications, systems, methods, apparatuses, and functionality described herein with reference toFIGS. 1-9.

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

Thecomputing system1002 includes various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components, power supplies, and so forth. The embodiments, however, are not limited to implementation by thecomputing system1002.

As shown inFIG. 10, thecomputing system1002 comprises aprocessor1004, asystem memory1006 and asystem bus1008. Theprocessor1004 can be any of various commercially available computer processors, including without limitation an 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 multi processor architectures may also be employed as theprocessor1004.

Thesystem bus1008 provides an interface for system components including, but not limited to, thesystem memory1006 to theprocessor1004. Thesystem bus1008 can be any of several types of bus structure that may further interconnect to 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 thesystem bus1008 via a slot architecture. Example slot architectures may include without limitation Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and the like.

Thesystem memory1006 may include various types of computer-readable storage media in the form of one or more higher speed memory units, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., one or more flash arrays), polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, an array of devices such as Redundant Array of Independent Disks (RAID) drives, solid state memory devices (e.g., USB memory, solid state drives (SSD) and any other type of storage media suitable for storing information. In the illustrated embodiment shown inFIG. 10, thesystem memory1006 can includenon-volatile memory1010 and/orvolatile memory1012. A basic input/output system (BIOS) can be stored in thenon-volatile memory1010.

Thecomputing system1002 may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive (HDD)1014, a magnetic floppy disk drive (FDD)1016 to read from or write to a removablemagnetic disk1018, and anoptical disk drive1020 to read from or write to a removable optical disk1022 (e.g., a CD-ROM or DVD). TheHDD1014,FDD1016 andoptical disk drive1020 can be connected to thesystem bus1008 by aHDD interface1024, anFDD interface1026 and anoptical drive interface1028, respectively. TheHDD interface1024 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. Thecomputing system1002 is generally is configured to implement all logic, systems, methods, apparatuses, and functionality described herein with reference toFIGS. 1-9.

The drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-readable instructions, computer-executable instructions, and so forth. For example, a number of program modules can be stored in the drives andmemory units1010,1012, including anoperating system1030, one ormore application programs1032,other program modules1034, andprogram data1036. In one embodiment, the one ormore application programs1032,other program modules1034, andprogram data1036 can include, for example, the various applications and/or components of thesystem100, e.g., theapplet103, counter104,private key105,diversified key106,customer ID107,operating system112,account application113,web browser115, theauthentication application123, theaccount data124, thecard data126,terms127, URL withencrypted data108, and/or theencrypted data208.

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

Amonitor1044 or other type of display device is also connected to thesystem bus1008 via an interface, such as avideo adaptor1046. Themonitor1044 may be internal or external to thecomputing system1002. In addition to themonitor1044, a computer typically includes other peripheral output devices, such as speakers, printers, and so forth.

Thecomputing system1002 may operate in a networked environment using logical connections via wire and/or wireless communications to one or more remote computers, such as aremote computer1048. Theremote computer1048 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to thecomputing system1002, although, for purposes of brevity, only a memory/storage device1050 is illustrated. The logical connections depicted include wire/wireless connectivity to a local area network (LAN)1052 and/or larger networks, for example, a wide area network (WAN)1054. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network, for example, the Internet. In embodiments, thenetwork130 ofFIG. 1 is one or more of theLAN1052 and theWAN1054.

When used in a LAN networking environment, thecomputing system1002 is connected to theLAN1052 through a wire and/or wireless communication network interface oradaptor1056. Theadaptor1056 can facilitate wire and/or wireless communications to theLAN1052, which may also include a wireless access point disposed thereon for communicating with the wireless functionality of theadaptor1056.

When used in a WAN networking environment, thecomputing system1002 can include amodem1058, or is connected to a communications server on theWAN1054, or has other means for establishing communications over theWAN1054, such as by way of the Internet. Themodem1058, which can be internal or external and a wire and/or wireless device, connects to thesystem bus1008 via theinput device interface1042. In a networked environment, program modules depicted relative to thecomputing system1002, or portions thereof, can be stored in the remote memory/storage device1050. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

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

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

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

The foregoing description of example embodiments has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the present disclosure be limited not by this detailed description, but rather by the claims appended hereto. Future filed applications claiming priority to this application may claim the disclosed subject matter in a different manner, and may generally include any set of one or more limitations as variously disclosed or otherwise demonstrated herein.

Claims (20)

What is claimed is:

1. A non-transitory computer-readable storage medium having computer-readable program code embodied therewith, the computer-readable program code executable by a processor to cause the processor to:

receive, by an application executing on the processor from an account application executing on a device and via a network, authentication credentials associated with an account;

determine, by the application, that the authentication credentials are valid to access the account;

receive, by the application, a request to activate a contactless card assigned to the account, the request specifying a uniform resource locator (URL), a parameter of the URL comprising encrypted data, the encrypted data based at least in part on a private key assigned to the contactless card, wherein the URL is generated by the contactless card and read by the device;

decrypt, by the application, the encrypted data based on the private key;

determine, by the application, that the contactless card is a first type of contactless card, the first type of contactless card one of a plurality of types of contactless cards;

determine, by the application, a plurality of terms associated with the first type of contactless card;

transmit, by the application, the determined plurality of terms to the account application executing on the device;

receive, by the application from the account application, an indication specifying acceptance of the plurality of terms; and

storing, by the application based on the decryption of the encrypted data and the received indication specifying acceptance of the plurality of terms, an indication in a database specifying the contactless card is activated for use.

2. The non-transitory computer-readable storage medium ofclaim 1, the computer-readable program code executable by the processor to cause the processor to:

determine the contactless card is of the first type of contactless card based on a unique identifier assigned to the contactless card; and

transmit an indication to the account application executing on the device specifying that the contactless card is activated for use.

3. The non-transitory computer-readable storage medium ofclaim 1, the computer-readable program code executable by the processor to cause the processor to:

encrypt, by the application, a counter value and the private key to generate a diversified key; and

decrypt, by the application, the encrypted data using the diversified key.

4. The non-transitory computer-readable storage medium ofclaim 1, the computer-readable program code executable by the processor to cause the processor to:

receive, by the application, a plurality of attributes from a user profile associated with the contactless card, the plurality of attributes comprising at least the first type of contactless card and an address associated with the contactless card; and

determine, by the application, the plurality of terms based on the first type of contactless card and the address associated with the contactless card, wherein at least one term of the plurality of terms is based on the address.

5. The non-transitory computer-readable storage medium ofclaim 1, the computer-readable program code executable by the processor to cause the processor to:

determine, by the application based on a user profile associated with the contactless card, that the contactless card is a replacement of a previous contactless card specified in the user profile;

determine, by the application, a date of the previous contactless card;

determine, by the application, a previous plurality of terms associated with the previous contactless card; and

determine, by the application based on the date of the previous contactless card and a date of the contactless card, a subset of the plurality of terms associated with the contactless card that have changed relative to the plurality of terms associated with the previous contactless card.

6. The non-transitory computer-readable storage medium ofclaim 5, the computer-readable program code executable by the processor to cause the processor to:

format, by the application, the subset of the plurality of terms according to a modified format, wherein the modified format comprises one or more of a highlight effect, a bold effect, or an italics effect applied to the subset of the plurality of terms; and

transmit, by the application, the formatted subset of the plurality of terms to the account application.

7. The non-transitory computer-readable storage medium ofclaim 6, the computer-readable program code executable by the processor to cause the processor to:

transmit, by the application to the account application executing on the device, a uniform resource locator (URL) directed to the plurality of terms associated with the contactless card.

8. A system, comprising:

a processor; and

a memory storing instructions which when executed by the processor, cause the processor to:

receive, by an application executing on the processor via a network, a request from a device specifying a uniform resource locator (URL), a parameter of the URL comprising encrypted data, the encrypted data based at least in part on a private key assigned to a contactless card, the request to activate the contactless card, wherein the URL is generated by the contactless card and read by the device;

decrypt, by the application, the encrypted data based on an instance of the private key stored in the memory;

determine, by the application based at least in part on a profile, that the contactless card is a first type of contactless card, the first type of contactless card one of a plurality of types of contactless cards;

determine, by the application, a plurality of terms associated with the first type of contactless card;

transmit, by the application, the determined plurality of terms to a web browser executing on the device;

receive, by the application from the web browser, an indication specifying acceptance of the plurality of terms; and

store, by the application based on the decryption of the encrypted data and the received indication specifying acceptance of the plurality of terms, an indication in a database specifying the contactless card is activated for use.

9. The system ofclaim 8, the memory storing instructions which when executed by the processor, cause the processor to:

determine the contactless card is of the first type of contactless card based on a unique identifier assigned to the contactless card; and

transmit an indication to the web browser executing on the device specifying that the contactless card is activated for use.

10. The system ofclaim 8, the memory storing instructions which when executed by the processor, cause the processor to:

extract, by the application, the encrypted data from the URL; and

decode, by the application, the extracted encrypted data prior to the decryption.

11. The system ofclaim 8, the memory storing instructions which when executed by the processor, cause the processor to:

extract, by the application, a counter value from the encrypted data;

encrypt, by the application, the counter value and the private key to generate a diversified key; and

decrypt, by the application, the encrypted data using the diversified key.

12. The system ofclaim 8, the memory storing instructions which when executed by the processor, cause the processor to:

receive, by the application, a plurality of attributes from the profile, the plurality of attributes comprising at least the first type of contactless card and an address associated with the contactless card; and

determine, by the application, the plurality of terms based on the first type of contactless card and the address associated with the contactless card, wherein at least one term of the plurality of terms is based on the address.

13. The system ofclaim 8, the memory storing instructions which when executed by the processor, cause the processor to:

determine, by the application based on a user profile associated with the contactless card, that the contactless card is a replacement of a previous contactless card specified in the user profile;

determine, by the application, a date of the previous contactless card;

determine, by the application, a previous plurality of terms associated with the previous contactless card;

determine, by the application based on the date of the previous contactless card and a date of the contactless card, a subset of the plurality of terms associated with the contactless card that have changed relative to the plurality of terms associated with the previous contactless card;

format, by the application, the subset of the plurality of terms according to a modified format, wherein the modified format comprises one or more of a highlight effect, a bold effect, or an italics effect applied to the subset of the plurality of terms; and

transmit, by the application, the formatted subset of the plurality of terms to the web browser.

14. The system ofclaim 13, the memory storing instructions which when executed by the processor, cause the processor to:

transmit, by the application to the web browser executing on the device, a link directed to the plurality of terms associated with the contactless card.

15. A method, comprising:

receiving, by an application executing on a processor of a server via a network, a request from a device specifying a uniform resource locator (URL) comprising encrypted data, the encrypted data based at least in part on a private key assigned to a contactless card, wherein the encrypted data is a parameter of the URL, wherein the URL is generated by the contactless card and read by the device;

decrypting, by the application, the encrypted data based on the private key;

determining, by the application, that the contactless card is a first type of contactless card, the first type of contactless card one of a plurality of types of contactless cards;

determining, by the application, a plurality of terms associated with the first type of contactless card;

transmitting, by the application, the determined plurality of terms to a web browser executing on the device;

receiving, by the application from the web browser, an indication specifying acceptance of the plurality of terms; and

storing, by the application based on the decryption of the encrypted data and the received indication specifying acceptance of the plurality of terms, an indication in a database specifying the contactless card is activated for use.

16. The method ofclaim 15, further comprising:

determining the contactless card is of the first type of contactless card based on a unique identifier assigned to the contactless card; and

transmitting an indication to the web browser executing on the device specifying that the contactless card is activated for use.

17. The method ofclaim 15, further comprising:

extracting, by the application, the encrypted data from the URL; and

decoding, by the application, the extracted encrypted data prior to the decryption.

18. The method ofclaim 15, further comprising:

extracting, by the application, a counter value from the encrypted data;

encrypting, by the application, the counter value and the private key to generate a diversified key; and

decrypting, by the application, the encrypted data using the diversified key.

19. The method ofclaim 15, further comprising:

receiving, by the application, a plurality of attributes from a user profile associated with the contactless card, the plurality of attributes comprising at least the first type of contactless card and an address associated with the contactless card; and

determining, by the application, the plurality of terms based on the first type of contactless card and the address associated with the contactless card, wherein at least one term of the plurality of terms is based on the address.

20. The method ofclaim 15, further comprising:

determining, by the application based on a user profile associated with the contactless card, that the contactless card is a replacement of a previous contactless card specified in the user profile;

determining, by the application, a date of the previous contactless card;

determining, by the application, a previous plurality of terms associated with the previous contactless card;

determining, by the application based on the date of the previous contactless card and a date of the contactless card, a subset of the plurality of terms associated with the contactless card that have changed relative to the plurality of terms associated with the previous contactless card;

formatting, by the application, the subset of the plurality of terms according to a modified format, wherein the modified format comprises one or more of a highlight effect, a bold effect, or an italics effect applied to the subset of the plurality of terms; and

transmitting, by the application, the formatted subset of the plurality of terms to the web browser.

Images