Systems and methods for virtual physical transactions
By integrating virtual card information on contactless cards for physical transactions, the system addresses security vulnerabilities, allowing secure and safe use of temporary card numbers in physical transactions.
Patent Information
- Application Number
- PCT/US2026/026549
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-05
- Filing Date
- 2026-05-04
- Publication Date
- 2026-11-12
AI Technical Summary
Current contactless card technologies are vulnerable to security breaches and cannot seamlessly integrate virtual card information with physical transaction devices, limiting their use to digital transactions only.
Implementing virtual card information directly on contactless cards for use in physical transactions, enabling secure authentication and encryption processes using temporary card numbers that can be updated or replaced, reducing the risk of unauthorized access to sensitive card data.
Enables secure and safe use of virtual card numbers in physical transactions, protecting against data exposure and enhancing security in contactless card systems.
Smart Images

Figure US2026026549_12112026_PF_FP_ABST
Abstract
Description
Docket No. 1988.0497WOSYSTEMS AND METHODS FOR VIRTUAL PHYSICAL TRANSACTIONS CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority of U. S. Patent Application Serial No. 19 / 198,531, filed May 5, 2025, the disclosure of which is incorporated herein by reference in its entirety.BACKGROUND
[0002] Contactless card products have become so universally well-known and ubiquitous that they have fundamentally changed the manner in which financial transactions and dealings are viewed and conducted in society today. Contactless card products are most commonly represented by plastic or metal card-like members that are offered and provided to customers through credit card issuers (such as banks and other financial institutions). With a card, an authorized customer or cardholder is capable of purchasing services and / or merchandise without an immediate, direct exchange of cash.
[0003] Data security and transaction integrity are of critical importance to businesses facilitating these transactions and to the customers. This need continues to grow as electronic transactions performed with contactless cards constitute an increasingly large share of commercial activity. Although contactless cards are more secure than previous transaction card technologies, merchant systems are still vulnerable to malicious attacks that may expose cardholder information. For example, contactless card numbers, expiration dates, etc. used in physical transactions at a merchant location, for instance, via a point-of-sale (POS) device at a merchant checkout, may be stored on a merchant network. A security breach of this merchant network may allow unwanted exposure of contactless card data used as part of a physical transaction at the merchant location via the POS device.
[0004] Accordingly, there is a need to provide businesses and users with an appropriate solution that overcomes current deficiencies to provide data security, authentication, and verification for contactless cards, including when used in a transaction with a physical transaction device.BRIEF SUMMARY
[0005] A system for virtual physical transactions is disclosed herein. In some embodiments, the system includes at least one server device comprising a processor and a memory storing instructions that, when executed by the processor, cause the processor to perform various operations. For example, in some embodiments, the processor is configured to receive a messageDocket No. 1988.0497WOfrom a mobile device associated with a contactless card to activate a virtual physical transaction for the contactless card. In some embodiments, the processor is configured to generate virtual information for the contactless card, the virtual information comprising at least one virtual card number for the virtual physical transaction. In some embodiments, the processor is configured to transmit at least a portion of the virtual information to the mobile device for storage on the contactless card. In some embodiments, the processor is configured to receive a message from a physical transaction device to authenticate a physical transaction with the physical transaction device for the contactless card. In some embodiments, the processor is configured to authenticate the physical transaction using the virtual information.
[0006] A computer implemented method for virtual physical transactions is also disclosed herein. In some embodiments, the method includes authenticating a contactless card with a mobile device via a service provider application executed via the mobile device, the contactless card authenticated with a user account of a cardholder of the contactless card. In some embodiments, the method includes receiving a selection to activate a virtual physical transaction for the contactless card via the service provider application. In some embodiments, the method includes transmitting a message from the mobile device to a server device associated with the service provider application to activate the virtual physical transaction for the contactless card. In some embodiments, the method includes receiving, from the server device, virtual information for the contactless card, the virtual information comprising at least one virtual card number for the virtual physical transaction. In some embodiments, the method includes transmitting at least a portion of the virtual information to the contactless card.
[0007] A contactless card for virtual physical transactions is also disclosed herein. In some embodiments, the contactless card includes a processor, a wireless communication interface, and a memory storing an assigned card number, at least one virtual card number, a virtual number indicator, and instructions, that when executed by the processor, cause the processor to perform various operations. In some embodiments, the processor is configured to establish a wireless connection with a mobile device via the wireless communication interface. In some embodiments, the processor is configured to receive a virtual number from the mobile device. In some embodiments, the processor is configured to store the virtual number as the at least one virtual card number. In some embodiments, the processor is configured to receive a message from the mobile device to activate virtual physical transactions. In some embodiments, theDocket No. 1988.0497WOprocessor is configured to modify the virtual number indicator to indicate that virtual physical transactions are active.BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.
[0009] FIG. 1 illustrates an example of a system configured to operate in accordance with one embodiment.
[0010] FIG. 2 illustrates an example of a sequence flow in accordance with one embodiment.
[0011] FIG. 3 A illustrates an example of a sequence flow in accordance with one embodiment.
[0012] FIG. 3B illustrates an example of a sequence flow in accordance with one embodiment.
[0013] FIG. 3C illustrates an example of a sequence flow in accordance with one embodiment.
[0014] FIG. 4 illustrates an example of a message in accordance with one embodiment.
[0015] FIG. 5 illustrates an example of a method in accordance with one embodiment.
[0016] FIG. 6 illustrates an example of a distributed network authentication system in accordance with one embodiment.
[0017] FIG. 7 illustrates an example of a method in accordance with one embodiment.
[0018] FIG. 8 illustrates an example of a system in accordance with one embodiment.
[0019] FIG. 9 illustrates an example of a contactless card in accordance with one embodiment.
[0020] FIG. 10 illustrates an example of a contactless card component in accordance with one embodiment.
[0021] FIG. 11 illustrates an example of a sequence flow in accordance with one embodiment.
[0022] FIG. 12 illustrates an example of a mobile device in accordance with one embodiment.
[0023] FIG. 13 illustrates an example of a server device in accordance with one embodiment.
[0024] FIG. 14 illustrates an example of a system in accordance with one embodiment.
[0025] FIG. 15 illustrates an example of a system in accordance with one embodiment.
[0026] FIG. 16 illustrates an example of a sequence flow in accordance with one embodiment.
[0027] FIG. 17 illustrates an example of a sequence flow in accordance with one embodiment.Docket No. 1988.0497WO
[0028] FIG. 18 illustrates an example of a sequence flow in accordance with one embodiment.
[0029] FIG. 19 illustrates an example of a sequence flow in accordance with one embodiment.
[0030] FIG. 20 illustrates an example of a sequence flow in accordance with one embodiment.
[0031] FIG. 21 illustrates an example of a sequence flow in accordance with one embodiment.
[0032] FIG. 22 illustrates an example of a sequence flow in accordance with one embodiment.
[0033] FIG. 23 illustrates an example of a logic flow in accordance with one embodiment.
[0034] FIG. 24 illustrates an example of a logic flow in accordance with one embodiment.
[0035] FIG. 25 illustrates an example of a logic flow in accordance with one embodiment.DETAILED DESCRIPTION
[0036] Embodiments disclosed herein are generally directed to systems and methods for implementing virtual card numbers for use by contactless cards involved in a physical transaction. In general, a physical transaction involves the use of a contactless card with a physical transaction device, such as a point-of-sale (POS) device, an embedded card reader (ECR), and / or the like that requires the contactless card to come into physical contact with the physical transaction device. Physical contact includes actual physical interfacing between the contactless card and a physical transaction device and wireless communication requiring proximity of the contactless card to the physical transaction device (e.g., Bluetooth, NFC, etc.). Physical contact allows the physical transaction device to interact with the hardware and software of the contactless card to facilitate a transaction. In some examples, physical contact between the contactless card and the physical transaction device may include insertion, touching, or other physical interfacing of the contactless card with a corresponding reader element of the physical transaction device. However, physical contact does not require that the contactless card actually touch the physical transaction device, as physical contact may include bringing the contactless card within a certain distance of the physical transaction device to facilitate wireless communication between the contactless card and the physical transaction device.
[0037] Virtual transaction cards or virtual transaction card numbers are a digital-only simulation of transaction cards that may be used by consumers for computer-based transactions. Virtual transaction cards are typically associated with physical transaction cards (i.e., the tangible card provided to the user by the card service provider). By eliminating the need for physical cards, the security risks associated with physical cards are avoided, such as card skimming, the transaction card being lost or stolen, and / or the like.Docket No. 1988.0497WO
[0038] Conventional virtual cards, virtual card numbers, digital cards, and / or the like are used in computer-based transactions, such as online purchases or mobile device-based transactions. For example, a virtual card may be generated that is associated with a physical contactless card (i.e., the tangible card provided to the user by the card service provider). The virtual card exists as a file or other data structure that includes a set of virtual card information (e.g., card number, expiration date, card verification value (CVV), and / or the like) that may be used as part of a transaction. The virtual card may be loaded into a virtual wallet or other application on a mobile device. The virtual card (or card number) may be used in an online or mobile device transaction. In one example, a cardholder of a physical contactless card may have a corresponding virtual card associated with the physical contactless card (or physical contactless card account). The user may visit a merchant website and use the virtual card information to make a purchase instead of using the card information for the physical contactless card. In another example, a user may store the virtual card in a wallet application or transaction application (e.g., Apple® Pay, Google™ Pay, Paypal®, Venmo®, and / or the like). The user may use the virtual card with a physical transaction device that interacts with the transaction application on the mobile device. For instance, a user may use a virtual card via Apple® Pay with a POS device at a merchant checkout that accepts Apple® Pay.
[0039] However, current virtual card technology is not able to operate with physical transaction devices, unless facilitated via a mobile device application. For example, if a user is checking out at a retailer physical store location (i.e., a “brick-and-mortar” location) that uses a POS device that does not accept mobile device payment (e.g., Apple® Pay, etc.), then the user must use the physical contactless card. In another example, if the user is refueling a vehicle using an ECR at a gas pump that does not accept mobile device payment, then the user must use the physical contactless card. In such instances, the user is not able to take advantage of existing virtual card technologies.
[0040] Although, as described in more detail in the present disclosure, contactless card technology (e.g., “chip” or “EMV” technology) provides enhanced security compared with previous transaction cards, they are still vulnerable to malicious attacks. For example, skimming or “shimming” devices have been developed that are specifically made to maliciously read contactless card “chip” elements to steal card data. Other examples include card data harvesting from POS and ECR devices, security breaches of merchant systems (i.e., that store card data obtained from POS and ECR transactions), man-in-the-middle (MITM) attacks, relay attacksDocket No. 1988.0497WO(e.g., forwarding wireless messages between a contactless card and a physical transaction device), and / or the like.
[0041] Accordingly, there is a need to provide businesses and users with an appropriate solution that overcomes current deficiencies to provide data security, authentication, and verification for contactless cards, including when used in a transaction with a physical transaction device. Embodiments provide systems and methods to implement virtual card technologies for contactless cards for use with physical transaction devices.
[0042] In one embodiment, a user may load virtual card information into the memory of a contactless card and set an indicator that the virtual card information is to be used in physical transactions instead of the card information assigned by the service provider. The user may initiate the virtual card information through a service provider application executing on a mobile device. For example, the user may establish communication between the contactless card and the mobile device application. Through the mobile device application, the user may elect to use virtual card information on the physical contactless card for one or more physical transactions. In some embodiments, the mobile device application communicates this request to a server or backend system of the service provider. In various embodiments, the service provider provisions the virtual card information (e.g., virtual card number, expiration date, CVV, zip code, etc.) and updates a record associated with the physical contactless card to use the virtual card information for one or more subsequent physical transactions. The service provider may provide the virtual card information to the mobile device application. The virtual card information may be written to the physical contactless card via the mobile device application. During a subsequent contactless card transaction with a physical transaction device, the virtual card information may be used instead of the assigned card information stored on the contactless card.
[0043] Contactless cards are configured to perform virtual physical transactions using systems and methods according to various embodiments. A virtual physical transaction involves the use of virtual or temporary information stored directly on the contactless card that is different from the “original” or “assigned” card information, card numbers, card identifiers, and / or the like that are stored on the contactless card at the time of manufacture and / or personalization. The assigned card information is static and permanently stored on the contactless card. In some embodiments, the virtual information is or includes a virtual number or virtual card number. In general, a virtual card number is a temporary card number that is used in place of the original, assigned card information for one or more transactions. The virtual card number can be used in place of a creditDocket No. 1988.0497WOcard number, an account number (e.g., a primary account number (PAN)), a unique identifier (pUID), and / or the like. The virtual card number is temporary and, therefore, can be used and erased from the card or modified, updated, replaced, and / or the like. In this manner, the contactless card can be authenticated and / or used for a financial transaction without requiring use of the assigned card information.
[0044] Virtual physical transactions and the contactless cards capable of performing virtual physical transactions according to embodiments described in the present disclosure provide multiple technical advantages over existing transaction processes and transaction cards. In one non-limiting example of a technological advantage, the described embodiments allow virtual or temporary card information to be used in transactions involving a contactless card and a physical transaction device, such as a POS or ECR device at a merchant brick-and-mortar location. Using existing systems, virtual cards or virtual card information only existed in digital form, for example, stored on a mobile device. Existing systems only allowed for virtual card information to be used for web-based or mobile payment -based transactions. Physical transactions at physical transaction devices using existing transaction cards require the use of the assigned information stored on the transaction card, including for EMV transactions. However, virtual physical transactions of the described embodiments allow for the use of virtual card numbers in physical transactions. Therefore, embodiments provide the safety and security of virtual cards and virtual numbers to be achieved in physical transactions.
[0045] In another non-limiting example of a technological advantage, the described embodiments allow virtual or temporary card information to be used in a secure, chip-based contactless transaction card implementing various security, encryption, and authentication protocols, such as EMV, Triple DES (3DES), and / or the like. For example, in some embodiments, the virtual card number is stored on the contactless card as a card identifier, for instance, a card number, a pUID, a PAN, and / or the like, that is used in encryption and authentication processes described in the present disclosure. Using existing transaction cards, including EMV or “chip” cards, authentication of a physical transaction requires the use of the assigned information stored on the transaction card, for instance, to generate cryptograms, authentication information, and / or the like. However, virtual physical transactions using a contactless card according to some embodiments may proceed with encryption and authentication processes formed using virtual information stored on the contactless card.Docket No. 1988.0497WO
[0046] In a further non-limiting example of a technological advantage, the described embodiments reduce or even eliminate the risk of unauthorized access to assigned contactless card information, such as the original, assigned card number, a pUID, a PAN. Using existing systems and transaction cards, certain card information (e.g., card number, pUID, PAN, portions thereof, and / or the like) may be stored at a physical transaction device or on a merchant network. If the physical transaction device or merchant network is compromised, the card information may be exposed. However, embodiments are able to provide virtual information for physical transactions. Accordingly, the card information stored at a physical transaction device or on a merchant network resulting from the transaction is only virtual, temporary card information. A user performing transactions using a contactless card according to some embodiments can perform a physical transaction while avoiding the exposure of the unalterable contactless card information assigned at manufacture and / or personalization as a result of a security breach of a physical transaction device or merchant network.
[0047] Details of the above-identified embodiments and additional advantages thereof are discussed in the following description.
[0048] In some instances, contactless card functions discussed herein may be utilized in a multiissuer computing environment. These functions may include tap-to functions where a user may tap their contactless card on a device, such as a mobile device, to perform a function. For example, a user may utilize their contactless card to verify their identify, perform a payment, launch applications, login into applications, autofill a form or a field, navigate to a specified web location or application on a device, unlock a door, initiate a contactless card, verify themselves, and so forth.
[0049] The systems discussed here may enable users to perform these functions in a multi-issuer environment. Further, the systems discussed herein may enable card issuers or payment providers, such as a banks, to issue contactless cards with tap-to functions to customers while maintaining a high-level security. The systems discussed differ from previous solutions because they provide a single platform for multiple issuers to provide the tap-to functionality. Traditionally, each issuer must set up and maintain their own systems to provide contactless card features. This includes maintaining their own hardware, software, databases, security protocols, and so forth, which can become extremely costly for the issuer to maintain. However, embodiments discussed enable issuers to offload much of the processing, storage, and security functionality to a neutral or central system. As will be discussed in more detail, the central systemDocket No. 1988.0497WOis configured to provide contactless card features for multiple issuers while maintaining a high level of security and data integrity. Each issuer's functionality and data may be separately managed and secured such that one issuer cannot access another issuer's data or functions. As will be discussed in more detail, these features may be provided by a switchboard system that is configured to process and perform each contactless card function in a secure manner. Additional benefits for issuers may include providing a highly secure authentication option for a mobile web, which typically lacks the robust authentication options available in a native application.
[0050] Further, embodiments discussed herein support tap-to mobile web experiences on both major mobile platforms (iOS®, Android®) by leveraging App Clips® and Javascript® SDK with WebNFC®. In some embodiments, embodiments discuss herein can also support tap-to-mobile web experiences on mobile platforms by leveraging Instant Apps. For iOS®, embodiments include providing a tap-to software development kit including functions and services to perform the operations discussed herein on the iOS® platform. The SDK may be installed into the host application, e.g., a native app or web browser app, and includes App Clip® support. The SDK provides functional support for NFC between the mobile device and the contactless card, installing a native app via App Clips®, and functionality to obscure data and / or portions of a display. In one example, the SDK may be configured to download and install the app from an app store, such as Apples® App Store.
[0051] In the Android® operating system environment, embodiments include utilizing a JavaScript SDK. The JavaScript SDK may be installed into a website, e.g., via website source code. The JavaScript SDK also includes functions to support NFC between the mobile device and the contactless card via WebNFC®. The JavaScript SDK may also include functions to provide customizable user interface (UI) capabilities and obfuscation. In embodiments, the JavaScript SDK supports websites utilizing Hypertext Transfer Protocol Secure (HTTPS) and supports the React® library. Embodiments are not limited in this manner and other JavaScript UI libraries may be supported.
[0052] With general reference to notations and nomenclature used herein, one or more portions of the detailed description which follows may be presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substances of their work to others skilled in the art. A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations are those requiringDocket No. 1988.0497WOphysical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities.
[0053] Further, these manipulations are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. However, no such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein that form part of one or more embodiments. Rather, these operations are machine operations. Useful machines for performing operations of various embodiments include digital computers as selectively activated or configured by a computer program stored within that is written in accordance with the teachings herein, and / or include one or more apparatus specially constructed for the required purpose or a digital computer. Various embodiments also relate to one or more apparatus or systems for performing these operations. These apparatuses may be specially constructed for the required purpose. The required structure for a variety of these machines will be apparent from the description given.
[0054] Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate a description thereof. The intention is to cover all modification, equivalents, and alternatives within the scope of the claims.
[0055] FIG. 1 illustrates an example of system 100 configured to operate in accordance with the embodiments discussed herein. The system 100 includes additional devices and systems configured to enable contactless card issuers to provide tap-to card services. Specifically, the system 100 enables any number of issuer systems to provide card services to their clients through a switching fabric, i.e., a switchboard system, in a secure and safe manner.
[0056] In embodiments, the switchboard system includes one or more nodes 104 configured to perform routing operations. Each switchboard node 104 may include a sessionDocket No. 1988.0497WOand nonce generator 106, a message router 108, an authentication 110 function, an operation data 112 store, and a metrics store 114. Further, each of the nodes may be configured the same and share configurations, but each switchboard node 104 may independently process and route messages and requests to the appropriate systems, such as merchant systems and issuer systems. Each of the nodes 104 is configured to act as a broker of trust between an issuer system, a merchant system 122, and / or a validation system 124, for example. Each switchboard node 104 is configured to route each message to the correct issuer system while maintaining data security. For example, a switchboard node 104 may route a message between an issuer system and a merchant system while the node cannot access the private data in the message.
[0057] The switchboard system 100 may be configured as a server system with a collection of hardware, software, and networking components that work together to provide client services. Hardware components may include one or more server computers, storage devices, and network adapters. The server computers are configured to run server applications, such as those executable on each of the nodes 104. In some instances, each of the server computers may be configured to operate one or more nodes, e.g., in a virtual environment. The storage devices are configured to store data that is accessed by the applications, and the network adapters are used to connect the server computer to the network.
[0058] Each of the server computers may be configured to execute software, including the operating system, the applications, and security software. The networking components of a server system include the network switch, router, and firewall. The network switch is used to connect the server computers to other devices on the network. The router is used to route traffic between different networks. The firewall is used to protect the server system from unauthorized access and attacks.
[0059] In some embodiments, the nodes 104 may operate in a cloud-based computing environment, e.g., a collection of hardware, software, and networking components that enable the delivery of cloud computing services. The switchboard nodes 104 and the computing services are delivered over the Internet and can be accessed from anywhere in the world with an Internet connection. In embodiments, client 136 may access a switchboard node 104 through a DNS 102 or a Domain Name System (DNS). The DNS 102 is a hierarchical and distributed naming system for computers, services, and other resources connected to the Internet or other networks. It associates various information with domain names assigned to each registered participant. In one example, the DNS 102 may translate a name known to software executing on a client 136 to routeDocket No. 1988.0497WOdata to one or more of switchboard node 104 of the switchboard system. In embodiments, the DNS 102 may generate a number, such as an Internet Protocol (IP) address, an address record (A-record), or another Hostname (C-name record). FIG. 2 illustrates an example a sequence 200 for a client to identify and resolve an identifier for one of the nodes 104 of the switchboard system. At a high level, the DNS 102 translates known domain names to numerical Internet Protocol (IP) addresses needed for locating and identifying computer services and devices with the underlying network protocols. Clients use the global DNS system to select the best node to use, as illustrated in the sequence 200.
[0060] In embodiments, a client 136 communicates with the switchboard system to perform one or more partner services 132, such as conducting a transaction with a merchant, validating the customer, or other tap-to functions. In some embodiments, partner services 132 may include services associated with a physical transaction using a physical transaction device. Once the client 136 identifies a switchboard node 104 and resolves an address to communicate with the switchboard node 104, the client 136 may send one or more messages to the switchboard node 104 to authenticate and perform a desired operation. The switchboard node 104 includes an authentication 110 function that is configured to authenticate the client 136. In embodiments, the client 136 sends a message or authorization request to the switchboard node 104 with the following header set:• X-Sb-Api-Key: < CLIENT API KEY>• X-Sb-Dvc-Fngrprnt: Device-specific device fingerprint
[0061] The CLIENT API KEY may have the following example structure: 65535-GReyx5BuEAaE72bWbFZJfHRL8DbtlUum, where Table 1 describes the value, name, and meaning:Value Nane Meaning5535 Client ID Individual identifier of client GReyx5BuEAftE72bWbFZJfHRL8DbtlUum Client Key Randomly assigned keyTable 1
[0062] The switchboard node 104 may authorize or authenticate the client 136 or user, and the switchboard node 104 may utilize the additional components, such as the session and nonce generator 106 and the message router 108, to perform the operations. Note the validation systemDocket No. 1988.0497WO124 never interacts with the merchant systems 122, nor vice versa. The nodes 104 brokers all communication.
[0063] In embodiments, the switchboard system may utilize a hyper ledger fabric 120 to manage and synchronize the shared operation data 112 and member management across the network. The hyper ledger fabric 120 is a distributed ledger framework having a permissioned network model that ensures only authorized participants can join the network and access the data that is stored on a ledger.
[0064] In embodiments, the hyper ledger fabric 120 may be generated by creating one or more sets of peers, an ordering service, and a channel. Once the network is created, the system 100 deploys chaincode to the network, or a node 104 is permitted to access the fabric. The chaincode is the code that runs on a blockchain and executes a network control 126 and operation data 112 logic code. Once the chaincode is deployed, each of the switchboard nodes 104 is configured to invoke transactions on the blockchain to add data to the blockchain, e.g., operational data. A switchboard node 104 or another device can query the ledger to retrieve data. The ledger is a distributed database that stores all the data added to the blockchain.
[0065] All nodes 104 keep an independently verifiable log of their actions that can be transmitted to a centralized aggregator to build a picture of overall network usage. The system 100 can manage network operation data and management at a central level and have a centralized view of network use, aggregated and abstracted to the appropriate level.
[0066] FIG. 2 illustrates an example a sequence 200 for a client to utilize the DNS to resolve and communicate with one or more nodes of the switchboard system. The illustrated sequence 200 includes a client 136, a DNS 102, and a switchboard node 104. At 202, the sequence 200 includes the client 136 sending a request to a default DNS server for a text record switchboard, {domain}, {tld}. The text record may be preconfigured in a client app and / or a client SDK. At 204, the DNS 102 returns one or more records. A DNS record structure may include the following:• Root Record:o Name: switchboard. {domain}. {tld}o Type: TXTo Resolution:• { nodename_l }. { operator_a}. { region_i }. switchboard, {domain}. {tld}, • {nodename_2}. {operator_a}. {region_i}.switchboard, {domain}. {tld},Docket No. 1988.0497WO• {nodename_l }. {operator_b }. {region_ii }.switchboard, {domain}. { tld}, • { nodename_2 }. { operator_b }. { region_ii }. switchboard. { domain}. {tld }, • * etc.o Used For determining where there are active nodes• Node Record:o Name: {nodename}. { operator}. {region}.switchboard. {domain}. {tld} o Type: A / AAAA or CNAMEo Resolution: Actual node hostname or IPo Used For: communicating with a node 104
[0067] In embodiments, the client 136 may determine the current timezone at 206. For example, the client app or the SDK may utilize a get current timezone function, such as in JavaScript: Inti. DateTimeFormat().resolvedOptions(). timeZone). Embodiments are not limited in this manner, and the app or the SDK may determine the timezone via another / different function call. At 208, the client 136 is configured to map the timezone to a region or short-version identifier of the region. One example includes America / New York ->na-e. The region may be based on DNS names, for example. Table 2 illustrates a few examples of timezone mappings to regions:Timezone Region Short- Version Amer ica / New __York North America E st na-eAmerica / Buenos.... Aires South America sa- US / Pacific North merica / West na-wEurope / Paris Europe euTable 2
[0068] Embodiments are not limited to these examples, and other timezone-to-region mappings may be utilized. Further and in embodiments, regions can also be represented as a bidirectional graph structure with the edges representing geographic neighbors. For example, na-e <-> na-w and sa <-> na-w and sa <-> na-e. This representation is useful for node selection.
[0069] At 210, the client 136 may identify or select a DNS record option returned at 204 that is in the region. If there are multiple matches, the client 136 may select one at random. If there is no node available in the region, the client 136 may determine and use a data graph of neighboring regions to select a node in the closest region where a node is available at 212. For example, sa has no node but is connected to na-e where there is a node and so na-e is selected.Docket No. 1988.0497WO
[0070] At 214, the client 136 may resolve a selected node's hostname. In embodiments, the client 136 may automatically resolve the hostname using the client’s HTTP request default resolver. At 216, the DNS 102 may return a result, and at 218, the client 136 may communicate with a switchboard node 104 and begin the process to interact with the switchboard.
[0071] FIG. 3 A - FIG. 3C illustrate an example of a sequence 300 to perform operations between a contactless card and services provided by a card issuer and / or a merchant. The illustrated sequence 300 includes actions and communications performed by a contactless card 802, a client 136, including a client app 390 and a client SDK 392, a DNS 386, a switchboard system including one or more nodes 104, partner services 132, including a merchant and / or a validator 388, and control services 134, including a client server 384 or system. In embodiments, the client app 390 may be any application configured to execute on a client 136, such as a banking app, a merchant app, a social media app, a travel app, a gaming app, a productivity app, an entertainment app, and so forth. In embodiments, the client app 390 includes a web browser to provide websites and pages. The client app 390 may include and / or utilize the client SDK 392, which may be a set of instructions that enable the client app 390 to communicate with other components of the switchboard system.
[0072] In embodiments and as shown in FIG. 3A, at 302 the client 136, including the client app 390, may send a request and establish a session with a client server 384 such that a result may be associated with the correct client device or user. The request establishes a relationship between the client 136 and the client server 384, which may be an issuer server. At 304, the client server 384 generates a session and CLIENT SESSION INFORMATION. At 306, the client server 384 returns the session information, e g., the CLIENT SESSION INFORMATION. In embodiments, the CLIENT SESSION INFORMATION may be client implementation-specific user session identification information.
[0073] At 308, the client 136 may initiate a contactless card authentication process with the client 136. For example, the client 136 may call a function and / or pass information to the client 136 to initiate authentication via a contactless card 802. At 310 - 314, the client 136 may utilize the DNS 386 to identify a node and establish communication with the node. Specifically, at 310, the client 136, including the client SDK 392, may send a request for switchboard hostnames, and at 312 the DNS 386 may return information including one or more hostnames. At 314, the client 136 may determine a switchboard node to communicate. FIG. 2 illustrates an example of a more detailed sequence 200 to establish communication with a switchboard node 104.Docket No. 1988.0497WO
[0074] At 316, the client 136 may send a request for a session to the switchboard system 100. In embodiments, the request for the session may be a function request in the format < FUNCTION REQUEST>. In embodiments, the FUNCTION REQUEST may be the data / function that the client 136 would like to request once the contactless card 802 has been validated. The function could be for any service discussed herein, e.g., authenticate the user, perform a transaction, request autofill data, etc. At 318, the switchboard system 100 may generate a nonce and a signed session token. The signed session token may be a JSON Web Token (JWT). When generating the JWT, the following elements should be set:• iss: The unique ID of the current node,• nonce: An 8 hex character, randomly generated nonce,• exp: The expiration timestamp (+5 minutes),• client id: The requesting client’s Client ID,• sub: The requesting client’s Device Fingerprint,• sid: Arbitrary session info sent from the client,• scope: The function being requested to be performed.
[0075] The nonce may be unique, random bytes generated to ensure the unrepeatability of a message with the contactless card 802. The nonce is critical to the security and operation of the switchboard system. The nonce validity is tracked by tying the nonce to a session that can be validated by any member of the platform. As mentioned, sessions are JSON Web Tokens signed using a node-specific private key issued by the network. These JWTs are verifiable by a system with the corresponding public key, which the system can also verify by confirming the JWT was issued by the network or an approved delegate. The signed session token is a JWT-generated token to establish the validity and expiration of the nonce and to associate the contactless card tap to the current client session. For example, the signed session token includes < NONCE>,< CLIENT SESSION INFO>, and< FUNCTION REQUEST> signed with < NODE PRIVATE KEY>, where the NODE PRIVATE KEY is the switchboard system 100 private key. The switchboard system 100 may include a NODE PUBLIC / PRIVATE KEY, which is a keypair used to sign and validate JWTs.
[0076] At 320, the switchboard system 100 may return session information to the client 136. The session information may include the signed session token (< SIGNED SESSION TOKEN>), the NONCE < NONCE>, the function terms of service < FUNCTION TOS>, and the terms of service version < TOS VERSION>. The FUNCTION TOS may be the terms of service that theDocket No. 1988.0497WOuser must consent to in order to allow the client to execute the requested function, and the TOS VERSION may be the version of the terms of service. At 322, the client SDK 392 may determine and / or receive user consent to the terms of service. In one example, the client SDK 392 captures and records the user consent to< FUNCTION TOS> on < CONSENT DATE>with< TOS VERSION>. The CONSENT DATE may be the timestamp for the user’s consent to the TOS.
[0077] At 324, the client 136 exchanges one or more messages with the contactless card 802. In one example, the exchange may be based on the contactless card being tapped to a client device. In embodiments, the client SDK 392 may provide data to the contactless card 802 to use during the session to perform the function. The data may be provided to the contactless card 802 in an NDEF message. In one example, the data is written to the card in NDEF format using a binary update command. The data may include a NONCE to provide a level of security that the message received from the card is part of the same session. Additionally, the data may include additional information, such as one or more control bits to control the format generated by the contactless card. Table 3 below illustrates an example of an NDEF message format.Docket No. 1988.0497WOTable 3
[0078] The updated MAC may be calculated to protect the control indicators in embodiments. Specifically, The MAC M is determined by calculating a MAC over the 10 bytes of the update data U with the Update MAC Card Key (MCK), as described in FIG. 4.
[0079] At 324, the contactless card 802 may generate and provide a message to the client's device, including the client SDK 392. The data in the message may be utilized by the system discussed herein to perform the function requested. One example of the message is illustrated and discussed in FIG. 4.
[0080] At 326, the client, including the client SDK 392, may send a message and information to the switchboard system 100. The message may be the message received from the contactless card 802, e g., message 400 in FIG. 4. In addition, the client SDK 392 may send the consent date, the TOS version, and the signed session token to the switchboard system 100. The switchboard system 100 may utilize the information to ensure the session is valid. At 328, the switchboard system 100 verifies the signed session token is valid, e.g., is the previously provided signed session token and includes the nonce previously generated and in the message.
[0081] In some embodiments, the switchboard system 100 is configured to determine which issuer system or client-server it should route the message to for processing. At 330, the switchboard system 100 may determine the issuer ID by extracting the issuer ID from the message received from the contactless card 802 via the client SDK 392. As mentioned, the issuer ID identifies the issuer of the contactless card 802.
[0082] FIG. 3B continues the sequence 300 from FIG. 3A. In embodiments, the switchboard system 100 is configured to generate and communicate secure communications with the issuerDocket No. 1988.0497WOsystem, e.g., the client server 384 and the validator 388. At 332, the switchboard system 100 sends a request for a key to the client server 384. The key may be utilized to perform secure communications. In one example, the key request may be an elliptical curve Diffie-Hellman (ECDH) key request. Embodiments are not limited in this manner. Alternative key protocols may be utilized, e.g., Supersingular isogeny Diffie-Hellman key exchange (SIDH or SIKE), a private / public key pairing (RSA), etc.
[0083] At 334, the client server 384 generates a portion of the key. In some instances, the client server 384 may generate half of the ECDH key for encryption / decryption of PII. Specifically, the client server 384 may generate < CLIENT EC PUBLIC KEY> and < CLIENT EC PRIVATE KEY> using Elliptic Curve P256. The CLIENT EC PUBLIC KEY AND CLIENT EC PRIVATE KEY is the first half of the ECDH key negotiation.
[0084] At 336, the client-server 384 stores the generated portion of the key in storage. Specifically, the client server 384 may store < CLIENT EC PUBLIC KEY> and < CLIENT EC PRIVATE KEY> with < KEY ID>, where the KEY ID is used by the Client Server to cache its short-lived EC public / private key for later ECDH key completion, e.g., to identify the ECDH key portions to generate the whole ECDH key. In one example, the key may be stored in a secure memory location and may be used when PII is received for the session.
[0085] In embodiments, the client server 384 may return the public key portion to the switchboard system 100 with the KEY ID at 338. The switchboard system 100 may store the public key portion with the KEY ID for later use, e.g., generation of the ECDH key. At 340, the switchboard system 100 may request a validation to be performed by the validator 388. In one example, the switchboard system 100 may send a request validation as Request Validation < MESSAGE>, < SIGNED SESSION TOKEN>, < CLIENT EC PUBLIC KEY>, < CONSENT DATE>, and the < TOS VERSION>. The validator 388 may make an out-of-band request back to the switchboard system 100 for the public key to verify the session at 342. At 344, the switchboard system 100 may provide the node's public key, i.e., < NODE PUBLIC KEY>. Further at 346, the validator 388 may utilize the node's public key to verify the secure session token.
[0086] In embodiments, the validator 388 may validate the message at 348. In embodiments, the validator 388 may perform a number of validations including ensuring the nonce in the message is correct along with additional information, such as the card's unique identifier (pUID), and the counter value (pATC). FIGs. 15-17 discuss additional details of a validation process that may be performed.Docket No. 1988.0497WO
[0087] At 350, the validator 388 may store information associated with the session. For example, the validator 388 may store the < CONSENT DATE> with the < TOS VERSION> and the < PUID>. The validator 388 may also generate another portion of the key, e.g., the ECDH key. For example, the 388 may Generate < ISSUER EC PUBLIC KEY> and < ISSUER EC PRIVATE KEY> using Elliptic Curve P256. The ISSUER EC PUBLIC KEY and ISSUER EC PRIVATE KEY may be the second half of the ECDH key negotiation.
[0088] At 354, the validator 388 may generate the complete ECDH key. For example, the validator 388 generates the < ECDH KEY> from < ISSUER EC PRIVATE KEY> and < CLIENT EC PUBLIC KEY>. The ECDH KEY is the final key generated using ECDH key negotiation.
[0089] The validator 388 may utilize the ECDH KEY to encrypt data for the function. For example, if the validator 388 validates the message in some instances, the validator 388 may execute a function request to create a function result and encrypt the result with the ECDH KEY at 356. For example, the validator 388 may execute < FUNCTION REQUEST> to create < FUNCTION RESULT> and encrypt the same with the < ECDH KEY>. The function result may be any result based on the requested function, e.g., verification of the card.
[0090] At 358, the validator 388 may return the function result to the switchboard system 100. In some instances, the function result is returned encrypted. For example, the validator 388 may return the < ENCRYPTED FUNCTION RESULT> and the < ISSUER EC PUBLIC KEY>.
[0091] FIG. 3C continues the sequence 300 from FIG. 3B. In embodiments, at 360, the switchboard system 100 sends the function result to the client server 384 to process the result. In one example, the switchboard system 100 may send the < ENCRYPTED FUNCTION RESULT>, < KEY ID>, < ISSUER EC PUBLIC KEY>, and < SIGNED SESSION TOKEN>. At 362 and 364, the client server 384 may make a request for and receive the public key from the switchboard system 100. In some instances, the exchange may be performed via out-of-band communication channels. The public key for the node may be < NODE PUBLIC KEY>. The public key may be used to verify the sender of the function result, etc. At 366, the client server 384 may verify the signed session key with the node's public key < NODE PUBLIC KEY> to verify the sender of the information. At 368, the client server 384 may extract client information from the signed session token. For example, the client server 384 may Extract < CLIENT SESSION INFO> from < SIGNED SESSION TOKEN>, i.e., extracting the client implementation-specific user session identification information.Docket No. 1988.0497WO
[0092] Further, at 370, the client server 384 may retrieve the client's private key with the KEY ID. Specifically, the client server 384 may get and remove the < CLIENT PRIVATE KEY> from a cache using the < KEY ID>. At 372, the client server 384 may generate or compute the ECDH key. For example, the client server 384 may compute the < ECDH KEY> with the < CLIENT PRIVATE KEY> + < ISSUER EC PUBLIC KEY>. The client server 384 may decrypt the function result with the computed key at 374. Specifically, the client server 384 may decrypt the < ENCRYPTED FUNCTION RESULT> with the < ECDH KEY> to determine the < FUNCTION RESULT>. At 376, the client server 384 associates the function result with the session.
[0093] In embodiments, the switchboard system 100 may return whether the function result was successfully completed or not at 378 to the client SDK 392. Further at 380, the client SDK 392 may notify the client app 390 of the result. At 382, the client app 390 may utilize the feature. For example, the 382 may communicate with the client server 384 to continue the feature using the < CLIENT SESSION INFO to fetch the redacted < FUNCTION RESULT>.
[0094] FIG. 4 illustrates an example of a message 400 that may be communicated by a contactless card to perform the functions described herein, such as those discussed in FIGs. 3A-3C. One or more of the fields in the message 400 may also be utilized to route the message 400 through the switchboard system and perform authentication / validation techniques.
[0095] In embodiments, the message 400 includes an applet version 402 field, an issuer discretionary indicator 404 field, an Issuer Identifier 406 field, a pKey ID 408 field, a pUID 410 field, a pATC 412 field, a nonce 414 field, and an encrypted cryptogram 416.
[0096] In embodiments, the fields may be in plain text or encrypted. For example, the applet version 402 field may include an applet version in plain text. The applet version indicates which applet version is installed on a contactless card and may be used by the other systems to determine how to process the message 400 when communicated. For example, different Applet versions require different validation logic, e.g., an older message may be routed through the issuer system to perform various operations for validation, while a newer message may be routed through the switchboard system to perform the various operations, including validation.
[0097] In embodiments, the message 400 includes an issuer discretionary indicator 404 field that may include issuer data and be set at the time of personalization. In addition, the message 400 includes an issuer identifier 406 field that may include a unique ID assigned to the entity issuing the card, e.g., the issuer. For example, when joining the system, each issuer may be assigned a unique identifier during an onboarding operation. The issuer ID can be used by theDocket No. 1988.0497WOswitchboard system 100 to route a message and its contents to the appropriate services that are associated with that particular issuer.
[0098] In embodiments, the message 400 includes a pKey ID 408 field. In some instances, the pKey ID 408 field may include data that identifies a set of master keys for a card issuer. The issuer’s set of master keys may utilize each card's set of derived master keys or unique derived keys (UDK). Further, each card’s own set of master keys (UDKs) may be generated during the personalization of the card. The card’s UDKs may be utilized to generate session keys that are used to generate the application cryptogram. The session keys generated by a card may be regenerated by a system, e.g., the validator system, utilizing pKey ID to identify the issuer’s master keys to regenerate session keys by the system to perform a validation.
[0099] In embodiments, each contactless card 802 is given a unique 16-decimal digit identity (pUID) at the time of personalization. Derivation of the card applet’s unique keys using the pUID is performed off-card. The resultant application keys are injected during the personalization of the card. In embodiments, a card’s application keys are the same as the card’s derived master keys or UDKs. In some embodiments, the pUID may be a virtual card number stored on the contactless card (see, for example, virtual number 1026 of FIG. 10). In various embodiments, use of the pUID for the creation or derivation of keys and / or encryption processes may use the pUID stored on the contactless card 802 and assigned at the time of personalization. In other embodiments, use of the pUID for keys, encryption, and / or the like during a transaction may use a virtual number stored on the contactless card 802.
[0100] The message 400 may include a pUID 410 field, including a card unique identifier assigned to the contactless card at personalization time. The pUID 410 field data may be a combination of alphanumeric characters used to identify each card and associated with a user uniquely.
[0101] In embodiments, the message 400 includes a pATC 412 field configured to hold a counter value. The counter value keeps a count of reads (taps) made on the contactless card in a hexadecimal format in one example. Further, a counter value may be used to generate session keys to encrypt at least a portion of a message.
[0102] In embodiments, each time a message 400 is created, a new session key is derived and utilized to generate one or more portions of the message 400. Specifically, a session key is used to calculate the cryptographic MAC (Application Cryptogram). The card's applet supports aDocket No. 1988.0497WOsession key derivation option to generate a unique cryptogram session key (ASK) and a unique encipherment session key (DESK).
[0103] In embodiments, a portion of the data provided in message 400 is static and set on the card during the personalization of the card and other data is dynamic and may be generated by the card during an operation, e.g., when a read operation is being performed. Note that in some instances, the static information may be updateable, but may require the customer and card to go through a secure update process, which may be controlled by the issuer. For example, a virtual card number and / or a virtual number indicator may be updatable (see, for example, FIG. 14). In some embodiments, the virtual card number may include a virtual number to be used as part of a transaction. In various embodiments, the virtual number indicator may be used to indicate whether the virtual card number or the assigned card number (i.e., the pUID, PAN, etc. assigned by the service provider during personalization) should be used.
[0104] In embodiments, the contactless card 802 may communicate a message between a device, such as a mobile device, during a read operation. For example, in response to the contactless card 802 being tapped onto a surface of the device, e.g., brought within wireless communication range, a read operation may be performed on the contactless card 802, and the contactless card 802 may generate and provide the message to the device. For example, once within range, the contactless card 802 and the device may perform one or more exchanges for the contactless card 802 to send the message to the device.
[0105] The wireless communication may be in accordance with a wireless protocol, such as near-field communication (NFC), Bluetooth, WiFi, and the like. In some instances, a message may be communicated between a contactless card 802 and a device via wired means, e.g., via the contact pad, and in accordance with the EMV protocol.
[0106] As discussed above, the contactless card 802 may be deployed with a unique card key, e.g., the UDK, that is generated from an issuer's master key and is used to generate session keys. The following discusses the generation of the UDK and the session keys (ASK and DESK). Further, the contactless card may generate encrypted data or a cryptogram comprising data as discussed herein with the generated keys. The encrypted data may be encrypted with session keys that are changed each time data is encrypted. In one embodiment, the session keys are generated from card master keys or unique diversified keys that are stored on the contactless card 802. The unique diversified keys may be generated from the issuer’s master keys. For example, in some instances, operations to generate the unique diversified keys may be performed off the card atDocket No. 1988.0497WOpersonalization time and then stored in the memory of the card. Further, the issuer's master key(s) may be utilized to generate card master keys. The card master keys may also be known as application keys or UDKs. Each contactless card may have one or more UDKs.
[0107] In embodiments, each contactless card includes one or more applications, such as an authentication application, which is given a unique 16-digit identity (pUID) at time of personalization and / or a virtual card number that is written to the card during a virtual card process (see, for example, FIG. 14). Each contactless card may also receive application keys, which may also be known as unique card keys (UDKs) or card master keys using the pUID (the original pUID or the virtual card number). In some instances, these operations are performed off-card, and the resultant keys are injected during personalization. However, in other instances, one or more of the operations may be performed on the card, e.g., at the time of manufacture, each time an operation is performed with a key, following assignment of a virtual card number, the virtual number indicator being activated, and so forth.
[0108] Embodiments include a system configured to generate a number of issuer master key sets and assign each a unique three-byte pKey identifier (pKey ID). As mentioned, systems discussed herein may support many card issuers, and each card issuer may have one or more of its own sets of unique issuer master keys that can be identified with a pKey ID. For each application, such as the authentication application, the system may perform the following operations to generate application keys or UDKs.
[0109] In embodiments, the system assigns a pKey ID or a pUID, a card application's unique 16-decimal digital identity, to a card. In various embodiments, the pKey ID or pUID may be a virtual card number (e g., virtual number 1026 of FIG. 10). The system initiates generating a card's UDK(s). Specifically, the system generates a 16-digit quantity (X) from the 16-digit pUID. In one example, the 16-digit X may be generated by randomly rearranging the 16-digit pUID. In another example, X may be the same as the 16-digit pUID. Embodiments are not limited in this manner, and other techniques may be utilized to generate X from the 16-digit pUID. In embodiments, the 16-digit quantity X may be utilized to generate one or more UDKs.
[0110] In instances, the system computes or calculates a first portion (ZL) by encrypting X with an issuer master key. An encryption algorithm, such as DES or DES variant, may be utilized in embodiments. Embodiments are not limited in this manner, and other examples of encryption algorithms include AES and public-key algorithms, such as (RSA).Docket No. 1988.0497WO
[0111] The system calculates or computes a second portion ZR by XOR'ing X with FFFFFFFFFFFFFFFF and encrypting the result with an issuer master key. Again, an encryption algorithm such as DES, AES, RSA, etc., may be used to encrypt the result of the XOR'ing. The system generates an application key or UDK. Specifically, the system concatenates ZL with ZR to form the application key. Embodiments are not limited to concatenating the two portions (ZL and ZR). They may be combined using other techniques. Additionally, the above-described process can be performed any number of times to generate additional application keys, e.g., by utilizing different master issuer keys. In embodiments, a contactless card 802 stores the generated application key(s) or UDK(s).
[0112] In embodiments, the contactless card 802 utilizes the application key(s) or UDK(s) to generate session keys for each encrypted data that are generated. The following is one processing flow that may be performed by the contactless to generate a unique cryptogram session key (ASK).
[0113] To generate the ASK, the contactless card 802 computes an SKL by encrypting [ATC[2] || ATC[3] || 'F0' || '00' || [ATC[0] || [ATC[1] || [ATC[2] || [ATC[3]] with an application key. Further, the contactless card 802 computes SKR by encrypting [ATC[2] || ATC[3] || 'OF' || '00' || [ATC[0] || [ATC[1] || [ATC[2] || [ATC[3]] with the application key. Finally, the contactless card 802 concatenates SKL with SKR to form an authentication session key (ASK). In embodiments, the ASK is used to perform operations utilizing the contactless card 802, such as encrypting the cryptographic MAC.
[0114] In embodiments, the contactless card 802 also supports session key derivation to generate a unique encipherment session key DESK. The contactless card 802 computes an SKL by encrypting [ATC[2] || ATC[3] || 'F0' || '00' || '00' || '00' || '00' || '00'] with a Data Encryption Key (DEK) or UDK. Further, the contactless card 802 computes SKR by encrypting [ATC[2] || ATC[3] || 'OF' || '00' || ‘00 || ‘00’ || ‘00’ || ‘00’] with the DEK or UDK. The contactless card 802 concatenates SKL with SKR to form the Data Encipherment Session Key (DESK).
[0115] In embodiments, the contactless card 802 generates encrypted data or a cryptogram utilizing the session keys. Specifically, the contactless card 802 generates a cryptogram C by calculating a MAC over the 32-byte transaction data T using the Authentication Session Key (ASK).
[0116] The contactless card 802 may process the data to generate the cryptogram. Specifically, the contactless card 802 divides T into four blocks of 8 bytes of data: T = T1 || T2 || T3 || T4. TheDocket No. 1988.0497WOcontactless card 802 computes B = DES(ASKL) [Tl], where DES is the Data Encryption Standard or another symmetric encryption algorithm and ASKL is a portion of the ASK, e.g., the “left” half of the key. The contactless card 802 computes B = [B XOR T2], and the contactless card 802 computes B = DES(ASKL) [B], The contactless card 802 computes B = [B XOR T3], and the contactless card 802 computes B = DES(ASKL) [B], The contactless card 802 computes B = [B XOR T4], and the contactless card 802 computes B = DES(ASKL) [B], The contactless card 802 computes B = DES-1(ASKR) [B], where DES'1is the reciprocal DES operation and ASKR is a portion of the ASK, e.g., the right half. The contactless card 802 computes the cryptogram C = DES (ASKL) [B],
[0117] In embodiments, the contactless card 802 may also encipher the cryptogram to secure the data further. For example, the contactless card 802 may generate an 8-byte random number [RND] and the card computes El = DES3(DESK) [RND], where DES3 is a symmetric encryption algorithm such as the Triple Data Encryption Standard. The contactless card 802 then computes B = [El] XOR [C], where C is the cryptogram generated as discussed above. The contactless card 802 computes E2 = DES3(DESK) [B], where B is computed above. Further, the contactless card 802 generates the 16-byte enciphered payload E = [El] || [E2],
[0118] In embodiments, a device or the contactless card 802 may decrypt the payload E by determining, receiving, or retrieving the payload E. The device computes a RND = DES3' '(DESK) [El], The device determines B = DES3-1(DESK) [E2], and the device computes C = [El] XOR [B],
[0119] In embodiments, the contactless card 802 generates or calculates a message authentication code (MAC). In some instances, the MAC may be an updated MAC. In embodiments, the updated MAC is included in data communicated from the contactless card 802 to another device, such as a mobile device, a point-of-sale (POS) terminal, embedded card reader (ECR), or any other type of computer. In one example, the updated MAC may be included in an NDEF message.
[0120] In embodiments, the updated MAC may be calculated to protect the control indicators and include an updated date / time. For example, the updated MAC M is determined by calculating a MAC over the 10 bytes of the updated data U with the Updated MAC Card Key (MCK) as follows.
[0121] Embodiments include determining data to process through a number of calculations and computations. In one example, the data U equals the [Control Indicators (2 bytes) || Update DateDocket No. 1988.0497WOTime (8 bytes) || ‘80’ || ’0000000000’]. For the calculations, the data may be divided into two separate portions. Specifically, the data U is broken into two blocks of 8 bytes of data, where U = Ui || U2. Further, operations may be performed on Ui and U2.
[0122] Embodiments include applying an algorithm to the first portion (Ui) of the data. In one example, a result B may be computed where B = DES(MCKL) [UI], where DES is a Data Encryption Standard algorithm using a first portion (L) of the MAC Card Key (MCKL).
[0123] Further, an additional operation may be performed on the result B. Specifically, the result B may be exclusively or'd (XOR) with a second portion of the data (U2).
[0124] The updated result B may be further processed. For example, result B may be further processed by applying the DES algorithm using MCKL again to B. The result, the inverse DES, may process B with a second portion (R) of the MCK (MCKR), and the MAC M may be determined by applying the DES algorithm with the MCKL to result B.
[0125] FIG. 5 illustrates an example of method 500 in accordance with embodiments discussed herein. In block 502, the method 500 includes receiving, by a node in a system, a request to establish a session to perform a function from a client device, wherein the function is at least partially performed utilizing a contactless card, such as the contactless card 802. In some instances, the node may be one of a plurality nodes of a switchboard system. The node may be previously selected by the sending device via a DNS operation performed.
[0126] In block 504, the method 500 includes generating, by the node, session information corresponding to the session to perform the function, wherein the session information comprises a nonce and a signed session token. The nonce and / or the signed session token may be utilized by systems to perform the functions described herein while ensuring the node routing the data is authenticated, the message from the contactless card is authenticated, and to keep track of the session for the function.
[0127] In block 506, the method 500 includes sending the session information to the client device by the node. The client device may communicate with a contactless card to receive data from the card to authenticate and perform a function. In some instances, the client device may send the nonce from the node to the contactless card. The contactless card may utilize the nonce when generating the message to communicate back to the client device. Finally, the node incorporates the nonce into a cryptographic portion of the message (see, e g., FIG. 4).
[0128] In block 508, the method 500 includes receiving, by the node, a message from the contactless card via the client device. The message may be generated by the contactless card.Docket No. 1988.0497WOFIG. 4 illustrates one example of a message 400. In some embodiments, the node verifies the message. For example, the node may verify a nonce in the message and a signed session token.
[0129] In block 510, the method 500 extracts an issuer identifier from the message by the node, where the issuer identifier is associated with the issuer of the contactless card. In some instances, the issuer identifier may be in a plaintext format.
[0130] In block 512, the method 500 identifies, by the node, a device associated with the issuer identifier. For example, the node may perform a lookup to determine a server associated with the issuer identifier and the function to be performed.
[0131] In block 514, the method 500 communicates, by the node, with the device to securely perform the function.
[0132] FIG. 6 illustrates a distributed network authentication system 600 according to an example embodiment. As further discussed below, the system 600 can include a client node 602, an API 604, a network 606, a distributed ledger node 610, mapping 612, and a client device 614. Although FIG. 6 illustrates single instances of the components, the system 600 can include any number of components.
[0133] The system 600 can include the client node 602, which can be a network-enabled computer as described herein. In some examples, the client node 602 can be a server, which can be a dedicated server computer or a bladed server, or can be a personal computer, a laptop computer, a notebook computer, a palm top computer, a network computer, a mobile device, a wearable device, or any processor-controlled device capable of supporting the system 600.
[0134] In some examples, the client node 602 can execute one or more applications, such as software applications, that enable, for example, network communications with one or more components of the system 600, transmit and / or receive data, and perform the functions and processes described herein.
[0135] The client node 602 can contain the API 604. For example, various different APIs can be provided for an application (e.g., executed on a computing device, such as a network-enabled computer) that can interact with a service. For example, an application executed on a device (e.g., a smart phone, smart watch, tablet, laptop, or other device) can interact with a web-based service by calling the API 604 to interact with the service, such as by performing a remote call to an API for interacting with a web-based service.Docket No. 1988.0497WO
[0136] The API 604 can be provided in the form of a library that includes specifications for routines, data structures, object classes, and variables. In some cases, such as for representational state transfer (REST) services, an API (e.g., a REST API or RESTful API, or an API that embodies some RESTful practices) is a specification of remote calls exposed to the API consumers (e.g., applications executed on a client computing device can be consumers of a REST API by performing remote calls to the REST API). REST services generally refer to a software architecture for coordinating components, connectors, and / or other elements, within a distributed system (e.g., a distributed hypermedia system).
[0137] The client node 602 can communicate with one or more other components of the system 600 either directly or via the network 606. The network 606 can comprise one or more of a wireless network, a wired network, or any combination of a wireless network and a wired network and may be configured to connect the components of the system 600. While FIG. 6 illustrates communication between the components of the system 600 through the network 606, it is understood that any component of the system 600 can communicate directly with another component of the system 600, e.g., without involving the network 606.
[0138] The system 600 can include a validation node 608, which can be a network-enabled computer as described herein. In some examples, the validation node 608 can be a server, which can be a dedicated server computer or a bladed server, or can be a personal computer, a laptop computer, a notebook computer, a palm top computer, a network computer, a mobile device, a wearable device, or any processor-controlled device capable of supporting the system 600.
[0139] In some examples, the validation node 608 can execute one or more applications, such as software applications, that enable, for example, network communications with one or more components of the system 600, transmit and / or receive data, and perform the functions and processes described herein.
[0140] In some examples, each validation node can be associated with a routing number, and the routing number identifies the entity controlling the keys for the authentication namespace. The authentication namespace can be related to one or more of a particular entity, a particular set of cards, or a particular set of security keys (e.g., master keys, diversified keys, session keys) associated with an entity, a set of cards, or a type of cards.
[0141] The system 600 can include the distributed ledger node 610, which can be a network-enabled computer as described herein. In some examples, the distributed ledger node 610 can be a server, which can be a dedicated server computer or a bladed server, or can be a personalDocket No. 1988.0497WOcomputer, a laptop computer, a notebook computer, a palm top computer, a network computer, a mobile device, a wearable device, or any processor-controlled device capable of supporting the system 600.
[0142] In some examples, the distributed ledger node 610 can execute one or more applications, such as software applications, that enable, for example, network communications with one or more components of system 600, transmit and / or receive data, and perform the functions and processes described herein.
[0143] The distributed ledger node 610 can containing the mapping 612. In some examples, the mapping 612 can be in the form of one or more databases. Exemplary databases can include, without limitation, relational databases, non-relational databases, hierarchical databases, object-oriented databases, network databases, and any combination thereof. The one or more databases can be centralized or distributed. The one or more databases can be hosted internally by any component of the system 600, or the one or more databases can be hosted externally to any component of the system 600. In some examples, the one or more databases can be contained in the distributed ledger node 610, and in other examples the one or more databases can be stored outside of distributed ledger node 610 but in data communication with the distributed ledger node 610. The one or more databases can be implemented in a database programming language. Exemplary database programming languages include, without limitation, Structured Query Language (SQL), MySQL, HyperText Markup Language, JavaScript, Hypertext Preprocessor Language, Practical Extraction and Report Language, Extensible Markup Language, and Common Gateway Interface. Queries made to the one or more databases can be implemented in the same database programming language used to implement the one or more databases. For example, if the one or more databases are an SQL database, then queries made to the database can be made in SQL (e.g., SELECT column 1, column2 FROM table 1, table2 WHERE column2=’ value’;). It is understood that the one or more databases can be implemented in any database programming language and that the programming implementation of the query can be adjusted as necessary for compatibility with the one or more databases and to reflect the particular information to be queried.
[0144] In some examples, the one or more databases can be contained within the distributed ledger node 610. In other examples, the one or more databases can be remote from distributed ledger node 610 but in data communication with the distributed ledger node 610. DataDocket No. 1988.0497WOcommunication between the one or more databases and the distributed ledger node 610 can be a direct data communication or data communication via a network, such as the network 606.
[0145] In some examples, the client node 602 can be in data communication with the distributed ledger node 610. The distributed ledger node 610 can contain the mapping 612, and the mapping 612 may include, for example, a mapping between a validation node address and the validation node 608, a mapping between a routing number and a validation node address, and / or a mapping between a routing number and the validation node 608. In some examples, the mapping 612 can include a digital signature associated with an entity having permission to validate for a routing number. Based on one or more of these associations, the client node 602 can call the validation node 608 for validation and / or provide direction to the client device to reach the appropriate validation node. This can be accomplished by calling a validation API associated with the validation node 608.
[0146] In some examples, iterations of the mappings described herein, such as the mapping 612, can also include a software or applet version number. The version number can be used to identify a validation node or validation node address or choose between multiple validation addresses for one validation node.
[0147] In some examples, the client node 602 and the distributed ledger node 610 can be permissioned (e.g., allowed to join a network) with the aid of a certificate and / or a cryptographic authentication mechanism (e.g., a non-fungible token). The certificate and / or a cryptographic authentication mechanism may be issued by, e.g., a consortium authority or other administrative entity associated with the distributed network. If granted appropriate permissions, the distributed ledger node 610 can update the mapping 612 to reflect a different association between, for example, a routing number, a validation node address, and a validation node. In some examples, degrees of permissions can be issued. For example, if the client node 602 were to function to route data to the validation node 608 (or other validation nodes), then the client node 602 can be given a certain level of permissions. As another example, if the distributed ledger node 610 were to have the capability to update the mapping 612, then the distributed ledger node 610 can have a different, higher level of permissions.
[0148] The system 600 can include the client device 614, which can be a network-enabled computer as described herein. In some examples, the client device 614 can be a server, which can be a dedicated server computer or a bladed server, or can be a personal computer, a laptop computer, a notebook computer, a palm top computer, a network computer, a mobile device, aDocket No. 1988.0497WOwearable device, or any processor-controlled device capable of supporting the system 600. The client device 614 can also be a mobile device; for example, a mobile device may include an iPhone, iPod, or iPad from Apple®, any other mobile device running Apple’s iOS® operating system, any device running Microsoft’s Windows® Mobile operating system, any device running Google’s Android® operating system, and / or any other smartphone, tablet, or like wearable mobile device. In some examples, the client device 614 can be in data communication with another network-enabled computer not shown in FIG. 6, such as a smart card (e.g., a contactless card or a contact-based card).
[0149] In some examples, the client device 614 can execute one or more applications, such as software applications, that enable, for example, network communications with one or more components of the system 600, transmit and / or receive data, and perform the functions and processes described herein.
[0150] In some examples, upon receipt of an authentication request, the client device 614 can call (e.g., via an API) the client node 602. The call can include a routing number and / or an applet or software version number, and the client node 602 can query distributed ledger node 610 and the mapping 612. Once the query returns the identification of a validation node (e.g., the validation node 608) and / or a validation node address associated with that routing number and / or applet or software version, the client node 602 can reply to the client device 614. The client device 614 can then proceed with authentication with the validation node. The authentication can be performed by, for example, the systems and methods described herein, such as by generation, encryption, transmission, decryption, and validation of a cryptogram as described herein.
[0151] In some examples, the client node 602 can be co-resident with the validation node 608. In these examples, the client node 602 can handle the authentication in a single call from the client device 614. In some examples, this can be acceptable only if it is permissible for the full authentication transmission (e.g., a cryptogram as described herein) to be sent to client nodes that are not involved in authentication.
[0152] In some examples, if the client node 602 receives, from the client device 614, a routing number that is not handled by its location, the client node 602 can return a code indicating that this routing number is not handled, along with validation node address for the responsible validation node. The client device 614 can then send the full authentication transmission to the validation node 608 using the received validation node address.Docket No. 1988.0497WO
[0153] In some examples, the client node 602 can enter the distributed network with different permissions. For example, the client node 602 can be a read-only router of data. As another example, the client node 602 can have permission to send messages to the distributed ledger node 610 updating one or more routing paths for one or more routing numbers. However, the client node 602 would be prevented from updating one or more routing paths for one or more routing numbers for other entities that control other routing numbers that are not associated with the client node 602 or that did not grant this permission. As another example, the distributed ledger node 610 can contain contracts and / or records that can validate the permission of a specific entity to change a specific routing record based on its digital signature. As another example, the consortium authority or other administrative entity controlling the distributed network can have additional privileges to, without limitation, add new members (e.g., client nodes, distributed ledger nodes, validation nodes, and / or client devices), add new signature credentials, add new keys, add new certifications, and also revoke any of the foregoing. In some examples, the foregoing permissions can be delegated to the client node 602, the distributed ledger node 610, and / or the validation node 608 if security, legal, and / or financial conditions are met. However, delegation is not required.
[0154] In some examples, one or more APIs can facilitate communication between components of the system 600 via the network 606. In other examples, one or more APIs are not required. Rather, the components of system 600 could be in direct communication and / or dedicated to one or more specified entities to allow the specified entities to keep data from being transferred to, transferred from, or transferred via non-specified entities. This may further promote data security and avoid detection of data traffic patterns by non-specified entities.
[0155] In some examples, entities could establish a standard for nodes having APIs based on the intended function of those nodes. For example, a first standard could be established for data routing nodes and a second standard could established for nodes performing mapping and / or authentication functions. As another example, a routing API, a mapping API, and a validation API can be established, which can allow for the same device or hardware configuration to perform these functions. However, the use of keys, including secret keys by the validation node 608 for authentication, can require storage of the keys in one or more HSMs, to promote key security and ensure that the keys are never entered into memory.
[0156] FIG. 7 illustrates a method 700 performed by a distributed network authentication system according to an example embodiment. For example, the method can be performed by theDocket No. 1988.0497WOdistributed network authentication system 600 and or by another distributed network authentication system.
[0157] In block 702, a client device can transmit an authentication request to a client node. The authentication request can include, without limitation, a routing number, a software version number, and / or an applet version number. The request can be made by an API call or other communication between the client device and the client node.
[0158] In block 704, after receiving the authentication request, the client node can transmit a query (e.g., via an API call) to a distributed ledger node. The distributed ledger node can contain a mapping, and the distributed ledger node can submit the query to the mapping.
[0159] In block 706, the query can return an identification of a validation node and / or a validation node address, and the distributed ledger node can transmit this identification to the client node.
[0160] In block 708, the client node can transmit the identification to the client device. After receiving the identification, the client device can proceed with authentication with the identified validation node and / or the identified validation node address, in block 710.
[0161] FIG. 8 illustrates a data transmission system 800 according to an example embodiment. As further discussed below, the system 800 may include a contactless card 802, a client device 804, a network 806, and a server 808. Although FIG. 8 illustrates single instances of the components, the system 800 may include any number of components.
[0162] The system 800 may include one or more contactless cards 802, which are further explained below. In some embodiments, the contactless card 802 may be in wireless communication, utilizing NFC in an example, with the client device 804.
[0163] The system 800 may include the client device 804, which may be a network-enabled computer. As referred to herein, a network-enabled computer may include, but is not limited to a computer device or a communications device including, for example, a server, a network appliance, a personal computer, a workstation, a phone, a handheld PC, a personal digital assistant, a thin client, a fat client, an Internet browser, or other device. The client device 804 also may be a mobile device; for example, a mobile device may include an iPhone, iPod, or iPad from Apple®, any other mobile device running Apple’s iOS® operating system, any device running Microsoft’s Windows® Mobile operating system, any device running Google’s Android® operating system, and / or any other smartphone, tablet, or like wearable mobile device.Docket No. 1988.0497WO
[0164] The client device 804 can include a processor and a memory, and it is understood that processing circuitry may contain additional components, including processors, memories, error and parity / CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary, to perform the functions described herein. The client device 804 may further include a display and input devices. The display may be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays. The input devices may include any device for entering information into the user’s device that is available and supported by the user’s device, such as a touch-screen, keyboard, mouse, cursor-control device, touch-screen, microphone, digital camera, video recorder or camcorder. These devices may be used to enter information and interact with the software and other devices described herein.
[0165] In some examples, the client device 804 may execute one or more applications, such as software applications that enable, for example, network communications with one or more components of the system 800 and transmit and / or receive data.
[0166] The client device 804 may be in communication with one or more server(s) 808 via one or more network(s) 806 and may operate as a respective front-end to back-end pair with the server 808. The client device 804 may transmit, for example, from a mobile device application executing on the client device 804, one or more requests to the server 808. The one or more requests may be associated with retrieving data from the server 808. The server 808 may receive the one or more requests from the client device 804. Based on the one or more requests from the client device 804, the server 808 may be configured to retrieve the requested data from one or more databases (not shown). Based on receipt of the requested data from the one or more databases, the server 808 may be configured to transmit the received data to the client device 804, the received data being responsive to the one or more requests.
[0167] The system 800 may include one or more networks 806. In some examples, the network 806 may be one or more of a wireless network, a wired network, or any combination of wireless network and wired network and may be configured to connect the client device 804 to the server 808. For example, the network 806 may include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless local area network (LAN), a Global System for Mobile Communication, a Personal CommunicationDocket No. 1988.0497WOService, a Personal Area Network, Wireless Application Protocol, Multimedia Messaging Service, Enhanced Messaging Service, Short Message Service, Time Division Multiplexing based systems, Code Division Multiple Access based systems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11 family of networking, Bluetooth, NFC, Radio Frequency Identification (RFID), Wi-Fi, and / or the like.
[0168] In addition, the network 806 may include, without limitation, telephone lines, fiber optics, IEEE Ethernet 802.3, a wide area network, a wireless personal area network, a LAN, or a global network, such as the Internet. In addition, the network 806 may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. The network 806 may further include one network or any number of the exemplary types of networks mentioned above, operating as a stand-alone network or in cooperation with each other. The network 806 may utilize one or more protocols of one or more network elements to which the network 806 is communicatively coupled. The network 806 may translate to or from other protocols and to one or more protocols of network devices. Although the network 806 is depicted as a single network, it should be appreciated that according to one or more examples, the network 806 may comprise a plurality of interconnected networks, such as, for example, the Internet, a service provider's network, a cable television network, corporate networks, such as credit card association networks, and home networks.
[0169] The system 800 may include one or more servers 808. In some examples, the server 808 may include one or more processors, which are coupled to memory. The server 808 may be configured as a central system, server, or platform to control and call various data at different times to execute a plurality of workflow actions. The server 808 may be configured to connect to the one or more databases. The server 808 may be connected to at least one client device 804.
[0170] FIG. 9 illustrates an example configuration of a contactless card 802, which may include a contactless card or a payment card, such as a credit card, a debit card, or a gift card, issued by a service provider as displayed as service provider indicia 902 on the front or back of the contactless card 802. In some examples, the contactless card 802 is not related to a payment card and may include, without limitation, an identification card. In some examples, the contactless card 802 may include a dual interface contactless payment card, a rewards card, and so forth. The contactless card 802 may include a substrate 908, which may include a single layer or one or more laminated layers composed of plastics, metals, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene,Docket No. 1988.0497WOpolycarbonate, polyesters, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card 802 may have physical characteristics compliant with the ID-1 format of the ISO / IEC 7816 standard, and the contactless card 802 may otherwise be compliant with the ISO / IEC 14443 standard. However, it is to be understood that the contactless card 802 according to the present disclosure may have different characteristics, and the present disclosure does not require a contactless card 802 to be implemented in a payment card.
[0171] The contactless card 802 may also include identification information 906 displayed on the front and / or back of the card and a contact pad 904. The contact pad 904 may include one or more pads and be configured to establish contact with a client device, such as an ATM, a user device, a smartphone, a laptop, a desktop, or a tablet computer via transaction cards. The contact pad 904 may be designed in accordance with one or more standards, such as the ISO / IEC 7816 standard, and enable communication in accordance with the EMV protocol. The contactless card 802 may also include processing circuitry, antenna, and other components as will be further discussed in FIG. 10. These components may be located behind the contact pad 904 or elsewhere on the substrate 908, for example, within a different layer of the substrate 908, and may be electrically and physically coupled with the contact pad 904. The contactless card 802 may also include a magnetic strip or tape, which may be located on the back of the card (not shown in FIG.9). The contactless card 802 may also include a Near-Field Communication (NFC) device coupled with an antenna capable of communicating via the NFC protocol. Embodiments are not limited in this manner.
[0172] As illustrated in FIG. 10, the contact pad 904 of FIG. 9 may include processing circuitry 1016 for storing, processing, and communicating information, including a processor 1002, a memory 1004, and one or more interface(s) 1006. It is to be understood that the processing circuitry 1016 may contain additional components, including processors, memories, error and parity / CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamperproofing hardware, as necessary, to perform the functions described herein.
[0173] The memory 1004 may be a read-only memory, write-once read-multiple memory, or read / write memory, e.g., RAM, ROM, and EEPROM, and the contactless card 802 may include one or more of these memories. A read-only memory may be factory programmable as read-only or one-time programmable. One-time programmability provides the opportunity to write onceDocket No. 1988.0497WOthen read many times. A write once / read-multiple memory may be programmed at a point in time after the memory chip has left the factory. Once the memory is programmed, it may not be rewritten, but it may be read many times. A read / write memory may be programmed and reprogramed many times after leaving the factory. A read / write memory may also be read many times after leaving the factory. In some instances, the memory 1004 may be an encrypted memory utilizing an encryption algorithm executed by the processor 1002 to encrypt data. In some embodiments, at least a portion of the memory 1004 may be a read / write memory, for example, allowing for the writing of virtual numbers 1026 and / or virtual number indicator 1030.
[0174] The memory 1004 may be configured to store one or more applet(s) 1008, one or more counter(s) 1010, a customer identifier 1014, and one or more account number(s) 1012, which may be virtual numbers 1026, and a virtual number indicator 1030. The one or more applet(s) 1008 may comprise one or more software applications configured to execute on one or more contactless cards, such as a lava® Card applet. However, it is to be understood that applet(s) 1008 are not limited to Java Card applets and, instead, may be any software application operable on contactless cards or other devices having limited memory. The one or more counter(s) 1010 may comprise a numeric counter sufficient to store an integer. The customer identifier 1014 may comprise a unique alphanumeric identifier assigned to a user of the contactless card 802, and the customer identifier 1014 may distinguish the user of the contactless card from other contactless card users. In some examples, the customer identifier 1014 may identify both a customer and an account assigned to that customer and may further identify the contactless card 802 associated with the customer’s account. As stated, the account number(s) 1012 may include thousands of one-time use virtual numbers 1026 associated with the contactless card 802. The applet(s) 1008 may be configured to manage the account number(s) 1012, for example, to select an account number(s) 1012, mark the selected account number(s) 1012 as used, and transmit the account number(s) 1012 to a mobile device or a client device 804 for autofilling by an autofilling service.
[0175] In some embodiments, the applet(s) 1008 may manage or select the account number(s) 1012, including virtual number(s) 1026 based on a virtual number indicator 1030. In various embodiments, the virtual number indicator 1030 may indicate a value or field associated with whether a virtual physical transaction is active on the contactless card 802 for a physical transaction. For example, if the virtual number indicator 1030 indicates that a virtual physical transaction is active (i.e., a virtual number 1026 is to be used as the card number for a physical transaction), then the applet(s) 1008 may use the virtual number 1026. In some embodiments, theDocket No. 1988.0497WOvirtual number indicator 1030 may be a binary value (e.g., yes / no, 0 / 1) having one value (e.g., “yes” or “1”) that indicates that a virtual physical transaction is active another value (e.g., “no” or 0) that indicates that a virtual physical transaction is not active. In various embodiments, the virtual number indicator 1030 may include a field, string, or other data structure storing other information, such as which number of a plurality of virtual numbers 1026 should be used. In other embodiments, the virtual number indicator 1030 may include virtual transaction information that defines the parameters of a virtual physical transaction, such as specifying that certain virtual numbers should be used with certain merchants, certain types of devices, certain geographic locations, and / or the like.
[0176] In some embodiments, the memory 1004 can include (e.g., have stored therein) the data from the fields illustrated in FIG. 4. The processor 1002 can then use the data from the fields to generate the message 400 as described above.
[0177] The processor 1002 and memory elements of the foregoing exemplary embodiments are described with reference to the contact pad 904, but the present disclosure is not limited thereto. It is to be understood that these elements may be implemented outside of the contact pad 904, entirely separate therefrom, or as further elements in addition to the processor 1002 and the memory 1004 elements located within the contact pad 904.
[0178] In some examples, the contactless card 802 may comprise one or more antenna(s) 1018. The one or more antenna(s) 1018 may be placed within the contactless card 802 and around the processing circuitry 1016 of the contact pad 904. For example, the one or more antenna(s) 1018 may be integral with the processing circuitry 1016, and the one or more antenna(s) 1018 may be used with an external booster coil. As another example, the one or more antenna(s) 1018 may be external to the contact pad 904 and the processing circuitry 1016.
[0179] In an embodiment, the coil of contactless card 802 may act as the secondary coil of an air core transformer. A terminal may communicate with the contactless card 802 by cutting power or amplitude modulation. The contactless card 802 may infer the data transmitted from the terminal using the gaps in the contactless card’s power connection, which may be functionally maintained through one or more capacitors. The contactless card 802 may communicate back by switching a load on the contactless card’s coil or load modulation. Load modulation may be detected in the terminal’s coil through interference. More generally, using the antenna(s) 1018, the processor 1002, and / or the memory 1004, the contactless card 802 provides a communications interface to communicate via NFC, Bluetooth, and / or Wi-Fi communications.Docket No. 1988.0497WO
[0180] As explained above, the contactless card 802 may be built on a software platform operable on smart cards or other devices having limited memory, such as JavaCard, and one or more or more applications or applets may be securely executed. The applet(s) 1008 may be added to the contactless card 802 to provide a one-time password (OTP) for multifactor authentication (MFA) in various mobile application-based use cases. The applet(s) 1008 may be configured to respond to one or more requests, such as near field data exchange requests, from a reader, such as a mobile NFC reader (e.g., of a mobile device or a point-of-sale terminal) and produce an NDEF message that comprises a cryptographically secure OTP encoded as an NDEF text tag.
[0181] One example of an NDEF OTP is an NDEF short-record layout (SR=1). In such an example, one or more applet(s) 1008 may be configured to encode the OTP as an NDEF type 4 well known type text tag. In some examples, NDEF messages may comprise one or more records. The applet(s) 1008 may be configured to add one or more static tag records in addition to the OTP record.
[0182] In some examples, the one or more applet(s) 1008 may be configured to emulate an RFID tag. The RFID tag may include one or more polymorphic tags. In some examples, each time the tag is read, different cryptographic data is presented that may indicate the authenticity of the contactless card. Based on the one or more applet(s) 1008, an NFC read of the tag may be processed, the data may be transmitted to a server, such as a server of a banking system, and the data may be validated at the server.
[0183] In some examples, the contactless card 802 and the server may include certain data such that the contactless card 802 card may be properly identified. The contactless card 802 may include one or more unique identifiers (not pictured). Each time a read operation takes place, the counter(s) 1010 may be configured to increment. In some examples, each time data from the contactless card 802 is read (e.g., by a mobile device), the counter(s) 1010 is transmitted to the server for validation and determination as to whether the counter(s) 1010 are equal (as part of the validation) to a counter of the server.
[0184] The one or more counter(s) 1010 may be configured to prevent a replay attack. For example, if a cryptogram has been obtained and replayed, that cryptogram is immediately rejected if the counter(s) 1010 has been read, used, or otherwise passed over. If the counter(s) 1010 has not been used, the counter(s) 1010 may be replayed. In some examples, the counter that is incremented on the card is different from the counter that is incremented for transactions. TheDocket No. 1988.0497WOcontactless card 802 is unable to determine the application transaction counter(s) 1010 since there is no communication between the applet(s) 1008 on the contactless card 802.
[0185] In some examples, the counter(s) 1010 may get out of sync. In some examples, to account for accidental reads that initiate transactions, such as reading at an angle, the counter(s) 1010 may increment but the application does not process the counter(s) 1010. In some examples, when the client device 804 is woken up, NFC may be enabled and the client device 804 may be configured to read available tags, but no action is taken responsive to the reads.
[0186] To keep the counter(s) 1010 in sync, an application, such as a background application, may be executed that would be configured to detect when the client device 804 wakes up and synchronize with the server of a banking system, indicating that if a read occurred due to detection, then the counter(s) 1010 should be moved forward. In other examples, Hashed One Time Password may be utilized such that a window of mis-synchronization may be accepted. For example, if within a threshold of 10, the counter(s) 1010 may be configured to move forward. But if within a different threshold number, for example within 10 or 1000, a request for performing re-synchronization may be processed, which requests via one or more applications that the user tap, gesture, or otherwise indicate one or more times via the user’s device. If the counter(s) 1010 increase in the appropriate sequence, then it possible to know that the user has done so.
[0187] The key diversification technique described herein with reference to the counter(s) 1010, the master key, and the diversified key is one example of encryption and / or decryption in a key diversification technique. This exemplary key diversification technique should not be considered limiting of the disclosure, as the disclosure is equally applicable to other types of key diversification techniques.
[0188] During the creation process of the contactless card 802, two cryptographic keys may be assigned uniquely per card. The cryptographic keys may comprise symmetric keys which may be used in both encryption and decryption of data. A Triple DES (3 DES) algorithm may be used by EMV and implemented by hardware in the contactless card 802. By using the key diversification process, one or more keys may be derived from a master key based upon uniquely identifiable information for each entity that requires a key.
[0189] In some examples, to overcome deficiencies of 3DES algorithms, which may be susceptible to vulnerabilities, a session key may be derived (such as a unique key per session). However, rather than using the master key, the unique card-derived keys and the counter may beDocket No. 1988.0497WOused as diversification data. For example, each time the contactless card 802 is used in operation, a different key may be used for creating the message authentication code (MAC) and for performing the encryption. This results in a triple layer of cryptography. The session keys may be generated by the one or more applets and derived by using the application transaction counter with one or more algorithms (as defined in EMV 4.3 Book 2 Al.3.1 Common Session Key Derivation).
[0190] Further, the increment for each card may be unique and either assigned by personalization or algorithmically assigned by some identifying information. For example, odd numbered cards may increment by 2 and even numbered cards may increment by 5. In some examples, the increment may also vary in sequential reads, such that one card may increment in sequence by 1, 3, 5, 2, 2,... repeating. The specific sequence or algorithmic sequence may be defined at personalization time or from one or more processes derived from unique identifiers. This can make it harder for a replay attacker to generalize from a small number of card instances.
[0191] The authentication message may be delivered as the content of a text NDEF record in hexadecimal ASCII format. In another example, the NDEF record may be encoded in hexadecimal format.
[0192] FIG. 11 is a timing diagram illustrating an example sequence flow 1100 for providing authenticated access according to one or more embodiments of the present disclosure. The sequence flow 1100 may include a contactless card 802 and a client device 804, which may include an application 1102 and a processor 1104.
[0193] At line 1108, the application 1102 communicates with the contactless card 802 (e.g., after being brought near the contactless card 802). Communication between the application 1102 and the contactless card 802 may involve the contactless card 802 being sufficiently close to a card reader (not shown) of the client device 804 to enable NFC data transfer between the application 1102 and the contactless card 802.
[0194] At line 1106, after communication has been established between the client device 804 and the contactless card 802, the contactless card 802 generates a message authentication code (MAC) cryptogram. In some examples, this may occur when the contactless card 802 is read by the application 1102. In particular, this may occur upon a read, such as an NFC read, of a near field data exchange (NDEF) tag, which may be created in accordance with the NFC Data Exchange Format. For example, a reader application, such as the application 1102, may transmit a message, such as an applet select message, with the applet ID of an NDEF producing applet.Docket No. 1988.0497WOUpon confirmation of the selection, a sequence of select file messages followed by read file messages may be transmitted. For example, the sequence may include “Select Capabilities file”, “Read Capabilities file”, and “Select NDEF file”. At this point, a counter value maintained by the contactless card 802 may be updated or incremented, which may be followed by “Read NDEF file.” At this point, the message may be generated which may include a header and a shared secret. Session keys may then be generated. The MAC cryptogram may be created from the message, which may include the header and the shared secret. The MAC cryptogram may then be concatenated with one or more blocks of random data, and the MAC cryptogram and a random number (RND) may be encrypted with the session key. Thereafter, the cryptogram and the header may be concatenated, and encoded as ASCII hex and returned in NDEF message format (responsive to the “Read NDEF file” message).
[0195] In some examples, the MAC cryptogram may be transmitted as an NDEF tag, and in other examples, the MAC cryptogram may be included with a uniform resource indicator (e.g., as a formatted string). In some examples, the application 1102 may be configured to transmit a request to the contactless card 802, the request comprising an instruction to generate a MAC cryptogram.
[0196] At line 1110, the contactless card 802 sends the MAC cryptogram to the application 1102. In some examples, the transmission of the MAC cryptogram occurs via NFC. However, the present disclosure is not limited thereto. In other examples, this communication may occur via Bluetooth, Wi-Fi, or other means of wireless data communication. At line 1112, the application 1102 communicates the MAC cryptogram to the processor 1104.
[0197] At line 1114, the processor 1104 verifies the MAC cryptogram pursuant to an instruction from the application 1102. For example, the MAC cryptogram may be verified, as explained below. In some examples, verification of the MAC cryptogram may be performed by a device other than client device 804, such as a server of a banking system in data communication with the client device 804. For example, the processor 1104 may output the MAC cryptogram for transmission to the server of the banking system, which may verify the MAC cryptogram. In some examples, the MAC cryptogram may function as a digital signature for purposes of verification. Other digital signature algorithms, such as public key asymmetric algorithms, for example, the Digital Signature Algorithm and the RSA algorithm or zero knowledge protocols, may be used to perform this verification.Docket No. 1988.0497WO
[0198] FIGS. 1-11 are generally directed to systems and methods to authenticate a contactless card based on information on the contactless card. However, as previously discussed, some embodiments disclosed herein can include systems and methods for synchronizing a counter stored on the contactless card with a corresponding counter stored on a server and associated with the contactless card.
[0199] As disclosed herein, it is to be understood that the contactless card can be one that includes EMV technology and certificates and / or one that includes authentication technology and encrypted cryptograms as disclosed herein. Embodiments are not limited in this regard and can be used in connection with contactless cards as would be known and understood by one of ordinary skill in the art.
[0200] FIGS. 12-16 are generally directed to embodiments for performing a virtual physical transaction according to some embodiments.
[0201] FIG. 12 is a block diagram that illustrates an example of a mobile device 1202 in accordance with disclosed embodiments. It is to be understood that the mobile device 1202 can be the same as or similar to the client device 614 and / or the client device 804.
[0202] As seen, the mobile device 1202 can include an interface 1204, a memory 1206, a processor 1212, and a display device 1214. The memory 1206 can be configured to store computer instructions configured to be executed by the processor 1212 to cause the processor 1212 to execute certain actions, and the computer instructions can be part of applications 1208 and / or an operating system 1210.
[0203] In some embodiments, the interface 1204 can include one or more antennas, such as a short-range communication antenna, one or more user interface devices, such as a key pad with hard or soft keys, and / or a camera, a microphone, a scanner, a card reader, or another device capable of reading or capturing images, information, or data within its range or field of view. Additionally or alternatively, the interface 1204 can include a Wi-Fi interface, a Bluetooth interface, an NFC interface, a serial bus interface, a universal serial bus (USB), and so forth.
[0204] In some embodiments, the memory 1206 can be any type of memory configured to store instructions to be processed by the processor 1212. Examples of the memory 1206 can include volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth.
[0205] In some embodiments, the processor 1212 can be any type of processor, microprocessor, circuit, circuit element (e.g., transistor, resistor, capacitor, inductor, and so forth), integratedDocket No. 1988.0497WOcircuit, application specific integrated circuit (ASIC), programmable logic device (PLD), digital signal processor (DSP), field programmable gate array (FPGA), multi-core processor, and so forth.
[0206] In some embodiments, the display device 1214 can include a display screen or other output device for displaying data, information, and / or graphics to a user of the mobile device 1202.
[0207] The memory 1206 can include the applications 1208 and / or the operating system 1210. In this regard, the applications 1208 can include any type of application configured to operate on the mobile device 1202. For example, the applications 1208 can include mobile banking applications, mobile credit card applications, business applications, social networking applications, marketplace applications, classifieds applications, communication applications, business productivity applications (e g., email, word processor, spreadsheet, etc.), storefront applications, money transfer applications, gaming applications, merchant applications, shopping mobile applications, and so forth.
[0208] The applications 1208 can be configured to operate within the operating system 1210. In some embodiments, the operating system 1210 can be an Android® operating system, Apple iOS® operating system, Windows Mobile Operating System®, and so forth. The operating system 1210 can be configured to provide services and instructions that execute and enable the applications 1208 to operate with hardware. For example, the operating system 1210 can be configured to operate with the hardware associated with the processor 1212 to process detections made by the interface 1204 and / or to transmit corresponding signals and data via the interface 1204. In some embodiments, the operating system 1210 can provide data to the applications 1208 processed by the operating system 1210. The applications 1208 can process such data, including performing authentications of the data, communicating the data to other devices or servers, and so forth. In some embodiments, at least a portion of the operating system 1210 can be configured to perform one or more authentication steps.
[0209] FIG. 13 is a block diagram that illustrates an example of a server device 1302 in accordance with disclosed embodiments. It is to be understood that the server device 1302 can be the same as or similar to the client node 602, the validation node 608, the distributed ledger node 610, and / or the server 808.
[0210] As seen, the server device 1302 can include an interface 1304, a memory 1306, and a processor 1308. The memory 1306 can be configured to store computer instructions configuredDocket No. 1988.0497WOto be executed by the processor 1308 to cause the processor 1308 to execute certain actions. The computer instructions can be part of an operating system 1310.
[0211] In some embodiments, the interface 1304 can be wired or wireless. For example, the interface 1304 can include a Wi-Fi 33 interface, a Bluetooth interface, an NFC interface, a serial bus interface, a universal serial bus (USB), and so forth.
[0212] In some embodiments, the memory 1306 can be any type of memory configured to store instructions to be processed by the processor 1308. Examples of the memory 1306 can include volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth.
[0213] In some embodiments, the processor 1308 can be any type of processor, microprocessor, circuit, circuit element (e.g., transistor, resistor, capacitor, inductor, and so forth), integrated circuit, application specific integrated circuit (ASIC), programmable logic device (PLD), digital signal processor (DSP), field programmable gate array (FPGA), multi-core processor, and so forth.
[0214] As explained above, the memory 1306 can include the operating system 1310. In some embodiments, the operating system 1310 can include a Microsoft Windows server operating system, a Linux / Unix server operating system, a cloud server operating system, such as an Amazon AWS operating system, and so forth. The operating system 1310 can be configured to provide services and instructions that execute to operate with hardware. For example, the operating system 1310 can be configured to operate with the hardware associated with the processor 1308 to process signals and data received by the interface 1304, including performing authentication of such data and updating stored data, including counter values. In some embodiments, at least a portion of the operating system 1310 can be configured to perform one or more authentication steps.
[0215] FIG. 14 is a block diagram that illustrates an example of a system 1400 in accordance with disclosed embodiments. The system 1400 can include at least a mobile device 1202, a contactless card 1404, and a server device 1302 in communication with the mobile device 1202. It is to be understood that the mobile device 1202 can be the same as or similar to the client device 614 and / or the client device 804. It is also to be understood that the server device 1302 can be the same as or similar to the client node 602, the validation node 608, the distributed ledger node 610, and / or the server 808.Docket No. 1988.0497WO
[0216] In some embodiments, the contactless card 802 can be used in connection with a virtual physical transaction. In various embodiments, a virtual physical transaction includes a physical transaction (i.e., using the contactless card 802 with a physical transaction device) using virtual card information, such as virtual numbers 1026, stored on the contactless card 802.
[0217] As shown in FIG. 14, the user may authenticate 1451 the contactless card 802 with a user device, such as the mobile device 1202, using processes according to some embodiments described in the present disclosure. For instance, the contactless card 802 can be tapped on or brought within a communication range of the mobile device 1202 and can exchange information with the mobile device 1202 to confirm an identity of an authorized cardholder. In particular, in some embodiments, a user can tap or otherwise bring the contactless card 802 within a communication range of a short-range communication antenna of the mobile device 1202, and the contactless card 802 can transmit data to the mobile device 1202 and / or the mobile device 1202 can read the data from the contactless card 802. In some embodiments, such data can be retrieved from a memory embedded in a body of the contactless card 802 and transmitted via an antenna embedded in the body of the contactless card 802. The authentication of the contactless card with the mobile device 1202 via server device 1302 and / or the switchboard system may proceed according to the encryption and authentication processes described with respect to FIGS.1-11.
[0218] In some embodiments, the authentication information exchange 1451 between the mobile device 1202 and the contactless card 802 to establish authentication between the mobile device 1202 and the contactless card 802 may be generated based on the account numbers assigned to the card at the time of manufacture and / or personalization. For example, encrypted data (e.g., message 400 in FIG. 4 or portions thereof) used for authentication of the mobile device 1202 and the contactless card 802 used in authentication 1451 may be based on the account numbers assigned to the card at the time of manufacture and / or personalization.
[0219] In other embodiments, the authentication information exchange 1451 may include virtual information, such as a virtual pUID, PAN, and / or the like. For example, encrypted data (e.g., message 400 in FIG. 4 or portions thereof) used for authentication of the mobile device 1202 and the contactless card 802 used in authentication 1451 may be based on virtual information. In some embodiments, a virtual number may be dedicated for use for authentication 1451. For example, a virtual authentication card number (e.g., pUID) may be stored on the contactless card and used for the authentication information exchange 1451. In variousDocket No. 1988.0497WOembodiments, the active or previously used virtual information may be used for the authentication information exchange 1451. Embodiments are not limited in this context, as other methods for selecting virtual information for the authentication information exchange 1451 may be used.
[0220] The user may activate a service provider application 1430 that may be or may include a banking app, credit card app, digital wallet app, and / or the like that allows the user to interact with the contactless card 802 (e.g., via applet(s) 1008) and a service provider backend that manages the contactless card 802 and associated information and processes transactions as described in the present disclosure.
[0221] The user may select to access virtual functions for the contactless card 802 via the application 1430. In some embodiments, the application 1430 may present GUI elements that allow a user to specify, define, delete, modify, or otherwise interact with virtual functions for the contactless card 802.
[0222] In one example, a view function allows a user to view virtual information for the contactless card 802 on a display of the mobile device 1202. The virtual information may include virtual card numbers and / or virtual physical transaction parameters. The virtual information may include transactions performed using virtual card numbers and associated data (e.g., time, place, transaction type, transaction amount, virtual number, and / or the like). The virtual information may be pulled from information stored on the mobile device 1202, the contactless card 802, and / or the server device 1302.
[0223] In some embodiments, the contactless card 802 may be associated with one “universal” virtual card number. The universal virtual card number may be used in all virtual physical transactions. In other embodiments, the contactless card 802 may be associated with a plurality of virtual card numbers. A portion of the plurality of virtual card numbers may be associated with specific parameters (e.g., Virtual Card Number A may be used in connection with Merchant A, Virtual Card Number B may be used in connection with Geographic Location B, etc.). One of the plurality of virtual card numbers may be a default virtual card number used if a parameterbased situation does not exist (e.g., parameters and associated virtual card numbers have been specified for Merchant A and Geographic Location B; the default virtual card number is used for all virtual physical transactions that occur outside of Merchant A and Geographic Location B). A portion of the plurality of virtual card numbers may be associated with time limits or expirationDocket No. 1988.0497WOdates. For example, a virtual card number may be deleted or deactivated after a specified duration (e.g., 24 hours or a threshold number of uses).
[0224] In some embodiments, a virtual card number may have a limited number of uses. For example, a virtual card number may be a one-time use number that is automatically removed following use in a virtual physical transaction. In various embodiments, the number of uses may be a form of the duration parameter that may be specified by a user via the mobile device 1202. In some embodiments, a default for a contactless card 802 may be a single-use virtual card number that must be specifically changed by the user (for instance, a limit of 5 uses, no use limit, and / or the like).
[0225] In one example, a modify function allows a user to modify the virtual information associated with the contactless card. The modify function may allow a user to add virtual information, such as a virtual card number, to the contactless card 802 (and, therefore, to the card information 1420). For example, via the application 1430, the user may select to add a virtual number to the contactless card 802. Virtual information (such as a virtual card number) may be generated by the mobile device 1202 and pushed for storage at the contactless card 802 and / or the server device 1302 (as card information 1420). In other embodiments, the request by a user to generate virtual information (such as a virtual card number) selected at the mobile device 1202 may be communicated 1452 to the server device 1302, and the server device 1302 generates the virtual information. The virtual information generated by the server device 1302 is transmitted to the mobile device 1202 (and may be stored on the mobile device 1202). The mobile device 1202 transmits the virtual information to the contactless card 802 for storage on the contactless card 802.
[0226] The modify function may allow a user to view and delete virtual information stored on the contactless card 802. For example, a user may view a list of virtual card numbers stored on the contactless card 802 via a display of the mobile device 1202. The list of virtual card numbers may be presented with context information, such as associated parameters (e.g., Virtual Number A is used in connection with Merchant A), creation date, number of uses, transaction amounts, transaction totals, expiration date, active / inactive status, and / or the like. The user may select one or more virtual card numbers and delete the virtual card number, activate / deactivate the virtual card number, associate the virtual card number with a parameter, change the expiration date of the virtual card number, and / or the like.Docket No. 1988.0497WO
[0227] In some embodiments, when a virtual card number is deleted, the user may select to regenerate the virtual card number using the application 1430 through the mobile device 1202. For instance, a deleted virtual card number associated with a parameter (e.g., a duration parameter) that has been deleted may be regenerated. In one example, the deleted virtual card number may be regenerated directly by the user via adding a new virtual card number through the modify function. In another example, the deleted virtual card number may be regenerated by the mobile device 1202 or the server device 1302 when the corresponding virtual card number is required for a virtual physical transaction. For example, a contactless card 802 may have one virtual card number used for virtual physical transactions. The user may delete the virtual card number, such that no virtual card number is stored on the contactless card 802. The mobile device 1202 (either directly or via the server device 1302) may determine that there is no virtual card number on the contactless card 802 and a new virtual card number is generated and pushed for storage on the contactless card. In another example, when virtual physical transactions are activated, if a corresponding virtual card number does not exist, the mobile device 1202 (either directly or via the server device 1302) may generate a virtual card number and push it for storage on the contactless card 802. In an additional example, the mobile device 1202 may access the virtual information associated with the contactless card 802 and determine whether a virtual card number exists relating to each parameter. If a virtual card number does not exist for a parameter, the mobile device 1202 (either directly or via the server device 1302) may generate a virtual card number and push it for storage on the contactless card 802 (or use a default virtual card number). In a further example, responsive to a user deleting a virtual card number, the mobile device 1202 may ask the user whether they would like to create a new virtual card number to replace the deleted virtual card number. The mobile device 1202 (either directly or via the server device 1302) may generate a virtual card number and push it for storage on the contactless card 802 responsive to the user selecting to create a new virtual card number to replace the deleted virtual card number.
[0228] The modify function may allow a user to define parameters for virtual physical transactions. For instance, the parameters may specify a duration for the virtual physical transaction (e.g., time duration, such as the virtual card number is active for 24 hours, number of uses duration, such as a one-time use virtual card number), a geographic location (e.g., the virtual card number is active within a certain geographic location or range), a time of day (e.g., the virtual card number is to be used after 8:00 pm), a specific merchant, specific devices or deviceDocket No. 1988.0497WOconfigurations (e.g., POS, ECR, fuel pumps, checkout kiosks, chip readers, etc.), and / or the like. In various embodiments in which the contactless card 802 stores multiple virtual card numbers, the modify function may allow a user to specify which virtual card number is to be used with which parameter (e.g., a first virtual card number is to be used for a specific merchant parameter, a second virtual card number is to be used for a specific geographic location parameter, and / or the like).
[0229] In one example, an activation function allows a user to activate a virtual physical transaction for the contactless card 802. Activation of virtual physical transactions for the contactless card 802 may cause future transactions with the card to proceed using virtual information stored on the contactless card 802. As part of the activation of the virtual physical transaction, the user may specify transaction parameters for the virtual physical transaction via the application 1430 according to some embodiments. For example, a user selects the activation function and specifies a parameter that only the next physical transaction with the contactless card 802 is a virtual physical transaction. In another example, a user selects the activation function and specifies that all future transactions are to be virtual physical transactions until virtual physical transactions are deactivated by the user. In a further example, a user selects the activation function and specifies a parameter that transactions with Merchant A are virtual physical transactions. In an additional example, activated virtual physical transactions may be performed accordingly to previously-defined parameters existing prior to activation. For instance, a user may activate virtual physical transactions, but only according to defined parameters. Accordingly, although virtual physical transactions are activated, if a geographic region parameter has been defined, then virtual physical transactions may only be active when within the geographic region.
[0230] In some embodiments, a deactivation function allows a user to deactivate or otherwise disable virtual physical transactions for the contactless card 802. If the virtual physical transactions for the contactless card 802 are deactivated, the virtual number indicator is updated to reflect that virtual physical transactions have been deactivated. When virtual physical transactions are deactivated for the contactless card 802, physical transactions involving the contactless card 802 revert back to using the assigned card information (e.g., the pUID, PAN, etc. assigned at the time of manufacture and / or personalization).
[0231] In some embodiments, multiple virtual card numbers may be stored on a contactless card. The deactivation function may allow a user to view, select, and deactivate one or moreDocket No. 1988.0497WOspecific virtual card numbers instead of, for instance, disabling all virtual physical transactions for the entire contactless card 802.
[0232] The virtual physical transaction activation and parameters (e.g., virtual physical transaction activation information) may be transmitted 1452 to the server device 1302. In some embodiments, the transmission 1452 may include the virtual number indicator, which may be used by the server device 1302 to determine whether a virtual physical transaction is active and, if so, the parameters of the virtual physical transaction. The server device 1302 may generate virtual information for the virtual physical transaction. The virtual information may be or may include a virtual card number, a virtual PAN, a virtual pUID, a virtual expiration date, a virtual CVV, zip code, and / or the like. The server device 1302 may store the virtual information in association with the contactless card 802 (or an account associated with the contactless card 802) as card information 1420. In this manner, when the virtual physical transaction is performed, the server device 1302 may use the virtual information stored in the card information 1420 to process and authenticate the transaction (i.e., instead of the assigned card information, such as the pUID, PAN, etc., assigned to the card at the time of personalization). In some embodiments, the virtual information may be presented to the user via an interface of the mobile device 1202. In other embodiments, the virtual information may be stored in the application. For example, as part of the virtual physical transaction, a physical transaction device may ask for a zip code, CVV, and / or the like, which may be virtual. The user may look up the virtual zip code, CVV, and / or the like on the application 1430 to enter into the physical transaction device to proceed with the transaction.
[0233] The server device 1302 may communicate 1453 the virtual information to the mobile device 1202, such as any virtual numbers to be used in a future virtual physical transaction. The mobile device 1202 may transmit 1454 the virtual information to the contactless card 802. In some embodiments, the contactless card 802 may store the virtual information as the virtual number 1026 in the memory 1004. In various embodiments, the virtual number indicator 1030 may be set on the contactless card to correspond with the virtual information.
[0234] In some embodiments, the virtual information may include one or more of a virtual number (to be used in a virtual physical transaction), an indicator setting (to update the virtual number indicator 1030), parameter values (numerical or alphanumerical values associated with virtual physical transactions, such as merchant identifiers, device identifiers, and / or the like). For example, via application 1430, a user may specify that the next transaction should be a virtualDocket No. 1988.0497WOphysical transaction. The virtual information may include a virtual card number and an indicator that the next transaction is a virtual physical transaction.
[0235] In some embodiments, the virtual number indicator may be one or more numbers, one or more alphanumeric characters, a string, a field, and / or the like (see, for example, virtual number indicator 1030 of FIG. 10). In some embodiments, the virtual number indicator may include a field of bits, bytes, numbers, characters, and / or the like to store information on the contactless card 802 associated with virtual physical transactions. In various embodiments, the virtual number indicator may include a bit or other value indicating whether a virtual physical transaction is active (for instance, set to “1” or “yes” to indicate that the next transaction is a virtual physical transaction). In another example, a virtual physical transaction counter may be set to indicate that only the next transaction is to be a virtual physical transaction.
[0236] The virtual number indicator may be a string or field of values that includes one or more parameter bits, values, codes, and / or the like indicating whether a parameter has been set or active. For example, a duration bit may be set to indicate that a duration parameter has been defined. In another example, a geographic location bit may be set to indicate that a geographic location parameter has been defined. In an additional example, a virtual card number bit may specify which virtual card number of a plurality of virtual card numbers stored on the contactless card 802 should be used in a virtual physical transaction.
[0237] The values associated with the virtual number indicator bits, bytes, numbers, alphanumeric characters, or symbols may be stored on the contactless card 802 and / or the server device 1302. For instance, the duration bit may be set to indicate that a duration has been defined, the duration value (e.g., 24 hours, a specific date or date range, etc.) may be stored on the contactless card 802 and / or may be stored on the server device 1302 as card information 1420. In various embodiments, if a parameter bit is set, the corresponding value may be determined and used as part of the virtual physical transaction. For example, if the duration bit is set, the corresponding duration value may be determined (e.g., located in memory, a database, or file stored on the contactless card or server device) and used to evaluate whether a physical transaction is still active (i.e., whether the time defined by the duration has expired).
[0238] Accordingly, in one embodiment, the virtual number indicator may include a string of values that may be evaluated to determine whether a virtual physical transaction is active and, if active, parameters for performing the virtual physical transaction. For instance, the virtual number indicator may be a string of binary bits that may have the form: <virtual physicalDocket No. 1988.0497WOtransaction activated><duration parameter activated Xgeographic parameter activated><merchant parameter activated>. In one example, the string 1100 (where “1” = “yes” and “0” = “no) indicates that a virtual transaction is activated, a duration parameter is active, and the geographic and merchant parameters have not been defined or are otherwise inactive. The virtual number indicator may be transmitted to the mobile device 1202 from the contactless card 802 and to the server device 1302. The corresponding parameter information may be stored on the mobile device 1202 and / or the server device 1302.
[0239] In another embodiment, the virtual number indicator may be a string of bits, bytes, words, integers, decimal values, alphanumeric characters, codes, symbols, and / or the like that may store activation information and parameter values. For example, the virtual number indicator may be a string having the form: <binary: virtual physical transaction activated>.<binary: duration parameter activated >.<integer: duration (minutes)>.<integer: merchant code>. In one example, the virtual number indicator having the value 1.1.1440.100 may indicate that virtual physical transactions are active, that the duration parameter is active, the duration is 24 hours (1440 minutes), and the virtual physical transaction is active for Merchant A (defined by merchant code 100, for instance, stored in memory, a database, a file, or other data or memory structure).
[0240] In some embodiments, the virtual number indicator only indicates whether virtual physical transactions are active on the contactless card 802. The server device 1302 determines that virtual physical transactions are active based on the virtual number indicator and evaluates parameters stored in the card information 1420 to determine whether the transaction is to proceed as a physical transaction (i.e., using assigned card information) or as a virtual physical transactions (i.e., using virtual card number(s).
[0241] Accordingly, via application 1430, a user (e.g., visiting a different geographic area) may specify that all transactions over a specified time period (the duration of the trip) or in a specific location (the different geographic area) are to be virtual physical transactions. The virtual information may include one or more virtual card numbers and an indicator that all transactions during the time period or at the specified geographic location are to be virtual physical transactions.
[0242] In various embodiments, the virtual information is stored (in various forms) on the contactless card 802. In some embodiments, the virtual information may be stored on the contactless card 802 and the server device 1302. For example, the virtual number may be storedDocket No. 1988.0497WOon the contactless card 802 and the server device 1302 (e.g., as card information 1420). However, the parameters for the virtual physical transaction may be stored only at the server device 1312. In this manner, in some embodiments, the contactless card 802 only has to store indicator values or bits, and the actual parameter values (e.g., geographic locations, time durations, merchants, etc.) can be stored and evaluated at the server device 1302. When a transaction via a physical transaction device is initiated, the server device 1302 may determine whether a virtual physical transaction is active based on the parameters. For instance, the server device 1302 may check whether conditions in the virtual information, such as time, location, device, merchant, etc. are active and proceed accordingly. In some embodiments, the server device 1302 may evaluate the parameters based on transaction information received from the physical transaction device. For example, if the virtual information stored in the card information 1420 indicates that virtual physical transactions are to be conducted in City A and the user is in City B, then a virtual physical transaction will not be performed. If the user subsequently performs a physical transaction in City A, while the virtual information is still active, then a virtual physical transaction will be performed.
[0243] FIG. 15 is a block diagram that illustrates an example of a system 1500 in accordance with disclosed embodiments. The system 1400 can include at least a physical transaction device (e.g., a POS device) 1502, a server device 1302, and a contactless card 802. In the embodiment depicted in FIG. 15, a virtual physical transaction is active on the contactless card 802 (e.g., indicated via the virtual number indicator on the card and / or the virtual information stored for the contactless card 802 at server device 1302).
[0244] A user may initiate a physical transaction with POS device 1502 via physical contact (e.g., touching (“tap-to”), inserting, or via wireless communication, such as Bluetooth, NFC, and / or the like) of the contactless card 802 with the POS device 1502. For instance, the contactless card 802 can be tapped on or brought within a communication range of the POS device 1502 and can exchange information with the POS device 1502 to confirm an identity of an authorized cardholder.
[0245] The POS device 1502 may perform authentication of the contactless card 802 and the transaction via communicating with the server device 1302 according to embodiments described in the present disclosure. The server device 1302 determines via the virtual information 1420 stored in the card information 1420 or communicated via the contactless card 802 that a virtual physical transaction is active. For example, as part of the authentication process for theDocket No. 1988.0497WOcontactless card, the virtual number indicator 1030 may be communicated from the contactless card 802 to the server device 1302 via the POS device 1502. Parameters may be evaluated at the server device 1302 based on transaction information provided by the POS device 1502 (e.g., a location of the POS device, a merchant associated with the transaction or POS device, date and time information, and / or the like).
[0246] Based on the virtual information stored in the card information 1420 or the virtual number indicator 1030 transmitted by the contactless card via the POS device 1502, the server device 1302 determines that the virtual card information should be used for the transaction. Accordingly, transaction processes for the contactless card 802 facilitated by the POS device 1502 use the virtual number 1026 where applicable. For example, the virtual number 1026 may be used as a PAN, pUID, CVV, expiration date, zip code, and / or the like for the contactless card 802. In another example, the virtual number 1026 may be used as part of a key, encryption value, and / or the like used to authenticate the contactless card 802 with the server device 1302 and / or the POS device 1502.
[0247] The physical transaction between the contactless card 802 and the POS device 1502 may be processed using the virtual number 1206. In some embodiments, a merchant, retailer, or other entity associated with the POS device 1502 may store information associated with the contactless card 802, either on the POS device 1502 itself or on associated network. For example, an entity associated with the POS device 1502 may store a credit card number, PAN, pUID, expiration date, zip code, CVV, and / or the like. If the entity network or POS device 1502 is maliciously accessed for unauthorized purposes, the information of the contactless card 802 may be compromised. However, during a virtual physical transaction according to various embodiments, some or even all of the information of the contactless card 802 stored at the POS device 1502 or on an entity network may be virtualized so that the ability of unauthorized users to use the contactless card 802 information is limited and even completely eliminated. In addition, the need for a user to obtain a new physical card in the event of a security breach of the POS device 1502 or related entity networks is eliminated because the attackers do not have the physical contactless card information.
[0248] Included herein are one or more logic flows and sequence flows representative of exemplary methodologies for performing novel aspects of the disclosed architecture. While, for purposes of simplicity of explanation, the one or more methodologies shown herein are shown and described as a series of acts, those skilled in the art will understand and appreciate that theDocket No. 1988.0497WOmethodologies are not limited by the order of acts. Some acts may, in accordance therewith, occur in a different order and / or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation. Blocks designated with dotted lines may be optional blocks of a logic flow.
[0249] A logic flow or a sequence flow may be implemented in software, firmware, hardware, or any combination thereof. In software and firmware embodiments, a logic flow or a sequence flow may be implemented by computer executable instructions stored on a non-transitory computer readable medium or machine readable medium. The embodiments are not limited in this context.
[0250] In sequence flows 1600-2200 of FIGS. 16-22, for the sake of simplifying the diagrams and avoiding redundancy, certain steps for establishing communication between components and / or authenticating components are not depicted. Unless specified otherwise, communication and authentication between components, such as contactless card 802, mobile device 1202, and / or server device 1302, may occur according to processes described in FIGS. 1-11 of the present disclosure. Functions performed by the mobile device 1202 may be performed by the application 1430. Functions performed by the contactless card may be performed by the applet(s) 1008.
[0251] Sequence flows 1600-2000 include processes for a contactless card 802, a mobile device 1202, and a server device 1302 for provisioning, modifying, and / or the like virtual information on a contactless card 802 according to some embodiments. Sequence flows 2100 and 2200 include processes for a contactless card 802, a server device 1302, and a physical transaction device 1502 (e.g., a POS or ECR device) for performing a virtual physical transaction according to some embodiments.
[0252] FIG. 16 is a timing diagram illustrating an example sequence flow 1600 for provisioning virtual information, such as a new virtual card number, for a contactless card according to embodiments of the present disclosure.
[0253] As shown in FIG. 16, at line 1601, the mobile device 1202 receives user input to add a virtual card number to the contactless card 802. The mobile device 1202 generates a new virtual card number at line 1602. At line 1603, the new virtual card number is transmitted to the server device 1302. The server device 1302 stores the new virtual card number as card information forDocket No. 1988.0497WOthe contactless card 802 at line 1604. The mobile device 1202 also transmits the new virtual card number to the contactless card 802 at line 1605. The contactless card 802 stores the new virtual card in memory number at line 1606.
[0254] FIG. 17 is a timing diagram illustrating an example sequence flow 1700 for provisioning virtual information, such as a new virtual card number, for a contactless card according to embodiments of the present disclosure.
[0255] As shown in FIG. 17, at line 1601, the mobile device 1202 receives user input to add a virtual card number to the contactless card 802. The mobile device 1202 communicates the new virtual number request to the server device 1302 at line 1701. The server device 1302 generates a new virtual card number at line 1702. The server device 1302 stores the new virtual card number as card information 1420 for the contactless card 802 at line 1703. At line 1705, the server device 1302 communicates the new virtual card number to the mobile device 1202. The mobile device 1202 transmits the new virtual card number to the contactless card 802 at line 1605. The contactless card 802 stores the new virtual card number at line 1606.
[0256] FIG. 18 is a timing diagram illustrating an example sequence flow 1800 for activating virtual physical transactions for a contactless card according to embodiments of the present disclosure.
[0257] As shown in FIG. 18, at line 1801, the mobile device 1202 receives user input to activate virtual physical transactions for the contactless card 802. At line 1802, the mobile device 1202 requests acknowledgment that the contactless card 802 has a virtual card number stored on the contactless card 802. At line 1803, the contactless card 802 sends acknowledgement that a virtual card number is stored on the contactless card 802 (or sends the actual active virtual card number(s)). If the contactless card 802 indicates that an active virtual card number does not exist, then a new virtual card number may be added, for instance, according to sequence flow 1600 or 1700.
[0258] At line 1804, the mobile device 1202 communicates to the server device 1302 that virtual physical transactions for the contactless card 802 has been activated via the mobile device 1202. The server device 1302 verifies that a virtual card number for the contactless card is stored in the card information for the contactless card at the server device at line 1805 (e.g., via checking the card information for the contactless card). If the server device 1302 cannot verify that an active virtual card number exists for the contactless card 802, then a new virtual card number may be added (or a previous virtual card number stored on the contactless card may be replaced), forDocket No. 1988.0497WOinstance, according to sequence flow 1600 or 1700. Responsive to verification of a virtual card number for the contactless card 802 via line 1805, the server device updates the card information for the contactless card 802 at line 1806, indicating that virtual physical transactions are active for the contactless cad 1802.
[0259] At line 1807, the server device 1302 transmits an acknowledgement message to the mobile device 1202 that virtual physical transactions have been successfully updated for the contactless card 802 at the server device 1302. Responsive to receiving the acknowledgement at line 1807, the mobile device 1202 sends instructions to the contactless card 802 to update the virtual number indicator at line 1808. At line 1809, the contactless card 802 updates the virtual number indicator to indicate that virtual physical transactions have been activated.
[0260] FIG. 19 is a timing diagram illustrating an example sequence flow 1900 for deactivating virtual physical transactions for a contactless card according to embodiments of the present disclosure.
[0261] As shown in FIG. 19, at line 1901, the mobile device 1202 receives user input to deactivate virtual physical transactions for the contactless card 802. At line 1902, the mobile device 1202 communicates a deactivation message to the contactless card 802. At line 1903, the contactless card 802 updates the virtual number indicator to indicate that virtual physical transactions have been deactivated. The contactless card 802 transmits a deactivation acknowledgement message to the mobile device 1202 at line 1904.
[0262] At line 1905, the mobile device 1202 communicates a deactivation message to the server device 1302. At line 1906, the server device 1302 updates the card information for the contactless card 802 to indicate that virtual physical transactions have been deactivated. The server device 1302 transmits a deactivation acknowledgement message to the mobile device 1202 at line 1907.
[0263] FIG. 20 is a timing diagram illustrating an example sequence flow 2000 for activating or updating (e.g., changing the value) of a virtual physical transaction parameter for a contactless card according to embodiments of the present disclosure.
[0264] As shown in FIG. 20, at line 2001, the mobile device 1202 receives user input to activate or update a virtual physical transaction parameter for the contactless card 802. For example, a user may provide input to mobile device 1202 for a “merchant” parameter that virtual physical transactions are to be performed for Merchant A (or not for Merchant B). At line 2002, the mobile device 1202 requests acknowledgment that the contactless card 802 has a virtual card number stored on the contactless card 802. At line 2003, the contactless card 802 sends acknowledgementDocket No. 1988.0497WOthat a virtual card number is stored on the contactless card 802 (or sends the actual active virtual card number(s)). If the contactless card 802 indicates that an active virtual card number does not exist, then a new virtual card number may be added, for instance, according to sequence flow 1600 or 1700.
[0265] At line 2004, the mobile device 1202 communicates to the server device 1302 that a virtual physical transaction parameter has been activated or updated via the mobile device 1202. At line 2004, any parameter information is also transmitted by the mobile device 1202 to the server device, such as corresponding values. For instance, if a duration parameter has been set specifying that virtual physical transactions are active for 24 hours, the 24 hours information is transmitted at line 2004.
[0266] The server device 1302 verifies that a virtual card number for the contactless card 802 is stored in the card information for the contactless card 802 at the server device 1302 at line 2005 (e.g., via checking the card information for the contactless card). If the server device 1302 cannot verify that an active virtual card number exists for the contactless card 802, then a new virtual card number may be added (or a previous virtual card number stored on the contactless card may be replaced), for instance, according to sequence flow 1600 or 1700. Responsive to verification of a virtual card number for the contactless card 802 via line 2005, the server device 1302 updates the card information for the contactless card 802 at line 2006, indicating that a virtual physical transaction parameter has been activated and / or updating the new value information.
[0267] At line 2007, the server device 1302 transmits an acknowledgement message to the mobile device 1202 that the card information for the contactless card 802 been successfully updated at the server device 1302. Responsive to receiving the acknowledgement at line 2007, the mobile device 1202 sends instructions to the contactless card 802 to update the virtual number indicator at line 2008. At line 2009, the contactless card 802 updates the virtual number indicator to indicate that a virtual physical transaction parameter has been activated and / or updating any value, code, etc. information stored in the virtual number indicator.
[0268] FIG. 21 is a timing diagram illustrating an example sequence flow 2100 for performing a virtual physical transaction according to some embodiments. In the embodiment of FIG. 21, virtual parameter activation is globally set for the contactless card 802 via a bit or other value in the virtual number indicator. For example, whether virtual physical transactions are active forDocket No. 1988.0497WOthe contactless card 802 is not dependent on a parameter (e.g., whether the card is being used at a particular merchant, time period, location, and / or the like).
[0269] As shown in FIG. 21, at line 2101, responsive to the contactless card 802 establishing operable communication with the physical transaction device 1502, the physical transaction device 1502 initiates the transaction with the contactless card 802 at line 2101. The contactless card 802 determines whether virtual physical transactions are active for the contactless card at line 2102. For example, the contactless card 802 may evaluate the value of a bit or other value in the virtual number indicator. If the virtual number indicator indicates that virtual physical transactions are not active, then the transaction may proceed as a typical physical transaction using the assigned card number(s) for the contactless card 802. If the virtual number indicator indicates that virtual physical transactions are active, the contactless card 802 may access the virtual card number for the card and generate the card information (e.g., according to FIGS. 1-11) using the virtual card number at line 2103.
[0270] The contactless card 802 may transmit the card information to the physical transaction device 1502 at line 2104. The physical transaction device 1502 may forward the card information to the server device 1302 for authentication and transaction processing at line 2105. Additional communication exchanges between the physical transaction device 1502, the server device 1302, and / or the contactless card 802 may occur that are specific to transaction processing and / or authentication for the particular protocol (for instance, standard EMV protocols), but are not shown to simplify the figure. Information necessary for the server device 1302 to process the transaction, such as the transaction amount, location, protocol information, and / or the like may also be transmitted by the physical transaction device 1502 in line 2105 (and / or in the additional communication exchanges).
[0271] At line 2106 the server device 1302 may determine whether virtual physical transactions are active for the contactless card. For example, the server device 1302 may access card information for the contactless card 802 and evaluate a value indicating whether virtual physical transactions are active (e.g., the same or similar to the virtual number indicator stored on the contactless card 802). If the card information indicates that virtual physical transactions are not active, then the transaction may proceed as a typical physical transaction using the assigned card number for the contactless card. If the card information indicates that virtual physical transactions are active, the server device 1302 may authenticate and process the transaction basedDocket No. 1988.0497WOon the virtual card number for the contactless card 802 stored in the card information at line 2107.
[0272] Responsive to the server device 1302 authenticating the transaction, the server device 1302 may transmit an acknowledgement and / or other information for the physical transaction device 1502 to process the transaction at line 2108. At line 2109, the physical transaction device 1502 may process the transaction. The physical transaction device 1502 may transmit a transaction successful message to the contactless card 802 at line 2110 and to the server device 1302 at line 2111 responsive to the successful processing of the transaction by the physical transaction device 1502.
[0273] FIG. 22 is a timing diagram illustrating an example sequence flow 2200 for performing a virtual physical transaction according to some embodiments. In the embodiment of FIG. 22, one or more parameters have been set in the virtual number indicator. Accordingly, whether virtual physical transactions are active for the contactless card 802 is dependent on the properties of the transaction (e.g., whether the card is being used at a particular merchant, time period, location, and / or the like).
[0274] As shown in FIG. 22, at line 2201, responsive to the contactless card 802 establishing operable communication with the physical transaction device 1502, the physical transaction device 1502 initiates the transaction with the contactless card 802 at line 2201. The contactless card 802 accesses the virtual information stored on the contactless card, such as the virtual number indicator, at line 2202. At line 2202, the contactless card 802 transmits the virtual information to the physical transaction device 1502. At line 2203, the physical transaction device 1502 forwards the virtual information to the server device 1302. Also at line 2203, physical transaction information may be transmitted to the server device 1302 by the physical transaction device 1502, such as physical transaction device type, merchant information, location information, day and / or time information, and / or the like.
[0275] The server device 1302 evaluates the properties of the transaction based on the virtual information to determine whether a virtual physical transaction is active for the contactless card 802 for the particular transaction at line 2205. For example, if a duration parameter has been set, as indicated by the virtual number indicator or based on card information stored on the server device 1302, the server device 1302 may evaluate the condition for the parameter (e.g., whether the time period is active). In another example, if a merchant parameter has been set, as indicated by the virtual number indicator or based on card information stored on the server device 1302,Docket No. 1988.0497WOthe server device 1302 may evaluate the condition for the parameter (e.g., whether the merchant specified in the card information matches the merchant for the current transaction).
[0276] The server device 1302 transmits the virtual determination (i.e., whether virtual physical transactions are active) to the physical transaction device 1502 at line 2206. The physical transaction device 1502 forwards the virtual determination to the contactless card at line 2207.
[0277] If the virtual determination indicates that virtual physical transactions are not active, the contactless card 2203 may access the assigned card number(s) for the card and generate the card information (e g., according to FIGS. 1-11) using the assigned card number(s) at line 2208.
[0278] If the virtual determination indicates that virtual physical transactions are active, the contactless card 2203 may access the virtual card number for the card and generate the card information (e g., according to FIGS. 1-11) using the virtual card number(s) at line 2208.
[0279] The contactless card 802 may transmit the card information to the physical transaction device 1502 at line 2209. The physical transaction device 1502 may forward the card information to the server device 1302 for authentication and transaction processing at line 2210. Additional communication exchanges between the physical transaction device 1502, the server device 1302, and / or the contactless card 802 may occur that are specific to transaction processing and / or authentication for the particular protocol (for instance, standard EMV protocols), but are not shown to simplify the figure. Information necessary for the server device 1302 to process the transaction, such as the transaction amount, location, protocol information, and / or the like may also be transmitted by the physical transaction device 1502 in line 2210 (and / or in the additional communication exchanges).
[0280] At line 2211, the server device 1302 may authenticate and process the transaction based on the virtual card number for the contactless card 802 stored in the card information for the contactless card responsive to virtual physical transactions being active.
[0281] Responsive to the server device 1302 authenticating the transaction, the server device 1302 may transmit an acknowledgement and / or other information for the physical transaction device 1502 to process the transaction at line 2212. At line 2213, the physical transaction device 1502 may process the transaction. The physical transaction device 1502 may transmit a transaction successful message to the contactless card 802 at line 2214 and to the server device 1302 at line 2215 responsive to the successful processing of the transaction by the physical transaction device 1502.Docket No. 1988.0497WO
[0282] FIG. 23 illustrates an embodiment of a logic flow in accordance with various features of the present disclosure. The logic flow 2300 may be representative of some or all of the operations executed by one or more embodiments described herein, for example, the logic flow 2300 may be representative of some or all of the operations of a virtual physical transaction process according to embodiments of the present disclosure.
[0283] The logic flow 2300 may include receiving a message from a mobile device associated with a contactless card to activate a virtual physical transaction for the contactless card at block 2302. For example, the server device 1302 may receive a communication 1452 from the mobile device 1202 for a virtual physical transaction for the contactless card 802.
[0284] The logic flow 2300 may include generating virtual information for the contactless card, the virtual information comprising at least one virtual card number for the virtual physical transaction at block 2304. For example, the server device 1302 may generate a virtual card number (pUID, PAN, or other card numbers or information) to be used by the contactless card 802. The virtual information may be stored at the server device 1302 as card information 1420.
[0285] The logic flow 2300 may include transmitting at least a portion of the virtual information to the mobile device for storage on the contactless card at block 2306. For example, the server device 1302 may communicate 1453 the virtual information to the mobile device 1202, such as any virtual numbers to be used in a future virtual physical transaction.
[0286] The logic flow 2300 may include receiving a message from a physical transaction device to authenticate a physical transaction with the physical transaction device for the contactless card at block 2308. For example, a physical transaction device (e g., POS device) 1502 may perform authentication of the contactless card 802 and the transaction via communicating with the server device 1302 according to embodiments described in the present disclosure.
[0287] The logic flow 2300 may include authenticating the physical transaction using the virtual information at block 2310. For example, the server device 1302 may determine via the virtual information 1420 stored in the card information 1420 or communicated via the contactless card 802 that a virtual physical transaction is active. For example, as part of the authentication process for the contactless card, the virtual number indicator 1030 may be communicated from the contactless card 802 to the server device 1302 via the POS device 1502. Based on the virtual information stored in the card information 1420 or the virtual number indicator 1030 transmitted by the contactless card via the POS device 1502, the server device 1302 determines that the virtual card information should be used for the transaction. Accordingly, transaction processesDocket No. 1988.0497WOfor the contactless card 802 facilitated by the POS device 1502 use the virtual number 1026 where applicable. For example, the virtual number 1026 may be used as a PAN, pUID, CVV, expiration date, zip code, and / or the like for the contactless card 802. In another example, the virtual number 1026 may be used as part of a key, encryption value, and / or the like used to authenticate the contactless card 802 with the server device 1302 and / or the POS device 1502.
[0288] FIG. 24 illustrates an embodiment of a logic flow in accordance with various features of the present disclosure. The logic flow 2400 may be representative of some or all of the operations executed by one or more embodiments described herein, for example, the logic flow 2400 may be representative of some or all of the operations of activating virtual physical transactions for a contactless card via a mobile device according to embodiments of the present disclosure.
[0289] The logic flow 2400 may include authenticating a contactless card with a mobile device via a service provider application executed via the mobile device at block 2402. For example, the user may authenticate 1451 the contactless card 802 with a user device, such as the mobile device 1202, using processes according to some embodiments described in the present disclosure. For instance, the contactless card 802 can be tapped on or brought within a communication range of the mobile device 1202 and can exchange information with the mobile device 1202 to confirm an identity of an authorized cardholder (for instance, as described with respect to FIGS. 1-11 of the present disclosure).
[0290] The logic flow 2400 may include receiving a selection to activate a virtual physical transaction for the contactless card via the service provider application at block 2404. For example, a user may select to activate virtual physical transactions for the contactless card 802 via the application 1430 executing on the mobile device 1202. Activation of virtual physical transactions for the contactless card 802 may cause future transactions with the card to proceed using virtual information stored on the contactless card 802.
[0291] The logic flow 2400 may include transmitting a message from the mobile device to a server device associated with the service provider application to activate the virtual physical transaction for the contactless card at block 2404. For example, the virtual physical transaction activation may be transmitted 1452 to the server device 1302. In some embodiments, the transmission 1452 may include the virtual number indicator, which may be used by the server device 1302 to determine whether a virtual physical transaction is active. The server device 1302 may store a copy of the virtual number indicator or may update a similar data structure based onDocket No. 1988.0497WOthe virtual number indicator to indicate that virtual transactions are active for the contactless card. A copy of the virtual number indicator may be stored on the contactless card.
[0292] The logic flow 2400 may include receiving, from the server device, virtual information for the contactless card, the virtual information comprising at least one virtual card number for the virtual physical transaction at block 2404. For example, the server device 1302 may generate virtual information for the virtual physical transaction. The virtual information may be or may include a virtual card number, a virtual PAN, a virtual pUID, a virtual expiration date, a virtual CVV, zip code, and / or the like. The server device 1302 may store the virtual information in association with the contactless card 802 (or an account associated with the contactless card 802) as card information 1420. In this manner, when the virtual physical transaction is performed, the server device 1302 may use the virtual information stored in the card information 1420 to process and authenticate the transaction (i.e., instead of the assigned card information, such as the pUID, PAN, etc., assigned to the card at the time of personalization).
[0293] The logic flow 2400 may include transmitting at least a portion of the virtual information to the contactless card at block 2404. For example, the server device 1302 may communicate 1453 the virtual information to the mobile device 1202, such as any virtual numbers to be used in a future virtual physical transaction. The virtual card number generated by the server device 1302 may be forwarded by the mobile device 1202 to the contactless card. The forwarded virtual card number may be stored as a virtual card number on the contactless card 802.
[0294] FIG. 25 illustrates an embodiment of a logic flow in accordance with various features of the present disclosure. The logic flow 2500 may be representative of some or all of the operations executed by one or more embodiments described herein, for example, the logic flow 2500 may be representative of some or all of the operations of contactless card setting a virtual card number and activating virtual physical transactions according to embodiments of the present disclosure.
[0295] The logic flow 2500 may include establishing a wireless connection with a mobile device via the wireless communication interface at block 2502. For example, the user may authenticate 1451 the contactless card 802 with a user device, such as the mobile device 1202, using processes according to some embodiments described in the present disclosure. For instance, the contactless card 802 can be tapped on or brought within a communication range of the mobile device 1202 and can exchange information with the mobile device 1202 to confirm an identity of anDocket No. 1988.0497WOauthorized cardholder (for instance, as described with respect to FIGS. 1-11 of the present disclosure).
[0296] The logic flow 2500 may include receiving a virtual number from the mobile device at block 2504. For example, a user may add virtual information, such as a virtual card number, to the contactless card 802 (and, therefore, to the card information 1420). For example, via the application 1430, the user may select to add a virtual card number to the contactless card 802. A virtual number may be generated by the mobile device 1202 or the server device 1302. The virtual card number may be pushed to the contactless card 802 via the mobile device 1202. The virtual number may be a virtual pUID, PAN, or other card number to be used in virtual physical transactions by the contactless card 802.
[0297] The logic flow 2500 may include storing the virtual number as a virtual card number at block 2506. For example, the contactless card 802 may store the virtual number transmitted by the mobile device 1202 as a virtual card number (e.g., virtual number 1026 stored in memory 1004).
[0298] The logic flow 2500 may include receiving a message from the mobile device to activate virtual physical transactions at block 2508. For example, a user may select to activate virtual physical transactions for the contactless card 802 via the application 1430 executing on the mobile device 1202. The mobile device 1202 may transmit a message to the contactless card 802 that virtual physical transactions have been activated.
[0299] The logic flow 2500 may include modifying the virtual number indicator to indicate that virtual physical transactions are active at block 2510. For example, responsive to receiving the message that virtual physical transactions have been activated, the contactless card 802 may update a bit or value of the virtual number indicator to indicate the status of virtual physical transactions. For example, the virtual number indicator may include a bit in which a value of “1” indicates that virtual physical transactions are active and a value of “0” indicates that virtual physical transactions are not active. The contactless card 802 may set this indicator bit to have a value of “1” to indicate that virtual physical transactions are active.
[0300] It is noted that the systems and methods described herein may be tangibly embodied in one of more physical media, such as, but not limited to, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a hard drive, read only memory (ROM), random access memory (RAM), as well as other physical media capable of data storage. For example, data storage may include random access memory (RAM) and read only memory (ROM), which may be configuredDocket No. 1988.0497WOto access and store data and information and computer program instructions. Data storage may also include storage media or other suitable type of memory (e.g., such as, for example, RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, flash drives, any type of tangible and non-transitory storage medium), where the files that comprise an operating system, application programs including, for example, web browser application, email application and / or other applications, and data files may be stored. The data storage of the network-enabled computer systems may include electronic information, files, and documents stored in various ways, including, for example, a flat file, indexed file, hierarchical database, relational database, such as a database created and maintained with software from, for example, Oracle® Corporation, Microsoft® Excel file, Microsoft® Access file, a solid state storage device, which may include a flash array, a hybrid array, or a server-side product, enterprise storage, which may include online or cloud storage, or any other storage mechanism. Moreover, the figures illustrate various components (e.g., servers, computers, processors, etc.) separately. The functions described as being performed at various components may be performed at other components, and the various components may be combined or separated. Other modifications also may be made.
[0301] Throughout the present disclosure, reference is made to a card, such as a contact-based card and a contactless card.” It is understood that the present disclosure is not limited to a particular type of card, and instead this disclosure encompasses a contact-based card, a contactless card, or any other card. It is further understood that the present disclosure is not limited to cards having a certain purpose (e.g., payment cards, gift cards, identification cards, membership cards, transportation cards, access cards), to cards associated with a particular type of account (e.g., a credit account, a debit account, a membership account), or to cards issued by a particular entity (e.g., a commercial entity, a financial institution, a government entity, a social club). Instead, it is understood that the present disclosure includes cards having any purpose, account association, or issuing entity.
[0302] As used herein, the term “card entity” can include, without limitation, financial institutions (e.g., banks). However, it is understood that the term “card entity” is not limited thereto, and the present disclosure can include corporations, state, local, and federal governments, and any other entity issuing, personalizing, activating, authenticating, and / or validating cards for use in transactions.Docket No. 1988.0497WO
[0303] As used herein, the term “tap” can include, without limitation, a tap of a card on a device. However, it is understood that the term “tap” is not limited to a particular gesture, and the present disclosure can include a tap, a swipe, a wave, and / or any combination thereof.
[0304] As used herein, the term “transaction” can include, without limitation, financial transactions. However, it is understood that the term “transaction” is not limited thereto, and the present disclosure can include financial transactions, identity verification transactions, area access transactions, user authentication transactions, membership verification transactions, eligibility verification transactions, and any other operation involving a card.
[0305] In the preceding specification, various embodiments have been described with references to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense.
Claims
Docket No. 1988.0497WOCLAIMSWhat is claimed is:
1. A system, comprising:at least one server device comprising a processor and a memory storing instructions that, when executed by the processor, cause the processor to:receive a message from a mobile device associated with a contactless card to activate a virtual physical transaction for the contactless card;generate virtual information for the contactless card, the virtual information comprising at least one virtual card number for the virtual physical transaction;transmit at least a portion of the virtual information to the mobile device for storage on the contactless card;receive a message from a physical transaction device to authenticate a physical transaction with the physical transaction device for the contactless card; and authenticate the physical transaction using the virtual information.
2. The system of claim 1, wherein the virtual information comprises a virtual number indicator indicating whether the virtual physical transaction is active or non-active.
3. The system of claim 1, wherein the message comprises at least one virtual physical transaction parameter for the virtual physical transaction, the at least one virtual physical transaction parameter comprising a duration, a geographic location, a merchant, or a physical transaction device type.
4. The system of claim 1, wherein the at least one virtual card number is used in the virtual physical transaction as a unique identifier (pUID) or a primary account number (PAN) for the contactless card.
5. The system of claim 1, wherein the at least one virtual card number includes at least one of an expiration date, a zip code, or a card verification value (CVV).Docket No. 1988.0497WO6. The system of claim 1, wherein the physical transaction device comprises a point-of-sale (POS) device or an embedded card reader (ECR) at a physical merchant location.
7. The system of claim 1, wherein the at least one virtual card number is used as authentication credentials for the contactless card.
8. A computer-implemented method comprising:authenticating a contactless card with a mobile device via a service provider application executed via the mobile device, the contactless card authenticated with a user account of a cardholder of the contactless card;receiving a selection to activate a virtual physical transaction for the contactless card via the service provider application;transmitting a message from the mobile device to a server device associated with the service provider application to activate the virtual physical transaction for the contactless card;receiving, from the server device, virtual information for the contactless card, the virtual information comprising at least one virtual card number for the virtual physical transaction; and transmitting at least a portion of the virtual information to the contactless card.
9. The computer-implemented method of claim 8, further comprising transmitting an activation message to the contactless card via the mobile device indicating that the virtual physical transaction is active.
10. The computer-implemented method of claim 1, further comprising:receiving at least one virtual physical transaction parameter for the virtual physical transaction at the mobile device via the service provider application, the at least one virtual physical transaction parameter comprising a duration, a geographic location, a merchant, or a physical transaction device type; andtransmitting the at least one virtual physical transaction parameter to the server device in the message.
11. The computer-implemented method of claim 8, wherein the at least one virtual card number is used in the virtual physical transaction as a unique identifier (pUID) or a primary account number (PAN) for the contactless card.Docket No. 1988.0497WO12. The computer-implemented method of claim 8, wherein the at least one virtual card number includes at least one of an expiration date, a zip code, or a card verification value (CVV).
13. The computer-implemented method of claim 1, wherein the physical transaction device comprises a point-of-sale (POS) device or an embedded card reader (ECR) at a physical merchant location.
14. A contactless card, comprising:a processor;a wireless communication interface; anda memory storing an assigned card number, at least one virtual card number, a virtual number indicator, and instructions, that when executed by the processor, cause the processor to:establish a wireless connection with a mobile device via the wireless communication interface,receive a virtual number from the mobile device,store the virtual number as the at least one virtual card number,receive a message from the mobile device to activate virtual physical transactions, andmodify the virtual number indicator to indicate that virtual physical transactions are active.
15. The contactless card of claim 14, the instructions, when executed by the processor, to cause the processor to:establish the wireless connection with a physical transaction device via the wireless communication interface, the wireless connection established based on a physical connection between the contactless card and the physical transaction device,receive an initiation message from the physical transaction device to initiate a transaction, anddetermine whether virtual physical transactions are active via evaluating the virtual number indicator responsive to receiving the transaction initiation message.Docket No. 1988.0497WO16. The contactless card of claim 15, the instructions, when executed by the processor, to cause the processor to:use the at least one virtual card number as card information responsive to determining that virtual physical transactions are active,use the assigned card number as card information responsive to determining that virtual physical transactions are inactive, andprovide the card information for authentication and transaction processing to the physical transaction device to process the transaction.
17. The contactless card of claim 15, wherein the physical transaction device comprises a point-of-sale (POS) device or an embedded card reader (ECR) at a physical merchant location.
18. The contactless card of claim 14, the instructions, when executed by the processor, to cause the processor to:receive parameter information from the mobile device associated with a virtual physical transaction parameter, andmodify the virtual number indicator to indicate the parameter information.
19. The computer-implemented method of claim 8, wherein the at least one virtual card number is used in the virtual physical transaction as a unique identifier (pUID) or a primary account number (PAN) for the contactless card.
20. The contactless card of claim 14, the instructions, when executed by the processor, to cause the processor to:establish the wireless connection with a physical transaction device via the wireless communication interface, the wireless connection established based on a physical connection between the contactless card and the physical transaction device,receive an initiation message from the physical transaction device to initiate a transaction, andtransmit the virtual number indicator to the physical transaction device to determine whether virtual physical transactions are active via evaluation of the virtual number indicator by a server device communicatively coupled to the physical transaction device.
