METHOD AND SYSTEM FOR GENERATING A DYNAMIC CARD VERIFICATION VALUE FOR PROCESSING A TRANSACTION

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

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.

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

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

4. 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.

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

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

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

8. 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.

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

10. 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.

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

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

13. 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.

14. 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.

15. 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.

16. 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.

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.

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

19. 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.

20. 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.

21. 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.

22. 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.

23. 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.

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

25. 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.

26. 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.

27. 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.

28. 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.

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.

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

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.

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

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

34. 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.

35. 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.

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

37. 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.

38. 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.

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

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

41. 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.

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.

43. 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.

44. 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.

45. 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.

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.

47. 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.

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

49. 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.

50. 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.

51. 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.

52. 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.

53. 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.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG. 1 depicts an exemplary system embodiment in accordance with the present invention.

[0021] FIG. 2 depicts a flowchart of an exemplary method embodiment in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0022] Referring now to FIG. 1, there is shown an exemplary system 100 for processing a transaction using a transaction card 110. Exemplary transaction card 110 is depicted in an exploded manner, in which various components internal and external to the card are depicted schematically. The location of the various components is not limited to the depictions shown. Transaction card 110 has a card near field communication (NFC) interface 112, a card memory 114, and a card processor 116. Card memory 114 and processor 116 may be securely combined onto a single secure element chip. The foregoing electronic components may be stored on one or more integrated circuit (IC) chips embedded in the card. In some embodiments, one or more of card memory 1114, card processor 1116, and NFC interface 1112 that is/are separate and discrete from the respective NFC interface 112, card memory 114, and card processor may be provided. In one embodiment, memory 1114, processor 1116, and NFC interface 1112 may be provided for conducting card-present, physical payment transactions, and memory 114, processor 116, and NFC interface 112 may be provide for conducting non-payment transactions in accordance with method embodiments, such as card-not-present financial transactions, as further discussed herein. In other embodiments, card memory 114, card processor 116, and NFC interface 112 may configured both for processing payment and non-payment transactions. In still other embodiments, memory 1114 may be a segmented portion of memory 114, processor 1116 may be co-located with processor 116 on a single dual-processor chip, and a single NFC interface 112 controllable by both processor 1116 and 116 may be provided, with appropriate separation between memory segment 1114 and the remaining portion of memory 114 such that a breach in the security of memory 114 does not result in a pathway to breach memory segment 1114.

[0023] Physical (card-present) financial transactions may be conducted via a point of sale (POS) card reader (not shown) that reads information from payment module 10. Payment module 10 may be a dual interface (DI) integrated circuit IC chip operable to provide payment information to a card reader via physical contact with the card reader through contacts accessible from a surface of the card, or via a contactless communication with a radio frequency identification (RFID) chip included in the module, as is well known in the art.

[0024] As depicted, front surface 111 of card 110 also has printed, embossed, or laser marked indicia forming a card number and a cardholder name. The back surface 113 (depicted rotated 180 degrees about axis A, for illustrative purposes) of card 110 shows a magnetic stripe 12 and a machine readable code 14, which may be bar code, a QR-code, or any code known in the art. Although not pictured, the card may have other features commonly found in a card, such as a security hologram, a photograph of the cardholder, a signature stripe, biometric readers, display screens, decorative features, and the like, without limitation. Additional human and/or machine-readable indicia may also be provided, such as issuing financial institution information (e.g. bank name), card branding (e.g. VISA, AMERICAN EXPRESS, MASTERCARD, etc.), the expiration date, membership club information, affinity information (e.g. branding associated with a university, a sports team, a charitable cause, etc.), and the like. The various features shown on card 110 are not limited to any particular location. Although not limited to any particular type of card, exemplary cards may comprise at least one layer that is metal, ceramic, and/or glass, such as compositions depicted in one or more co-pending applications owned by CompoSecure, the common assignee of this application.

[0025] As described further herein, machine-readable instructions embodied in the card memory, readable by the card processor, are configured to cause the card NFC interface, when prompted by an incoming non-payment NFC communication 132, to return information 133 via an outgoing non-payment NFC communication 136. The NFC communication may take the form of an NFC data exchange format (Ndef) message. The information 133 may include information identifying an IP address or web address 134, or the information may cause a module of application software (i.e. an app) to open on the mobile device, which app may provide the web or IP address. Card memory 114 may also contain instructions for causing card processor 116 to perform the operative steps for conducting financial transactions (e.g. for providing card information to a card reader in response to a suitable prompt as a payment NFC communication or via contacts on the card), or a discrete memory and processor may be associated with functions for performing financial transactions, and memory 114 and processor 116 may be dedicated to performing only the method and system as described herein for generating a dynamic CVV (dCVV).

[0026] Mobile device 120 (e.g. a cellular telephone, tablet, portable computer, etc. with NFC capability) has a mobile device memory 122, a mobile device processor 124, a mobile device user interface 126 (e.g. a touch screen, voice command capability, virtual keyboard capability, without limitation), a mobile device display 127 (which may encompass the majority of the surface area of the device), a mobile device NFC interface 128, and a telecommunications interface 129 configured to connect to a global computer information network 130. The mobile device is associated with the transaction card, typically by a cardholder downloading application software (an app) associated with the issuer of the card (e.g. VISA, AMERICAN EXPRESS, MASTERCARD, a financial institution such as a bank, credit union, a brokerage firm, and/or the like), and then entering information and performing other processes that cause the app and the device to be associated with the card and the cardholder. As understood by those of skill in the art, the application software utilized on a mobile device may include a thin portion that resides in local computer memory of the mobile device, and a thick portion that resides in the cloud (e.g. on a server accessible to the mobile device over the global computer information network 130). The application software comprises machine-readable commands embodied in memory that whey read by the machine causing a processor to perform corresponding method steps.

[0027] Instructions embodied in the mobile device memory 122, readable by the mobile device processor 124, are configured to cause the mobile device 120, when prompted via the user interface 126, to carry out certain method steps as described herein, which include initiate the (outgoing from the mobile device, and incoming to the card) non-payment NFC communication 132 with the transaction card, receiving the information 133 containing the IP address or web address 134 from the transaction card via the (outgoing from the card, but incoming to the mobile device) non-payment NFC communication 136 from the transaction card; and transmitting a prompt 138 to the IP address or web address over the global computer information network 130.

[0028] In embodiments in which the information 133 (e.g. Ndef message) transmitted from the card to the mobile device opens an app, all cards can be programmed to transmit the same Ndef message, and each app can be configured to contain unique information corresponding to the web address or IP address to which prompt 138 is directed. In other embodiments, the secure element 114, 116 may be personalized with the unique IP address to be communicated as the information 133 in the Ndef message. In some embodiments, the NFC communication 132 may be prompted by an interaction between the card and the mobile device, such as a card tap that causes the phone to sense the RFID chip in the card, prompting the initial NFC communication. In an app-driven embodiment, a user may first open an app on the mobile device, and cause the app to send the non-payment NFC communication 132 to the card. In another embodiment, the user may prompt the non-payment NFC communication by entering information on a web page (e.g. a check out web page on which payment information is entered) that causes a communication to be sent to the mobile device that prompts the mobile device to initiate a non-payment NFC communication to the card.

[0029] As indicated herein, communications from one element in FIG. 1 to another are depicted as going directly from one component to another, but it should be understood that because each of the devices is connected via the depicted node (signified by a dark circle attached to a line emanating from each device) connected to a global computer information network (present and non-limiting examples of which are commonly referred to as the Internet or the World Wide web) 130, the communications travel through various switches, relays, servers, nodes, and the like from one connected device to another, and may include wired and wireless communications using any of various protocols known in the art, without limitation. The communications may be encrypted, for security purposes.

[0030] Computer server 140 comprises a processor 142 for generating a dynamic Card Verification Value (dCVV), e.g. 1234 or 931, signified as #### in the figures, although not limited to any number of digits. While the code is typically a numeric code, it is not so limited, and may be, for example, any code formed from alphanumeric characters or a combination of alphanumeric and special (e.g. #, $, %, &, @) characters. The computer server 140 is connected to or in communication with the IP address or web address 134, and is programmed with instructions for causing the dCVV generating processor 142 to generate a dCVV code in response to the prompt 138 from the mobile device and to send a secure communication 146 containing the dynamic CVV code to the mobile device via the IP address or web address over the global computer information network 130. The term secure communication typically refers to an encrypted text message, an encrypted email, or an encrypted communication sent over the internet, decrypted by the device or carrier, and then presented by the app on the mobile device associated with the transaction card. The secure communication is typically sent over a cellular telephone network, without limitation to any particular technology (e.g. GSM, CDMA, LTE, etc.) or generation (e.g. 4g, 5g, etc.), such as but not limited to via a short messaging service (SMS) or via XML messages sent over Secure Sockets Layer (SSL) connections with authentication (e.g. using digital certificates). By contrast, the prompt received from the mobile device to the server 140 may use a different communications protocol, such as may be used by any standard over-the-internet communications protocol, such as Hypertext Transfer Protocol (HTTP) or HTTP over Transport Layer Security (TLS) or SSL. Although the secure communication containing the dCVV is sent to the mobile device in some embodiments, the invention is not limited thereto. The secure communication containing the dCVV may be sent to any secure location accessible to a cardholder. As non-limiting examples, the communication may be sent to an email address, or to a designated mobile device different than the initiating mobile device.

[0031] Point of sale (POS) transaction portal 180, connected to transaction processor 150 and to the global computer information network 130, is configured to receive the transaction information 162, including the dCVV, from a cardholder transaction input device 160 over the global computer information network as part of a card-not-present transaction and send the transaction information to the transaction processor. Transaction processor 150 connected to the global computer information network 130 (either separate from, or commonly located with, the POS transaction portal 180) is configured to receive input transaction information 162, including the dCVV code, relayed by the POS transaction portal from cardholder transaction input device 160, and to cause the transaction information 162 to be communicated to a payment transaction clearinghouse 170, over the global computer information network. Payment transaction clearinghouse 170 is in communication with the transaction processor 150 and the computer server 140 via the global computer information network 130 (or via any means known in the art), and includes a computer memory 172 and a computer processor 174. The payment transaction clearinghouse is 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-generation processor, and to send an authentication verification 176 to the transaction processor over the global computer information network.

[0032] In a typical operation, cardholder transaction input device 160 typically accesses the POS transaction portal 180 over the global computer information network. Although depicted as a laptop computer, cardholder transaction input device 160 may include a mobile device (which may be, but is not necessarily, the same mobile device 120 as used for performing other steps in the method), a computer, a tablet, a kiosk, a telephone interface including human operator assisted interfaces in which a human transcribes information verbally transmitted by phone to a device connected to the Internet, automated interfaces with speech recognition and/or operated by touch tone prompts, a gaming system, or any device known in the art now or in the future capable of receiving input of transaction information via a card not present transaction. Notably, although tailored especially for card not present transactions, the invention is not limited thereto, and there may be circumstances in which the cardholder transaction input device 160 may be a typical card reader known in the art (e.g. capable of reading information from a physical card via a payment NFC communication, via an RFID chip, a contact chip reader, a mag stripe reader, a bar code reader, or the like) associated with a user interface for receiving an input comprising the dCVV. As used herein, the term cardholder is not limited to the authorized user of a card, but to anyone carrying out a transaction using the transaction card and the dynamic CVV.

[0033] Within the overall process of conducting a payment transaction, the cardholder transaction input device 160 is typically queried by the POS transaction portal 180 for transaction information 162, which may include any or all of the cardholder name, the card number, cardholder address information (including one or all of street address, house or unit number, city, state, country, and zip code), optionally, a cardholder telephone number, and the dCVV. The step of providing the dCVV as part of the transaction information, in accordance with one embodiment of the invention, includes performing the steps of exemplary method 200 depicted in FIG. 2.

[0034] In step 210 of method 200, the cardholder initiates a non-payment NFC communication between the transaction card 110 and the mobile device 120 connected to the Internet 130. In step 220, the card sends (and the mobile device receives) information 133 corresponding to IP address or web address 134 from the transaction card 110 in the non-payment NFC communication, and in step 230, the mobile device 120 transmits a prompt to the IP address or web address 134 over the Internet 130. In step 240, the dCVV-generation processor, connected to or in communication with the IP address or web address, generates the dCVV code in response to the prompt. In step 250, the server sends a secure communication containing the dCVV code to the mobile device, which relays the dCVV number to the cardholder (e.g. by visually displaying it or by another means, e.g. audibly or tactilely via a braille generator for the visually and/or hearing impaired). The cardholder (e.g. via the cardholder transaction input device 160) then supplies the dCVV to the transaction processor in step 260. In step 270, the transaction processor communicates the transaction information, including the dynamic CVV supplied by the cardholder, to the payment transaction clearinghouse. In step 280, the payment transaction clearinghouse authenticates the transaction, which typically includes verifying the dynamic CVV supplied by the cardholder matches the dynamic CVV generated by CVV-generation processor.

[0035] To the extent transaction cards are referenced herein, suitable cards include cards in conformance with the ISO/IEC 7810 ID-1 standard, in which the cards have lateral dimensions of 85.6053.98 mm (3 in2 in), with rounded corners having a radius of 2.88-3.48 mm (about in), and an overall thickness of 0.76 mm ( 1/32 in), but the invention is not limited to cards having any particular size, shape or proportion. Similarly, although described herein primarily with reference to implementations using a transaction card, it should be understood that the methods and systems as described herein may be implemented using devices other than cards. For example, any passive proximity integrated circuit (i.e. a circuit configured for returning a signal in response to a query event such as movement through a field or receipt of a signal created by a reader), readable by any proximity coupling device (i.e. a reader configured to create the query event), may be used for performing the method steps. Thus the role of the transaction card as described herein may be performed by any transaction instrument of any shape and size having such a passive proximity circuit configured to be coupled to a proximity coupling device, and configured to exchange the messages as set forth herein. Thus, in addition traditional cards, the passive transaction instruments used in connection with the various embodiments of the invention may include watches, rings, wristbands, jewelry, key fobs, without limitation to any particular type of apparatus. Accordingly, use of the term dynamic card verification value and its abbreviation dCVV in the claims herein is not intended to limit the claimed invention only to embodiments that use traditional transaction cards, and no such limitation should be inferred from use of such terms. Additionally, while discussed herein primarily in the context of NFC communications, the invention is not limited to any particular communication protocol or proximity for the non-payment communications between the mobile device and the transaction instrument. Rather, a passive transaction instrument of any construction may be used for exchanging the messages as discussed herein using any communication methodology between the mobile device and the transaction instrument.

[0036] Although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Rather, various modifications may be made in the details within the scope and range of equivalents of the claims and without departing from the invention.