System and method for transaction card-based authentication - Patents.com

Abstract

A method is provided for communication with a transaction card having a card data processor, a Near Field Communication (NFC) interface, and a card memory that stores a unique card identifier, in which a user communication device establishes an NFC session with the transaction card and sends an NFC Data Exchange Format (NDEF) Write Tag command to the transaction card that includes session-specific challenge information. The user communication device sends an NDEF Read Tag command to the transaction card and receives card-specific challenge response information from the transaction card. The challenge response information is used to authenticate the transaction card.

Description

[Technical field]

[0001] The present disclosure relates generally to transaction security, and more specifically to an exemplary system, method, and computer-accessible storage medium for implementing a challenge-response security protocol using a transaction card.

[0002] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to U.S. Patent Application No. 17 / 214,073, filed March 26, 2021, the disclosure of which is incorporated herein by reference in its entirety. [Background technology]

[0003] The development of electronic commerce has brought convenience to consumers and businesses. Transactions can be conducted between parties at any time from virtually any location. The use of cards, such as credit cards and debit cards, has enhanced the ability to conduct transactions over networks by allowing consumers to conduct purchase transactions or other business by simply providing authentication information including name, card number, and other data such as, for example, the card's expiration date, card security code, or billing zip code.

[0004] However, increased card usage also increases the risk of fraud and theft. Despite efforts to make card-based transactions more secure, smart cards and other devices are often vulnerable to replay attacks, in which card and / or transaction information is intercepted and then fraudulently used to perform additional transactions. Summary of the Invention

[0005] An exemplary aspect of the present invention provides a method of communicating with a transaction card having a card data processor, a near field communication (NFC) interface, and a card memory having a unique card identifier stored therein. The method includes establishing a first NFC session with the transaction card by a user communication device, and sending an NFC Data Exchange Format (NDEF) Write Tag command by the user communication device to the transaction card, the NFC Data Exchange Format (NDEF) Write Tag command including session-specific challenge information. The method further includes sending an NDEF Read Tag command by the user communication device to the transaction card, and receiving card-specific challenge response information from the transaction card by the user communication device. The method also includes authenticating the transaction card using the challenge response information.

[0006] Another aspect of the invention provides a user communication device comprising a communication device data processor and an NFC interface in communication with the data processor. The NFC interface is configured to communicate with one or more transaction cards. The user communication device further comprises a communication device memory accessible by the data processor and including a card communication application with instructions executed by the data processor. The communication application is configured to establish a first NFC session with the transaction card and send an NDEF write tag command to the transaction card including session specific challenge information. The application is further configured to send an NDEF read tag command to the transaction card, receive card specific challenge response information from the transaction card, and authenticate the transaction card.

[0007] Another aspect of the invention provides a transaction card comprising a card microprocessor, a near field communication (NFC) interface, and a card memory having stored thereon a card identifier and one or more applets. The one or more applets include instructions for the card microprocessor to receive an NDEF write tag command including challenge information from a user communication device via the NFC interface and generate a digital signature using the challenge information. The one or more applets include further instructions for receiving an NDEF read tag command from the user communication device via the NFC interface and transmitting the digital signature to the user communication device. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a flow chart of operations in a method of communicating with a transaction card according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a flow chart of operations in a method for authenticating communications between a transaction card and a user communications device in accordance with an embodiment of the present invention. [Diagram 3] FIG. 1 is a schematic diagram of a transaction card authentication system according to an embodiment of the present invention. [Figure 4] FIG. 4 is a block diagram of a transaction card microprocessor chip according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] The following description of the embodiments provides non-limiting representative examples with reference to symbols to particularly illustrate the features and teachings of various aspects of the present invention. Although the present invention will be described in connection with specific embodiments and environments, it will be understood that the present invention is not limited to these embodiments and environments. On the contrary, it is contemplated that various alternatives, modifications, and equivalents are included within the spirit and scope of the invention described. Furthermore, it should be recognized that the described embodiments can be implemented separately or combined with other embodiments.

[0010] As used herein, the term "transaction card" refers to any identification or payment card associated with a user or user account. This may specifically include credit cards, debit cards, or gift cards issued by a service provider. Smart transaction cards are often used to perform transactions through near field communication (NFC) or brief contact communication (e.g., a "tap") with a transaction processing device. Due to inherent limitations in transaction processing devices, such cards may not be suitable for use in authentication, except as part of a low-level protocol.

[0011] The present invention provides an approach that enhances the value of smart transaction cards in implementing multi-factor security protocols. The approach includes a challenge-response protocol that leverages the capabilities of a user processing device to send NFC data exchange format (NDEF) WRITE and READ commands to a transaction card. In the method of the present invention, a user can establish an NFC communication session between the transaction card and the user device (e.g., by tapping or bringing the user device within communication range of the card). The user device sends a WRITE NDEF to the transaction card. The transaction card reads information from the WRITE command and uses it to create a digital signature. The user device then sends a READ NDEF command to the transaction card, which sends the digital signature to the user device. The signature may be accompanied by a certificate signed by a trusted authority. The user device may then verify the card signature itself or pass the signature to a verification system. In either case, the verification of the signature may be used as an authentication factor in authenticating the presence of the transaction card and / or in multi-factor authentication of the user.

[0012] FIG. 1 illustrates a basic method M100 of communication between a user communication device and a transaction card. Method M100 may be used as part of a user and / or card authentication process. As described in more detail below, a transaction card usable in the method of the present invention may have a card data processor, a near field communication interface, and a card memory. The card memory may store card specific information including a unique card identifier. In some embodiments, the card memory may store one or more cryptographic keys. The user communication device may be any data processing device having near field communication capabilities, and is typically a network-enabled computer system. As used herein, the term network-enabled computer system (and / or device) may include, but is not limited to, a server, a microprocessor or system of microprocessors, a network appliance, a personal computer (PC), a workstation, and a portable processing device such as a smart phone, a smart pad, a handheld PC, a personal digital assistant (PDA). In some examples, the computer device may use instructions stored on a computer-accessible storage medium (e.g., a storage device such as a hard disk, a floppy disk, a memory stick, a CD-ROM, a RAM, a ROM, or a collection thereof). The computer-accessible storage medium may include executable instructions. Additionally or alternatively, storage devices may be provided separate from the computer-accessible storage medium that may provide instructions to the processing device to configure the processing device to perform certain example procedures, processes, and methods as described herein. In particular, the portable processing device may include NFC functionality that allows communication with other NFC-enabled devices by touching or bringing the devices into close proximity with each other.

[0013] In some embodiments of the invention, the user communication device may be a merchant terminal or other device configured to perform financial and other transactions. Such a merchant device may be specifically configured to perform transactions based on an account associated with a transaction card and / or a transaction card administrator or processor. In other embodiments of the invention, the user communication device may be a mobile device associated with a user who is the owner of an account associated with the transaction card.

[0014] At S110 of method M100, an NFC communication session is initiated between a user communication device and a transaction card. This is typically accomplished by tapping the card to the user communication device or bringing the card within NFC communication range of the user communication device. The act of initiating the NFC session may be performed as part of a purchase or other transaction involving an account associated with the transaction card. However, in some embodiments, the act may be performed as part of an authentication or authorization protocol associated with a transaction that does not involve an account associated with the transaction card. For example, a purchase may be made from a merchant using another card. The merchant may request authentication of a user / account holder using a smart transaction card, which may allow NFC communication to be established between the merchant terminal and the transaction card.

[0015] In some embodiments, the act of establishing NFC communication may be performed in response to receiving an authentication request from a transaction processing server or authentication server. Such a request may be sent by the server in response to a request to perform a transaction that requires verification of the presence of a transaction card or that requires authentication of the transaction card or user. Upon receiving the authentication request, the user communication device may display or communicate instructions to initiate NFC communication with the transaction card.

[0016] In an embodiment of the present invention, a user communication device may include an application for sending standardized NDEF messages for communicating with an NFC-enabled device. Such methods may specifically be used to communicate with standardized tags (e.g., radio frequency identification (RFID) tags) and include a "WRITE TAG" command for assigning information to the tag and a "READ TAG" command for reading information from the tag. At S120 of method M100, the user communication device sends a WRITE TAG command to a transaction card. The WRITE TAG command includes challenge information that the transaction card uses in generating a challenge response. The challenge information may be or include information specific to the NFC session. This may include, for example, a one-time, random, pseudo-random, or other unpredictable numeric value. The challenge information may be generated by the user communication device or may be generated by a requesting processing or authentication server. In some embodiments, the challenge information may be included in an authentication request received by the user communication device from the processing or authentication server. In other cases, the user communicating device may send NFC session information to a requesting server and receive session-specific challenge information in response.

[0017] The user communication device transmits a read tag command to the transaction card at S130 and receives a transmitted read tag response from the transaction card at S140. In some embodiments of the present invention, the read tag command must be transmitted to the transaction card within the same NFC communication session as the write tag command. In such embodiments, terminating the NFC session prior to the read tag command will result in an unauthenticated termination of the transaction card. In such a situation, a new NFC session and new challenge information will be required for card authentication. However, in other embodiments, method M100 may include terminating the NFC session (e.g., by removing the transaction card from the NFC communication range) and initiating a second NFC communication session prior to the operation of transmitting the read tag command. In some embodiments, such termination and reinitiation of NFC communication is a permissible occurrence, while in other embodiments it may be required.

[0018] Regardless of whether a single NFC session or multiple sessions are used, method M100 may include a time limit for transmitting a read tag command. The time limit may be based on a predetermined maximum time interval between transmitting a write tag command and transmitting a read tag command. In embodiments in which multiple NFC sessions are allowed or required, a maximum time interval between the end of a first session and the start of a second session may be specified.

[0019] The read tag response includes challenge response information unique to the transaction card, which may include, for example, a card identifier. The challenge response information may be or include information generated by the transaction card's data processing chip using information permanently assigned and / or hardwired into the transaction card's memory. In certain embodiments, the challenge response information may include information encrypted by the card's data processing chip. The challenge response information may also include a digital authentication certificate from a trusted source. Such a certificate may be used as a public key in encrypting and decrypting the challenge response information.

[0020] At S150, the transaction card is authenticated using the challenge response information. In some embodiments, the authentication operation may be performed entirely by the user communication device. This may include a comparison of the card-specific information with previously stored card information. Alternatively or additionally, the authentication may include decryption of the encrypted information by the transaction card data processor. Successful decryption indicates a positive authentication of the transaction card. However, the above approach may require that one or more private encryption keys stored in the transaction card memory must also be available to the user communication device. To avoid this requirement, in some embodiments, the user communication device may transmit some or all of the challenge response information to the authentication requesting server or directly to an authentication server that has access to the card-specific encryption keys. In such an embodiment, the user communication device can receive an authentication response indicating that the transaction card has been authenticated or that the authentication has failed.

[0021] In embodiments in which authentication is performed by the user communications device, method M100 may further include sending a result of the authentication to the requesting processing server or an authentication server.

[0022] FIG. 2 illustrates a basic method M200 for a smart transaction card to authenticate communication with a user communication device, according to an exemplary embodiment of the present invention. A typical transaction card that can be used to perform method M200 has a card data processor, an NFC interface, and a card memory having a unique card identifier stored therein. In some embodiments, the card memory may also store one or more card-specific cryptographic keys. At S210 of method M200, an NFC communication session is established between the card data processor and the user communication device. The user communication device may be, for example, a merchant transaction terminal, a portable user device, or other network-enabled device or system. The NFC communication session may be initiated by tapping the card to the user communication device or by bringing the card within NFC communication range of the user communication device. At S220, the card data processor receives a write tag command from the user communication device via the card's NFC interface. The write tag command includes challenge information that may be or include information specific to the NFC session. This may include, for example, a one-time, random, pseudo-random, or other unpredictable numerical value.

[0023] At S230, the card data processor generates a challenge response using the challenge information. The challenge response information may be or may include a card-specific signature and / or a session-specific signature. In certain embodiments, the signature may be or may include information from the challenge information encrypted by the card processor using one or more card-specific cryptographic keys. A public key (such as a trusted source certificate) may also be used for encryption. The challenge response may also include a card identifier and / or a public key used to encrypt the challenge information.

[0024] The card data processor receives a read tag command from the user communication device via the card NFC interface at S240, and transmits a challenge response back to the user communication device at S250.

[0025] With reference to Figure 3, an exemplary transaction card authentication system 100 according to one embodiment of the present invention may include a user device 110, a transaction card 150, a processing server 120, and a card information database 140. The user device 110 may communicate with the processing server 120 via a network 105. Additionally, the processing server 120 and / or the user device 110 may communicate with an authentication server 130. Although Figure 3 depicts certain components connected in a particular manner, the system 100 may include additional components or multiple components connected in various ways. In particular, the system 100 may include multiple user devices 110 and multiple transaction cards 150.

[0026] The systems and components of system 100 may be or include network-enabled computer devices and systems configured to process account-related transactions. Specifically, these systems may be configured to execute one or more software applications that receive data as input from entities accessing the network-enabled computer systems, process the received data, transmit data over a network, and receive data over a network, for example, to process transactions originating from a merchant transaction device or an account holder's device. Various network-enabled computer systems may include one or more software applications for sending notifications to account holders (e.g., via the account holder's computer system or mobile device). It will be understood that the depiction of FIG. 3 is merely an example, and that the functions and processes described herein may be performed by any number of network-enabled computers. It will also be understood that even if the illustrated system 100 has only one instance of a particular component, multiple instances of those components may be used. System 100 may also include other devices not shown in FIG. 3.

[0027] In the exemplary embodiments illustrated herein, an account holder may be any individual or entity that desires to conduct a transaction (which may be, but is not limited to, a financial transaction) with a merchant using a transaction account. An account may be held by any place, location, object, entity, or other mechanism for holding money or conducting transactions in any form, including, but not limited to, electronic form. An account may be associated with one or more transaction cards, such as, for example, a credit card, a debit card, or a prepaid card.

[0028] The various components of the system 100 may be configured to process transactions involving, among other things, the use of a transaction card, such as a smart transaction card 150. The transaction card 150 may be any device having a processor configured to communicate via NFC and perform digital transactions, and having memory capable of storing identification and cryptographic information. This may include transaction cards equipped with chips ("smart" cards), portable and non-portable user computing devices. As shown in Figures 3 and 4, a typical transaction card 150 usable in various embodiments of the present invention is a smart card with a microprocessor chip 151. The microprocessor chip 151 includes processing circuitry for storing and processing information, including a microprocessor 152 and a memory 156. It will be appreciated that the processing circuitry may include additional components, including a processor, 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. Memory 156 may be read-only memory, write-once read-multiple memory, or read / write memory, such as RAM, ROM, and EEPROM, and chip 151 may include one or more of these memories. Memory 156 may be configured to store one or more software applications for execution by microprocessor 152. Information associated with an account may also be stored in memory 156. In particular, memory 156 may persistently store a unique alphanumeric identifier and one or more public and private card encryption keys.

[0029] Microprocessor chip 151 further includes an NFC interface 154 configured to establish communication with user device 110 or other devices when card 150 is within a predefined NFC range. In some embodiments, NFC interface 154 may comprise a radio frequency identification chip configured to communicate via NFC or other short-range protocols. In some embodiments, microprocessor chip 151 may include circuitry configured to communicate with user device 110 via other means, such as Bluetooth, satellite communications, Wi-Fi, wired communications, and / or any combination of wireless and wired connections.

[0030] In certain embodiments, the chip 151, memory 156 of the microprocessor chip 151 may store one or more applets with instructions for generating encrypted information and transmitting it to a receiving device (e.g., user device 110) via the NFC interface 154. Such encrypted information may be or include an encrypted verification block or signature that may be used by the user device 110 or processing server 120 to authenticate and verify the presence of the transaction card 150.

[0031] The memory 156 may specifically store an authentication application having instructions for the data processor 152 to establish an NFC communication session with the user communication device 110 and to receive a light tag command sent by the user communication device 110 via the NFC interface 154. The application may be configured to recognize the light tag command as an authentication challenge and, based on such recognition, generate a challenge response based on the challenge information contained therein. The challenge response may include challenge response information specific to the transaction card, which may include, for example, a card identifier. The challenge response information may be or include information generated by the data processor 152 using information permanently or temporarily stored in the card memory 156. In certain embodiments, the authentication application is configured to cause the processor 152 to generate a digital signature specific to the transaction card 150 and / or the NFC session. The digital signature and / or other challenge response information may be or include a cryptogram encrypted using the challenge information received in the light tag command by the card data processing chip. The ciphertext may be created by the processor 152 using one or more of a public and private encryption key stored in memory 156. The challenge-response information may also include a digital authentication certificate retrieved from memory 156.

[0032] The authentication application may also be configured to receive a read tag command via NFC from the user communication device 110. In response, the application may transmit a challenge response via the NFC interface 154. In some embodiments, the authentication application may be configured such that the operation of generating a digital signature and / or other challenge response information is not performed unless or until a read tag command is received. In such an embodiment, the operation of generating the challenge response information and the operation of transmitting the challenge response information may both be performed in response to receiving a read tag command. In some embodiments, either or both of these operations may be conditional on the time interval between the write tag command and the read tag command being less than a specified maximum time interval. If the maximum time interval is exceeded, the microprocessor 152 may transmit a “timeout” error message to the user communication device 110 via the NFC interface 154.

[0033] In some embodiments, the authentication application may be configured to terminate the authentication procedure if the NFC session with the user communicating device 110 is terminated before receiving a Read Tag command. In other embodiments, the application may allow or require the termination of the first NFC session after receiving a Write Tag command and the establishment of a second NFC session thereafter to receive a Read Tag command. As above, the transmission of the challenge response may be conditional on the Read Tag command being received within a maximum time interval after the Write Tag command.

[0034] The user communication device 110 may be any computing or communication device including a server, a network appliance, a personal computer (PC), a workstation, and a portable interface device such as a smartphone, a smart pad, a handheld PC, or a personal digital assistant (PDA). The user communication device 110 may be a transaction terminal (e.g., a merchant or bank terminal) used to perform financial transactions and other interactions with an account holder. The user device 110 includes an on-board data processor 111 in communication with a memory module 113, a user interface 114, a network communication interface 112, and an NFC interface 116. The user device 110 may optionally include an image capture device 115 (e.g., a digital camera). The data processor 111 may include a microprocessor and associated processing circuitry, and may include additional components including a processor, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and tamper-proof hardware as necessary to perform the functions described herein. The memory 113 may be, for example, a read-only memory, a write-once read-multiple memory, or a read / write memory, such as RAM, ROM, and EEPROM, and the user device 110 may include one or more of these memories.

[0035] The user interface 114 of device 110 includes a user input mechanism, which may be any device for inputting information and commands into user device 110, such as a touch screen, keyboard, mouse, cursor control device, microphone, stylus, or digital camera. The user interface 114 may also include a display, which may be any type of device for displaying visual information, such as computer monitors, flat panel displays, and handheld device displays, including liquid crystal displays, light emitting diode displays, plasma panels, and cathode ray tube displays.

[0036] The network communication interface 112 is configured to establish and support wired or wireless data communication capabilities for connecting the device 110 to the network 105 or other communication networks. The communication interface 112 may also be configured to support communication with a short-range wireless communication interface for communication via a short-range system such as Bluetooth.

[0037] The NFC interface 116 of the user device is configured to establish near field wireless communication with other NFC enabled devices, including in particular the data processing chip 151 of the transaction card 150. The NFC interface 116 is further configured to transmit information to the data processing chip 151 via the chip NFC interface 154 and to receive information transmitted by the data processing chip 151.

[0038] In an embodiment of the invention, the memory 113 may store one or more applications usable by the data processor 111 to conduct and / or monitor transactions between the user device 110 and one or more processing servers 120 and authentication servers 130 via the network 105, and / or one or more merchant transaction terminals (not shown) via NFC, short range communications or network 105. These applications may include instructions usable by the data processor 111 to identify transaction events, store event data in the memory 113, and communicate the event data to the servers 120, 130. Some applications may include instructions related to receiving and interpreting instructions from the one or more processing servers 120 or one or more authentication servers 130.

[0039] In a particular embodiment, the memory 113 may include one or more applets configured to write NDEF formatted information to and / or read formatted information from an NFC-enabled tag device (e.g., an RFID tag). These applets may include, among other things, instructions for executing a write tag command that causes formatted information to be transmitted to and stored in a memory of a receiving tag, and instructions for executing a read tag command that causes formatted information to be transmitted by the tag and received by the user device 110. The memory 113 may also have stored therein a card communication application that may invoke the NDEF applet for use in a communication session with the transaction card 150. The card communication application may include instructions for the data processor 111 to establish a first NFC session with the transaction card 150 via the NFC interface 116 and to transmit an NDEF write tag command to the transaction card 150 via the NFC interface 116. The application may also include instructions for assembling or receiving session-specific challenge information that may be formatted for transmission via the NDEF write tag command. Such challenge information may include, for example, a session identifier and a timestamp to distinguish the NFC session from other sessions. The challenge information may alternatively or additionally include information specific to the intended transaction card 150 whose presence is required to complete the authentication or authorization process. The challenge information may be generated by the data processor 111 using information received by the data processor 111 from the processing server 120 or the authentication server 130 via the network communication interface 112 and / or information stored in the memory 113.

[0040] In some embodiments, the application may be configured to receive an authentication request from the transaction processing server 120 or the authentication server 130. Such a request may be sent by the server in response to a request to perform a transaction that requires verification of the presence of a particular transaction card 150 or that requires authentication of the transaction card 150 or a user. Such a request may include challenge information that is included in the write tag command. The application may be further configured to display information and instructions to a user of the user communication device 110 via the user interface 114. The user instructions may include, for example, instructions to initiate NFC communication with the transaction card 150.

[0041] The card communication application may further include instructions for the data processor 111 to send an NDEF read tag command to the transaction card 150 and receive formatted response information from the transaction card 150 in return. The response information may include a card identifier and / or challenge response information constructed by the transaction card 150 using the challenge information. The application may also include instructions for the data processor 111 to authenticate the transaction card 150 using the challenge response information. This may be accomplished by directly comparing the challenge response information with expected response information stored in memory 113 or received from the requesting processing server 120 or authentication server 130.

[0042] In some embodiments, the act of authenticating the transaction card 150 may include sending challenge response information to the authentication server 130 and receiving an authentication response back from the authentication server 130. In some embodiments, the challenge response information may be sent directly to the authentication server 130 over the network 105. In other embodiments, the user communications device 110 may send the challenge response information over the network 105 to the processing server 120, which sends the challenge response information to the authentication server 130.

[0043] In some embodiments, the challenge-response information authentication may include information encrypted by the transaction card using an encryption key associated with the card or account. In such embodiments, the card communications application may be configured to retrieve the necessary encryption keys from memory 113 and use them to decrypt the encrypted information. The application may condition authentication of card 150 on successful decryption of the challenge-response information.

[0044] Once the communications application has established the authentication result, it may be configured to transmit the authentication result over the network 105 to the processing server 120, the authentication server 130, or other requesting system.

[0045] Processing server 120 is a system of one or more network-enabled processing servers configured to process transactions for accounts associated with transaction cards 150. Processing server 120 is configured to selectively communicate with one or more user communication devices 110 (e.g., account holder mobile or other devices and merchant transaction terminals) over network 105. Processing server 120 may be configured to store and retrieve account and transaction information in an account information database (not shown) and transaction card information in a card information database 140. Processing server 120 may receive transaction processing requests from any of the user devices 110 and is configured to use information from such requests to determine whether to process the requested transaction.

[0046] In some embodiments, the processing server 120 may require verification of the presence of an authorized transaction card 150 in order to process a transaction. In some such embodiments, the processing server may send a verification request to a user communication device 110 associated with the card 150 or its associated account. In other embodiments, the processing server 120 may send a request to a user communication device 110 (e.g., a merchant terminal) associated with the transaction to be processed. In either case, the verification request includes instructions for the user communication device 110 to establish an NFC communication session between the user communication device 110 and the transaction card 150 to verify that the card 150 is owned by the account owner and / or is in the presence of the transaction requester. In some embodiments, the verification is performed by the user communication device 110 and the processing system 120 simply receives a response from the device 110 indicating the verification result. However, in some embodiments, the user communication device 110 may not perform the verification and instead transmit challenge response information received from the transaction card 150 to the processing server 120. The processing server 120 may be configured to use the challenge response information to complete the authentication / verification of the transaction card 150. However, in some embodiments, the processing server 120 can forward the challenge-response information to the authentication server 130 to complete the authentication / verification process.

[0047] In some embodiments, processing server 120 may generate challenge information that may be included in a verification request for submission by user communication device 110 to card 150. The challenge information may include card and / or transaction specific information. Alternatively, or in addition, it may include an unpredictable challenge value, such as a random or pseudo-random number.

[0048] The authentication server 130 may be a system of one or more network-enabled processing servers configured to selectively communicate with the user communication device 110 and / or the processing server 120 over the network 105. The authentication processor 130 may also be able to access the card information database 140 directly or via the processing server 120 over the network 105. The authentication server 130 may be configured to send a card authentication request to the user communication device 110 and receive an authentication response from the user communication device 110. The authentication server 130 may be configured to generate challenge information for inclusion in the authentication request. Such challenge information may be or include card-specific information obtained from the card database 140. The challenge information may also or instead include one-time request or transaction-specific information used by the transaction card 150 to generate challenge response information. The authentication server 130 may be further configured to receive an authentication request response from the user communication device 110, the response including the challenge response information generated by the transaction card 150. The authentication server 130 may be configured to use the challenge-response information to verify that such information was generated by the intended transaction card 150 .

[0049] The card database 140 may store one or more data records associated with the transaction card 150. In some embodiments, these records may include one or more private encryption keys that are assigned to the transaction card 150 and stored in the card memory 156. The one or more encryption keys may be accessed by the processing server 120 or the authentication server 130 as needed for decryption of the card-encrypted information included in the challenge-response information. The processing server 120 and / or the authentication server 130 may be configured to use the decryption key and one or more public keys associated with the transaction card to decrypt the card-encrypted information and verify that the challenge-response information was provided by the expected transaction card 150. In some embodiments, the public encryption key may be part of or included in the challenge-response information.

[0050] The present invention provides a significant improvement in transaction security by providing enhanced security to the process of ensuring the presence of an authorized transaction card. By using session-specific information in combination with card-specific information to authenticate the presence of a particular account-associated card, the present invention makes it difficult or impossible for an intercepting entity to use that information in a replay attack. This method can be further strengthened by having the card itself encrypt the session-specific information using a private encryption key available only to the card and a limited-access card database.

[0051] It will be readily apparent to those skilled in the art that the present invention is susceptible of wide utility and application. Numerous embodiments and applications of the invention other than those described herein, as well as numerous variations, modifications and equivalent arrangements, will be apparent from, or will reasonably be suggested by, the invention and the foregoing description thereof without departing from the spirit or scope of the invention.

Claims

1. A method for communicating with a transaction card having a card data processor, a communications interface, and a card memory storing a unique card identifier, comprising: an application executing on a communications device sending a write command to the transaction card, the write command including a session specific challenge; the application sending a read command to the transaction card; receiving card specific challenge response information from the transaction card by the application; authenticating the transaction card using the card-specific challenge response information; A method comprising:

2. The method of claim 1 , wherein the card-specific challenge-response information includes card-encrypted information.

3. The method described in claim 2, wherein the card-specific challenge response information further includes a digital authentication certificate.

4. The operation of authenticating the transaction card comprises: attempting to decrypt the card-encrypted information using at least one card unique key associated with the unique card identifier; establishing a positive authentication result in response to the card encrypted information being successfully decrypted; The method of claim 2 , comprising:

5. The method of claim 1 , wherein the session-specific challenge information comprises a random number.

6. The method of claim 1 , wherein the session-specific challenge information is generated by the application and the authenticating the transaction card is performed by the application.

7. Authenticating the transaction card comprises: the application sending the card-specific challenge-response information to an authentication server; the application receiving an authentication result from the authentication server; The method of claim 1 , comprising:

8. The method of claim 1, further comprising the application receiving the session-specific challenge information from an authentication server.

9. The communication interface includes a near field communication (NFC) interface, the write command comprises an NFC Data Exchange Format (NDEF) Write Tag command; The read command includes an NDEF read tag command. The method of claim 1.

10. The method of claim 9, further comprising the application establishing a first NFC session with the transaction card prior to sending the write command.

11. Before the operation of transmitting the NDEF read tag command, transmitting the first NFC session; the communications device establishing a second NFC session with the transaction card within a predetermined time interval after the first NFC session is terminated; The method of claim 10 further comprising:

12. A communications device data processor; a communications interface configured to communicate with the communications device data processor and to communicate with one or more transaction cards; a communications device memory including a communications device application accessible by said communications device data processor and comprising instructions for execution by said communications device data processor; when executed by the communications device data processor, the communications device application sending a write command to the transaction card, the write command including a session-specific challenge; Sending a read command to the transaction card; receiving card-specific challenge response information from the transaction card; authenticating the transaction card; A communication device configured to:

13. The card-specific challenge-response information includes card encryption information, The communications device application, as part of authenticating the transaction card, attempting to decrypt the card-encrypted information using at least one card-specific key associated with the transaction card; establishing a positive authentication result in response to successful decryption of the card encrypted information; 13. The communication device of claim 12.

14. The communication device according to claim 1, further comprising a network communication interface configured to communicate with the communication device data processor and to selectively communicate with an authentication server over a network; the communication device application receives the session-specific challenge information from the authentication server; 13. The communication device of claim 12.

15. The communications device application, as part of authenticating the transaction card, Sending the card-specific challenge response information to the authentication server; receiving an authentication result from the authentication server; 15. The communication device of claim 14.

16. The communication device application, determining a time interval between the acts of transmitting the read command and receiving the card-specific challenge response information; if the time interval is less than a predetermined maximum communication interval, authenticating the transaction card; 13. The communication device of claim 12.

17. The communication device of claim 12, wherein the session-specific challenge information includes a pseudo-random number.

18. A card microprocessor; A communication interface; a card memory for storing one or more applets containing instructions for execution by said card microprocessor; wherein the one or more applets, when executed by the card microprocessor, receiving a write command including challenge information from a communication device via the communication interface; generating a digital signature using the challenge information; receiving a read command from the communication device via the communication interface; transmitting the digital signature to the communication device; Transaction card.

19. the card memory stores at least one card-specific cryptographic key; the digital signature includes at least a portion of the challenge information and a cryptogram encrypted using the at least one card-specific cryptographic key.

20. The transaction card of claim 18.

20. the card memory stores a card identifier and at least one public key certificate; the one or more applets transmit the card identifier and the at least one public key certificate along with the digital signature.

20. The transaction card of claim 19.

Images