# US 2023/0419328 A1 · Method and system for generating a dynamic card verification value for processing a transaction

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0419328 A1
- Document ID: US20230419328A1
- Status: Published application
- Kind: A1
- Application number: 18/037,465
- Filed: 2021-11-17
- Published: 2023-12-28
- Earliest claimed: 2020-11-19
- Assignees: CompoSecure, LLC
- Applicants: CompoSecure, LLC
- Inventors: Adam Lowe; Todd Nuzum
- Web page: https://patentgrep.com/patent/US20230419328A1

## CPC

- G06Q 20/4018: {using the card verification value [CVV] associated with the card}
- G06Q 20/023: {the neutral party being a clearing house}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/353: {Payments by cards read by M-devices}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Systems, methods, transaction cards, mobile devices, processors, and computer memory programmed with machine-readable instructions, for providing a dynamic Card Verification Value (dCVV) to a user of a transaction card. A mobile device associated with the user and with the transaction card initiates a non-payment near field communication (NFC) with the transaction card, receives a message from the transaction card in the non-payment NFC communication, transmits a prompt to an IP address or web address over a global computer information network, and receives a secure communication from containing the dCVV from a server accessible from the IP address or web address in response to the prompt. The dCVV code is then provided to the user. In embodiments, the non-payment NFC may be initiated via a card tap, a user interface, or a communication from a website.

## Claims

### Claim 1

A method of providing a dynamic Card Verification Value (dCVV) to a user of a transaction instrument, the method comprising the steps of:
(a) a mobile device, associated with the user and with an account associated with the transaction instrument, initiating a non-payment communication with the transaction instrument;
(b) the mobile device receiving a message from the transaction instrument in the non-payment communication;
(c) the mobile device transmitting a prompt to an IP address or web address over a global computer information network;
(d) the mobile device receiving a secure communication in response to the prompt, the communication containing the dCVV code; and
(e) providing the dCVV code to the user.

### Claim 2 (depends on 1)

The method of claim 1, wherein the transaction instrument is a transaction card.

### Claim 3 (depends on 1)

The method of claim 1, wherein the non-payment communication is a near-field communication (NFC).

### Claim 4 (depends on 1)

The method of claim 1, wherein the communication containing the dCVV code originates from a server associated with a dCVV generation processor that is configured to generate the dCVV code.

### Claim 5 (depends on 1)

The method of claim 1, comprising providing the dCVV code to the user via the mobile device.

### Claim 6 (depends on 5)

The method of claim 5, wherein the mobile device provides the dCVV code visually, audibly, or tactilely.

### Claim 7 (depends on 1)

The method of claim 1, wherein the mobile device is connected to the Internet.

### Claim 8 (depends on 1)

The method of claim 1, wherein the message received by the mobile device from the transaction instrument is configured to cause the mobile device to open a module of application software, wherein the application software is programmed with the web address or IP address to which the prompt in step (c) is directed.

### Claim 9 (depends on 1)

The method of claim 1, wherein the message received by the mobile device from the transaction instrument includes the web address or IP address.

### Claim 10 (depends on 1)

The method of claim 1, wherein the mobile device initiates the non-payment communication after an interaction between the mobile device and the transaction instrument.

### Claim 11 (depends on 10)

The method of claim 10, wherein the interaction between the mobile device and the transaction instrument is a tap on the mobile device.

### Claim 12 (depends on 1)

The method of claim 1, wherein the mobile device initiates the non-payment communication via a user interface of a module of application software.

### Claim 13 (depends on 1)

The method of claim 1, wherein the mobile device receives a prompt from a web page, generated by the web page in response to entry of information on the web page, wherein the prompt from the web page causes the mobile device to send the non-payment communication.

### Claim 14 (depends on 1)

The method of claim 1, further comprising the step of:
(f) the user of the transaction instrument supplying, over the global computer information network, the dCVV code to a transaction portal as part of transaction information.

### Claim 15 (depends on 14)

The method of claim 14, further comprising the step of:
(g) a transaction processor associated with the transaction portal communicating the transaction information, including the dCVV code, to a payment transaction clearinghouse.

### Claim 16 (depends on 15)

The method of claim 15, further comprising the step of:
(h) the payment transaction clearinghouse authenticating the transaction, wherein authenticating includes verifying the dCVV code supplied by the cardholder matches the dCVV code generated by dCVV-generation processor.

### Claim 17

A system for processing a transaction using a transaction instrument, the system comprising:
a transaction instrument having a instrument passive communication interface, a instrument memory, a instrument processor, and instructions embodied in the instrument memory, readable by the instrument processor, and configured to cause the instrument passive communication interface, when prompted by a first non-payment communication, to return a message via a second non-payment communication;
a mobile device having a mobile device memory, a mobile device processor, a mobile device user interface, a mobile device communication interface configured for communication with the passive communication interface of the transaction instrument, a telecommunications interface configured to connect to a global computer information network, the mobile device memory having instructions embodied therein and readable by the mobile device processor, configured to cause the mobile device to:
(a) initiate the first non-payment communication from the mobile device to the transaction instrument;
(b) receive the message from the transaction instrument via the second non-payment communication from the transaction instrument to the mobile device; and
(c) transmit a prompt from the telecommunications interface to an IP address or web address over the global computer information network in response to receipt of the message from the transaction card;
a computer server connected to or in communication with the IP address or web address and connected to a dCVV-code-generating processor, the computer server configured to, in response to receipt of the prompt from the mobile device, cause the dCVV-code-generating processor to generate a dynamic Card Verification Value (dCVV) code, the computer server further configured to send a secure communication containing the dynamic CVV code to the mobile device over the global computer information network.

### Claim 18 (depends on 17)

The system of claim 17, wherein the transaction instrument comprises a transaction card.

### Claim 19 (depends on 17)

The system of claim 17, wherein the passive communication interface comprises a near-field communication (NFC) interface, and the non-payment communications comprise NFC communications.

### Claim 20 (depends on 17)

The system of claim 17, further comprising:
a transaction portal accessible from the global computer information network and configured to receive transaction information, including the dynamic CVV, over the global computer information network.

### Claim 21 (depends on 20)

The system of claim 20, further comprising:
a transaction processor in communication with the transaction portal and configured to process a payment transaction, the transaction processor configured to receive the transaction information, including the dynamic CVV code, from the transaction portal, and to communicate the transaction information to a payment transaction clearinghouse, over the global computer information network.

### Claim 22 (depends on 21)

The system of claim 21, further comprising:
the payment transaction clearinghouse, connected to the global computer information network, in communication with the transaction processor and the computer server connected to the dCVV-code-generation processor, the payment transaction clearinghouse comprising a computer memory and a computer processor, the payment transaction clearinghouse configured to receive the transaction information from the transaction processor over the global computer information network, to authenticate the transaction by verifying the dCVV code supplied with the transaction information matches the dCVV code generated by dCVV-code-generation processor, and to send an authentication verification to the transaction processor over the global computer information network.

### Claim 23 (depends on 17)

The system of claim 17, wherein the message received by the mobile device from the transaction instrument is a message configured to cause the mobile device to open a module of application software, wherein the application software is programmed with the web address or IP address to which prompt in step (c) is directed.

### Claim 24 (depends on 17)

The system of claim 17, wherein the message received by the mobile device from the transaction instrument includes the web address or IP address.

### Claim 25 (depends on 17)

The system of claim 17, wherein the mobile device is configured to initiate the non-payment communication in response to an interaction between the mobile device and the transaction instrument.

### Claim 26 (depends on 17)

The system of claim 17, wherein the mobile device is configured to initiate the non-payment communication in response to a tap of the transaction instrument on the mobile device.

### Claim 27 (depends on 17)

The system of claim 17, wherein the mobile device is configured with instructions for causing the mobile device to initiate the non-payment NFC in response to receipt of a prompt from a user interface.

### Claim 28 (depends on 17)

The system of claim 17, further comprising a web page embodying machine-readable instructions residing on a computer processor, the web page configured to prompt the mobile device to initiate the non-payment communication in response to entry of information on the web page.

### Claim 29

A mobile device comprising:
a memory;
a processor;
a user interface;
a proximity coupling device interface;
a telecommunications interface configured to connect to a global computer information network;
at least one of: a display, an sound generator, and a haptic stimulus generator; instructions embodied in the memory and readable by the processor, configured to cause the mobile device to perform the steps of:
(a) initiating a first non-payment communication with a transaction instrument associated with a transaction account associated with the mobile device;
(b) receiving a second non-payment communication from the transaction instrument containing a message;
(c) transmitting a prompt to an IP address or web address over a global computer information network in response to receipt of the message;
(d) receiving a secure communication from the IP address or web address, the secure communication including a dCVV code; and
(e) communicating the dCVV code visually via the display, audibly via the sound generator, or tactilely via the haptic stimulus generator.

### Claim 30 (depends on 29)

The mobile device of claim 29, wherein the proximity coupling device comprises a near field communication (NFC) interface.

### Claim 31

A transaction instrument, comprising:
a passive proximity circuit communication interface;
a memory;
a processor;
instructions embodied in the memory, readable by the processor, and configured to cause the passive proximity circuit communication interface, when prompted by a first non-payment communication from a mobile device, to return a message via a second non-payment communication, wherein the message comprises information selected from: an IP address or web address, or instructions for causing a module of application software to open on the mobile device, wherein the application software is configured with the IP address or the web address.

### Claim 32 (depends on 31)

The transaction instrument of claim 31, wherein the passive proximity circuit communication interface comprises a near field communication (NFC) interface.

### Claim 33 (depends on 31)

The transaction instrument of claim 31, wherein the transaction instrument further comprises a contactless payment module.

### Claim 34 (depends on 33)

The transaction instrument of claim 33, wherein the memory further contains instructions readable by the processor for causing the contactless payment module to conduct one or more payment communications with a card reader.

### Claim 35 (depends on 34)

The transaction instrument of claim 34, wherein the instrument comprises one or more of a first discrete memory or memory portion, a first discrete processor or processing portion, and a first discrete interface configured to conduct the first and second non-payment communications, and one or more of a second discrete memory or memory portion, a second discrete processor or processing portion, and a second discrete interface configured to conduct the one or more payment communications.

### Claim 36 (depends on 31)

The transaction instrument of claim 31, wherein the transaction instrument comprises a transaction card.

### Claim 37 (depends on 36)

The transaction instrument of claim 36, wherein the transaction instrument comprises a transaction card, and the contactless payment module comprises a dual interface (DI) module also comprising contacts for physical connection to a card reader.

### Claim 38 (depends on 37)

The transaction instrument of claim 37, further comprising one or more of a magnetic stripe, a machine-readable code, and human-readable indicia comprising information required for conducting a payment transaction.

### Claim 39 (depends on 38)

The transaction instrument of claim 38, wherein the human-readable indicia comprises embossed, printed, or laser-marked alphanumeric information.

### Claim 40 (depends on 36)

The transaction instrument of claim 36, wherein the transaction card comprises at least one layer comprising metal, ceramic, or glass.

### Claim 41 (depends on 31)

A method for initiating a dynamic Card Verification Value (dCVV) code request, the method comprising the steps of:
(a) providing a transaction instrument of claim 31;
(b) receiving the first non-payment communication; and
(c) returning the message via the second non-payment communication, wherein the IP address or web address has connected thereto a system configured to generate and return the dCVV in response to a prompt.

### Claim 42

A dynamic Card Verification Value (dCVV) code generating system comprising:
a computer server connected to or in communication with a unique IP address or web address on a global computer information network;
a dCVV-code-generating processor connected to the computer server; and
a communications interface configured to send secure communications via the global computer information network;
the system configured to, in response to receipt of a prompt from a mobile device via the IP address or web address, cause the dCVV-code-generating processor to generate a dCVV code, and to transmit a secure communication containing the dCVV code in a secure communication over the global computer information network to a secure location accessible to a cardholder.

### Claim 43 (depends on 42)

The dCVV-code-generating system of claim 42, wherein the system is configured to transmit the secure communication containing the dCVV code to the mobile device.

### Claim 44 (depends on 43)

The dCVV-code-generating system of claim 43, wherein the system is configured to receive the prompt by a first type of communications protocol and to send the secure communication via a second type of communications protocol.

### Claim 45 (depends on 42)

A method for providing a dynamic Card Verification Value (dCVV) code, the method comprising the steps of:
(a) providing the dCVV-code-generating system of claim 42 accessible via the IP address or web address;
(b) receiving the prompt from the mobile device;
(c) generating the dCVV code; and
(d) transmitting the secure communication to the secure location.

### Claim 46

A non-transitory computer memory media comprising instructions readable by a machine for causing a mobile device to perform the method steps of:
(a) associating a transaction account and a transaction instrument with the mobile device;
(b) initiating a first non-payment communication with the transaction instrument using a communication interface embedded in the mobile device;
(c) receiving a second non-payment communication from the transaction card containing a message;
(d) transmitting a prompt to an IP address or web address over a global computer information network via a telecommunications interface of the mobile device;
(e) receiving a secure communication from the IP address or web address, the secure communication including a dCVV code; and
(f) communicating the dCVV code visually via a display, audibly via a sound generator, or tactilely via a haptic stimulus generator embedded in the mobile device.

### Claim 47 (depends on 46)

The non-transitory computer memory media of claim 46, wherein the instructions comprise instructions for sending the first non-payment communication and the second non-payment communication as near field (NFC) communications.

### Claim 48 (depends on 46)

The non-transitory computer memory media of claim 46, wherein at least a portion of the memory is embedded in the mobile device.

### Claim 49 (depends on 46)

The non-transitory computer memory media of claim 46, wherein at least a portion of the memory is embedded in a server accessible to the mobile device over the global computer information network.

### Claim 50 (depends on 46)

The non-transitory computer memory media of claim 46, wherein the instructions include instructions corresponding to application software configured to store the IP address or web address.

### Claim 51 (depends on 46)

The non-transitory computer memory media of claim 46, wherein the instructions include instructions for initiating the non-payment communication in response to an interaction between the mobile device and the transaction instrument.

### Claim 52 (depends on 51)

The non-transitory computer memory media of claim 51, wherein the instructions include instructions for initiating the first non-payment communication in response to a tap of the transaction instrument on the mobile device.

### Claim 53 (depends on 46)

The non-transitory computer memory media of claim 46, wherein the instructions include instructions for causing the mobile device to initiate the non-payment communication in response to receipt of a prompt from a user interface.
