Steganographic image encoding of biometric template information on cards.
Steganographically encoded images on contactless cards enhance financial card security by providing efficient and secure user verification and transaction authentication, addressing vulnerabilities in existing authentication methods.
Patent Information
- Application Number
- JP2021534345
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-12-24
- Filing Date
- 2020-11-24
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2040-11-24
AI Technical Summary
Existing authentication mechanisms for financial cards, such as credit cards, are time-consuming and vulnerable to compromise, relying on login credentials that can be easily hacked, limiting secure account access and transaction verification.
Utilizing steganographically encoded images, particularly fingerprint templates, on contactless cards for user verification and transaction authentication, combining offline and online protocols to enhance security and convenience.
Provides secure and efficient user verification and transaction authorization, preventing unauthorized access by encoding images in a manner that is not easily discernible, enhancing security and reducing reliance on traditional login credentials.
Smart Images

Figure 0007582947000001 
Figure 0007582947000002 
Figure 0007582947000003
Abstract
Description
[Technical field]
[0001] Related Applications This application claims priority to U.S. patent application Ser. No. 16 / 726,565, entitled "STEGANOGRAPHIC IMAGE ENCODING OF BIOMETRIC TEMPLATE INFORMATION ON A CARD," filed Dec. 24, 2019, the contents of which are incorporated herein by reference in their entirety.
[0002] Incorporation by Reference Statement This application is related to Application No. 16 / 135,954, entitled "SYSTEM AND METHOD FOR PROVIDING CARD INTERACTION," filed on September 19, 2018, which is incorporated by reference in its entirety.
[0003] Technical Field FIELD OF THE DISCLOSURE
[0002] Embodiments herein relate generally to computing platforms, and more particularly to authenticating users utilizing steganographically encoded images. [Background technology]
[0004] Activation of many cards, and more specifically financial cards (e.g., credit cards), involves a time-consuming process in which the cardholder calls a phone number, visits a website, and enters or otherwise provides card information. Additionally, while the increasing use of chip-based financial cards offers more secure features for in-person purchases than previous technologies (e.g., magnetic strip cards), access to an account still typically relies on login credentials (e.g., username and password) to verify the cardholder's identity and / or otherwise complete a transaction. However, if the login credentials are compromised, other persons may be able to access the user's account.
[0005] Therefore, there is a need for improved authentication mechanisms for competing transactions, including account access and payment transactions. Summary of the Invention
[0006] The embodiments disclosed herein provide systems, methods, articles of manufacture, and computer-readable media for utilizing steganographically encoded images to verify a user and / or complete a transaction, including but not limited to a payment transaction. According to one or more examples, an online or offline protocol is used to verify and / or authenticate a user to initiate an exchange of information that utilizes steganographic images for authentication.
[0007] According to one example, a computer-implemented method utilizing an application executing on a computer system may initiate a transaction to verify a user's identity and / or authorize the transaction using a steganographically encoded image. In various embodiments, the application may be launched by tapping a contactless card on a user device, e.g., a mobile device. The method may include an application executed on a processor circuit associated with a user's computing device, the application using near field communication (NFC) communicating with a contactless card, the contactless card having a radio frequency identification (RFID) chip, the contactless card being within NFC range of a digital reader associated with a third party device, the application communicating with the contactless card to perform at least one verification operation, and in response to performing the at least one verification operation, communicating with the contactless card to receive a steganographic image for authenticating a user associated with the computing device, the steganographic image including the user's government-issued identification steganographically encoded using a fingerprint template of the user, the steganographic image being created by verifying at the verification device that an image of the user's identification is authentic, and creating the steganographic image at the verification device after verification.
[0008] According to another example, a system authenticates and / or verifies a user and / or authorizes a transaction using online and / or offline authentication and steganographically encoded images. The system may include a processor circuit and a memory storing instructions that, when executed by the processor circuit, cause an application executing on the processor circuit associated with a computing device to receive from a user first application user credentials associated with a user profile, a processor associated with the application to compare the first application user credentials with stored second application user credentials for a first match, the stored second application user credentials being associated with the user's identity, and in response to finding the first match, authenticate the user's identity by initiating communication with a communication interface of the contactless card, the communication including: i) performing at least one of a) a hostless verification operation and b) an issuer-based verification operation; and ii) an exchange of information including an image of the user's government identification, the image including a steganographic encoding of a fingerprint template associated with the user.
[0009] According to yet another example, a contactless card is provided having a communications interface for communicating with a computing device and processing circuitry for storing information, the information including an identification image of a user, the identification image being steganographically encoded with a fingerprint template associated with the user. [Brief description of the drawings]
[0010] [Figure 1] 1 illustrates an embodiment of a system for verifying or authenticating a user in accordance with a payment protocol. [Diagram 2] 1 illustrates at least one embodiment of tapping to verify a user utilizing an authentication protocol. [Diagram 3]3 illustrates at least one embodiment that utilizes steganographic images based on tapping and verifying in FIG. 2. [Figure 4A] 1 shows an example of a contactless card. [Figure 4B] 1 shows an example of a contactless card. [Diagram 5] 1 illustrates an embodiment of a first logic flow. [Figure 6] 1 illustrates a second logic flow embodiment. [Figure 7A] 13 illustrates a third logic flow embodiment. [Figure 7B] 13 illustrates a fourth logic flow embodiment. [Figure 7C] 13 illustrates a fourth logic flow embodiment. [Figure 8] 1 illustrates an embodiment of a computing architecture. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Aspects of the present disclosure include systems, methods, and / or techniques for providing authenticated cardholder access. In general, various embodiments relate to creating a steganographically encoded image and utilizing the steganographically encoded image to verify a user and / or authorize a transaction, such as a payment transaction. In various embodiments, the steganographically encoded image is used in combination with one or both of offline and online authentication protocols, e.g., a user may be authenticated offline and / or online to receive or otherwise utilize the steganographic image. In various embodiments, the steganographically encoded image is a fingerprint template encoded into an identification, such as a government identification, which may be authenticated utilizing one or more verification techniques that may be authenticated before or after steganographically encoding the fingerprint template into an image of the government identification and / or a medium reflecting an image of the government identification. Consistent with the disclosed embodiments, the systems and methods may utilize one or more computing devices, processors, web servers, account servers, and / or contactless devices (e.g., radio frequency identification (RFID) cards).
[0012] Various embodiments of the present disclosure provide one or more advantages with respect to verifying a user and completing a transaction, such as a payment transaction. In various embodiments, utilizing a steganographically encoded image provides an advantage in itself, since a steganographic image is not easily identifiable by the naked eye or by conventional scanning techniques, by having at least one feature associated with identifying the user, e.g., a fingerprint template, encoded in the image or medium in a secure and hidden manner, preventing the image from being compromised or misused. These advantages can be enhanced in a verification context. In various embodiments, the medium or image containing the steganographic image is a proven identification of the user, which can provide an initial way to verify and / or identify the user before scanning and decrypting the image to obtain the fingerprint template, which can be compared to a scan of the user's fingerprint as an additional security measure. Additionally, these advantages can be further enhanced with an additional layer of security, including utilizing the steganographic image only after an offline and / or online authentication protocol has been performed that allows access to the steganographically encoded image. Thus, various embodiments may significantly improve security associated with verifying a user and / or authenticating a transaction initiated by a user.
[0013] FIG. 1 illustrates a schematic diagram of an exemplary system 100 consistent with disclosed embodiments. As shown, the system 100 includes one or more contactless cards 101, one or more mobile devices 110, and a server 120. The contactless card 101 is representative of any type of payment card, such as a credit card, a debit card, an ATM card, a gift card, etc. In various embodiments, the contactless card 101 or card 101 is a virtual payment card. The contactless card 101 may include one or more chips (not shown), such as a radio frequency identification (RFID) chip, configured to communicate with the mobile device 110 via NFC, EMV standards, or other short-range protocols in wireless communication. Although NFC is used as an exemplary communication protocol, the present disclosure is equally applicable to other types of wireless communication, such as other suitable communication protocols compliant with EMV standards, Bluetooth, and / or Wi-Fi. The mobile device 110 is representative of any type of network-enabled computing device, such as a smartphone, a tablet computer, a wearable device, a laptop, a portable gaming device, etc. Server 120 represents any type of computing device, such as a server, a workstation, a computer cluster, a cloud computing platform, a virtualized computing system, or the like.
[0014] As shown, the contactless card's memory 102 includes a data store of card data 103, counter 104, master key 105, diversified key 106, unique customer identifier 107, and account number 108. Card data 103 generally includes account related information, such as information used to process payments using contactless card 101. For example, card data 103 may comprise an account number, an expiration date, a billing address, and a card verification value (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 the disclosure. Card data 103 may further include a name, a billing address, a shipping address, and other account related information. Account number 108 stores a single-use virtual account number with an associated expiration date and CVV value. For example, account number 108 may include thousands of single-use virtual account numbers, expiration dates, and CVV values.
[0015] As shown, the memory 112 of the mobile device 110 includes an instance of an operating system (OS) 112, and the processor 119 may perform one or more operations associated with applications of the operating system (OS) 112 and / or any other suitable operations associated with processor activity, including comparison operations and execution instructions associated with the memory 111. Examples of operating systems 112 include Android® OS, iOS®, Linux®, and Windows® operating systems. As shown, the OS 112 includes one or more applications, including an account application 113, an authentication or verification application or service 114 (hereinafter referred to as an “authentication application” for convenience), one or more other applications 115, and / or one or more access applications 116. The account application 113 allows a user to perform various account-related operations, such as viewing an account balance, purchasing items, and processing payments. Initially, a user may authenticate using authentication credentials to access the account application 113. For example, the authentication credentials may include a username and password, biometric credentials, etc.
[0016] The authentication application 114 is generally configured to determine when a user requires authentication for a transaction, service, or accessibility request, including completing a payment associated with the application. For example, the authentication application 114 may determine that a user requires access to a particular application and / or is required to complete a transaction or payment associated therewith, such as an access application 116. The access application 116 may be or include an application configured to allow access to one or more features of a particular service associated with a user account, such as a transportation service (e.g., public transportation), a bank account, a health insurance account, a financial account or application including account balances, brokerage information, or any other suitable financial data, a service application (e.g., retail services, delivery services, entertainment services, gaming services, etc.), and any other suitable application that may require user authentication. In various embodiments, the access application 116 may be associated with a payment function, e.g., a credit or bank account for making or receiving payments, and / or the authentication transaction may still involve a non-payment function, e.g., activation of a credit or debit card, for authentication or verification. In various embodiments, the access application 116 is a retail or goods / service delivery application, and one or more functions associated with the access application 116 include completing a payment related to goods or services provided in connection with the access application 116. As described below, the transaction or payment related thereto may be completed by utilizing a steganographically encoded image, and in various embodiments, the steganographically encoded image may be utilized in accordance with an online and / or offline authentication protocol.In various embodiments, the authentication application 114 may utilize a separate API interface and calls for access to the access application 116 to facilitate the authentication protocol. The authentication application 114 may be configured to verify the user by utilizing any suitable protocol, including one or more of encryption techniques, EMV standards, or any verification process that utilizes an authentication protocol compliant with the EMV standard. In various embodiments, the authentication application 114 is configured to synchronize the counter 104 associated with the contactless card 101 with a server 120 associated with the issuer that can communicate with the contactless card 101 and the mobile device when authentication of the user occurs.
[0017] In various embodiments, the authentication application 114 may coordinate with the server 120 and / or the contactless card 101 to record approval of non-payment transactions associated with the counter 104. The log may be a counter log 121 located in the memory 122 of the server 120 or in the memory 102 of the contactless card 101. The log may keep separate transaction tallies of transactions that are payment transactions and non-payment transactions, regardless of the total tally of the counter 104 and the server 120 or the contactless card 101. The server 120 and / or the authentication application 114 in communication with the contactless card may utilize the information contained therein for fraud prevention measures. For example, the authentication application 114 and / or the server 120 may reject a payment transaction if a threshold number of non-payment transactions between the non-payment transactions and the payment transactions is too low (or too high), or vice versa. In various embodiments, the counter log 121 including the identification information, e.g., counts, between the non-payment transactions and the payment transactions may be used for any other suitable purpose during online or offline verification protocols.
[0018] In various embodiments, the authentication application 114 is associated with the account application 113. For example, the authentication application 114 may be installed on the mobile device 110 with the account application 113, and the user is prompted to enable the authentication application 114 following installation. More generally, each time the account application 113 is opened, the account application 113 may determine whether the authentication application 114 has been enabled as a default authentication application for the OS 112. If the authentication application 114 has not been enabled as a default authentication application, the account application 113 may prompt the user to enable the authentication application 114 as a default authentication application for the OS 112 and / or to enable one or more features of the authentication application 114. Once enabled as a default authentication application for the OS 112, the authentication application 114 may programmatically identify when an authorization application requires authentication and utilize a payment protocol to enable verification even when the payment is not associated with verification or authorization. In various embodiments, to initiate an authentication or verification protocol (e.g., at least one operation associated with an online or offline verification technique or protocol), the authentication application 114 may prompt the user to tap the contactless card 101 to the mobile device 110 to initiate one or more operations associated with the authentication application 114 or therewith, including accessing or utilizing the steganographically encoded image 117b stored on the contactless card 101 and / or the mobile device 110.
[0019] The system 100 may include a steganography application 117a stored in the memory 111 of the mobile 110 and / or the memory 122 of the server 120. In various embodiments, the steganography application 117a may perform one or more steganography operations, including noise-based processes, chafing and winnowing, embedding and encryption techniques, mimicking and / or any other suitable steganographic encoding technique or techniques, and may be used to encode an image or template onto another image and / or medium reflecting the other image. For example, the encoding application 117a may encode a fingerprint template of a user relating to an identification of the user, such as the user's government identification, onto an image of the user's government identification and / or onto a medium, e.g., a plastic frame, reflecting an image of the user's government identification, e.g., a driver's license. The steganographically encoded image, e.g., fingerprint template, will be invisible to the naked eye and / or to a scanning device that cannot decode the identification image in a manner consistent with the technique used to steganographically encode the fingerprint template onto the identification image (or medium). Note that in various embodiments, the fingerprint template is not an actual fingerprint image but a data set including fingerprint features, and the fingerprint template may be compared to an actual fingerprint by configuring a scanning device to scan a fingerprint with a user's finger, recreating the fingerprint template from the fingerprint scan, and comparing and matching the extracted fingerprint template with a previously obtained fingerprint template (e.g., stored in the memory of the mobile device 110, the server 120, or any suitable device). The steganographically encoded image may be stored in memory 111 of the mobile device 110, memory 122 of the server 120, and / or memory 102 of the contactless card 101.
[0020] In various embodiments, the mobile device 110 may include a fingerprint scanner 138. The fingerprint scanner 138 may be configured to scan the fingerprint of a user's finger and create a fingerprint template from the scanned fingerprint template. The fingerprint scanner 138 may be further configured with an appropriate steganographic decoding application or technique for decoding the steganographically encoded image 117b, e.g., a government-issued user's identification having a steganographically encoded fingerprint template thereon. While the fingerprint scanner 138 shown is part of the mobile device 110, a scanner separate from the mobile device may be used to scan the user's finger and the steganographically encoded image 117b may be compared to the fingerprint obtained from the scan. The scan may be local, where the image 117b is scanned directly from either the mobile device 110 and / or the contactless card 101. If a match occurs, the scanner 138 may communicate a positive result to the authentication application 114, which may allow access to one or more functions of the access application 116, including completing a transaction associated therewith (e.g., a payment transaction).
[0021] In various other embodiments, the image 117b may be transmitted from the server 120 for a comparison to be performed, and / or in various embodiments, the fingerprint scan may be transmitted from the mobile device to a server, which may have an appropriate application, e.g., the management application 123, that derives a template from the fingerprint scan and compares it to a stored version of the steganographically encoded image 117b. The management application 123 may then communicate to an appropriate component of the mobile device 110, e.g., the authentication application 114, that there is a positive match, which may grant access to one or more functions of the access application 116, including completing a transaction associated therewith (e.g., a payment transaction).
[0022] In various embodiments, at a facility 146 associated with an issuer of a card service that includes services associated with the contactless card 101, a user may attest to their identity, e.g., a government-issued identity such as a driver's license. At the facility 146, a representative 147 may verify the authenticity of the identity by any suitable verification of the government identity, e.g., by electronically scanning it and comparing it to public records and performing a computer transaction utilizing server verification at a server associated with the issuer, e.g., server 120. The server is notified that the user is associated with the verified government identity without storing the government identity on server 120 (e.g., due to privacy concerns). Account data 124 on server 120 may be updated to indicate that there is a verified government identity associated with the user. At the facility 146, the representative may utilize any suitable scanner and steganography application, including but not limited to the fingerprint scanner 138 and steganography application 117a of the mobile device 110, to obtain an image of the government identification, scan the user's fingerprint, derive a fingerprint template from the scanned fingerprint, and steganographically encode the fingerprint template into the image of the government identification. The government image with the steganographic encoding, e.g., image 117b, may be stored locally on either the contactless card 101 and / or the mobile device 110, and the server 120 is notified that the procedure has been performed in the account data 124. In various embodiments, this may protect the user's privacy without compromising security, since the stored government image with the steganographic encoding of the fingerprint template, e.g., aggregate image 117b, may be used to locally verify the user. For example, when a user attempts to perform a transaction associated with the access application 116 at a location 148 (e.g., a retail store) having a computer system belonging to an issuer associated with the server 120, a representative at the location 148 may compare a physical copy of the user's government identification with a stored electronic version (in the mobile device 110 and / or contactless card 101) to access the first level of information.Because the identification has been officially verified, the local copy of the government identification may be compared to a physical copy of the user identification with a level of certainty that the government identification is authentic. The first level of information may be an account balance, a loyalty points balance, other information identified as first level information as described herein, and / or as other appropriate.
[0023] In various embodiments, offline and / or online authentication protocols (as described herein) may be used in combination with identity comparison for additional security for accessing the second level of information, for enhanced security for accessing the first level of information or for accessing the second level of information associated with the access application 116, such as social security numbers, sensitive information as may be appropriate (e.g., health information if the location 148 is a medical facility, etc.), for completing a payment transaction, for accessing any other information defined as second level of information as described herein, or for accessing in any other suitable manner. In various embodiments, the scan of the user's fingerprint may be performed utilizing any suitable scanner, such as, for example, scanner 138, and then the same or other scanner matching the steganographic encoding technique associated with the image 117b may scan and decode the fingerprint template associated with the image 117b and compare and match the fingerprint template obtained from the scan of the user's finger with the decoded template associated with 117b. A match may be an additional requirement to access or perform an activity associated with the first or second level information (e.g., making a payment), or it may be a condition for accessing a third level information and / or for performing an activity with a higher level of security risk, such as performing a payment transaction in association with an access application 116 that exceeds a certain monetary threshold. In various embodiments, access to the image 117b is conditional on performing either or both of an online and / or offline authentication protocol. In various embodiments, initiation of the offline and / or online protocol may be initiated by a first tap of the contactless card 101 on the mobile device, and a comparison of the fingerprint template associated with the image 117b to a fingerprint template obtained from a subsequent scan of the user's finger may be based on a second tap of the contactless card 101 on the mobile device 110, or vice versa.Additional conditions for accessing any level of information and / or performing a transaction in connection with the access application 116 include comparing user credentials (e.g., username and password) to stored user credentials, as described below, and the additional conditions may be the first condition required to initiate a transaction and / or access any level of information in connection with the access application 116.
[0024] Generally, in various embodiments described herein, an online verification or authentication protocol may include one or more of the following operations: An authentication application may initiate a transaction to verify a user's identity, the authentication application may initiate all or a portion of an application by prompting the user to tap a computing device, e.g., the contactless card 101 on a mobile device 110, to access the application 116, and / or utilize a steganographically encoded image 117b that may be scanned to access functionality of the application 116, and / or complete a transaction associated therewith. The transaction may include an NFC communication between a card reader 118 and the contactless card 101, and the contactless card 101 may provide the mobile device 110 with one or more inputs, including a current version of an application transaction counter (ATC). The contactless card 101 or the mobile device 110 (including any suitable components associated therewith) may generate an appropriate cryptogram based on the multiple inputs. The contactless card 101 or the mobile device 110 (including any suitable components associated therewith) may then transmit the cryptogram and the ATC to an issuer of the contactless card 101 (e.g., a server 120 associated with the issuer). The user may then be verified and receive access to one or more functions associated with the application 116 by receiving a response from the issuer verifying or authorizing the user, the received response being based on at least one cryptographic operation performed by the issuer (e.g., the server 120) in response to receiving the cryptogram. In various embodiments, once the user is verified, the server 120 may transmit an authentication instruction to an appropriate application, e.g., the authentication application 114, to access the steganographically encoded image 117b stored on either the mobile device 110 and / or the contactless card for purposes of performing an authentication operation (e.g., a fingerprint template comparison) to access one or more functions of the access application 116 and / or to perform a transaction in connection therewith.
[0025] In general, in various embodiments described herein, an offline verification or authentication protocol may include one or more of the following operations: The authentication application 114 may initiate an NFC communication between the mobile device 110 and the contactless card 101 to provide the user with access to one or more functions of the access application 116, and may receive one or more inputs from the contactless card 101, the communication may utilize a card reader 118. The authentication application 114 may facilitate receipt of a public key of a key pair from the contactless card 101 and cardholder identification information of the card's account holder (e.g., user). An application or component associated with the contactless card 101 and / or the authentication application 114 may instruct a component of the card 101 to generate a digital signature by using a private key of the card's key pair, and the mobile device 110 may receive the digital signature from the card 101 and verify the signature using the public key. As described herein, the protocol may be initiated by one or more taps of the contactless card 101 on the mobile device 110. In various embodiments, once the user is verified, the authentication application 114 may access the steganographically encoded image 117b stored on either the mobile device 110 and / or the contactless card for purposes of performing an authentication operation (e.g., fingerprint template comparison) to access one or more functions of the access application 116 and / or to perform a transaction in connection therewith.
[0026] Various embodiments may utilize a hybrid protocol including one or more operations of online and offline protocols, where the online protocol may be initiated by a first or second tap of the contactless card 101 on the mobile device 110 and / or a first or second user credential comparison, and the offline protocol may be initiated by a first or second tap of the mobile device 110 on the contactless card 101 and / or a first or second user credential comparison, and a combination of the offline and online protocols may be part of a single verification or authentication, or each may be associated with a partial verification or authentication.
[0027] In various embodiments, if the contactless card 101 is a virtual payment card, the authentication application 114 may obtain information related to the contactless card 101 by accessing a digital wallet embodied on the mobile device 110, the digital wallet including the virtual payment card.
[0028] As shown, the server 120 further 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, such as an application transaction counter ("ATC") 104, a customer ID 107, an associated contactless card 101, an account holder name, an account billing address, one or more shipping addresses, one or more virtual card numbers, and biographical information for each account. The memory 122 includes a management application 123 and instances of the card data 103, the counter 104, the master key 105, and diversified keys 106 for one or more accounts from the account data 124.
[0029] The system 100 is configured to implement key diversification to protect data, which may be referred to herein as a key diversification technique. The system 100 may implement an online authentication protocol or a hybrid online and offline authentication protocol. Both the online authentication protocol and the hybrid offline and online authentication protocol may utilize one or more operations of the server 120.
[0030] In various embodiments, the authentication application 114 receives from the user first application user credentials associated with a user profile. The first application user credentials may include biometric data, an established gesture associated with user recognition, a username and password combination, and the like. The processor 119 compares the first application user credentials to the stored second application user credentials. The stored second application user credentials may be associated with a user identity and may be stored in either the memory 111 of the mobile device 110 or the memory 122 of the server 120. In various embodiments, the stored second application user credentials are maintained in the server 120 and the first match is performed by the server 120. In various embodiments, upon determining a first match between the first application user credentials and the stored second application user credentials, the authentication application 114 may allow the user to access one or more first level user account options and / or information of a user account associated with the access application 116. The user account may be a financial account, a health insurance account, and / or other similar accounts associated with any service provider (e.g., a transit account, an entertainment account, etc.). Once a first match is determined, the user may access a particular first level user account option associated with the access application 116 without utilizing the steganographically encoded image 117b and / or without performing additional operations associated with online and / or offline authentication or verification protocols. In various embodiments, the first level access may occur without or prior to completion of a transaction, e.g., completion of a payment, in association with the access application 116, which requires additional authentication, such as execution of an online and / or offline authentication protocol and / or utilization of the steganographically encoded image 117b.The first level of user account options may include viewing account balance, viewing recent transactions, etc. To perform second level user account options, as stated and implied, for greater access and / or certain account functions, i.e., performing payment transactions, a second level of authentication may be required, such as by fully completing online and / or offline authentication protocols and / or utilizing steganographically encoded images 117b.
[0031] In general, the server 120 (or other computing device) and the contactless card 101 may be provisioned with the same master key 105 (also referred to as a master symmetric key). More specifically, each contactless card 101 is programmed with a separate master key 105 that has a corresponding pair in 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 customer record associated with the contactless card 101 in the account data 124 of the server 120 (and / or may be stored in a different secure location). The master key may be kept secret from all parties other than the contactless card 101 and the server 120, thereby enhancing the security of the system 100.
[0032] The master key 105 may be used in combination with the counter 104 to enhance security using key diversification. The counter 104 comprises a value that is synchronized between the contactless card 101 and the server 120. The counter value 104 may comprise a number that changes each time data is exchanged between the contactless card 101 and the server 120 (and / or 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 application 113 may communicate with the contactless card 101 when the contactless card 101 is sufficiently close (e.g., within NFC range) to the card reader 118 of the mobile device 110. The card reader 118 may be a digital reader with NFC capabilities, e.g., an NFC reader, and may be configured to read from and / or communicate with the contactless card 101 (e.g., via NFC, Bluetooth, RFID, etc.). Thus, the exemplary card reader 118 includes an NFC communication module, a Bluetooth® communication module, and / or an RFID communication module.
[0033] For example, a user may request authorization or verification to access an access application 116. One or more components of the system 100, including the authentication application 114, may initiate communications (e.g., API calls or other suitable mechanisms) with the access application 116 to utilize one or more payment protocols to verify or authenticate the user, regardless of whether the access application 116, or the particular aspect sought to be accessed by a user of the access application 116, involves making a payment.
[0034] In various embodiments, the one or more protocols may include online technologies as discussed elsewhere herein. The authentication application 114 provides a prompt to the user to tap the contactless card 101 to the mobile device 110, thereby bringing the contactless card 101 close enough to the card reader 118 of the mobile device 110 to enable NFC data transfer between the contactless card 101 and the card reader 118 of the mobile device 110. In various embodiments, the mobile device 110 may trigger the card reader 118 via an API call. Additionally and / or alternatively, the mobile device 110 may trigger the card reader 118 based on periodically polling the card reader 118. More generally, the mobile device 110 may trigger the card reader 118 to communicate using any feasible method.
[0035] In various embodiments, prior to initiating communication in connection with the contactless card 101, the card reader 118, and the mobile device 110, and / or immediately after establishing communication between the contactless card 101 and the card reader 118, the authentication application 114 may receive the first application user credentials as a prerequisite for initiating card activation and / or online or offline authentication protocols. The user may provide the first application user credentials after receiving a prompt from the authentication application to enter the credentials. As described above, the first application user credentials may include biometric data, an established gesture associated with user recognition, a username and password combination, facial recognition, etc. As described above, in various embodiments, the authentication application 114 communicates the first application user credentials to the processor 119. The processor 119 compares the first application user credentials to the stored second application user credentials. The stored second application user credentials may be located in memory 111 associated with mobile device 110, memory 102 associated with contactless card 101, and / or memory 122 associated with server 120. In various embodiments, the first application user credentials are provided to server 120, which compares the first application user credentials with the stored second application user credentials. In various embodiments, as described above, processor 119 communicates the comparison result to authentication application 114 (e.g., for a match).In various embodiments, the first match may initiate or serve as a prerequisite for one or more of: i) initiating the remainder of an online verification protocol to verify or authenticate the user to access the access application 116, and / or ii) granting the user access to first level user account options of the user account associated with the access application 116 (e.g., viewing account balance and / or recent transactions), and / or iii) utilizing the steganographically encoded image 117b to access one or more features associated with and / or complete a transaction related thereto, e.g., a payment transaction. Thus, in various embodiments, the verification authentication application, in response to finding a first match, initiates additional operations (associated with an online or offline verification process) to verify the identity of the user.
[0036] In various embodiments, a first match of the first application user credentials with the stored second application user credentials may or may not grant a first level of access to an application, e.g., the access application 116, but the first match may in any event serve as a prerequisite for initiating at least one of the online and / or offline protocols. In various embodiments, if the first level of access was not initially granted, then the first level of access will be granted upon successful completion of at least one of the online and / or offline protocols. In various embodiments, the second level of access to the access application 116 is granted immediately upon completion of at least one of the online and / or offline verification protocols and / or utilization of the steganographically encoded image 117b, where the second level of access may refer to completing a payment transaction in connection with the access application 116. In various embodiments, both the verification protocol and the use of the steganographically encoded image 117b (e.g., decoding the associated fingerprint template and comparing it to a fingerprint template derived from a subsequent user finger scan fingerprint) are required to access the second level of information and / or perform a transaction. In various embodiments, the offline and / or online protocol may be sufficient to allow access to the second level of information and / or transactions that meet certain conditions, e.g., below a certain monetary threshold, while third level of information and / or transactions of heightened security concerns, e.g., above a certain monetary threshold, may require the use of the steganographically encoded image 117b.
[0037] In various embodiments, additional prerequisites may be applied as conditions for initiating either the offline and / or online protocols, such as initiating an offline authentication protocol only if there is a network failure that prevents online authentication from taking place.
[0038] In various embodiments, regardless of other prerequisites, a first tap of the contactless card 101 on the mobile device 110 initiates one of the online and offline verification protocols, and a second tap, and subsequent taps, initiate the other one of the online and offline verification protocols.
[0039] In various embodiments, after communication is established between the mobile device 110 and the contactless card 101, regardless of whether one or more prerequisites apply or are performed, the contactless card 101 generates a message authentication code (MAC) cryptogram. In various embodiments, this may occur when the contactless card 101 is read by the account application 113. In particular, this may occur upon reading, such as an NFC read, of a Near Field Radio Exchange (NDEF) tag, which may be created according to an NFC data exchange format. For example, the account application 113 and / or a reader, such as the card reader 118, may send a message, such as an applet selection message, with the applet ID of the NDEF generating applet. In various embodiments, the generated cryptogram may be an Authorization Request Cryptogram (ARQC) consistent with the EMV standard.
[0040] In various embodiments, once the selection is confirmed, a sequence of select file messages followed by read file messages may be sent. For example, the sequence may include "select feature file", "read feature file", and "select NDEF file". At this point, a counter value 104 maintained by the contactless card 101 may be updated or incremented, followed by "read NDEF file". At this point, a message may be generated, which may include a header and a shared secret. A session key may then be generated. A MAC ciphertext may be created from the message, which may include a header and a shared secret. The MAC ciphertext may then be concatenated with one or more blocks of random data, and the MAC ciphertext and random number (RND) may be encrypted with the session key. The ciphertext and header may then be concatenated and encoded as ASCII hexadecimal numbers and returned in an NDEF message format (in response to the "read NDEF file" message). In various embodiments, the MAC ciphertext may be sent as an NDEF tag, and in other examples, the MAC ciphertext may be included with a uniform resource indicator (e.g., as a formatted string). Contactless card 101 may then transmit the MAC cryptogram to mobile device 110, which may then forward the ACA cryptogram to server 120 for verification, as described below. (However, in various embodiments described elsewhere herein, e.g., in an offline context, mobile device 110 may verify the MAC cryptogram.)
[0041] More generally, when preparing to transmit data (e.g., to the server 120 and / or the mobile device 110), the contactless card 101 may increment the counter value 104. The contactless card 101 may then provide the master key 105 and the counter value 104 as inputs to an encryption algorithm, which generates the diversified key 106 as an output. The encryption 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 encryption 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, and / or other algorithms or techniques consistent with applicable versions of ISO / IEC 1833 and / or ISO / IEC 7816. The contactless card 101 may then encrypt data (e.g., the customer identifier 107 and any other data) using the diversified key 106. The contactless card 101 may then transmit the encrypted data (e.g., encrypted customer ID 109) to the account application 113 of the mobile device 110 (e.g., via an NFC connection, a Bluetooth connection, etc.). The account application 113 of the mobile device 110 may then transmit the encrypted data to the server 120 over the network 130. In at least various embodiments, the contactless card 101 transmits the counter value 104 along with the encrypted data. In such embodiments, the contactless card 101 may transmit the counter value 104 encrypted or unencrypted.
[0042] Upon receiving the encrypted customer ID 109, the management application 123 of the server 120 may perform the same symmetric encryption using the counter value 104 as an input to the encryption and the master key 105 as the key for the encryption. As mentioned, the counter value 104 may be specified in the data received from the mobile device 110, or the counter value 104 is maintained by the server 120 to implement key diversification for the contactless card 101. The output of the encryption may be the same diversified key value 106 created by the contactless card 101. The management application 123 may then decrypt the encrypted customer ID 109 received over the network 130 using the diversified key 106, which reveals the data transmitted by the contactless card 101 (e.g., at least the customer identifier 107). By doing so, the management application 123 may verify the data transmitted by the contactless card 101 via the mobile device 110, for example, by comparing the decrypted customer ID 107 to the customer ID in the account data 124 for the account.
[0043] Although the counter 104, e.g., ATC, is used 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 replaced with a random nonce generated each time a new diversified key 106 is needed, the full value of the 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, and a cryptographic hash of the data. In various embodiments, one or more portions of the diversified key 106 may be used by the parties to create multiple diversified keys 106.
[0044] As shown, server 120 may include one or more hardware security modules (HSMs) 125. For example, one or more HSMs 125 may be configured to perform one or more cryptographic operations as disclosed herein. In various embodiments, one or more HSMs 125 may be configured as special purpose security devices configured to perform one or more cryptographic operations. HSMs 125 may be configured such that keys are never exposed outside of HSMs 125, but instead are maintained within HSMs 125. For example, one or more HSMs 125 may be configured to perform at least one of key derivation, decryption, and MAC operations. One or more HSMs 125 may be included within server 120 or in data communication with server 120.
[0045] As noted, key diversification techniques may be used to perform secure operations using contactless card 101. For example, once management application 123 verifies customer ID 109 encrypted using key diversification, management application 123 may send a message to authentication application 114 indicating that the user has been verified and / or authenticated, which may in turn grant the user access to authentication application 116. In various embodiments, the transmitted output may include an Authorization Response Cryptogram (ARPC).
[0046] As is specific to one or more embodiments described herein, including the discussion above, a server 120 that may be used in online authentication or verification, or hybrid online and offline operations, may be configured to operate consistent with the EMV standard, including performing operations utilizing the EMV payment protocol for non-payment purposes. A host server (or system) 120 may be associated with an issuer of a card associated with a user, the host system including a non-transitory computer-readable storage medium storing computer-readable program code executable by a processor, the processor and storage medium may include one or more hardware or software components, including those generally described in FIG. 8. The host system may be configured to receive transaction data associated with the access application 116 and / or the contactless card 101. Receipt of the transaction data may be facilitated as described herein, for example, by an authentication application 114 (or other suitable component or application of the mobile device 110) associated with the mobile device 110 and the user (or other suitable computing device). The authentication application 114 may initiate an authentication or verification transaction with one or more other components, for example, the contactless card 101 and the card reader 118. Transaction data is received by server 120 from authentication application 114. The transaction data may include i) a counter (e.g., ATC), a cryptogram based on one or more inputs of the transaction, and a symmetric key associated with the card. In various embodiments, the cryptogram is an Authorization Request Cryptogram (ARQC).
[0047] In various embodiments, once the server 120 receives the transaction data, the management application 123 may send a response (e.g., from the issuer) verifying the identity of the user based on the received cryptogram to the appropriate component of the mobile device 110, e.g., the authentication application 114, which may in turn grant access to relevant portions or functions of the access application 116 and / or grant access to the steganographically encoded image 117b that may be utilized to complete a transaction associated with the access application 116. In various embodiments, once the verification is complete, the authentication application 114 may approve access to utilize the steganographically encoded image 117b, e.g., the steganographic application 117a may extract a fingerprint template from the steganographically encoded image 117b and compare it to a fingerprint template obtained from a fingerprint scan of the user using the scanner 138, such that a successful match may result in access to one or more functions associated with the access application 116 and / or complete a transaction related thereto.
[0048] In various embodiments, the server 120 may utilize the counter log 121 to perform anti-fraud measures. In various embodiments, the counter log 121 may include a timestamp associated with a counter value associated with one or more non-payment transactions. In various embodiments, the counter log 121 may include a timestamp associated with a counter value associated with one or more payment transactions. In various embodiments, the counter value of the ATC associated with a particular transaction, e.g., whether it is a payment transaction or a non-payment transaction, may also be recorded. The management application 123 may be configured to compare the general number of payment transactions performed among the non-payment transactions. If the number of payment transactions after a non-payment transaction exceeds a certain threshold, the management application 123 may reject the payment transaction even if the transaction would otherwise have been completed (e.g., an excessively large number of payment transactions after a non-payment transaction may be considered fraudulent because it is assumed that a user may use a payment protocol for non-payments as well as payment transactions). In various embodiments, the opposite may be implemented. For example, a large number of non-payment transactions performed after a payment transaction exceeding a threshold may cause the management application 123 to reject the particular non-payment transaction when validation or authentication is performed. In various embodiments, for any transaction, e.g., a threshold value for the time between payment or non-payment, in that it exceeds a minimum or maximum threshold, the management application 123 may reject the authentication or verification operation. The counter log 121 may be used to perform any other suitable operation, including performing anti-fraud measures in any other suitable manner. In various embodiments, the anti-fraud measures, in addition to utilizing the steganographically encoded image 117b in a comparison context, may invalidate an approved transaction regardless of the level of security employed, e.g., by performing one or both of online and offline authorization protocols.
[0049] In addition to one or more online operations as outlined herein and above, the system 100 may facilitate one or more offline operations to verify or authenticate a user offline. In various embodiments, the offline operations are used in combination with the online techniques. In various embodiments, the offline operations may be used based on preconditions, for example, when a network failure prevents the use of one or more online operations.
[0050] In various embodiments, the authentication application 114 receives first application user credentials to access one or more aspects or features of the authentication application 116 in a manner similar to that discussed in connection with the embodiments described herein with respect to the online verification technique, and the offline verification or authentication technique may utilize a payment protocol consistent with the EMV standard for purposes other than completing a payment transaction. The user may provide the first application user credentials after receiving a prompt from the authentication application. The first application user credentials may include biometric data, an established gesture associated with user recognition, a username and password combination, facial recognition, and the like. In various embodiments, the authentication application 114 communicates the first application user credentials to the processor 119. The processor 119 compares the first application user credentials with the stored second application user credentials. The stored second application user credentials may be located in the memory 111 associated with the mobile device 110 or in the memory 102 of the contactless card 101.
[0051] In various embodiments, the processor 119 communicates the comparison result to the authentication application 114 (e.g., for a match). In various embodiments, a first match may allow the user to access first level aspects associated with the authentication application 116 (e.g., viewing account balances and / or recent transactions), e.g., user account options of the user account. In response to finding a first match, the authentication application 114 initiates verification or authentication of the user's identity with one or more offline operations. For example, the authentication application 114 may output a notification to bring the contactless card 101 close to the mobile device 110 for display on the mobile device 110. The authentication application 114 may then communicate with the contactless card 101 (e.g., after being brought close to the contactless card 101). The communication between the authentication application 114 and the contactless card 101 may include the contactless card 101 being sufficiently close to the card reader 118 of the mobile device 110 to allow NFC data transfer between the authentication application 114 and the contactless card 101. In various embodiments, the contactless card 101 transmits to the authentication application 114, or other suitable component or application of the mobile device 110, the public key of the public / private key pair and the card's account holder, e.g., the cardholder identification information of the user to be verified or authenticated in association with the access application 116. In various embodiments, the authentication application 114 may instruct the contactless card 101 to generate a digital signature using the private key of the card's key pair. In various embodiments, the cardholder identification information may be incorporated within or otherwise communicated along with the digital signature.
[0052] In various embodiments, the contactless card 101 transmits the digital signature to the authentication application 114 or other suitable component or application of the mobile device 110. In various embodiments, the authentication application 114 may communicate the digital signature to the processor 119, which may verify the digital signature using a public key. For example, the contactless card 101 may provide a hash of the card's public key encrypted by a trusted source (e.g., the card provider's private key), and verifying the digital signature may include decrypting the encrypted hash (e.g., with the card provider's public key), calculating a new hash of the digital signature, and comparing the decrypted original hash and the new hash for a match, at which point the card provider (e.g., issuer) and the transaction card may be authenticated. In various embodiments, once the transaction card is authenticated, the authentication application 114 may grant access to utilize the steganographically encoded image 117b. For example, the steganography application 117a may extract a fingerprint template from the steganographically encoded image 117b and compare it to a fingerprint template obtained from a fingerprint scan of a user using the scanner 138, and upon a successful match, may access one or more functions associated with the access application 116 and / or complete a transaction related thereto.
[0053] In various embodiments, as described and implied elsewhere herein, if the authentication application 114 determines that there is a network outage associated with the network 130 or that access to the server 120 is not possible for some other reason, offline authentication may be used, otherwise online authentication is used to authenticate the user and facilitate use of the steganographically encoded image 117b. In various embodiments, offline and online techniques may be implemented in sequence to add security and to facilitate use of the steganographically encoded image 117b.
[0054] In various embodiments, either the mobile device 110 and / or the contactless card 101 may be configured to utilize a counter log 121 (not explicitly shown with respect to the mobile device 110) to implement anti-fraud measures.
[0055] In various embodiments, for example when both online and offline techniques are implemented, verification of the digital signature may be performed by a server, such as server 120, connected to mobile device 110, for example by network 130. For example, processor 119 may output the digital signature for transmission to server 120, which may verify the digital signature.
[0056] 2 is a schematic diagram 200 illustrating an example embodiment of tapping to initiate an online verification and / or offline authentication protocol for utilizing steganographically encoded images to access functionality and / or complete a transaction in association with the access application 116. A graphical user interface (GUI) of the authentication application 114 on the mobile device 110 may include a prompt 206 for tapping the contactless card 101 to initiate authentication or verification of another application, e.g., the access application 116, and another API interface may be provided by the authentication application 114 to communicate the verification or authentication (once completed) to the access application 116. In various embodiments, the access application 116 provides a prompt 202 to enter user credentials for comparison (e.g., as described with reference to FIG. 1) for a first and / or second level of information access associated with the access application 116 as a prerequisite for receiving the tap prompt 206 or after the tap has been performed but prior to additional online or offline verification operations. In various embodiments, the authentication application 114 provides an interface for prompts 202 for entering user credentials for the access application 116 and / or other applications, such as the other applications 115 .
[0057] In various embodiments, when contactless card 101 is tapped to mobile device 110, authentication application 114 sends instructions to contactless card 101 via card reader 118 (e.g., via NFC, Bluetooth, RFID, etc.). In various embodiments, the instructions may specify to perform one or more encryption techniques, as described with respect to FIG. 1. In various embodiments, online authentication techniques are used, where authentication application 114 receives transaction data from server 120. In various embodiments, offline authentication techniques are used, where authentication application 114 and contactless card 101 utilize public / private key encryption techniques to authenticate the user. In various embodiments, the prompts to transmit data between contactless card 101 and mobile device 110 may specify to transmit data to authentication application 114 via any suitable protocol consistent with an EMV protocol or standard, and in various embodiments, authentication application 114 receives any suitable data directly from contactless card 101 via a protocol consistent with an EMV protocol or standard.
[0058] 3 is a schematic diagram 300 illustrating an example embodiment utilizing a steganographically encoded image after a tap is made to initiate an online verification and / or offline authentication protocol, for example, to access functionality in association with an access application 116 and / or to complete a transaction. Whether online verification or authentication including utilization of a server 120 is used to perform authentication or verification of a user, whether offline verification including utilization of a mobile device 110, a contactless card 101, and / or a card reader 118 is used to perform authentication or verification of a user without involving a server 120, and / or whether hybrid offline and online verification including utilization of a mobile device 110, a card reader 118, a contactless card 101, and / or a server 120 is used to perform authentication or verification of a user, a steganographic image 307 is generated on a display of a mobile device suitable for scanning by any suitable scanning device. The steganographic image 307 may have a visible portion, e.g., a government identification, and an encoded portion, e.g., a fingerprint template of a user, which may only be understood when scanned by a suitable scanner having a suitable decryption or decryption operation to decrypt or decrypt the fingerprint template in conjunction with the steganographic encryption employed to steganographically encrypt the fingerprint template to the government identification. Once decrypted, the fingerprint template may be compared to other fingerprint templates associated with the user to grant the user access to any aspect of the access application 116 and / or complete a transaction associated therewith.The steganographic image 307 may be created by a certification process at a facility, e.g., facility 146, as described herein, the server 120 may be notified of this certification (without necessarily requiring the image 117b to be uploaded to the server), and the use of the image 117b may be recognized as authentic and appropriate by an issuer associated with the server 120, such as when the authentication application 114 communicates that a template comparison has been successfully performed by the steganographic encoding application 117a, the management application 123 may approve one or more operations in connection with the access application 116 (if an online authentication protocol is used).
[0059] FIG. 4A illustrates a contactless card 101 that may comprise a payment card, such as a credit card, a debit card, and / or a gift card. As shown, the contactless card 101 may be issued by a service provider 405 that is displayed on the front or back of the card 101. In various embodiments, the contactless card 101 may comprise, but is not limited to, an identification card unrelated to a payment card. In various embodiments, the payment card may comprise a dual interface contactless payment card. The contactless card 101 may comprise a substrate 410 that may include a single layer or one or more laminated layers composed of plastic, metal, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyester, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In various embodiments, the contactless card 101 may have physical characteristics that conform to the ID-1 format of the ISO / IEC 7810 standard, or the contactless card 101 may otherwise conform to the ISO / IEC 14443 standard. However, it should be understood that contactless cards 101 according to the present disclosure may have different characteristics and the present disclosure does not require that contactless cards be implemented as payment cards.
[0060] The contactless card 101 may also include identification information 415 displayed on the front and / or back of the card, and a contact pad 420. The contact pad 420 may be configured to establish contact with other communication devices, such as the mobile device 110, a user device, a smartphone, a laptop, a desktop, or a tablet computer. The contactless card 101 may also include processing circuitry, an antenna, and other components not shown in FIG. 4A. These components may be located behind the contact pad 420 or elsewhere on the substrate 410. The contactless card 101 may also include a magnetic strip or tape that may be located on the back of the card (not shown in FIG. 4A). The contactless card 101 may include a display interface 416 capable of displaying a steganographic image 417. The display interface 416 may correspond to the display 141 shown in FIG. 1A. The steganographic image 417 may have a visible portion, e.g., a government identification, and an encoded portion, e.g., a fingerprint template of a user, which may only be understood when scanned by a suitable scanner having a decryption or decryption operation suitable for decrypting or decrypting the fingerprint template in conjunction with the steganographic encryption employed to steganographically encrypt the fingerprint template to the government identification. Once decrypted, the fingerprint template may be compared to other fingerprint templates associated with the user to grant the user access to any aspect of the access application 116 and / or complete a transaction associated therewith. The steganographic image 417 may be created by a certification process at a facility, e.g., facility 146, as described herein, the server 120 may be notified of this certification (without necessarily requiring the image 117b to be uploaded to the server), and the use of the image 117b may be recognized as authentic and appropriate by an issuer associated with the server 120, such as when the authentication application 114 communicates that a template comparison was successfully performed by the steganographic encoding application 117a, the management application 123 may approve one or more operations in connection with the access application 116 (if an online authentication protocol is used).
[0061] 4B, contact pad 420 of contactless card 101 may include processing circuitry 425 for storing and processing information, including a microprocessor 430 and memory 102. It will be understood that processing circuitry 425 may include additional components including processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware as necessary to perform the functions described herein.
[0062] The memory 102 may be a read-only memory, a write-once read-multiple memory, or a read / write memory, e.g., RAM, ROM, and EEPROM, and the contactless card 101 may include one or more of these memories. Read-only memory may be read-only or one-time programmable at the factory. One-time programming allows it to be written once and read many times. Write-once / read-multiple memory may be programmed at some point after the memory chip leaves the factory. Once programmed, the memory may not be rewritten, but it may be read many times. Read / write memory may be programmed and reprogrammed many times after leaving the factory. Read / write memory may be read many times after leaving the factory.
[0063] The memory 102 may be configured to store one or more applets 440, one or more counters 104, a customer identifier 107, and a virtual account number 108. The one or more applets 440 may comprise one or more software applications configured to run on one or more contactless cards, such as a Java card applet. However, it is understood that the applet 440 is not limited to a Java card applet, but may instead be any software application operable on a contactless card or other device having limited memory. The one or more counters 104 may comprise a numeric counter sufficient to store an integer number. The customer identifier 107 may comprise a unique alphanumeric identifier assigned to a user of the contactless card 101, the identifier may distinguish a user of the contactless card from other contactless card users. In various embodiments, the customer identifier 107 may identify both a customer and an account assigned to that customer, as well as a contactless card associated with the customer's account. As noted, the account number 108 may include thousands of disposable virtual account numbers associated with the contactless card 101. The applet 440 of the contactless card 101 may be configured to manage the account number 108. The memory 102 may be configured to include a steganographic encoding 117b that may be displayed, for example, as shown and described in FIG. 4A and that may be scanned and decoded by any suitable scanning device for any suitable purpose described herein.
[0064] Although the processor and memory elements of the foregoing exemplary embodiments are described with reference to contact pads, the present disclosure is not limited thereto, and it will be understood that these elements may be implemented outside of the pads 420, completely separate therefrom, or as additional elements in addition to the processor 430 and memory 102 elements located within the contact pads 420.
[0065] In various embodiments, the contactless card 101 may include one or more antennas 455. The one or more antennas 455 may be disposed within the contactless card 101 and around the processing circuit 425 of the contact pad 420. For example, the one or more antennas 455 may be integrated with the processing circuit 425, the one or more antennas 455 may be used with an external booster coil, or as another example, the one or more antennas 455 may be external to the contact pad 420 and the processing circuit 425.
[0066] In one embodiment, the coil of the contactless card 101 may function as the secondary of an air-core transformer. The terminal may communicate with the contactless card 101 by disconnecting the power or amplitude modulation. The contactless card 101 may infer data transmitted from the terminal using a gap in the power connection of the contactless card, which may be maintained functionally via one or more capacitors. The contactless card 101 may return communication by switching the load of the coil of the contactless card or load modulation. Load modulation may be detected at the coil of the terminal by interference. More generally, using the antenna 455, the processing circuitry 425, and / or the memory 102, the contactless card 101 provides a communication interface for communicating via NFC, Bluetooth, and / or Wi-Fi communications.
[0067] As described above, the contactless card 101 may be built on a software platform operable on a memory limited smart card or other device, such as a Java card, and one or more applications or applets may be securely executed. The applet 440 may be added to the contactless card to provide a one-time password (OTP) for multi-factor authentication (MFA) in various mobile application-based use cases. The applet 440 may be configured to respond to one or more requests, such as a near field wireless data exchange request, from a reader, such as a mobile NFC reader (e.g., the mobile device 110), and generate an NDEF message comprising the cryptographically secure OTP encoded as an NDEF text tag.
[0068] One example of an NDEFOTP is the NDEF Short Record Layout (SR=1). In such an example, one or more applets 440 may be configured to encode the OTP as a text tag of the well-known type of NDEF Type 4. In various embodiments, an NDEF message may comprise one or more records. The applet 440 may be configured to add one or more static tag records in addition to the OTP record.
[0069] In various embodiments, one or more applets 440 may be configured to emulate an RFID tag. The RFID tag may include one or more polymorphic tags. In various embodiments, each time the tag is read, different encrypted data is presented that may indicate the authenticity of the contactless card. Based on one or more applications, an NFC read of the 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.
[0070] In various embodiments, the contactless card 101 and the server 120 may include specific data so that the card may be properly identified. The contactless card 101 may include one or more unique identifiers (not shown). Each time a read operation is performed, the counter 104 may be configured to increment. In various embodiments, each time data from the contactless card 101 is read (e.g., by the mobile device 110), the counter 104 is sent to the server for validation to determine (as part of the validation) whether the counter values 104 are equal.
[0071] One or more counters 104 may be configured to prevent replay attacks. For example, if a cryptogram is obtained and replayed, the cryptogram is immediately rejected if the counter 104 is read, used, or otherwise passed on. If the counter 104 is not used, it may be replayed. In various embodiments, the counter incremented on the card is different from the counter incremented for the transaction. The contactless card 101 cannot determine the application transaction counter 104 because there is no communication between the applets 440 on the contactless card 101. In various embodiments, the contactless card 101 may include a first applet 440-1, which may be a transaction applet, and a second applet 440-2. Each applet 440-1 and 440-2 may include a respective counter 104.
[0072] In various embodiments, the counter 104 may become out of sync. In various embodiments, an accidental read that initiates a transaction, such as a read at an angle, may be considered, and the counter 104 may increment, but the application does not process the counter 104. In various embodiments, when the mobile device 110 wakes up, NFC may be enabled and the device 110 may be configured to read available tags, but no action is taken in response to the read.
[0073] To keep the counter 104 synchronized, an application may be executed, such as a background application that may be configured to detect when the mobile device 110 wakes up and synchronize with the server 120 indicating that the reading generated by the detection will next advance the counter 104. 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 104 may be configured to advance. However, if within a different threshold number, e.g., within 10 or 1000, a request to perform a re-synchronization may be processed via one or more applications requesting that the user make one or more taps, gestures, or other indications via the user's device. If the counter 104 increments in the proper order, it is possible to know that the user is doing so.
[0074] The key diversification technique described herein with reference to counter 104, master key 105, and diversified key 106 is one example of an encrypting and / or decrypting key diversification technique. This exemplary key diversification technique should not be considered as limiting the disclosure, as the disclosure is applicable to other types of key diversification techniques as well.
[0075] During the contactless card 101 creation process, two encryption keys may be uniquely assigned to each card. The encryption keys may comprise symmetric keys that may be used to both encrypt and decrypt data. The Triple DES (3DES) algorithm may be used in EMV and is implemented by the contactless card 101 hardware. A key diversification process may be used to derive one or more keys from a master key based on uniquely identifiable information of each entity that requires a key.
[0076] In various embodiments, to overcome the deficiencies of the 3DES algorithm, which is susceptible to vulnerabilities, a session key (such as a unique key per session) may be derived, but instead of using a master key, a unique key and a counter derived from the card may be used as diversification data. For example, a different key may be used to create a message authentication code (MAC) and perform encryption each time the contactless card 101 is used during operation. This results in three layers of encryption. The session key may be generated by one or more applets and derived using the application transaction counter with one or more algorithms (defined in EMV 4.3 Book 2 A1.3.1 Common Session Key Derivation).
[0077] Additionally, the increments for each card may be unique and assigned by personalization or algorithmically assigned by some identifying information. For example, odd numbered cards may increment by 2 and even numbered cards may increment by 5. In various embodiments, the increments may also vary on successive reads, so that one card may sequentially increment by 1, 3, 5, 2, 2, ... repeatedly. The specific sequence or algorithmic sequence may be defined at the time of personalization or from one or more processes derived from a unique identifier. This may make it difficult for a replay attacker to generalize from a small number of card instances.
[0078] The authentication message may be delivered as the contents of a textual NDEF record in hexadecimal ASCII format. In another example, the NDEF record may be encoded in hexadecimal format.
[0079] 5 illustrates an embodiment of a logic flow 500. The logic flow 500 may represent some or all of the operations performed by one or more embodiments described herein. For example, the logic flow 500 may include some or all of the operations for creating a steganographically encoded image of a user's identity having a fingerprint template of the user thereon. In this context, the embodiments are not limited.
[0080] As shown, logic flow 500 begins at block 505, where one or more of any suitable components, operations, or systems or units may be used to create steganographically encoded image 117b. For example, steganographic application 117a may create image 117b in combination with scanner 138. Scanner 138 may perform a government identification (passport or driver's license) and user identification, such as the user's fingerprint by scanning the user's finger. The steganographic application may apply any suitable steganographic operation as discussed herein, or may be suitable to encode a fingerprint template of the user onto the image of the government identification. The image of the government identification that is part of the overall steganographic image 117b may be verified and verified at a facility associated with the issuer, as discussed herein, and the steganographic encoding may be performed at a facility associated with the issuer using a verification device at the facility. The verification device may be the user's mobile device 110 including a steganographic application 117a working with or otherwise associated with the issuer facility, or other computing device with appropriate steganographic encoding capabilities located or otherwise associated with the issuer facility, and may include transmitting the government identification and a fingerprint or fingerprint template to a server 120 associated with the issuer, which may be configured to extract the fingerprint template from the user's scanned fingerprint, steganographically encode the fingerprint template onto an image of the government identification, and then store the steganographic image 117b in the mobile device 110, the contactless card 101, and / or in memory of the server 120 for subsequent use in the verification operation. In various embodiments, including but not limited to situations where privacy is a concern, the attestation and steganographic encoding may be performed using a local device, such as the mobile device 110, without transmitting the steganographic image 117b to the server 120.In various embodiments, if the server 120 does not have a stored version of the steganographic image 117b, an application associated with the device containing the steganographic image, e.g., the authentication application 114 of the mobile device 110, may notify an appropriate application 123 of the server 120 that the authentication and steganographic encoding has occurred so that the server 120 may authorize the use of the steganographic comparison to authorize access to one or more features associated with the access application 116 and / or to complete a transaction associated therewith. At block 510, the steganographically encoded image 117b may be used by itself or in conjunction with other security features (as discussed herein or in other suitable manners) to authenticate the user and provide access to one or more features of the access application 116, including decoding the fingerprint template associated with the image 117b and comparing it to the derived fingerprint template of a subsequent fingerprint scan associated with the user.
[0081] 6 illustrates an embodiment of a logic flow 600. The logic flow 600 may represent some or all of the operations performed by one or more embodiments described herein. For example, the logic flow 600 may include some or all of the operations of authenticating a user's identity, creating a steganographically encoded image of the user's identity having the user's fingerprint template thereon, authenticating the authenticity of the steganographically encoded image 117b, and / or utilizing the steganographically encoded image 117b to provide access to one or more features of the access application 116 and / or authorize a transaction associated therewith. In this context, the embodiments are not limited.
[0082] As shown, logic flow 600 begins at block 610 where at least one verification device may verify and certify the authenticity of an identification associated with a user. In various embodiments, the verification device may be one or more devices associated with one or both of the user and the issuer, such as mobile device 110 and server 120, while in other embodiments, all of the verification devices may be devices located at a facility 146 associated with the issuer. At the facility 146 associated with the issuer, the user may present a government identification to an associate at the facility 146. The associate 147 may communicate with or utilize a device associated with the issuer, such as server 120, to verify and certify the authenticity of the image. For example, a computing device at the facility may communicate with server 120 using an appropriate application of the server, such as verification application 126. The verification application 126 may access a public records facility and transmit information associated with the user, including an official copy of the government identification from the public records, and the local computing device may compare the official copy to the presented copy to determine that it is authentic. In various embodiments, the account data 124 includes a public records database, while in other embodiments, a different database (not shown) is used. Alternatively, a verification application that is part of the other applications 115 or other local device specific to the facility may perform the scan using an appropriate scanning device, e.g., an identification scanning device, that verifies the authenticity of the government identification for the presented identification by scanning and receiving verification from an appropriate government identification, without utilizing the server 120 to perform the attestation. In various embodiments, even if the server 120 is not used to perform the attestation, an appropriate application, e.g., the authentication application 114, may communicate to the server 120 that the attestation was successful. Once the government identification is verified, a scan of an image of the government identification may be performed at the facility 146 using an appropriate scanner or image processing device.
[0083] At block 615, utilizing any of the steganographic techniques discussed herein (or otherwise suitable), an associate at the facility 146 may steganographically encode the fingerprint template onto an image of the government identification, including utilizing the fingerprint scanner 138 to obtain a fingerprint scan of the user, derive a fingerprint template therefrom, and then utilizing the steganographic application 117a to perform steganographic encoding of the template on the government identification to generate a steganographically encoded image 117b. At block 620, the steganographically encoded image 117b may be transmitted to or stored in any suitable memory of any suitable device, including the contactless card 101, the mobile device 110, and / or the server 120, for use in an authorization operation to access one or more functions associated with the access application 116 and / or to complete a payment transaction related thereto. For example, decoding of the fingerprint template may be performed by the fingerprint scanner 138 and / or the steganography application 117a or any other suitable scanner, device, or application and compared to the extracted fingerprint template associated with a subsequent fingerprint obtained from another scan of the user's finger, the other scan being initiated or requested when the authentication application 114 determines that one or more features of the access application 116 are being attempted to be accessed by the user.
[0084] 7A illustrates an embodiment of a logic flow 700A. The logic flow 700 may represent some or all of the operations performed by one or more embodiments described herein. For example, the logic flow 700A may include some or all of the operations for verifying or authenticating a user utilizing online or offline authentication techniques and steganographically encoded images. In this context, the embodiments are not limited.
[0085] As shown, logic flow 700A begins at block 705 where at least one of authentication application 114, OS 112, management application 123, and / or any other suitable application may initiate a transaction to verify the identity of the user and may utilize steganographic image 117b to obtain access to one or more features of access application 116 and / or complete a transaction associated therewith. In various embodiments, the verification may be initiated by tapping contactless card 101 on mobile device 110. In various embodiments, access application 116 provides a prompt to enter user credentials for comparison for a first and / or second level of information access associated with access application 116 as a prerequisite for receiving a tap prompt, or immediately after the tap is performed, but prior to additional online verification operations, the nature of the first level features being described elsewhere herein. In various embodiments, the user credentials are associated with a user profile and entered into an interface provided by mobile device 110, where, as previously described, the first application user credentials may include biometric data, established gestures associated with user recognition, a username and password combination, etc. The first application user credentials may be sent by the authentication application 114 to the management application 123 of the server 120, where the first application user credentials are compared to the stored second credentials. If the comparison results in a match between the first and second credentials, the management application 123 may send an indication of the match to the authentication application 114.
[0086] Regardless of whether access to various levels of information is granted as a result of the user credential comparison and / or whether there is a credential comparison server as a prerequisite for completing the online and / or offline authentication, at block 710, at least one online and / or offline verification operation utilizing the contactless card 101 described herein, including but not limited to at least one operation described with respect to Figures 7B and 7C, is performed to gain access to the steganographic image 117b. For example, the authentication application 114 may initiate an authentication protocol to access one or more functions with respect to and / or complete a transaction associated with the access application 116 based on a first tap of the contactless card 101 on the mobile device. At block 715, in response to successful completion of the communication and authentication protocol associated with the contactless card 101, the verification application may authorize the extraction (or use) of the steganographic image 117b from the memory of the contactless card 101 and / or the mobile device 110 for comparison to the user's other generated fingerprint templates (e.g., obtained using the fingerprint scanner 138 and / or any other suitable fingerprint scanner, including those associated with the retailer or service provider 148) to access one or more features of the access application 116 and / or complete transactions related thereto. In various embodiments, the subsequent fingerprint scan and fingerprint comparison occurs after a second tap of the contactless card 101 on the mobile device 110. In various embodiments, successful completion of the authentication protocol grants a second level of access to information and / or functionality of the access application 116, and successful comparison of the steganographic image 117b will grant access to a third level of information or functionality, e.g., to perform a payment transaction above a certain monetary threshold.
[0087] 7B illustrates an embodiment of a logic flow 700B. The logic flow 700B may represent some or all of the operations performed by one or more embodiments described herein. For example, the logic flow 700B may include some or all of the operations for verifying or authenticating a user utilizing an offline authentication technique, and for utilizing a steganographically encoded image associated with the user after (or before) successfully completing the offline authentication technique. In this context, the embodiments are not limited.
[0088] As shown, logic flow 700B begins at block 725, where an application, e.g., authentication application 114 of mobile device 110, communicates with contactless card 101. In various embodiments, authentication application 114 receives from a user first application user credentials associated with a user profile. As described above, the user may provide the first application user credentials after receiving a prompt from authentication application 114 and / or may provide user credentials after the user taps contactless card 101 on mobile device 110. In various embodiments, as described above, the first application user credentials may include biometric data, an established gesture associated with user recognition, a username and password combination, etc. In various embodiments, processor 119 compares the first application user credentials with stored second application user credentials. The stored second application user credentials may be associated with the user's identity. The user's identity may include a personal identification number (PIN), the user's name, address, date of birth, etc. In various embodiments, after finding a first match, the authentication application 114 allows access to a first level of user account options including view accounts, view recent transactions, etc. In various embodiments, the user credential comparison is skipped entirely. At block 730, the authentication application 114 receives the public key of the card's public / private key pair from the contactless card 101.
[0089] At block 735, the authentication application 114 instructs the contactless card 101 to generate a digital signature by using the private key of the card's key pair. The contactless card 101 generates the digital signature, the authentication application 114 receives the digital signature from the contactless card 101 at block 740, and at block 745 the mobile device may verify the digital signature (by operation of the processor 119 and / or with the aid of an application such as the authentication application 114) using the public key of the card's key pair.
[0090] Once the offline verification involving digital signature verification is complete, a second level of information or functionality may be granted for the access application 116 at block 745. In various embodiments, the flow 700B may proceed directly to block 770 without performing the operations associated with block 755, and access to the first level of information or functionality and / or the second level of information and functionality is granted only if the steganographic image 117b is utilized to perform authentication in any manner as disclosed herein. In various embodiments, the flow may skip block 755, and access to the first level and / or second level of operations may be granted based on completion of the verification (or upon a credential comparison match as described herein for first level access) without utilizing the steganographic image 117b.
[0091] In various embodiments, the steganographic image 117b may be used to authorize access to the third level of information associated with the access application 116 and / or complete a transaction associated therewith. For example, as shown with respect to flow 700B, the authentication application 114 may determine whether the functionality being accessed or the transaction being performed with respect to the access application has a security concern, such as involving a payment transaction above a certain threshold. If the authentication application 114 determines that additional security measures are required, the flow proceeds to block 755. Any suitable component associated with FIG. 1 and / or other suitable component, such as a scanning device associated with a merchant, may scan the user's fingerprint to obtain a fingerprint image of the user and obtain a fingerprint template from the fingerprint image. At block 760, any suitable component, such as the steganographic application 117a, may compare the extracted fingerprint template to the fingerprint template portion of the steganographic image 117b for a match, and upon determining a successful match, access to the third level of information and / or completion of a transaction with a high threshold of concern, e.g., a transaction above a certain monetary threshold, may be completed or allowed. In various embodiments, the comparison may be performed at the server 120, for example, the fingerprint templates may be compared for a match by the management application 123, which upon confirmation of a match may send a confirmation to the authentication application 114 to authorize associated access to functionality associated with the application 116 and / or completion of a transaction associated therewith.
[0092] In various embodiments, flow 700B may include a prerequisite for performing operations 725-745 in that operations 755 and 760 are performed first, the fingerprint templates may be compared by any local appropriate component, including but not limited to the fingerprint scanner 138, the steganography application 117a, and / or an appropriate third party component (e.g., a scanner associated with the service or retail provider 148), and / or the fingerprint templates may be sent to the server 120 and the management application may compare them for a match. If a match is found, the match is communicated to the authentication application 114. In various embodiments, this confirmation may result in access to a second level of information associated with the access application 116, and the offline protocols associated with 725-745 may be completed to access a third level of information and / or to complete the transaction of increased security concern.
[0093] 7C illustrates an embodiment of logic flow 700C. Logic flow 700C may represent some or all of the operations performed by one or more embodiments described herein. For example, logic flow 700C may include some or all of the operations for verifying or authenticating a user utilizing online authentication techniques and a steganographically encoded image associated with the user. In this context, the embodiments are not limited.
[0094] As shown, logic flow 700C begins at block 765 where at least one of authentication application 114, OS 112, management application 123, and / or any other suitable application may initiate a transaction to verify the identity of the user and may utilize steganographically encoded image 117b to access functionality associated with access application 116. In various embodiments, the verification may be initiated by tapping contactless card 101 on mobile device 110. In various embodiments, access application 116 provides a prerequisite for receiving a tap prompt, or a prompt to enter user credentials for comparison for first and / or second level information access associated with access application 116 immediately after the tap is performed, but prior to additional online verification operations. The nature of the first level functionality is described elsewhere herein. In various embodiments, the user credentials are associated with a user profile and entered into an interface provided by mobile device 110. As previously discussed, the first application user credentials may include biometric data, an established gesture associated with user recognition, a username and password combination, and the like. The first application user credentials may be sent by the authentication application 114 to the management application 123 of the server 120, where the first application user credentials are compared to the stored second credentials.
[0095] According to various embodiments, communication between the mobile device 110 and the contactless card 101 is initiated, the communication utilizing the card reader 118, the communication being based on an NFC protocol. In various embodiments, the communication is conditional on a first level comparison resulting in a match, and in various embodiments, instead of sending the first application credential for comparison at the server 120, a comparison is made between the mobile device 110 and the contactless card 101. The stored second credential is stored in the memory 102 of the contactless card. In various embodiments, the comparison on the user credential is omitted, and a tap of the contactless card 101 on the mobile device 110 initiates a prompt to select which application requires authentication, e.g., the access application 116, and the NFC communication between the contactless card 101 and the mobile device 110 initiates an online verification or authentication of the user using a payment protocol consistent with the EMV standard, but for purposes including verification or authentication for purposes other than simply completing a sale or purchase. In various embodiments, as described above, a user taps contactless card 101 to mobile device 110, causing contactless card 101 to generate and transmit encrypted data (e.g., encrypted customer ID 109). Contactless card 101 may increment counter value 104 in memory 102 in response to receiving the instruction to generate encrypted data.
[0096] In various embodiments, at block 767, the contactless card 101 uses the counter value 104 and the master key 105 in the memory 102 and an encryption algorithm to generate a diversified key 106. The contactless card 101 may use the diversified key 106 and the encryption algorithm to encrypt data (e.g., the customer identifier 107) to generate encrypted data (e.g., the encrypted customer ID 109).
[0097] At block 770, the contactless card 101 may send the encrypted data to the account application 113 of the mobile device 110, for example, using NFC. In at least one embodiment, the contactless card 101 further includes an indication of the counter value 104 along with the encrypted data. At block 772, the account application 113 or the authentication application 114 of the mobile device 110 may send the data received from the contactless card 101 to the management application 123 of the server 120. At block 775, the management application 123 of the server 120 may generate the diversified key 106 using the master key 105 and the counter value 104 as inputs to an encryption algorithm. In one embodiment, the management application 123 uses the counter value 104 provided by the contactless card 101. In other embodiments, the management application 123 increments the counter value 104 in the memory 122 to synchronize the state of the counter value 104 in the memory 122 with the counter value 104 in the memory 102 of the contactless card 101.
[0098] At block 777, the management application 123 uses the diversified key 106 and the encryption algorithm to decrypt the encrypted data received from the contactless card 101 via the mobile device 110. In doing so, at least the customer identifier 107 may be obtained. By obtaining the customer identifier 107, the management application 123 may verify the data received from the contactless card 101 at block 780. For example, the management application 123 may compare the customer identifier 107 with the customer identifier of an associated account in the account data 124 and verify the data based on a match.
[0099] Upon completion of the online verification, a second level of information or functionality may be granted with respect to the access application 116. In various embodiments, the flow 700C may proceed directly to block 790 without performing the operations associated with block 782, and access to the first level of information or functionality and / or the second level of information and functionality is granted only if the steganographic image 117b is utilized to perform authentication in any manner as disclosed herein. In various embodiments, the flow may skip block 790, and access to the first level and / or second level of operations may be granted based on completion of the verification (or upon a match of the credential comparison as described herein for first level access) without utilizing the steganographic image 117b.
[0100] In various embodiments, the steganographic image 117b may be used to authorize access to a third level of information associated with the access application 116 and / or complete a transaction associated therewith. For example, as shown with respect to flow 700C, the authentication application 114 or the management application 123 may determine whether the functionality being accessed or the transaction being performed with respect to the access application has security concerns, such as involving a payment transaction that exceeds a certain threshold. If the authentication application 114 or the management application 123 determines that additional security measures are required, the flow proceeds to block 782. Any suitable component associated with FIG. 1 and / or other suitable component, such as a scanning device associated with the merchant, may scan the user's fingerprint to obtain a fingerprint image of the user and obtain a fingerprint template from the fingerprint image. At block 787, any suitable component, such as the steganographic application 117a, may compare and match the extracted fingerprint template with the fingerprint template portion of the steganographic image 117b and, upon determining a successful match, may authorize access to a third level of information and / or completion of transactions having a higher threshold of concern, e.g., transactions above a certain monetary threshold may be completed or allowed. In various embodiments, the comparison may be performed at the server 120, e.g., the fingerprint template may be compared for a match by the management application 123, and, upon confirming a match, may send a confirmation to the authentication application 114 to authorize associated access to functionality associated with the application 116 and / or completion of transactions associated therewith. In various embodiments, the steganographic image 117b may be included in the memory of the server 120 based on a previous sending operation.For example, once the steganographic encoding has been performed on the server and / or the steganographic encoding for the image 117b has been performed locally by a local application, e.g., a steganographic application 117a associated with the mobile device 110, the image 117b may be transmitted to the server 120 by any suitable component or application of the local device, e.g., an authentication application 114.
[0101] In various embodiments, flow 700C may include a prerequisite for performing operations 765-780 in that operations 784 and 787 are performed first, the fingerprint templates may be compared by any local appropriate component, including but not limited to the fingerprint scanner 138, the steganography application 117a, and / or an appropriate third party component (e.g., a scanner associated with the service or retail provider 148), and / or the fingerprint templates may be sent to the server 120, where the management application compares them for a match. If a match is found, the match is communicated to the management application 123. In various embodiments, this confirmation may result in access to a second level of information associated with the access application 116, and the online protocols associated with 765-780 may be completed to access a third level of information and / or complete the transaction for which security concerns have been raised.
[0102] In various embodiments, the contactless card 101 may be tapped to a device, such as one or more computer kiosks or terminals, to verify identity to receive a transaction item in response to a purchase, such as a coffee. Using the contactless card 101 may establish a secure method of proving identity in a loyalty program. For example, securely proving identity to obtain rewards, coupons, offers, etc., or to receive benefits is established in a manner different than simply scanning a bar card. For example, an encrypted transaction may occur between the contactless card 101 and a device, which may be configured to process one or more tap gestures. As described above, one or more applications may be configured to verify the user's identity and then have the user act or respond, for example, via one or more tap gestures. In various embodiments, data, such as bonus points, loyalty points, reward points, health care information, etc., may be written back to the contactless card.
[0103] In various embodiments, the contactless card 101 may be tapped to a device such as the mobile device 110. As described above, the user's identity may be verified by one or more applications, which may then grant the user a desired benefit based on the verification of identity.
[0104] In various embodiments, the exemplary authentication communication protocol may mimic, with some modifications, the EMV standard offline dynamic data authentication protocol commonly performed between transaction cards and point-of-sale devices. For example, the exemplary authentication protocol may not be used to complete a payment transaction with the card issuer / payment processor itself, and therefore some data values are unnecessary and may perform authentication without requiring a real-time online connection to the card issuer / payment processor. As known in the art, a point-of-sale (POS) system submits a transaction to a card issuer, including a transaction value. Whether the issuer approves or rejects the transaction may be based on whether the card issuer recognizes the transaction value. On the other hand, in certain embodiments of the present disclosure, transactions originating from a mobile device lack a transaction value associated with the POS system. Thus, in various embodiments, a dummy transaction value (i.e., a value that is recognizable to the card issuer and sufficient to allow activation to occur) may be passed as part of the exemplary authentication communication protocol. POS-based transactions may also reject transactions based on the number of transaction attempts (e.g., a transaction counter). A number of attempts exceeding a buffer value may result in a soft decline. A soft decline requires further validation before accepting the transaction. In some implementations, the transaction counter buffer value may be altered to avoid attrition of legitimate transactions.
[0105] In various embodiments, the contactless card 101 may selectively communicate information depending on the recipient device. When tapped, the contactless card 101 may recognize the device to which the tap is directed, and based on this recognition, the contactless card may provide the appropriate data to that device. This advantageously allows the contactless card to transmit only the information necessary to complete an immediate action or transaction, such as a payment or card authentication. Limiting the transmission of data and avoiding the transmission of unnecessary data may improve both efficiency and data security. The recognition and selective communication of information may be applied to a variety of scenarios, including card activation, balance transfers, account access attempts, commercial transactions, and incremental fraud reduction.
[0106] When a tap of the contactless card 101 is directed at a device running Apple's iOS® operating system, such as an iPhone®, iPod®, or iPad®, the contactless card may recognize the iOS® operating system and transmit the appropriate data to communicate with the device. For example, the contactless card 101 may provide the encrypted identity information necessary to authenticate the card using, for example, an NDEF tag via NFC. Similarly, when a tap of the contactless card is directed at a device running the Android® operating system, such as an Android® smartphone or tablet, the contactless card may recognize the Android® operating system and transmit the appropriate data to communicate with the device (such as the encrypted identity information necessary for authentication according to the methods described herein).
[0107] As another example, a contactless card tap may be directed to a POS device, including but not limited to a kiosk, checkout register, payment station, or other terminal. Upon performing the tap, the contactless card 101 may recognize the POS device and transmit only the information necessary for the action or transaction. For example, upon recognizing the POS device used to complete a commercial transaction, the contactless card 101 may communicate the payment information necessary to complete the transaction under the EMV standard.
[0108] In various embodiments, a POS device participating in a transaction may request or specify additional information provided by the contactless card, such as device-specific information, location-specific information, and transaction-specific information. For example, when a POS device receives a data communication from a contactless card, the POS device may request the additional information necessary to recognize the contactless card and complete the action or transaction.
[0109] In various embodiments, the POS device may be affiliated with an authorized merchant or other entity familiar with particular contactless cards or accustomed to performing particular contactless card transactions, although it will be understood that such an affiliation is not required for the performance of the described methods.
[0110] In various embodiments, such as at a shopping store, grocery store, convenience store, etc., the contactless card 101 may be tapped to a mobile device without having to open an application to indicate a desire or intent to use one or more reward points, loyalty points, coupons, offers, etc. to cover one or more purchases, thus providing the intent behind the purchase.
[0111] In various embodiments, one or more applications may be configured to determine that they were launched via one or more tap gestures on the contactless card 101, such as that the launch occurred at 3:51 p.m. and that the transaction was processed or made at 3:56 p.m., in order to verify the user's identity.
[0112] In various embodiments, one or more applications may be configured to control one or more actions in response to one or more tap gestures. For example, the one or more actions may comprise collecting rewards, collecting points, determining the most important purchases, determining the least expensive purchases, and / or reconfiguring to other actions in real time.
[0113] In various embodiments, data may be collected regarding the tapping action as a biometric / gesture authentication. For example, a cryptographically secure and intercept-resistant unique identifier may be transmitted to one or more backend services. The unique identifier may be configured to retrieve secondary information about the individual. The secondary information may comprise personally identifiable information about the user. In various embodiments, the secondary information may be stored within a contactless card.
[0114] In various embodiments, the device may include an application to split a bill or check a payment among multiple individuals. For example, each individual may, but need not, own a contactless card and be a customer of the same issuing financial institution. Each of these individuals may receive a push notification on the device via the application to split the purchase. Rather than accepting only one card tap to indicate payment, other contactless cards may be used. In various embodiments, individuals with different financial institutions may own contactless cards 101 to provide information to initiate one or more payment requests from the card-tapping individual.
[0115] In various embodiments, the disclosure refers to tapping a contactless card, however, it will be understood that the disclosure is not limited to tapping and includes other gestures (e.g., waving or other movements of the card).
[0116] FIG. 8 illustrates an embodiment of an exemplary computing architecture 800 comprising a computing system 802 that may be suitable for implementing various embodiments as described above. In various embodiments, the computing architecture 800 may comprise or be implemented as part of an electronic device. In various embodiments, the computing architecture 800 may represent, for example, a system implementing one or more components of the system 100. In various embodiments, the computing system 802 may represent, for example, the mobile device 110 and the server 120 of the system 100. The embodiments are not limited in this context. More generally, the computing architecture 800 is configured to implement all logic, applications, systems, methods, apparatus, and functions described herein with reference to FIGS. 1-7C.
[0117] The terms "system" and "component" and "module" as used in this application are intended to refer to any computer-related entity, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing architecture 800. 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 (of optical and / or magnetic storage media), an object, an executable, a thread of execution, a program, and / or a computer. As an example, both an application running on a server and the server may be a component. One or more components may reside within a process and / or thread of execution, and a component may be localized on one computer and / or distributed among two or more computers. Furthermore, components may be communicatively coupled to one another by various types of communication media to coordinate operations. Coordination may include unidirectional or bidirectional exchange of information. For example, components may communicate information in the form of signals communicated over the communication media. The information may be embodied as signals assigned to various signal lines. In such an assignment, each message is a signal. However, further embodiments may use data messages as an alternative. Such data messages may be transmitted over a variety of connections, examples of which include parallel interfaces, serial interfaces, and bus interfaces.
[0118] Computing system 802 includes various typical computing elements, such as one or more processors, multi-core processors, co-processors, processing circuits, 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 802.
[0119] As shown in Figure 8, computing system 802 includes a processor 804, a system memory 806, and a system bus 808. Processor 804 may be any of a variety of commercially available computer processors or computer process circuits, including, but not limited to, AMD Athlon, Duron, and Opteron processors, ARM applications, 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 used as processor 804. The processor 804 may be configured by associated memory instructions contained in the system memory 806 such that, when the instructions are executed on the processor (e.g., processor circuitry) 804, the processor may perform one or more operations associated with any one of FIGS. 5-7B and / or any other operations or techniques disclosed herein.
[0120] The system bus 808 provides an interface from the system memory 806 to system components including, but not limited to, the processor 804. The system bus 808 may be any of several types of bus structures 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 the system bus 808 through a slot architecture. Examples of slot architectures include, but are not limited to, Accelerated Graphics Port (AGP), CardBus, (Enhanced) Industry Standard Architecture ((E)ISA), MicroChannel Architecture (MCA), NuBus, Peripheral Component Interconnect (Enhanced) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and the like.
[0121] The system memory 806 may include various types of computer-readable storage media in the form of one or more high-speed memory units, such as read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (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, arrays of devices such as redundant array of independent disks (RAID) drives, solid-state memory devices (e.g., USB memory, solid-state drive (SSD)), and other types of storage media suitable for storing information. In the illustrated embodiment shown in FIG. 8, the system memory 806 may include non-volatile memory 810 and / or volatile memory 812. The non-volatile memory 810 may store a basic input / output system (BIOS).
[0122] The computing system 802 may include various types of computer-readable storage media in the form of one or more low-speed memory units, including an internal (or external) hard disk drive (HDD) 814, a magnetic floppy disk drive (FDD) 816 that reads from or writes to a removable magnetic disk 818, and an optical disk drive 820 that reads from or writes to a removable optical disk 822 (e.g., a CD-ROM or DVD). The HDD 814, FDD 816, and optical disk drive 820 may be connected to the system bus 808 by a HDD interface 824, a FDD interface 826, and an optical drive interface 828, respectively. The HDD interface 824 for external drive implementations may include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. The computing system 802 is generally configured to implement all of the logic, systems, methods, apparatus, and functions described herein with reference to FIGS. 1-7.
[0123] The drives and associated computer-readable media provide volatile and / or nonvolatile storage of data, data structures, computer-executable instructions, and the like. For example, a number of program modules may be stored on the drives and memory units 810, 812, including an operating system 830, one or more application programs 832, other program modules 834, and program data 836. In various embodiments, the one or more application programs 832, other program modules 834, and program data 836 may include, for example, various applications and / or components of the system 100, such as the operating system 112, account application 113, authentication application 114, other applications 115, access application 116, and management application 123.
[0124] A user may enter commands and information into the computing system 802 through one or more wired / wireless input devices, for example, a keyboard 838 and a pointing device such as a mouse 840. 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, grab, graphic tablet, joystick, keyboard, retina reader, touch screen (e.g., capacitive, resistive, etc.), track ball, track pad, sensor, stylus, etc. These and other input devices are often connected to the processor 804 through an input device interface 842 coupled to the system bus 808, but may 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.
[0125] A monitor 844 or other type of display device is also connected to the system bus 808 via an interface, such as a video adapter 846. The monitor 844 can be internal or external to the computing system 802. In addition to the monitor 844, computers typically include other peripheral output devices, such as speakers, printers, etc.
[0126] The computing system 802 may operate in a networked environment using logical connections via wired and / or wireless communications to one or more remote computers, such as a remote computer 848. The remote computer 848 may be a workstation, a server computer, a router, a personal computer, a portable computer, a microprocessor-based entertainment device, a peer device, or other common network node, and typically includes many or all of the elements described in connection with the computing system 802, although for simplicity, only a memory / storage device 850 is shown. The logical connections shown include wired / wireless connections to a local area network (LAN) 852 and / or larger networks, e.g., a wide area network (WAN) 854. Such LAN and WAN networking environments are common in offices and businesses, facilitating enterprise-wide computer networks, such as an intranet. All of these may connect to a global communications network, e.g., the Internet. In an embodiment, the network 130 of FIG. 1 is one or more of the LAN 852 and the WAN 854.
[0127] When used in a LAN networking environment, the computing system 802 is connected to the LAN 852 via a wired and / or wireless communication network interface or adapter 856. The adapter 856 may facilitate wired and / or wireless communication to the LAN 852, which may include a wireless access point disposed thereon for communicating with the wireless functionality of the adapter 856.
[0128] When used in a WAN networking environment, the computing system 802 may include a modem 858 or have other means for establishing communications over the WAN 854, such as connected to a communications server on the WAN 854 or via the Internet. The modem 858 may be internal or external, a wired and / or wireless device, and connects to the system bus 808 via the input device interface 842. In a networked environment, program modules depicted relative to the computing system 802, or portions thereof, may be stored in the remote memory / storage device 850. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
[0129] The computing system 802 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., IEEE 802.16 wireless modulation technology). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, Bluetooth wireless technologies, and the like. Thus, communication can be a predefined structure, as with traditional networks, or simply ad-hoc communication between at least two devices. Wi-Fi networks provide secure, reliable, and fast wireless connectivity using radio technologies called IEEE 802.11x (a, b, g, n, etc.). 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).
[0130] Various embodiments 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 component, a program, an application, a computer program, an application program, a system program, a machine program, an operating system software, a middleware, a 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, a computing code, a computer code, a code segment, a computer code segment, a word, a value, a symbol, or any combination thereof. The decision 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 levels, thermal tolerance, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.
[0131] At least one or more aspects of the various embodiments may be implemented by representative instructions stored on a machine-readable medium that represent various logic in a processor, and that, when read by a machine, causes the machine to manufacture logic that performs the techniques described herein. Such representations, known as "IP cores," are stored on tangible machine-readable media and provided to various customers or manufacturing facilities for loading into manufacturing machines that create the logic or processors. The various embodiments may be implemented using a machine-readable medium or article that may store, for example, instructions or sets of instructions that, when executed by the machine, cause the machine to perform methods and / or operations in accordance with the embodiments. Such machines 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 article, storage medium and / or storage unit, such as memory, removable or non-removable media, erasable or non-erasable media, writable or rewritable media, digital or analog media, hard disk, floppy disk, compact disk read only memory (CD-ROM), compact disk recordable (CD-R), compact disk rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various digital versatile disks (DVDs), tapes, cassettes, etc. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, etc., and may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language.
[0132] The foregoing description of exemplary embodiments has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit 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 by the appended claims. Future 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 demonstrated herein.
Claims
1. an application executing on a processor of a client device communicating with the contactless card using Near Field Communication (NFC) performing at least one verification operation; receiving, by the client device, a steganographic image from the contactless card in response to performing the at least one verification operation, the steganographic image including an image of a government issued identification steganographically encoded using a fingerprint template; authenticating, by the application, a user associated with the client device based on the steganographic image; Including, The authenticating step comprises: decrypting the fingerprint template from an image of the government issued identification contained in the steganographic image; receiving a fingerprint scan of a user's finger from a scanning device; extracting a scanned fingerprint template from the fingerprint scan; comparing the scanned fingerprint template with the decoded fingerprint template for a match; Including, performing the at least one verification operation the application receiving from the contactless card a public key of the contactless card's key pair and a user identification, the user identification including the steganographic image; the application directing generation of a digital signature by the contactless card using a private key of the contactless card's key pair; receiving the digital signature from the contactless card; verifying the digital signature using the public key; Including, method.
2. the application creating the steganographic image based on an attestation of the image of the government-issued identification, the attestation verifying that the image of the government-issued identification is authentic; The method of claim 1 further comprising:
3. The method comprises: the application comparing first application user credentials received from the user with second application user credentials stored in a memory of the client device, the second application user credentials being associated with an identity of the user, and performing the at least one verification operation in response to finding a match between the first application user credentials and the second application user credentials; The method of claim 1 further comprising:
4. performing the at least one verification operation determining whether a transaction associated with an NFC communication with the transaction device exceeds a threshold amount; performing additional security verification measures if the transaction exceeds the monetary threshold; and if the transaction does not exceed the monetary threshold, receiving a message that a user has been authenticated at the transaction device; The method of claim 1 further comprising:
5. Implementing the additional security verification measures includes: scanning a finger of a user associated with the fingerprint template using a scanning device to extract a scanned fingerprint template from the user; sending the scanned fingerprint template and the decoded fingerprint template to a server; at the server, comparing the scanned fingerprint template with the decrypted fingerprint template for a match; receiving, at the transaction device, instructions from the server to confirm the match; The method of claim 4 , comprising:
6. performing the at least one verification operation determining, by the application, that a user has initiated a transaction with a transaction device to identify the user; the application receiving encrypted data from the contactless card, the encrypted data being generated based on an encryption algorithm and a diversified key, the diversified key being stored in a memory of the contactless card and generated based on a master key and a counter value stored in the memory of the contactless card; the application transmitting the encrypted data to a server; the application receiving validation of the encrypted data from the server, the server decrypting the encrypted data based on the encryption algorithm and the diversified key stored in the memory of the server and validating the encrypted data, the diversified key stored in the memory of the server being generated based on a master key and a counter value stored in the memory of the server; receiving the steganographic image from the server by the application; The method of claim 1 , comprising:
7. An apparatus comprising: A processor circuit; and a memory storing instructions that, when executed by the processor circuit, cause the processor circuit to: an application running on the processor circuit communicating with the contactless card using Near Field Communication (NFC) performing at least one verification operation; In response to performing the at least one verification operation, the application receives from the contactless card a steganographic image for authenticating a user, the steganographic image including an image of a government issued identification steganographically encoded using a fingerprint template; and Run the command, the steganographic image is based on an authentication of the image of the government issued identification, and the memory stores instructions that, when executed by the processor circuit, cause the processor circuit to: decrypting the fingerprint template from an image of the government issued identification contained in the steganographic image; receiving a fingerprint scan of a user's finger from a scanning device; extracting a scanned fingerprint template from the fingerprint scan; determining, based on the comparison, that the scanned fingerprint template and the decoded fingerprint template match to authenticate a user; Run the command, The instructions for performing the at least one verification operation include: the application receiving from the contactless card a public key of the contactless card's key pair and a user identification, the user identification including the steganographic image; receiving, by the application, a digital signature generated by the contactless card using a private key of the key pair of the contactless card; verifying the digital signature using the public key; Execute, including instructions, Device.
8. The memory stores instructions that, when executed by the processor circuit, cause the processor circuit to: comparing first application user credentials received from the user with second application user credentials stored in the memory, the second application user credentials being associated with an identity of a user, and performing the at least one verification operation in response to finding a match between the first application user credentials and the second application user credentials; The apparatus of claim 7, further comprising:
9. The memory stores instructions that, when executed by the processor circuit, cause the processor circuit to: the application receiving from the contactless card a public key of the contactless card's key pair and a user identification, the user identification including the steganographic image; receiving, by the application, a digital signature generated by the contactless card using a private key of the key pair of the contactless card; verifying the digital signature using the public key; determining whether a transaction associated with an NFC communication with the transaction device exceeds a threshold amount; performing additional security verification measures if the transaction exceeds the monetary threshold; and if the transaction does not exceed the monetary threshold, receiving a message that a user has been authenticated at the transaction device; The apparatus of claim 7, further comprising:
10. The instructions for performing the at least one verification operation include: determining, by the application, that a user has initiated a transaction with a transaction device to identify the user; the application receiving encrypted data from the contactless card, the encrypted data being based on an encryption algorithm and a diversified key, the diversified key being based on a master key and a counter value; the application transmitting the encrypted data to a server; the application receiving from the server verification of the encrypted data, the server decrypting the encrypted data based on the diversified key instance and verifying the encrypted data; receiving the steganographic image from the server by the application; The apparatus of claim 7 , further comprising instructions for causing the apparatus to execute:
11. 1. A computer-readable storage medium comprising computer-readable instructions executable by a processor circuit, the computer-readable storage medium comprising: an application running on the processor circuit communicating with the contactless card using Near Field Communication (NFC) performing at least one verification operation; In response to performing the at least one verification operation, the application receives from the contactless card a steganographic image for authenticating a user, the steganographic image including an image of a government issued identification steganographically encoded using a fingerprint template; and Run the command, The steganographic image is based on an authentication of the image of the government issued identification, and the computer readable storage medium includes instructions executable by the processor circuitry to cause the processor circuitry to: decrypting the fingerprint template from an image of the government issued identification contained in the steganographic image; receiving a fingerprint scan of a user's finger from a scanning device; extracting a scanned fingerprint template from the fingerprint scan; determining, based on the comparison, that the scanned fingerprint template and the decoded fingerprint template match to authenticate a user; Run the command, The instructions for performing the at least one verification include: the application receiving from the contactless card a public key of the contactless card's key pair and a user identification, the user identification including the steganographic image; receiving, by the application, a digital signature generated by the contactless card using a private key of the key pair of the contactless card; verifying the digital signature using the public key; Execute, including instructions, A computer-readable storage medium.
12. The computer-readable storage medium includes instructions executable by the processor circuit, the instructions including: comparing first application user credentials received from the user with second application user credentials stored on the computer-readable storage medium, the second application user credentials being associated with an identity of the user, and performing the at least one verification operation in response to finding a match between the first application user credentials and the second application user credentials; The computer-readable storage medium of claim 11 , further comprising:
13. The instructions for performing the at least one verification include: the application receiving from the contactless card a public key of the contactless card's key pair and a user identification, the user identification including the steganographic image; the application directing generation of a digital signature by the contactless card using a private key of the key pair of the contactless card; receiving the digital signature from the contactless card; verifying the digital signature using the public key; determining whether a transaction associated with an NFC communication with the transaction device exceeds a threshold amount; performing additional security verification measures if the transaction exceeds the monetary threshold; and if the transaction does not exceed the monetary threshold, receiving a message that a user has been authenticated at the transaction device; 12. The computer-readable storage medium of claim 11, comprising instructions for causing the computer to execute:
14. The instructions for performing the at least one verification include: determining, by the application, that a user has initiated a transaction with a transaction device to identify the user; the application receiving encrypted data from the contactless card, the encrypted data being based on an encryption algorithm and a diversified key, the diversified key being based on a master key and a counter value; the application transmitting the encrypted data to a server; the application receiving from the server verification of the encrypted data, the server decrypting the encrypted data based on the diversified key instance and verifying the encrypted data; receiving the steganographic image from the server by the application; 12. The computer-readable storage medium of claim 11, comprising instructions for causing the computer to execute:
Citation Information
Patent Citations
System, device and method for personal identification
JP2002032755A
IC card offline pin verification method and IC card offline verification system
JP2016518661A
Systems and methods for cryptographic authentication of contactless cards
US10489781B1
