Efficient interaction handling using secrets

Abstract

A method includes an access device determining an interaction value associated with an interaction. The access device prompts a user to operate a user device for a secret. The access device receives the secret. The access device receives an initial communication from the user device and then receives a user device certificate including a public key. The access device then verifies the certificate. The access device concatenates at least the secret and a non-predictable number to form a concatenated value. The access device encrypts the concatenated value with the public key and then transmits the encrypted concatenated value. The user device decrypts the encrypted concatenated value with a private key, verifies the non-predictable number, verifies the secret, determines whether the interaction is approved, generates an interaction authorization result, and then provides the interaction authorization result to the non-contact access device. The access device receives the interaction authorization result.

Description

[0001] Cross-references to related applications

[0002] none. Background Technology

[0003] During some interactions between a user device and an access device, offline PIN authentication is required to perform contact-based interactions (e.g., contact between the user device and the access device). Furthermore, contact-based interactions are needed to perform high-value interactions. Therefore, if a contactless interaction is attempted, but the interaction value is too high, the contactless interaction cannot be performed; instead, a contact-based interaction must be used.

[0004] To address this issue, a two-tap interaction was created. In the first tap, the user device and the access device exchange data. The user is then prompted to enter a secret into the access device. The user then needs to tap the user device again on the access device to allow the access device to verify the secret.

[0005] Current dual-touch interaction methods are slow, inefficient, and cumbersome. Embodiments of this disclosure address this problem and others, individually and collectively. Summary of the Invention

[0006] The embodiments relate to methods and systems for efficient interactive processing using confidentiality.

[0007] One embodiment relates to a method comprising: determining an interaction value associated with an interaction by a contactless access device; prompting a user to operate a user device for a secret by the contactless access device in response to determining the interaction value; receiving the secret from the user by the contactless access device; after receiving the secret from the user, receiving initial communication from the user device via a wireless communication medium by the contactless access device; receiving a user device certificate including a public key from the user device by the contactless access device; verifying the user device certificate by the contactless access device; concatenating at least the secret and an unpredictable number to form a connection value; and having the contactless access device... The contactless access device encrypts the connection value using the public key; the contactless access device transmits the encrypted connection value to the user device via the wireless communication medium, wherein the user device decrypts the encrypted connection value using a private key corresponding to the public key, verifies the unpredictable number, verifies the secret by comparing the secret with another secret stored in the user device, determines whether to approve the interaction based at least on the verification of the secret, generates a user device interaction authorization result, and then provides the user device interaction authorization result to the contactless access device; and the contactless access device receives the user device interaction authorization result from the user device.

[0008] Another embodiment relates to a contactless access device, comprising: a processor; and a computer-readable medium coupled to the processor, the computer-readable medium including code executable by the processor to perform a method comprising: determining an interaction value associated with an interaction; prompting a user to operate a user device for a secret in response to determining the interaction value; receiving the secret from the user; after receiving the secret from the user, receiving initial communication from the user device via the wireless communication medium; receiving a user device certificate including a public key from the user device; verifying the user device certificate; and connecting at least the secret. The process involves: forming a connection value with an unpredictable number; encrypting the connection value with the public key; transmitting the encrypted connection value to the user device via the wireless communication medium, wherein the user device decrypts the encrypted connection value with a private key corresponding to the public key, verifies the unpredictable number, verifies the secret by comparing the secret with another secret stored in the user device, determines whether the interaction is approved based at least on the verification of the secret, generates a user device interaction authorization result, and then provides the user device interaction authorization result to the contactless access device; and receiving the user device interaction authorization result from the user device.

[0009] Another embodiment relates to a method comprising: upon entering communication range with a contactless access device during an interaction, an initial communication is provided by a user device via a wireless communication medium; the user device receives a read logging command from the contactless access device, wherein the read logging command requests at least one or more certificates from the user device; the user device obtains at least one or more certificates from a memory; the user device generates a read logging response message including at least one or more certificates; and in response to the read logging command, the user device provides the read logging response message to the contactless access device, wherein the one or more certificates include a user device certificate containing a public key, wherein the contactless access device verifies the user device certificate, at least... The process involves: receiving a confidential and unpredictable number provided by a user of the user device to the contactless access device to form a connection value; encrypting the connection value with the public key; transmitting the encrypted connection value to the user device via the wireless communication medium; receiving the encrypted connection value from the contactless access device by the user device; decrypting the encrypted connection value by the user device using a private key corresponding to the public key; verifying the confidentiality included in the connection value by the user device by comparing the confidentiality with another confidentiality stored in the user device; generating a user device interaction authorization result based on whether the interaction is approved, at least according to the verification of the confidentiality; and providing the user device interaction authorization result to the contactless access device.

[0010] Further details regarding embodiments of this disclosure can be found in the detailed description and the accompanying drawings. Attached Figure Description

[0011] Figure 1 A block diagram of an interactive processing system according to an embodiment is shown.

[0012] Figure 2 A block diagram showing the components of an access device according to an embodiment.

[0013] Figure 3 A block diagram showing components of a user device according to an embodiment.

[0014] Figures 4A-4B A flowchart illustrating contactless interaction using a confidential verification processing method according to an embodiment is shown. Detailed Implementation

[0015] Before discussing the implementation schemes of this disclosure, some terms may be described in further detail.

[0016] "User" can include an individual. In some embodiments, a user can be associated with one or more personal accounts and / or mobile devices. In some embodiments, a user can also be referred to as a cardholder, account holder, or consumer.

[0017] A “user device” can be a device operated by a user. Examples of user devices can include mobile phones, smartphones, cards, personal digital assistants (PDAs), laptops, desktop computers, server computers, vehicles (such as automobiles), simplified client devices, tablet PCs, and so on. Furthermore, a user device can be any type of wearable technology device, such as a watch, headphones, glasses, etc. A user device can include one or more processors capable of processing user input. A user device can also include one or more input sensors for receiving user input. As is known in the art, there are various input sensors capable of detecting user input, such as accelerometers, cameras, microphones, etc. User input obtained by input sensors can come from various data input types, including but not limited to audio data, visual data, or biometric data. A user device can include any electronic device that can be operated by the user, and said electronic device can also provide remote communication capabilities with a network. Examples of remote communication capabilities include using mobile phone (wireless) networks, wireless data networks (e.g., 3G, 4G, or similar networks), Wi-Fi, Wi-Max, or any other communication medium that can provide access to a network (such as the Internet or a private network).

[0018] A “user identifier” may include any piece of data capable of identifying a user. A user identifier may include any suitable alphanumeric string. In some embodiments, the user identifier may be derived from user identification information. In some embodiments, the user identifier may include an account identifier associated with the user.

[0019] "Interaction" can include mutual effects or influences. "Interaction" can include communication, contact, or exchange between parties, devices, and / or entities. Example interactions include transactions between two parties and data exchange between two devices. In some embodiments, interaction can include a user requesting access to secure data, secure web pages, secure locations, etc. In other embodiments, interaction can include payment transactions, in which two devices may interact to facilitate payment.

[0020] "Interaction data" may include data related to the interaction and / or data recorded during the interaction. In some embodiments, interaction data may be transaction data or network data. Transaction data may include multiple data elements having data values.

[0021] An "interaction value" can include a digital quantity associated with an interaction that involves interaction data. An interaction value can include resource quantity, resource value, the size of data transferred, etc. In some embodiments, if the interaction is a transaction, the interaction value can be the transaction amount.

[0022] "Confidential" can include things that are kept or intended to be kept from or unseen by others. A confidential information can include values ​​known to the user and securely stored by the user's device. A confidential information can include a PIN, password, biometrics, one-time password, access code, or username-password pair. The user can enter the confidential information into an access device to gain access to resources. The access device can communicate with the user device (as described further in detail herein) to verify the confidential information.

[0023] A “credential” can include any evidence of authorization, rights, or privileges. For example, an access credential can include permission to access certain tangible or intangible assets, such as buildings or documents. Instances of credentials can include passwords, passcodes, or confidential messages. In another instance, a payment credential can include any suitable information associated with and / or identifying an account (e.g., a payment account and / or a payment device associated with that account). This information can be directly related to the account or derived from account-related information. Instances of account information can include “account identifiers” such as PAN (primary account number or “account number”), tokens, sub-tokens, gift card numbers or codes, prepaid card numbers or codes, usernames, expiration dates, CVV (card verification value), dCVV (dynamic card verification value), CVV2 (card verification value 2), CVC3 card verification value, and so on. An instance of a PAN is a 16-digit number, such as “4147 0900 0000 1234”. In some embodiments, credentials can be considered sensitive information.

[0024] A “password” can include obscure text, such as encrypted text. A password can be formed by encrypting input data using an encryption key, such as a symmetric encryption key. In some embodiments, the password is reversible, allowing the same symmetric key to be used to obtain the input used to form the password for decryption. In some embodiments, the password can also be a digital signature if the input data is encrypted using the private key of a public / private key pair. The digital signature can be verified using the public key of the public / private key pair. In some embodiments, the password can include a dynamic card verification value (dCVV).

[0025] In embodiments of the invention, the password can be generated in any suitable manner. In some embodiments, the password input may include data elements, including account identifiers such as a master account and variable data elements such as a counter, time of day, or interaction value. Such data can be included using encryption processes such as DES, Triple DES, or AES using any suitable encryption key. The encryption key may also be a uniquely derived key or UDK and may be generated based on device-specific information such as an account, which can be encrypted using a master derived key (MDK). The password can be verified by another computer on a remote computer by either decrypting the password to its decrypted form and verifying the decrypted form with other data (e.g., the account number stored in a file), or by encrypting other input and comparing the encrypted result with the password.

[0026] A "certificate" or "digital certificate" can be an electronic document used to prove ownership. A certificate can be used to prove ownership of a public key. A digital certificate cryptographically links ownership of a public key to the entity that owns the public key. A digital certificate can include the public key being authenticated, identifying information about the entity that owns the public key, metadata associated with the certificate, and a digital signature.

[0027] "Unpredictable numbers" can include values ​​that cannot be or are not easily predicted. Unpredictable numbers can be generated using random or pseudo-random number generation processes. Unpredictable numbers can have any suitable size. For example, unpredictable numbers can have a length of 2 bytes, 4 bytes, 8 bytes, etc.

[0028] A "resource provider" can be an entity that can provide resources such as goods, services, information, and / or access. Examples of resource providers include merchants, data providers, transportation departments, government entities, venue and residential operators, etc. A "merchant" can typically be an entity that participates in a transaction and can sell goods or services or provide access to goods or services.

[0029] The term "verification" and its derivatives can refer to the process of using information to determine whether an underlying subject is valid under a given set of conditions. Verification may include any comparison of information to ensure that certain data or information is correct, valid, accurate, legitimate, and / or credible.

[0030] An "access device" can be any suitable device that provides access to a remote system. Access devices can also be used to communicate with a coordinating computer, communication network, or any other suitable system. Access devices can typically be located anywhere suitable, such as at the merchant's location. Access devices can take any suitable form. Some examples of access devices include POS or point-of-sale devices (e.g., POS terminals), cellular phones, personal digital assistants (PDAs), personal computers (PCs), tablet PCs, handheld dedicated readers, set-top boxes, electronic cash registers (ECRs), vending machines, automatic teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, etc.

[0031] The access device can use any suitable contact or contactless operating mode to send or receive data from or associated with a mobile communication device or payment device. For example, the access device may have a card reader, which may include electrical contacts, a radio frequency (RF) antenna, an optical scanner, a barcode reader, or a magnetic stripe reader to interact with portable devices such as payment cards.

[0032] An "authorization request message" can be an electronic message requesting authorization for an interaction. In some embodiments, the message is sent to the transaction processing computer and / or the issuer of the payment card to request authorization for the transaction. According to some embodiments, the authorization request message may comply with International Organization for Standardization (ISO) 8583, a standard for systems that exchange information about electronic transactions associated with payments made by a user using a payment device or payment account. The authorization request message may include an issuer account identifier that may be associated with the payment device or payment account. The authorization request message may also include additional data elements corresponding to "identification information," including (by way of example only): service code, card verification value (CVV), dynamic card verification value (dCVV), primary account number or "account number" (PAN), payment token, username, expiration date, etc. The authorization request message may also include "transaction information," such as any information associated with the current transaction, such as transaction value, merchant identifier, merchant location, acquiring bank identifier (BIN), card acceptor ID, information identifying the item being purchased, etc., and any other information that may be used to determine whether to identify and / or authorize the transaction.

[0033] An "authorization response message" can be a message responding to an authorization request. In some cases, an authorization response message can be an electronic message response to an authorization request message generated by the issuing financial institution or transaction processing computer. For example, an authorization response message may include one or more of the following status indicators: approved – the transaction is approved; rejected – the transaction is not approved; or call center – further information is pending, and the merchant must call the toll-free authorization number. An authorization response message may also include an authorization code, which can be a code indicating approval of the transaction returned by the credit card issuing bank to the merchant's access device (e.g., a POS device) in response to the authorization request message in the electronic message (directly or via the transaction processing computer). This code can serve as evidence of authorization.

[0034] "Authorizing entity" can be the entity requesting authorization. Instances of authorizing entities can be issuers, government agencies, document repositories, access administrators, etc. Authorizing entities can operate authorizing entity computers. "Issuer" can refer to a commercial entity (e.g., a bank) that issues and optionally maintains user accounts. Issuers can also issue payment credentials stored on user devices, such as cellular phones, smart cards, tablets, or laptops, to consumers, or in some embodiments to portable devices.

[0035] A “wireless communication medium” may include a communication channel operated by electromagnetic waves emitted by a radio. A wireless communication medium can allow two or more devices to communicate without physical contact. In some embodiments, the devices communicating via the wireless communication medium may be contactless devices. In some embodiments, the wireless communication medium may use near-field communication (NFC).

[0036] A “processor” can include means for performing a task. In some embodiments, a processor can include any suitable one or more data computing means. A processor can include one or more microprocessors that work together to perform a desired function. A processor can include a CPU that includes at least one high-speed data processor sufficient to execute program components for performing user and / or system-generated requests. A CPU can be a microprocessor, such as AMD’s Athlon, Duron, and / or Opteron; IBM and / or Motorola’s PowerPC; IBM and Sony’s Cell processors; Intel’s Celeron, Itanium, Pentium, Xeon, and / or XScale; and / or similar processors.

[0037] "Memory" can be any suitable device capable of storing electronic data. Suitable memory may include non-transient computer-readable media storing instructions executable by a processor to implement desired methods. Examples of memory may include one or more memory chips, disk drives, etc. Such memory can be operated using any suitable electrical, optical, and / or magnetic operating modes.

[0038] A "server computer" can include a powerful computer or cluster of computers. For example, a server computer can be a mainframe, a small cluster of computers, or a group of servers that work like cells. In one instance, a server computer can be a database server coupled to a web server. A server computer can include one or more computing devices and can use any of a variety of computing architectures, arrangements, and compilations to serve requests from one or more client computers.

[0039] Various embodiments relate to a method for performing offline contactless interaction using a secret while applying a touch card only once to a contactless access device. In embodiments of the invention, the secret is first received by the contactless access device (e.g., via user input). The contactless access device then takes several steps to verify the user device being used by the user, encrypts the secret, and sends the encrypted secret to the user device for verification. Upon successful secret verification, the contactless access device can continue processing the interaction.

[0040] Figure 1 A system 100 according to an embodiment of the present disclosure is illustrated. System 100 includes a user device 102, an access device 104, a resource provider computer 106, a transmission computer 108, a network processing computer 110, and an authorization entity computer 112. User device 102 is operable in communication with access device 104. Access device 104 is operable in communication with resource provider computer 106, which is operable in communication with transmission computer 108. Transmission computer 108 is operable in communication with network processing computer 110. Network processing computer 110 is operable in communication with authorization entity computer 112.

[0041] To simplify the explanation, Figure 1 A certain number of components are shown. However, it should be understood that embodiments of the invention may include more than one of each component. Furthermore, some embodiments of the invention may include more than one of each component. Figure 1 All components shown are either fewer or more components.

[0042] At least Figure 1Messages between devices in the network can be transmitted using secure communication protocols, such as, but not limited to, File Transfer Protocol (FTP); Hypertext Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS); SSL; ISO (e.g., ISO 8583), etc. The communication network can include any one and / or a combination of the following: direct interconnection; the Internet; a local area network (LAN); a metropolitan area network (MAN); Operational Mission as a Node on the Internet (OMNI); a secure custom connection; a wide area network (WAN); a wireless network (e.g., employing protocols such as, but not limited to, Wireless Application Protocol (WAP), I-mode, etc.); etc. The communication network can use any suitable communication protocol to generate one or more secure communication channels. In some instances, the communication channel can include a secure communication channel, which can be established in any known manner, such as by using mutual authentication and session keys, and by establishing a Secure Sockets Layer (SSL) session.

[0043] User device 102 may include any suitable device operable by a user. User device 102 may be a smartphone, smartwatch, tablet, laptop, desktop computer, etc. User device 102 may be able to receive communications from access device 104 and send communications to access device.

[0044] Access device 104 may include means for providing access to a remote system. Access device 104 may be able to communicate with user device 102 and resource provider computer 106. Access device 104 can typically be located in any suitable location, such as at the location of a merchant associated with resource provider computer 106. Access device may be a POS terminal, cellular phone, PDA, personal computer, tablet computer, handheld dedicated reader, set-top box, electronic cash register, vending machine, ATM, virtual cash register, kiosk, security system, access system, etc.

[0045] Resource provider computer 106 may include a computer associated with a resource provider. Resource provider computer 106 may receive information about the interaction (e.g., interaction data) from access device 104 during interaction with user device 102. Resource provider computer 106 may provide the interaction data to transmission computer 108. In some embodiments, resource provider computer 106 may be integrated with access device 104 in a single device.

[0046] The resource provider computer 106 or access device 104 can generate an authorization request message, which can be provided to the transmitting computer 108 during the interaction for authorization of the interaction.

[0047] The transmitting computer 108 can be any computer used to receive and forward authorization messages according to embodiments of the present invention. In one embodiment, the transmitting computer 108 can be a computer of an acquisition entity that enables a resource provider to perform a specific type of interaction. The transmitting computer 108 can receive authorization request messages from the resource provider computer 106 and can forward the messages to the network processing computer 110.

[0048] The network processing computer 110 can be any computer or server computer that processes interactions according to embodiments of the present invention. For example, the network processing computer 110 can be a computer on an interaction processing network such as VisaNet, and can be configured to receive, read, analyze, store, and retrieve interaction data, and determine appropriate actions based on predetermined logic. The network processing computer 110 can analyze the authorization request message to determine whether the message includes a token. If the network processing computer 110 determines that the authorization request message includes a token, the network processing computer 110 provides the token to a token store and retrieves an account identifier (e.g., PAN) corresponding to the token (e.g., represented by the token). The network processing computer 110 can then replace the token with the account identifier in the authorization request message.

[0049] Network processing computer 110 can determine authorizing entity computer 112 based on data in the authorization request message. For example, network processing computer 110 can analyze an account identifier and determine that the first six digits of the account identifier include an Issuer Identifier (IIN), which specifies the authorization system associated with the account represented by the account identifier. In one embodiment, authorizing entity computer 112 may be a computer of an issuing entity that issues credentials and / or account holder cards to users, such as banks, government agencies, secure networks, etc. When determining the authorizing entity computer, transaction processing computer 110 can determine the address of authorizing entity computer 112 so that the authorization request message can be routed to authorizing entity computer 112 for authorized interaction.

[0050] The authorizing entity computer 112 can be any computer or server computer used to process the interaction and determine whether to authorize the interaction according to embodiments of the invention. The authorizing entity computer 112 can be operated and / or maintained by the authorizing entity. Upon receiving an authorization request message, the authorizing entity computer 112 can determine whether to authorize the interaction. For example, the authorizing entity computer 112 can determine the authorization result based on data contained in the authorization request message. For example, the data may include an account identifier or PAN associated with the availability of funds or credit, which may be compared to an interaction value (e.g., transaction amount). The authorizing entity computer 112 can evaluate the received data and determine the authorization result as "approved" or "rejected".

[0051] Before further describing specific systems and methods for performing efficient interactive processing using confidentiality within system 100, a brief description of how interactive processing continues in the interactive infrastructure will be provided for context, based on some embodiments.

[0052] A user can use user device 102 to interact (e.g., transact) at the resource provider's location. The interaction can be a payment transaction (e.g., for purchasing goods or services), an access transaction (e.g., for accessing a transportation system), or any other suitable transaction. User device 102 can interact with access device 104 at the resource provider's location associated with resource provider computer 106. For example, a user can tap user device 102 against the NFC reader of access device 104, or otherwise bring user device 102 into near-field communication range with access device 104 to perform a contactless interaction. Alternatively, in other cases, a user can electronically indicate an interaction value to the resource provider, for example, through online interaction. In some cases, user device 102 can transmit an account identifier, such as a token, to access device 104.

[0053] For authorized interaction, an authorization request message may be generated by access device 104 or resource provider computer 106, and then forwarded to transport (e.g., acquiring) computer 108. Upon receiving the authorization request message, it may be sent to network processing computer 110. Network processing computer 110 then forwards the authorization request message to the corresponding authorization entity computer 112 associated with the user account of the user device 102.

[0054] After receiving the authorization request message, the authorizing entity computer 112 can send an authorization response message back to the network processing computer 110 to indicate whether the current interaction is authorized (or unauthorized). The network processing computer 110 then forwards the authorization response message back to the transport computer 108. In some embodiments, even if the authorizing entity computer 112 has authorized the interaction, the network processing computer 110 may refuse the interaction, for example, based on the value of a fraud risk score. The transport computer 108 then sends a response message back to the resource provider computer 106.

[0055] After receiving the authorization response message, the resource provider computer 106 can then provide the authorization response message to the user. For example, the response message can be displayed by the access device 104 or printed on a physical receipt. Alternatively, the resource provider can provide the user device 102 with a webpage or other instructions for the authorization response message as a virtual receipt. The receipt may include interactive data for interaction.

[0056] At the end of the day, routine clearing and settlement processing can be performed by the network processing computer 110. The clearing process is the exchange of financial details between the acquiring party and the authorizing entity to facilitate posting to the user's payment account and verifying the user's settlement position.

[0057] Figure 2 A block diagram of an access device 200 according to some embodiments is shown. An exemplary access device 200 may include a processor 204. The processor 204 may be coupled to a memory 202, a network interface 206, an input element 210, an output element 212, and a computer-readable medium 208. The computer-readable medium 208 may include a certificate verification module 208A, an encryption module 208B, and another suitable module.

[0058] Memory 202 can be used to store data and code. Memory 202 can be coupled internally or externally to processor 204 (e.g., a cloud-based data storage device) and can include any combination of volatile and / or non-volatile memory (such as RAM, DRAM, ROM, flash memory, or any other suitable memory device). For example, memory 202 can store interactive values, interactive data, certificates, etc.

[0059] One or more input elements 210 may include any suitable device capable of inputting data into the access device 200. Examples of input elements 210 include buttons, touchscreens, touchpads, microphones, etc. A user may use one or more input elements 210 to provide data to the access device 200. For example, a user may input confidential information into the access device 200 via one or more input elements 210 (e.g., a keyboard).

[0060] One or more output elements 212 may include any suitable means capable of outputting data. Examples of output elements 212 may include a display screen, a speaker, and a data transmission device. For example, output element 212 may include a display screen capable of displaying response values ​​to a user of access device 200.

[0061] Computer-readable medium 208 may include code executable by processor 204 to perform a method comprising: determining an interaction value associated with an interaction by a contactless access device; prompting a user to operate a user device for a confidentiality by the contactless access device in response to determining the interaction value; receiving a confidentiality from the user by the contactless access device; after receiving the confidentiality from the user, receiving initial communication from the user device via a wireless communication medium by the contactless access device; receiving a user device certificate including a public key from the user device by the contactless access device; verifying the user device certificate by the contactless access device; and connecting at least a confidentiality and a non-confidentiality access device. A predictable number is used to form a connection value; the connection value is encrypted by a contactless access device using a public key; the encrypted connection value is transmitted by the contactless access device to a user device via a wireless communication medium, wherein the user device decrypts the encrypted connection value using a private key corresponding to the public key, verifies an unpredictable number, verifies a secret by comparing the secret with another secret stored in the user device, determines whether to approve the interaction based at least on the verification of the secret, generates a user device interaction authorization result, and then provides the user device interaction authorization result to the contactless access device; and the contactless access device receives the user device interaction authorization result from the user device.

[0062] The certificate verification module 208A may include code or software executable by the processor 204 for verifying certificates. The certificate verification module 208A, in conjunction with the processor 204, can verify one or more certificates. The certificate verification module 208A, in conjunction with the processor 204, can verify certificates received from a user device during interaction.

[0063] For example, the certificate verification module 208A, in conjunction with processor 204, can verify an authorized entity certificate that includes the public key of the authorized entity certificate, wherein the authorized entity certificate is signed by a certificate authority using its private key. The certificate verification module 208A, in conjunction with processor 204, can use a stored or otherwise available certificate authority public key to verify the signature on the authorized entity certificate. The certificate verification module 208A, in conjunction with processor 204, can verify signatures with public keys in any suitable manner known to those skilled in the art.

[0064] Furthermore, the certificate verification module 208A, in conjunction with the processor 204, can verify a user device certificate that includes a public key (e.g., a user device public key, and in some embodiments, a confidential encryption public key), wherein the user device certificate is signed by an authorized entity using an authorized entity's private key corresponding to the authorized entity's public key. The certificate verification module 208A, in conjunction with the processor 204, can use the authorized entity's public key obtained from the authorized entity's certificate to verify the signature on the user device certificate.

[0065] Encryption module 208B may include code or software executed by processor 204 for encrypting data. Encryption module 208B, in conjunction with processor 204, can encrypt secrets (e.g., secrets obtained from a user via input element 210). For example, encryption module 208B, in conjunction with processor 204, can encrypt secrets using a public key obtained from a user device certificate. In some embodiments, encryption module 208B, in conjunction with processor 204, can encrypt secrets using a user device public key obtained from a user device certificate. In other embodiments, encryption module 208B, in conjunction with processor 204, can encrypt secrets using a secret encryption public key obtained from a user device certificate. Encryption module 208B, in conjunction with processor 204, may attempt to first utilize the secret encryption public key from the user device certificate, and then, if the user device certificate does not include a secret encryption public key, encryption module 208B, in conjunction with processor 204, can utilize the user device public key included in the user device certificate.

[0066] Network interface 206 may include an interface that allows access device 200 to communicate with an external computer. Network interface 206 enables access device 200 to transmit data to and from another device (e.g., a user device, a resource provider computer, etc.). Some examples of network interface 206 may include a modem, a physical network interface (e.g., an Ethernet card or other network interface card (NIC)), a virtual network interface, a communication port, a PCMCIA slot, and a card, etc. Wireless protocols enabled by network interface 206 may include Wi-Fi. TM Data transmitted via network interface 206 may be in the form of signals, which may be electrical signals, electromagnetic signals, optical signals, or any other signals that can be received by an external communication interface (collectively, "electronic signals" or "electronic messages"). These electronic messages, which may include data or instructions, may be provided between network interface 206 and other devices via a communication path or channel. As mentioned above, any suitable communication path or channel may be used, such as wires or cables, optical fibers, telephone lines, cellular links, radio frequency (RF) links, WAN or LAN networks, the Internet, or any other suitable medium.

[0067] Figure 3 A block diagram of a user device 300 according to an embodiment is shown. The exemplary user device 300 may include a processor 304. The processor 304 may be coupled to a memory 302, a network interface 306, an input element 310, an output element 312, and a computer-readable medium 308. The computer-readable medium 308 may include a confidentiality authentication module 308A and another suitable module.

[0068] Memory 302 can be used to store data and code. Memory 302 can be coupled internally or externally to processor 304 (e.g., a cloud-based data storage device) and can include any combination of volatile and / or non-volatile memory (such as RAM, DRAM, ROM, flash memory, or any other suitable memory device). For example, memory 302 can store user device certificates, etc.

[0069] Computer-readable medium 308 may include code executable by processor 304 for performing a method comprising: providing initial communication from a user device via a wireless communication medium upon entering communication range with a contactless access device during an interaction; receiving a read log command from the contactless access device by the user device, wherein the read log command requests at least one or more certificates from the user device; obtaining at least one or more certificates from memory by the user device; generating a read log response message including at least one or more certificates by the user device; and providing the read log response message to the contactless access device in response to the read log command, wherein the one or more certificates include a user device certificate containing a public key. The contactless access device verifies the user device certificate, connects at least a confidential and unpredictable number provided by the user of the user device to the contactless access device to form a connection value, encrypts the connection value with a public key, and transmits the encrypted connection value to the user device via a wireless communication medium; the user device receives the encrypted connection value from the contactless access device; the user device decrypts the encrypted connection value using a private key corresponding to the public key; the user device verifies the confidentiality included in the connection value by comparing the confidentiality with another confidentiality stored in the user device; the user device generates a user device interaction authorization result based on whether the interaction is approved at least according to the verification of the confidentiality; and the user device provides the user device interaction authorization result to the contactless access device.

[0070] The confidentiality verification module 308A may include code or software executable by the processor 304 for verifying confidentiality. The confidentiality verification module 308A, in conjunction with the processor 304, can verify confidentiality received from the access device. The confidentiality verification module 308A, in conjunction with the processor 304, can obtain confidentiality from a connection value obtained from the user device 300 by decrypting the encrypted connection value using the user device's private key or a confidentiality encryption private key.

[0071] After obtaining a secret, the confidentiality verification module 308A, in conjunction with the processor 304, can verify the secret included in the connection value by comparing the secret with another secret stored in the user device 300. For example, the confidentiality verification module 308A, in conjunction with the processor 304, can obtain a secret stored in the user device 300 (e.g., stored in memory). The confidentiality verification module 308A, in conjunction with the processor 304, can output an indication to the user device 300 indicating whether the secret matches a stored secret. The user device 300 can then use the indication of whether the secret matches a stored secret to notify an access device (e.g., a contactless access device) of an indication (in the form of a user device interactive authorization result, as described further in detail herein).

[0072] Network interface 306 may include an interface that allows user device 300 to communicate with an external computer. Network interface 306 enables user device 300 to transmit data to and from another device (e.g., user device, resource provider computer, etc.). Some examples of network interface 306 may include a modem, a physical network interface (e.g., an Ethernet card or other network interface card (NIC)), a virtual network interface, a communication port, a PCMCIA slot, and a card, etc. Wireless protocols enabled by network interface 306 may include Wi-Fi. TM Data transmitted via network interface 306 may be in the form of signals, which may be electrical signals, electromagnetic signals, optical signals, or any other signals that can be received by an external communication interface (collectively, "electronic signals" or "electronic messages"). These electronic messages, which may include data or instructions, may be provided between network interface 306 and other devices via a communication path or channel. As mentioned above, any suitable communication path or channel may be used, such as wires or cables, optical fibers, telephone lines, cellular links, radio frequency (RF) links, WAN or LAN networks, the Internet, or any other suitable medium.

[0073] Embodiments may use the systems and devices described herein to perform at least confidential interactive processing. Figures 4-5 illustrate some examples of such methods. In some embodiments, user device 402 and user device 502 may include Figure 1 and 3 Each of the user devices 102 or 300. In some embodiments, access device 404 and access device 504 may each include Figure 1 and 2 Access device 104 or access device 200.

[0074] Figure 4 illustrates a flowchart of a contactless interaction using a confidentiality verification process according to an embodiment. The method shown in Figure 4 will be described in the context of a single-tap contactless transaction flow that supports offline confidentiality, such as a PIN. However, it should be understood that the invention can be applied to other situations (e.g., performing access interactions to allow a user to access a secure location while verifying confidentiality, such as a password).

[0075] Prior to step 406, the user of user device 402 and the resource provider of access device 404 may initiate an interaction.

[0076] At step 406, access device 404 may obtain an interaction value associated with the interaction. The interaction value may be an amount, such as a transaction amount of $100. In some embodiments, access device 404 may obtain the interaction value from a resource provider's computer, as input from a resource provider, as input from an access device operator, etc. In other embodiments, access device 404 may obtain the interaction value by determining it based on interaction data associated with the interaction. For example, access device 404 may determine the interaction value based on one or more values ​​associated with one or more items that will be provided to the user device 402 upon completion of the interaction.

[0077] In some embodiments, access device 404 may determine whether to prompt the user of user device 402 for a secret. The secret may be a password, a one-time password, a personal identification number (PIN), etc.

[0078] For example, access device 404 can compare the interaction value with a threshold. The threshold can be a predetermined value that requires authentication of a secret. For example, the threshold could be $25. If the interaction value is greater than the threshold, access device 404 can determine that a secret needs to be obtained from the user and authenticated using user device 402. Then, access device 404 can proceed to step 408. If the interaction value is less than the threshold, access device 404 can determine that processing the interaction does not require a secret. In this case, access device 404 can then proceed with a secretless interaction with user device 402.

[0079] At step 408, after obtaining the interaction value, the access device 404 may prompt the user to operate the user device 402 regarding the confidentiality. For example, the access device 404 may use an input / output display or other suitable means to prompt the user to provide the confidentiality as input to the access device 404.

[0080] In some embodiments, if the user's device does not support offline confidentiality verification, the user may be offered the option to skip offline confidentiality input. In this case, in some embodiments, the access device 404 may present the user with an "Enter" or "Skip" option. In other embodiments, if the user device does not support confidentiality verification, the access device 404 may request the user to bring the user device into communication range (e.g., tap) to continue processing without verifying the confidentiality.

[0081] At step 410, after prompting the user of user device 402 to enter a secret, access device 404 can receive the secret from the user.

[0082] At step 412, after receiving the confidential information from the user, the access device 404 may prompt the user to bring the user device 402 into the communication range with the access device 404. The communication range may be a near-field communication range (e.g., less than 2 feet, less than 1 foot, less than 5 inches, less than 4 cm inches, or any other suitable near-field communication range based on the type of communication channel used by the user device 402 and the access device 404).

[0083] Based on the prompt provided by the access device 404 in step 412, the user of the user device 402 can bring the mobile device 402 into the communication range with the access device 404.

[0084] Once the user device 402 is within communication range of the access device 404, the access device 404 can establish a contactless connection with the user device 402 (e.g., via radio).

[0085] After receiving the secret from the user, the access device 404 may receive initial communication from the user device 402 via a wireless communication medium, as described in the initial communication round during steps 414-420.

[0086] In steps 414-420, access device 404 and user device 402 can perform application selection. For example, access device 404 can determine which applications both user device 402 and access device 404 support.

[0087] At step 414, when the access device 404 detects the presence of the user device 402, the access device 404 generates an available application request message (e.g., a “select command”).

[0088] At step 416, access device 404 may provide user device 402 with an available application request message to request information about which interactive applications (e.g., a list of AIDs) are available on user device 402. For example, access device 404 may provide a Proximity Payment System Environment (PPSE) selection command message to user device 402.

[0089] At step 418, after receiving the available application request message, user device 402 can obtain a list of available application identifiers (AIDs) stored by user device 402.

[0090] At step 420, after obtaining the list of available application identifiers, user device 402 can respond to the available application request message by sending an available application response message including the list of available application identifiers to access device 404. In some embodiments, user device 402 may provide file control information (FCI) to access device 404.

[0091] At step 422a, the access device 404 can then select a suitable application from the list of applications received in the available application response message. For example, the access device 404 can select an AID from the available AIDs.

[0092] At step 422b, access device 404 may then generate an application selection message including the selected AID (which may be a “Select AID” command).

[0093] At step 424, access device 404 may provide an application selection message to user device 402.

[0094] At step 426, after receiving the application selection message, user device 402 may then generate an application selection response indicating confirmation of the selected application. In some embodiments, the application selection response message may further include a request for interaction data that may be required to perform the interaction using the selected application / AID. The request may include a list of interaction data identifiers, and the list may be in the form of a Processing Option Data Object List (PDOL).

[0095] At step 428, after generating the application selection response message, user device 402 may provide the application selection response message to access device 404.

[0096] At step 430, after receiving the application selection response message, access device 404 initiates application processing. For example, access device 404 may generate a request message requesting user device 402 to indicate the selected application and the data (e.g., a list of data elements) used by the supported functions. In some embodiments, access device 404 may generate a Get Processing Option (GPO) command. Access device 404 may also include interactive information requested by user device 402 (e.g., PDOL-related data) in the GPO command.

[0097] At step 432, after generating the GPO command, the access device 404 provides the GPO command to the user device 402.

[0098] At step 434, after receiving the GPO command, user device 402 can generate dynamic interaction processing information using at least some of the received interaction data, and generate a GPO response message including the dynamic interaction processing information. In some embodiments, the GPO response message may include a set of interaction processing information. The interaction processing information may include one or more application file locators (AFLs), which can be used by access device 404 as file addresses to read account data stored on user device 402.

[0099] At step 436, after generating the GPO command, the access device 404 provides a GPO response to the access device 404.

[0100] Through steps 438-444, access device 404 can read application data from user device 402. Specifically, at step 438, access device 404 can generate a read record request message to read certificate data stored at user device 402.

[0101] In step 440, after generating the read record request message, the access device 404 provides the read record request message to the user device 402.

[0102] At step 442, after receiving the read log request message, user device 402 may generate a read log response message including one or more certificates. The certificates may be data accessible at the AFL location. In some embodiments, the read log response message may include a user device certificate. The user device certificate includes the user device public key and may be signed by an authorized entity's private key. In some embodiments, the read log response message may also include an authorized entity certificate. The authorized entity certificate includes an authorized entity public key and may be signed by a Certificate Authority (CA).

[0103] At step 444, after generating the read log response message, the user device 402 provides the read log response message to the access device 404 in response to the read log request message.

[0104] Therefore, access device 404 receives from user device an authorized entity certificate including the issuer's public key and signed by the certificate authority's private key, and a user device certificate including the user device's public key and signed by the issuer's private key.

[0105] At step 446, after obtaining the certificate, access device 404 can verify the authorized entity certificate. Access device 404 can verify the authorized entity certificate using a certificate authority public key stored on access device 404 and / or easily retrieved from a trusted online source. After verifying the authorized entity certificate, access device 404 can utilize the now-verified authorized entity public key included in the authorized entity certificate.

[0106] In some embodiments, if the authorized entity certificate is invalid, the access device 404 may stop communication with the user device 402 and terminate the transaction.

[0107] At step 448, after verifying the authorized entity certificate, access device 404 may verify the user device certificate. Access device 404 may use the authorized entity public key obtained from the valid authorized entity certificate to verify the user device certificate. After verifying the user device certificate, access device 404 may utilize the user device public key now verified and included in the user device certificate.

[0108] In some embodiments, if the user device certificate is invalid, the access device 404 may interrupt communication with the user device 402.

[0109] In some embodiments, the user device certificate may further include a cryptographic public key. The cryptographic public key can be used to encrypt secrets and may be a different public key from the user device public key. In some embodiments, access device 404 may use the cryptographic public key to encrypt only the secret. The cryptographic public key may be associated with a cryptographic private key stored on user device 402, which is configured to decrypt the encrypted secret encrypted with the cryptographic public key.

[0110] At step 450, after verifying the certificate received from user device 402, the access device may generate an acquisition query command. The acquisition query command may instruct user device 402 to generate an unpredictable number (UN) and return the unpredictable number.

[0111] At step 452, after generating the query command, the access device 404 can provide the query command to the user device 402.

[0112] At step 454, after receiving the query command, user device 402 can generate unpredictable numbers. For example, user device 402 can generate random or pseudo-random numbers that are difficult or impossible to predict. For example, user device 402 can generate unpredictable numbers using hexadecimal f30d, 815aa652, etc.

[0113] At step 456, after generating an unpredictable number in response to an inquiry command, user device 402 may provide the unpredictable number to access device 404.

[0114] At step 458, after receiving the unpredictable number, access device 404 can combine the confidential and unpredictable numbers. For example, access device 404 can concatenate at least the confidential and unpredictable numbers to form a concatenated value. In some embodiments, access device 404 can also concatenate codes, values, timestamps, etc., with the confidential and unpredictable numbers. For example, access device 404 can concatenate as follows: Concatenated_Value = ['7F' | Secret_Block | Unpredictable_Number].

[0115] In some embodiments, access device 404 may include padding or random padding (e.g., padding value) into the connection value to increase the length of the value (e.g., data size) to meet the length requirements of the user device public key.

[0116] At step 460, after obtaining the connection value, access device 404 can encrypt the connection value using the user device public key (or, if available, the ICC PIN encryption public key). For example, access device 404 can encrypt the following data block ['7F' | Secret_Block | Unpredictable_Number | Padding]. Therefore, access device 404 can perform the following operations:

[0117] At step 462, after encrypting the connection value, the access device 404 can generate a confidential verification request message that includes the encrypted connection value.

[0118] At step 464, after generating the confidentiality verification request message, the access device 402 can provide the confidentiality verification request message to the user device 402. For example, the access device can transmit an encrypted connection value via a wireless communication medium.

[0119] At step 466, after receiving the confidentiality verification request message, user device 402 can use the user device private key corresponding to the user device public key to decrypt the encrypted connection value.

[0120] At step 468, after decrypting the encrypted connection value to obtain a connection value that includes unpredictable numbers and secrets, user device 402 can verify the unpredictable numbers.

[0121] At step 470, after verifying the unpredictable number, user device 402 can verify the secret. For example, user device 402 can verify the secret by comparing it with another secret stored in user device 402.

[0122] At step 472, after verifying the secret, user device 402 determines whether the interaction is approved based at least on the verification of the secret. For example, if the secret has been verified, user device 402 may determine to approve the interaction. If the secret has not been verified, user device 402 may determine to reject the interaction.

[0123] At step 474, after determining whether the interaction is approved, user device 402 may generate or otherwise produce a user device interaction authorization result. The user device interaction authorization result may indicate whether user device 402 has approved the interaction. For example, if user device 402 determines to approve the interaction at step 472, then the user device 402 interaction authorization result may indicate that user device 402 has approved the interaction.

[0124] At step 476, after generating the user device interaction authorization result, the user device may provide the user device interaction authorization result to the access device 404 in a confidential verification response message.

[0125] At step 478, after receiving the confidentiality verification response message, the access device 404 generates a password request message.

[0126] At step 480, after generating the password request message, the access device 404 provides the password request message to the user device 402.

[0127] At step 482, after receiving the password request message, user device 402 can generate a password. User device 402 can generate the password in any suitable manner known to those skilled in the art.

[0128] At step 484, after generating the password, user device 402 provides the password to access device 404.

[0129] In some embodiments, user device 402 may provide the user device interaction authorization result and password to access device 404 in a single message. For example, after verifying the secret, user device 402 may generate a user device interaction authorization result indicating that the interaction has been approved. Once the interaction is approved, user device 402 may generate a password. Then, user device 402 may provide both the password and the user device interaction authorization result to access device 404.

[0130] At step 486, after receiving the password, access device 404 can verify that the user device's interaction authorization result indicates that the secret has been verified and the interaction has been approved by user device 402. If access device 404 determines that user device 402 refuses the interaction, access device 404 can exit the interaction process and can display a notification to the user regarding user device 402's refusal of the interaction or the secret being incorrect. In some embodiments, access device 404 can request the user to enter another secret using user device 402 for verification.

[0131] At step 488, after receiving the password, the access device 404 can generate an authorization request message that includes the password and interactive data with interactive values.

[0132] After generating the authorization request message, the access device 404 may provide the authorization request message to the resource provider computer (not shown) for further processing of the interaction.

[0133] The resource provider computer provides an authorization request message to the transmitting computer, which then provides the authorization request message to the network processing computer. The network processing computer can then provide the authorization request message to the authorizing entity computer for authorization interaction.

[0134] Upon receiving an authorization request message, the authorizing entity computer can determine whether to authorize the interaction. The authorizing entity computer can generate an indication of whether the interaction is authorized. The authorizing entity computer can generate an authorization response message that includes at least the indication of whether the interaction is authorized.

[0135] Authorized entity computers can provide authorization response messages to resource provider computers via network processing and transmission computers.

[0136] Upon receiving an authorization response message, the resource provider computer may provide the access device 404 with an authorization response message, or an indication of whether the interaction is authorized.

[0137] Access device 404 may display or otherwise notify the user and / or user device 402 of the authorization response message and / or an indication of whether the interaction is authorized.

[0138] The embodiments of this disclosure offer numerous advantages. For example, the user device and access device only need to be brought into communication range once to communicate and verify confidentiality. However, in previous methods, the user device and access device first needed to be brought into communication range to convey data about the interaction, and then again after the access device requested the user's PIN to verify it. The embodiments reduce the number of initial communication channel creation steps by 50%.

[0139] Although the steps of the flowcharts and method flows described above are shown or described in a specific order, it should be understood that embodiments of the present invention may include methods with steps in a different order. Furthermore, steps may be omitted or added, and they may still be present in embodiments of the present invention.

[0140] Any software component or function described in this application may be implemented as software code executed by a processor using any suitable computer language such as Java, C, C++, C#, Objective-C, Swift, or a scripting language such as Perl or Python, employing techniques such as conventional or object-oriented methods. The software code may be stored as a series of instructions or commands on a computer-readable medium for storage and / or transmission. Suitable media include random access memory (RAM), read-only memory (ROM), magnetic media (e.g., hard disk drive or floppy disk), or optical media (e.g., optical disc (CD) or digital versatile optical disc (DVD)), flash memory, and so on. The computer-readable medium may be any combination of such storage or transmission means.

[0141] Such programs can also be encoded and transmitted using carrier signals suitable for transmission over wired, optical, and / or wireless networks conforming to various protocols, including the Internet. Therefore, a computer-readable medium according to an embodiment of the invention can be created using data signals encoded with such programs. Computer-readable media encoded with program code can be packaged with a compatible device or provided separately from other devices (e.g., downloaded via the Internet). Any such computer-readable medium can reside on or within a single computer product (e.g., a hard disk drive, CD, or an entire computer system) and can exist on or within different computer products within a system or network. A computer system may include a monitor, printer, or other suitable display for providing a user with any of the results mentioned herein.

[0142] The above description is illustrative and not restrictive. Many variations of the invention will become apparent to those skilled in the art after reading this disclosure. Therefore, the scope of the invention should not be determined by reference to the foregoing description, but rather by reference to the pending claims together with their full scope or equivalents.

[0143] Without departing from the scope of the invention, one or more features from any embodiment may be combined with one or more features from any other embodiment.

[0144] As used herein, unless explicitly indicated otherwise, the terms “a,” “an,” or “the” are intended to mean “at least one / a kind.”

Claims

1. A method comprising: The interaction value associated with the interaction is determined by the contactless access device; In response to determining the interaction value, the contactless access device prompts the user to operate the user device for confidentiality purposes; The confidential information is received from the user by the contactless access device; After receiving the confidential information from the user, the contactless access device receives initial communication from the user device via a wireless communication medium. The contactless access device receives a user device certificate, including a public key, from the user device. The user device certificate is verified by the contactless access device; The contactless access device connects at least the confidential and unpredictable numbers to form a connection value; The connection value is encrypted by the contactless access device using the public key; The contactless access device transmits an encrypted connection value to the user device via the wireless communication medium, wherein the user device decrypts the encrypted connection value with a private key corresponding to the public key, verifies the unpredictable number, verifies the secret by comparing the secret with another secret stored in the user device, determines whether the interaction is approved based at least on the verification of the secret, generates a user device interaction authorization result, and then provides the user device interaction authorization result to the contactless access device. as well as The contactless access device receives the user device's interactive authorization result from the user device.

2. The method of claim 1, wherein the wireless communication medium uses NFC.

3. The method according to claim 1, wherein the confidentiality is a PIN, password, biometric, one-time password, access code, or username-password pair.

4. The method of claim 1, wherein after determining the interaction value, the method further comprises: The contactless access device determines whether to prompt the user to operate the user device based on the interaction value and a predetermined threshold.

5. The method of claim 1, wherein after receiving the confidential information, the method further comprises: The contactless access device prompts the user to bring the user device into the communication range of the contactless access device; The contactless access device generates a read log command message requesting at least one or more certificates from the user device; as well as When the user device is within communication range of the contactless access device, the contactless access device provides the read log command message to the user device, wherein the user device obtains at least one or more certificates, generates a read log response message including at least one or more certificates, and provides the read log response message to the contactless access device, wherein the one or more certificates include the user device certificate.

6. The method of claim 1, wherein the user device is a card.

7. The method of claim 1, wherein the public key is a user device public key, and wherein the method further comprises: The contactless access device receives an authorization entity certificate, including the authorization entity's public key, from the user device.

8. The method of claim 7, wherein the authorized entity certificate is signed by a certificate authority private key, and wherein, before verifying the user device certificate, the method further comprises: The authorized entity certificate is verified by the contactless access device using a certificate authority public key that can be used by the contactless access device and corresponds to the certificate authority private key; as well as If the authorized entity certificate is valid, the contactless access device obtains the authorized entity public key from the authorized entity certificate.

9. The method of claim 8, wherein the user device certificate is signed by an authorized entity private key corresponding to the authorized entity's public key, and wherein verifying the user device certificate further comprises: The contactless access device uses the public key of the authorized entity to verify the user device certificate; as well as If the user device certificate is valid, the contactless access device obtains the user device public key from the user device certificate.

10. A contactless access device, comprising: processor; as well as A computer-readable medium coupled to the processor, the computer-readable medium including code executable by the processor to perform a method comprising the following steps: Determine the interaction value associated with the interaction; In response to determining the interaction value, the user is prompted to operate the user device for confidentiality purposes; Receive the confidential information from the user; After receiving the secret from the user, initial communication is received from the user device via a wireless communication medium. Receive a user device certificate including a public key from the user device; Verify the user device certificate; Connect at least the aforementioned confidential and unpredictable numbers to form a connection value; Encrypt the connection value using the public key; The encrypted connection value is transmitted to the user device via the wireless communication medium, wherein the user device decrypts the encrypted connection value with a private key corresponding to the public key, verifies the unpredictable number, verifies the secret by comparing the secret with another secret stored in the user device, determines whether the interaction is approved based at least on the verification of the secret, generates a user device interaction authorization result, and then provides the user device interaction authorization result to the contactless access device. as well as Receive the user device interaction authorization result from the user device.

11. The contactless access device of claim 10, wherein the public key is a user device public key, and wherein the method further comprises: Receive an authorization entity certificate from the user device, which includes the authorization entity's public key and is signed by the certificate authority's private key. The authorized entity certificate is verified using a certificate authority public key that can be used with the contactless access device and corresponds to the certificate authority's private key; as well as If the authorized entity certificate is valid, then the authorized entity public key is obtained from the authorized entity certificate.

12. The contactless access device of claim 11, wherein the user device certificate is signed by an authorized entity private key corresponding to the authorized entity's public key, and wherein verifying the user device certificate further comprises: The user device certificate is verified using the public key of the authorized entity. as well as If the user device certificate is valid, the user device public key is obtained from the user device certificate.

13. The contactless access device of claim 10, wherein the public key is a confidential encryption public key, and wherein the user device certificate includes the confidential encryption public key and the user device public key.

14. The contactless access device of claim 10, wherein connecting at least the confidentiality and the unpredictable number to form the connection value further comprises: The secret, the unpredictable number, and the padding value are joined to form the join value, wherein the padding value increases the length of the join value to be equal to the length of the encrypted data specified by the public key.

15. The contactless access device according to claim 10, wherein after receiving the user device's interactive authorization result, the method further comprises: Generate an authorization request message that includes at least the interaction value and interaction data associated with the interaction; as well as The authorization request message is provided to a resource provider computer, wherein the resource provider computer provides the authorization request message to a transmission computer, the transmission computer provides the authorization request message to a network processing computer, and the network processing computer provides the authorization request message to an authorization entity computer for authorization of the interaction.

16. The contactless access device of claim 15, wherein the method further comprises: The network processing computer, the transmission computer, and the resource provider computer receive an authorization response message from the authorization entity computer, wherein the authorization response message is created by the authorization entity computer and includes an indication of whether the interaction is authorized.

17. The contactless access device of claim 10, wherein the method further comprises: Generate an interrogation command message requesting the unpredictable number from the user device; The query command message is provided to the user device, wherein the user device obtains the unpredictable number and provides the unpredictable number to the contactless access device; and Receive the unpredictable numbers from the user device.

18. A method comprising: When entering the communication range of the contactless access device during interaction, the user device provides initial communication from the user device via a wireless communication medium; The user device receives a read log command from the contactless access device, wherein the read log command requests at least one or more certificates from the user device; The user device obtains at least one or more certificates from the memory; The user device generates a read record response message that includes at least one or more of the certificates; In response to the read log command, the user device provides the read log response message to the contactless access device, wherein the one or more certificates include a user device certificate containing a public key, wherein the contactless access device verifies the user device certificate, at least connects a confidential and unpredictable number provided to the contactless access device by the user of the user device to form a connection value, encrypts the connection value with the public key, and transmits the encrypted connection value to the user device through the wireless communication medium; The encrypted connection value is received by the user device from the contactless access device; The user device uses the private key corresponding to the public key to decrypt the encrypted connection value; The user device verifies the secret included in the connection value by comparing the secret with another secret stored in the user device; The user device generates an interaction authorization result based on whether it approves the interaction, at least according to verification of the confidentiality; and The user device provides the user device interaction authorization result to the contactless access device.

19. The method of claim 18, wherein after providing the user device interaction authorization result to the contactless access device, the contactless access device generates an authorization request message including at least an interaction value and interaction data associated with the interaction, and provides the authorization request message to the resource provider's computer, wherein, The resource provider computer provides the authorization request message to the transmission computer, the transmission computer provides the authorization request message to the network processing computer, and the network processing computer provides the authorization request message to the authorization entity computer for authorization of the interaction.

20. The method of claim 18, further comprising: The user device receives an inquiry command message requesting the unpredictable number from the contactless access device; The unpredictable number is obtained from the user device; as well as The unpredictable numbers are provided to the contactless access device by the user device.

Images