System and method that enables mobile short-range wireless communication to update display on payment card

Abstract

To provide a method and a system for enabling update of a display on a payment card.SOLUTION: A method includes the steps of: transmitting, via a mobile device, a request to update a card number of a payment card to be reissued; receiving, by the mobile device in response to the transmitted request, an approval to reissue the payment card and update the card number; obtaining an updated card number from a secure source of the updated card number in response to received authorization; outputting an updated card number signal representing the updated card number via a near field wireless communication circuit of the mobile device in response to a command signal from a signal generation component; and receiving, via the near field wireless communication circuit in the mobile device, a signal indicating that updating of the card number is successful in response to an output of the updated card number signal.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a system and method that allows updating display on a payment card. [Background technology]

[0002] Payment cards such as credit cards, gift cards, and debit cards have become the preferred means of payment for transactions. The number of transactions involving payment cards has increased at an alarming rate. The number of fraudulent transactions has also increased at an alarming rate. As a result, the number of payment cards that need to be replaced has increased as well. While payment cards were once inexpensive, the current demand for security features means that the cost of payment cards is not trivial. For card issuers, this represents a significant burden, especially when multiplied by the number of cards that need to be replaced each year. Summary of the Invention

[0003] A method is disclosed that includes transmitting, via a mobile device, a request to update a card number on a payment card to be reissued. The request may include an indication that the card number presented on a display of the payment card and encoded on the magnetic strip of the payment card is invalid and cannot be used. In response to the transmitted request, the mobile device may receive approval to reissue the card and update the card number. In response to the received approval, the updated card number may be retrieved from a secure source of updated card numbers. In response to a command signal from a reissue application executing on the mobile device, an updated card number signal representative of the updated card number may be output via a near field communication circuit in the mobile device. In response to the output of the updated card number signal, a signal indicating successful updating of the card number is received via a near field communication circuit in the mobile device.

[0004] Another method is disclosed that includes issuing an authentication signal by a near field communication device of a payment card for reception by a near field communication device of a mobile device. The issued authentication signal includes a card number currently displayed on the payment card. The issued authentication signal may be issued after the payment card is introduced into any portion of a near field communication field surrounding the mobile device. The issued authentication signal may be an approval of a request to change the card number currently displayed on the visual display of the payment card. While the payment card remains within any portion of the near field communication field surrounding the mobile device, the method may include receiving, by the near field communication device of the payment card, an updated card number signal. The updated card number signal may include an updated card number. In response to receiving the updated card number signal, the card number currently displayed on the visual display of the payment card may be replaced with the updated card number.

[0005] An example of a system is disclosed that includes a reissue application on a mobile device, an authentication server, and a payment card. The reissue application may be executable by a processor of the mobile device and, when executed, is operable to reissue a card number for the payment card. The authentication server is operable to communicate with the reissue application. The payment card may include a payment card near field communication device, a rewritable visual display, a processor, and a memory. The rewritable visual display of the payment card may be operable to present a previously issued card number. The reissue application may, when executed, be operable to send a request to the authentication server to verify that the reissue application is associated with the payment card. In response to verifying that the reissue application is associated with the payment card, the reissue application may obtain an updated card number. The updated card number is different from the previously issued card number. A signal generation component of the reissue application generates an updated card number signal. The updated card number signal may further include information related to at least one of a card validation value, an expiration date, and an issuer. The reissue application may cause an updated card number signal to be output. The payment card may be operable to receive the updated card number signal via the payment card near field communication device. Based on the updated card number signal, the rewriteable visual display may be driven to present the updated card number in place of the previously issued card number. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a block diagram of a system operable to perform payment card reissuance in accordance with an example. [Diagram 2] 2 is an example of a contactless card suitable for use in the example system of FIG. 1. [Figure 3A] FIG. 3 is a block diagram illustrating example components of the contactless card of FIG. 2. [Figure 3B] 2 and 3A. FIG. 2 illustrates an example of an apparatus for providing power to a payment card to modify the rewritable visual display of the example payment card described with reference to FIGS. [Figure 4] 2 is a flow chart illustrating an example of a process performed by a mobile device in a system such as that shown in FIG. 1. [Diagram 5] 2 is a flow chart illustrating an example of a process performed by one or more components of the example system of FIG. 1. [Figure 6] 2 illustrates a computer architecture suitable for implementing one or more components of the example system of FIG. 1. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Related Applications This application claims priority to U.S. Patent Application Serial No. 16 / 506,973, entitled "SYSTEM AND METHOD ENABLING MOBILE NEAR-FIELD COMMUNICATION TO UPDATE DISPLAY ON A PAYMENT CARD," filed July 9, 2019. The contents of the aforementioned application are incorporated herein by reference in their entirety.

[0008] In various examples, systems and methods are described that utilize a mobile device associated with a payment card to update a card number on the payment card, thereby enabling the payment card to be reissued. The mobile device hosts a reissue application, which is a mobile computer application executing on a processor of the mobile device operable to communicate with a service provider that manages the payment card. The payment card includes a processing circuit and a rewritable visual display. Using cryptographic techniques, the mobile device and the payment card are authenticated to the service provider. Once authenticated, an updated card number is retrieved from a secure source and provided to the payment card via near field communication by the mobile device. In response to receiving the updated payment card number from the mobile device, the rewritable visual display on the payment card is updated with the updated card number. Other information may also be presented on the rewritable visual display of the payment card based on user preferences. Advantages of the disclosed embodiments include mobile reissue of payment cards, reduced latency to receive an updated card number, improved security based on security features of both the mobile device and the payment card, and other advantages that may become apparent upon review of the disclosed embodiments.

[0009] In the described example, the payment card may be a credit card-sized contactless card that includes an embedded integrated circuit, a memory device, and an interface that allows the card to communicate with a receiving device using a Near Field Communication (NFC) protocol. An example of a contactless payment card that can be used in the disclosed examples is described in U.S. Patent Application Serial No. 16 / 205,119, filed November 29, 2018 by Osborn et al., entitled "Systems and Methods for Cryptographic Authentication of Contactless Cards," which is incorporated herein by reference in its entirety (hereinafter the '119 Application).

[0010] 1 is a block diagram of a system operable to reissue a payment card according to one embodiment. System 100 may include a service provider 105, a mobile device 120, a data network 130, and a payment card 110.

[0011] The data network 130 may be a cellular network, a wide area network (WAN), the Internet, a Wi-Fi network, or a combination of different networks. The service provider 105 may include a data store 101 coupled to a payment account server 103, an application server 106, a service provider network 107, and an authentication server 150. The service provider 105 may be, as an example, a business that provides computer-based services to clients over the network 115. The combination of software and hardware that provides the service provider's particular service to the client is referred to herein as a "server." The server may communicate over the service provider's private network, often referred to as the service provider network 107. The service provider network 107 may comprise a wireless network, a wired network, or any combination of wireless and wired networks, as described above with respect to the data network 130.

[0012] In the system of FIG. 1, service provider 105 is shown to include application server 106 and authentication server 150. Although each server is illustrated as a separate device, it is understood that applications and servers may be distributed throughout an enterprise, and in the case of distributed resources such as "cloud" resources, may be distributed throughout service provider network 107. Application server 106 may support one or more application services provided by service provider 105, such as account management services. Authentication server 150 may be operable to provide one or both of first and second factor authentication using contactless cards, according to one embodiment, as disclosed in more detail below.

[0013] Data store 109 comprises data storage resources that may be used, for example, to store customer account, credentials and other authentication information, including dynamic password data, for use by application server 106 and authentication server 150. Data store 109 may be comprised of a combined data resource comprising any combination of local storage, distributed data center storage, or cloud-based storage.

[0014] The service provider network 107 may be a wide area data communications network or the like that enables various components of the service provider 105 to communicate with each other within the service provider 105 and with the data network 130 outside the service provider 105. The payment account server 103 may be coupled to the data store 101 and communicatively coupled to the data network 130 and the authentication server 150. The payment account server 103 may be operable to store payment account information 102 in the data store 101 that is associated with the payment card 110 as well as other payment cards (not shown). For example, the payment account information 102 may include at least one of a payment account balance, a payment account limit, information associated with the mobile device 120, user preference information such as a user's preference selections, transaction information, a payment card number history, a list of undeployed payment card numbers, information associated with users authorized to use the payment card 110, and the like.

[0015] In some examples, the payment account server 103 may be operable to store the updated card number 129. For example, in response to a request from the mobile device 120, the payment account server 103 may be operable to retrieve the updated card number 129 from the data store 101 and send the updated card number 129 to a reissue application 127 executing on the mobile device 120.

[0016] The application server 106 may be operable to manage the operation and delivery of different applications (i.e., computer applications or programming code), such as a reissue application 127, executable by a processor on a mobile device, server, or other computing device. For example, a user may select an icon, link, or other mechanism provided as part of the reissue application 127 to launch the application on the mobile device 120 and access the payment card number reissue service. The application server 106 may maintain user preferences, usernames, or similar information in a data store (not shown) similar to data store 101.

[0017] Authentication server 150 may include hardware and software for performing various authentication processes. Authentication server 150 is operable to communicate with payment account server 103 and application server 106 within service provider 105. For example, authentication server 150 may provide authentication status regarding a payment card whose card number is being reissued upon request from either payment account server 103 or application server 106. Additionally, mobile device 120 and data network 130 are operable to exchange communications between mobile device 120 and authentication server 150.

[0018] In one example, authentication server 150 may be operable to authorize payment card transactions and operations related to payment cards, such as authorizing re-issuance of payment card numbers, updates to account information, etc. For example, authentication server 150 may be operable to store information related to clients of service provider 105, including a client information table (not shown). Such information may be stored in data storage 101 and accessible to payment account server 103. Such information may include, but is not limited to, client usernames, client encryption keys, and counters.

[0019] Mobile device 120 may include a mobile device processor 124, a memory 122 that stores a reissue application 127, a transceiver (XCVRS) 187, and a near field communication (NFC) device 125. Mobile device 120 may optionally include a secure element 185 operable to store an updated card number 129. Reissue application 127 hosts signal generation component 121. In an example, reissue application 127, upon execution by mobile device processor 124, may cause mobile device processor 124 to operate to present on mobile device display 128 a user interface 126 that provides information related to payment card 110, including information associating payment card 110 with reissue application 127 on mobile device 120, and may enable the reissue application to respond to user input to user interface 126.

[0020] More specifically, the reissue application 127 may enable a user to manage a payment account maintained by the payment account server 103 in the data storage 101, such as setting authorized users, setting spending limits, setting and responding to purchase confirmation notifications, and requesting reissue of a payment card number. In one example, the reissue application 127 may be associated with the payment card 110 at the authentication server 150. The reissue application 127 may be provided, for example, by the service provider 105 and operable to link to different services and servers, such as the application server 106 and the authentication server 150, and to communicate with the payment card 110. The reissue application may include a signal generation component 121 that generates signals, such as command signals, for output to other devices, such as the service provider 105 or the payment card 110.

[0021] Mobile device 120 may include at least one input device (shown in a later example) coupled to a user interface 126 and a mobile device display 128. Mobile device 120 may further include mobile device display 128, which may be, for example, a touch screen display suitable for providing user interface 126, operable to display information in response to signals generated by republishing application 127 executing on the mobile device 120 processor. Mobile device display 128 may be operable to display user interface 126, presenting information in response to signals generated by republishing application 127 executing on the mobile device 120 processor.

[0022] The mobile device processor 124 may be operable to present, for example, via the reissue application 127, via a user interface 126 on the mobile device display 128, to the mobile device 120, a placement indication of where to place the payment card. The placement indication may indicate a placement of the payment card 110 relative to the mobile device 120 that allows for near field communication signals to be exchanged between the mobile device near field communication device 125 and the payment card near field communication device. The indicated placement may, for example, align the respective electric fields of the respective near field communication devices of the mobile device 120 and the payment card 110 for near maximum signal strength. The user preference indication signal generation indication may be information communicated between the mobile device 120 and the payment card 110. The user preference indication signal generation indication may be generated by the signal generation component 121 based on information related to a selected user preference, and output by the NFC device 125 to the payment card 110 as a user preference signal indication.

[0023] The signal generation component 121 may be hardware, software, firmware, or a combination thereof operable to generate a signal in response to instructions from a reissue application 127 executing on the mobile device processor 124. For example, the signal generation component 121 may be software that functions as part of the reissue application 127. In another example, the signal generation component 121 may be a component of the mobile device 120 associated with, for example, the transceiver 187 or the mobile device processor 124, that is utilized by the reissue application 127.

[0024] In some examples, the signal generation component 121 may be coupled to or part of the mobile device processor 124. In one example, the mobile device processor 124 may output a user preference indication signal generation instruction to the signal generation component 121. The user preference indication signal generation instruction may include user reference information to be output by the rewritable visual display 113 of the payment card 110. The signal generation component 121 may be operable to generate a user preference indication signal according to the user preference indication signal generation instruction. The user preference indication signal may include, for example, information related to a selected at least one of the selectable user preferences. In one example, the signal generation component may include programming code executed by the mobile device processor 124 to process the user preference indication signal generation instruction for output as a user preference indication signal. In one example, the signal generation component 121 receives instructions from the mobile device processor 124 to generate a signal for output to a payment card or other device, such as the issuer server 108, or an entity, such as the service provider 105. When sending the instructions to the issuer server 108 or the service provider 105, the instructions may be output to a respective one of the transceivers 187 for output by the mobile device 120 over the data network 130. The generated user preference indication signal may be forwarded to the mobile device near field communication device 125 for output from the mobile device 120.

[0025] In one example, mobile device 120 may be operable to detect, via mobile device near field communication device 125, an authentication signal emitted from payment card near field communication device 115. The authentication signal may be forwarded to authentication server 150, and in response to forwarding the authentication signal, mobile device 120 may receive a verification or authentication that payment card 110 is a valid payment card having an authenticated association with mobile device 120. For example, the verification or authentication may result in a service provider indicating that payment card 110 is valid for use in a transaction and that the association between mobile device 120 and payment card 110 has been verified and authenticated.

[0026] The mobile device 120 may include a secure element 185. In some examples, the mobile device processor 124 may be operable to retrieve the updated card number 129 from the mobile device's secure element 185 upon retrieving the updated card number 129. The mobile device processor 124 may report the updated card number of the payment card 110 to an issuer server 108 associated with the payment card's issuer. In response to reporting the updated payment, the updated card number may be deleted from the secure element 185 of the mobile device 120.

[0027] The payment card 110 may be operable to receive, via the payment card near field communication device 115, a user preference indication signal output by the near field communication device of the mobile device 120. The user preference indication signal may be processed by the microprocessor 112 of the payment card 110. The processed user preference indication signal may be forwarded to the display driver 633 and the rewritable visual display 113 for outputting an updated card number. The payment card near field communication device 115 may be operable to convert the updated card number signal output by the mobile device NFC device 125 into a voltage value suitable for driving the rewritable visual display 113 (i.e., an electronic ink display in this example) to replace text and / or graphics, such as a card number, presented on the display with new text and / or graphics, such as an updated card number. Payment card 110 may include a payment card near field communication (NFC) device 125, a display driver 633, a rewritable visual display 113, a microprocessor 112, a counter 114, and a memory 116. Rewritable visual display 113 of payment card 110 may be coupled to display driver 633 operable to present a card number. Rewritable visual display 113 may be, for example, an electronic ink display. Memory 116 may store applets 117 and other information 119. Applet 117 may include an instance of a reissue application, such as reissue application 127, which may be obtained from an application server 106 of service provider 105. In one example, memory 116 may include, among other information 119, a secure element (not shown). In some examples, payment card processor 112 may be operable to obtain an updated card number 129 from the secure element. Counter 114 may count the number of times payment card 110 has been used in a transaction or the like.The count of counter 114 may not be shared outside the card, making it difficult for an eavesdropping device to determine the count of counter 114. Details of applet 117 and other information 119 are described in further detail with reference to example figures 2-5.

[0028] Payment card 110 may be a contactless card that communicates wirelessly, e.g., near field communication (NFC), with mobile device 120. Through an NFC interaction between payment card 110 and mobile device 120, payment card 110 may harvest energy (described in more detail with reference to the example of FIG. 3B) from the mobile device's NFC signal to perform functions as described herein. For example, payment card 110 may include one or more chips, such as radio frequency identification chips, operable to communicate via NFC or other short-range protocols. In other examples, payment card 110 may communicate with mobile device 120 via other means, including, but not limited to, Bluetooth, satellite, and / or Wi-Fi. In some examples, the mobile device may be, for example, a card reader terminal, a cell phone, a laptop, and / or a tablet. Payment card 110 may be operable to communicate with mobile device 120 via NFC when payment card 110 is within range of the respective mobile device. As described in more detail below, the payment card 110 may contain username, encryption key and counter information from the counter 114 that can be converted using a cryptographic algorithm to generate a cryptogram that includes a dynamic password that a service provider can use to authenticate the mobile device.

[0029] The system 100 may also include an issuer server 108. The issuer server 108 may be associated with an issuer of the payment card 110 (e.g., Mastercard, Visa, American Express, Discover, etc.). The issuer server 108 may be coupled to a data network 130 and communicatively coupled to communicate with the service provider 105 and the mobile device 120. Components of the issuer server 108 and the service provider 105 may cooperate with each other to provide services to the mobile device 120. In some examples, the issuer server 108 may store an updated card number 129. The mobile device processor 124 via a reissuance application (app) 127 may enable the mobile device 120 to obtain the updated card number from the issuer server 108.

[0030] Details of the operational example will be described in more detail with reference to the examples of Figures 4 and 5. However, at this time, it is useful to briefly describe an operational example illustrating the interaction of each component of the system 100 with reference to Figure 1. In this example, the mobile device 120 may be operable to send a request to the authentication server 150, transmitted over the data network 130 by the reissue application 127. The request may be made to the authentication server 150 to verify that the mobile device 120 is associated with the payment card 110. In response to verifying that the mobile device 120 is associated with the payment card 110, the mobile device 120 may obtain an updated card number (CN) 129. As shown, the updated card number may be stored in a number of different locations within the system 100. For example, the updated card number 129 may be stored by the service provider 105 in a secure location on a payment account server coupled to the data storage device 101. In one example, the updated card number 129 may be stored with the payment account information 102. Payment account information 102 may include information associated with each payment card account that service provider 105 manages and services. Alternatively, issuer server 108 may store a number of unused or unassigned payment card numbers that may be used as updated card numbers 129.

[0031] In an embodiment, the updated card number 129 is different from the card number displayed on the payment card 110 prior to issuing the updated card number. The signal generation component 121 may be operable to generate an updated card number signal. The updated card number signal may include, for example, the updated card number and other associated information, such as a cryptographic key, an authenticated username, a card verification value, an expiration date, an issuer name, etc. In another example, the updated card number signal may be a signal that does not include the updated card number, and instead indicates that the updated card number is generated by a device, such as a payment card or issuer server, that receives the updated card number signal. In a further example, the card verification value may be another identifier, such as a hash value associated with the payment card 110, that can be used, for example, by the authentication server 150 to further verify or verify that the payment card 110 is authentic, valid, or associated with a user who also possesses the mobile device 120. The updated card number signal may be output via the near field communication device 125 of the mobile device. In this embodiment, payment card 110 may be operable to receive, via payment card near field communication device 115, an updated card number signal output by mobile device near field communication device 125. In response to receiving the updated card number signal, microprocessor 112 may be operable to process the updated card number signal, and based on the updated card number signal, writeable visual display 113 may be driven (by display driver 633) to present the updated card number in place of the displayed card number.

[0032] Payment card 110 may include many components, such as those shown in FIG. 1, but a more detailed description of an example payment card is provided with reference to FIGS. 2 and 3A-B.

[0033] 2 provides a front view of an example payment card 200 suitable for use in the example processes described herein. Payment card 200 may operate as a payment card, such as a credit card, debit card, gift card, etc., issued by a service provider / issuer whose name 205 appears on the front (or in some examples, the back) of payment card 200. Contactless, payment card 200 may include user identification information 215 displayed on the front and / or back of payment card 200, as well as service provider / issuer name 205, a rewritable visual display 207, and a contact pad 220.

[0034] Payment card 200 may include substrate 210, which may include a single layer or one or more laminated layers composed of plastic, metal, and other materials. Examples of materials that may be used to form substrate 210 include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyester, anodized titanium, palladium, gold, carbon, paper, biodegradable materials, or the like. In some examples, payment card 200 may have physical characteristics that conform to the ID-1 format of the ISO / IEC 7810 standard, and payment card 200 may otherwise conform to the ISO / IEC 14443 standard. However, it is understood that payment cards 200 according to the present disclosure may have different characteristics.

[0035] Rewritable visual display 207 may be an electronic ink display responsive to a drive signal to set the state of the display, and in response to the drive signal being removed, the electronic ink display remains in the state set by the last applied drive signal. For example, one example of a currently displayed or previously assigned payment card number may be "1234 5678 1234 5678" as shown on rewritable visual display 207. Payment card 200 may include a magnetic strip or tape, which may be located on the back of the card (not shown). As described in the example below, the currently displayed or previously assigned payment card number "1234 5678 1234 5678" may be overwritten with an updated card number, such as "0987 6543 2109 8765". As a result, a payment card with the updated card number may be reissued and used in future transactions.

[0036] As an example, payment card 200 may include a rewritable magnetic strip that is rewritten with an updated card number for use in future transactions at substantially the same time that the updated card number is provided to the electronic ink display.

[0037] Payment card 200 may also include user identification information 215 displayed on the front and / or back of the card, and a contact pad 220. User identification information 215 (shown as "Cardholder Name") may be the user's name or nickname. Contact pad 220 may be operable to establish contact with another communication device, such as a mobile device, a smart phone, a laptop, a desktop, a tablet computer, etc. Payment card 200 may include processing circuitry, an antenna, and other components as shown in other examples. These components may be located behind contact pad 220 or elsewhere on substrate 210.

[0038] As described above, payment card 200 may be built on a software platform operable, for example, on a smart card of program code, processing power, and memory, such as JavaCard. In some examples, an applet, such as 117 in FIG. 1, may be added to the contactless payment card to generate a card number reissue request as well as provide other services, such as issuing one-time passwords (OTPs) for multi-factor authentication (MFA) in various mobile application-based use cases. In this manner, the contactless payment card functionality enables communication with a mobile device for payment card number reissue, as described below with reference to FIGs. 3A-5.

[0039] FIG. 3A is a block diagram illustrating example components of the contactless payment card of FIG. 2 in greater detail.

[0040] 3A, beneath (and coupled to) the contact pads 320 may be processing circuitry 325 for processing and storing information, and one or more antennas 355. It will be appreciated that in addition to logic circuitry and the like, the processing circuitry 325 may include additional components necessary to perform the functions described herein, such as, for example, processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, tamper-proof hardware, etc.

[0041] One or more antennas 355 may be disposed beneath and within the payment card and contact pad 320 and around the processing circuitry of the contact pad 320. For example, one or more antennas 355 may be integral with the processing circuitry 325 while another of the one or more antennas may be used with an external booster coil. In another example, one or more antennas 355 may be external to the contact pad 320 and processing circuitry. One or more antennas 355 may also provide the necessary inductance to harvest power to drive, for example, the processing circuitry 325, memory 335, rewritable visual display 207 of FIG. 2, etc. The processing circuitry 325 may include a power management unit (not shown) operable to manage power and storage of the payment card 200.

[0042] In one example of energy harvesting, FIG. 3B shows an example of an apparatus 360 for providing power to a payment card to modify a rewritable visual display of the example payment card as described with reference to FIGS. 2 and 3A-B. In the example apparatus 360 of FIG. 3B, the antenna 362 may be an NFC compatible antenna configured to receive NFC signals. In the example of FIG. 3B, the antenna 362 may be operable to provide both communication and the inductance required for power harvesting. As mentioned above, the antenna 362 may be coupled to a communication interface (shown in the example of FIG. 3A) that provides a signal to a processing circuit for signal processing (as described with reference to FIG. 3A). For example, the power harvested by the antenna 362 may be derived from, for example, a 13.56 MHz NFC signal that generates an alternating current in the antenna 362. Of course, radio frequency signals of frequencies other than 13.56 MHz may be used. The matching circuit 363 may be part of the antenna 362 to match the incident magnetic field for maximum inductance. In this embodiment, the inductive-capacitive (LC) filter 364 may act as a low pass filter to remove high frequency components from the received signal that are not required for the communication output by the processing circuitry (shown in FIG. 3A).

[0043] The energy of the induced current and voltage is harvested by an energy harvesting component 361. The induced voltage may be on the order of 0.1 volts (V). The voltage may be provided to a power management unit 365 for rectification, smoothing, and other processing, or may be distributed to other components such as a display driver 333 or NFC circuitry 368, which may be controlled by a microprocessor (as shown in other embodiments). In an example, the induced voltage may power changes on a rewritable visual display such as an E-ink display. If the induced voltage is too low, the induced voltage may be increased using additional circuit elements or techniques, such as a transformer with more turns in the coil or an increased permanent magnetic field. If the payment card is not being reissued, since power is only required when the e-ink display is replaced, the payment card may harvest energy while being used with the NFC device and store the harvested energy in an energy storage device 367, which may be a battery, capacitor, supercapacitor, etc., to reserve power for future display replacements. The power management unit 365 may, in a further example, include an intermediate energy storage device, such as a capacitor, to smooth the voltage provided by the energy harvesting component 361.

[0044] In an embodiment, the signal received via NFC antenna 362 may be used to power NFC circuitry 368 directly, or may capture power via energy harvesting component 361 to drive display driver 333, under control of the processor, to update the payment card number and present other information via changes to the e-ink display, as described with reference to other embodiments.

[0045] Returning to the example of FIG. 3A, memory 335 may be a read-only memory, a write-once-read-multiple memory, or a read / write memory, e.g., RAM, ROM, and EEPROM, and processing circuitry 325 may include one or more of these memories. For example, read-only memory may be factory programmable as read-only or one-time programmable. One-time programmable offers the opportunity to write once and read many times. Writable memory may be programmed at some point after the memory chip leaves the factory. Once programmed memory cannot be rewritten, but can be read many times. Read-write memory may be programmed and reprogrammed many times after leaving the factory, and can be read many times.

[0046] Memory 335 may be operable to store one or more applets 340, one or more counters 345, and payment card account identifier(s) 350. One or more applets 340, one or more counters 345, and payment card account identifier(s) 350. One or more applets 340 may comprise one or more software applications associated with a respective one or more service provider applications (e.g., provided by service provider 105 of FIG. 1) operable to run on one or more payment cards, e.g., Java card applets. For example, an applet of applet 340 may be operable to respond to one or more requests, such as a Near Field Data Exchange (NDEF) request, from a reader, such as a Near Field Communication (NFC) reader, and generate an NDEF message consisting of a cryptographically secure OTP encoded as an NDEF text tag. According to one example, each applet may store a username of a user associated with a payment card account for accessing an associated service provider application. The one or more counters 345 may, in some examples, comprise a numeric counter sufficient to store an integer representative of the number of times the payment card 200 has been used.

[0047] Payment card account identifier 350 may include a unique alphanumeric identifier assigned to the user of payment card 200 and / or one or more cryptographic keys used to distinguish the payment card user from other payment card users. In some examples, payment card account identifier 350 may include information that identifies both a customer and an account assigned to the customer, and may further identify a payment card associated with the customer's account. According to some embodiments, username 342 may be derived from a combination of one or more of payment card account identifier 350 and / or one or more cryptographic keys 343.

[0048] 1 and 3, memory 335 may include information of username 342, encryption key 343, and counter 345, which may be transformed by microprocessor 330, for example, using a cryptographic algorithm, and used to generate an encryption key including a dynamic password that may be used by service provider authentication server 150 of FIG. 1 to authenticate payment card 110, mobile device 120, a user (not shown), or all three. For example, microprocessor 330 may use values ​​from one of payment card account identifier 350, encryption key 343, and counter 345 in the cryptographic processing functionality provided by microprocessor 330 to generate an encryption key including a dynamic password, along with a username, that may be used to authenticate re-issuance of payment card 110 and provision of an updated card number 129 to payment card 110 via mobile device 120. In one example, the dynamic password is for counter 345. In such an example, the dynamic password thus advantageously reflects the previous behavior of the holder of payment card 110. For example, a counter-based dynamic password may reflect the number of times a user has used payment card 110 to obtain a particular service (e.g., to advance money, authorize a transaction, etc.) from service provider 105, an element of knowledge that is virtually impossible for a malicious third party to grasp. For example, the number of times the payment card 110 has been used may be stored in secure memory on the payment card as a value for counter 345, which is incremented each time the payment card is used for a transaction.

[0049] Although the microprocessor 330 and memory 335 elements of the foregoing exemplary embodiment are described with reference to contact pads 320, the disclosure is not limited in this respect. It will be understood that these elements may be implemented outside of contact pads 320, may be implemented entirely separate from contact pads 320, or may be implemented as additional elements in addition to the microprocessor 330 and memory 335 elements disposed within contact pads 320.

[0050] 2 and 3A-B, in some examples, payment card 200 may include one or more antennas 355 disposed around processing circuitry 325 of contact pad 320. For example, one or more antennas may be integral with processing circuitry 325, or one or more antennas 355 may be used with an external booster coil. As another example, one or more antennas 355 may be external to contact pad 320 and processing circuitry 325. As one example, one or more antennas 355 may extend around an area of ​​the card to enhance the power transfer characteristics of the antenna when placed in an electric field, such as an NFC field of a mobile device.

[0051] The processing circuit 325 may include one or more communication interfaces 337, such as a radio frequency identification (RFID) chip 338 coupled to one or more antennas 355 operable to communicate with a mobile device, such as 120 of FIG. 1, in compliance with ISO / IEC 14443 via one or more short-range wireless communication protocols, such as Near Field Communication (NFC), Europay, MasterCard, Visa (EMV) standards, etc. In some examples, the RFID chip 338 may also be referred to as a payment card near field communication device, such as 115 of FIG. 1. Although NFC is used as an exemplary communication protocol, the present disclosure is equally applicable to other types of wireless communication, such as EMV standards, Bluetooth, and / or Wi-Fi. The RFID chip 338 may include additional components as shown in the example of FIG. 3A.

[0052] Payment card account identifier 350 may include a unique alphanumeric identifier assigned to the user of payment card 200 and / or one or more cryptographic keys 343 that may be used to distinguish the payment card user from other payment card users. In some examples, payment card account identifier 350 may include information that identifies both a customer and an account assigned to the customer, and may further identify the payment card associated with the customer's account (i.e., a payment card number). According to some embodiments, username 342 may be derived from a combination of one or more of payment card account identifier 350 and / or one or more cryptographic keys 343.

[0053] As an example, payment card number re-issuance may utilize a passwordless authentication protocol that practically applies the contactless payment card cryptographic exchange protocol as a first factor authentication mechanism to facilitate access to application services without compromising the security of the application services.

[0054] The payment card cryptographic exchange protocol includes registering the client's payment card with the application service, binding the contactless card to the client, and using the cryptographic exchange protocol to perform first factor, second factor and / or other authentication of the client's access request utilizing either applet 340, a counter value from counter 345, a key value from cryptographic key 343, and microprocessor 330.

[0055] To ensure valid authentication of the payment account, mobile device, and payment card, the three are typically tied together by correlating digital credentials of the payment account, mobile device, and payment card with each other.

[0056] For example, a payment card may be registered with the service provider 105 to receive reissue application services. As part of registration, a username, such as 342, may be stored in the data store 109 coupled to the authentication server 150. In some examples, the username may be automatically generated by the service provider 105, unknown to the mobile device, and loaded into both a user information table (not shown) stored in the data store 109 and an applet 340 downloaded to the payment card 110. As an example, a payment card is associated with a user and the user's payment account maintained by the payment account server 103 and stored in the data store 101. The payment card number (e.g., 1234 5678 1234 5678), user information, and the user's payment account information (i.e., account number or other identifier) ​​may be maintained and stored by the service provider 105 via the payment account server 103. The payment account information 102 also includes information regarding the mobile device, the payment card, and the user's payment account associated with the user. For example, payment account information 102 may include information about mobile device 120, such as a unique identifier associated with the mobile device (e.g., a phone number, a Mobile Equipment Identifier (MEID), an International Mobile Equipment Identity (IMEI), an International Mobile Subscriber Identity (IMSI), a serial number, a Media Access Control (MAC) address, and / or the like), application information related to the application used to take the image (e.g., an identifier for the instance of the application, a version of the application, and / or the like), and / or the like.Once a payment card is registered with the service provider 105 and bound to a mobile device, application authentication using the payment card's cryptographic algorithms may be performed to allow authentication of the payment card, the mobile device, and the user, thereby allowing re-issuance of the payment card via the re-issuance application. Examples of cryptographic algorithms suitable for use in the disclosed examples include Triple Data Encryption Algorithm (3DES), Advanced Encryption Standard (AES), symmetric Hash Based Message Authentication (HMAC) algorithms such as HMAC-SHA-256, and symmetric Cypher-Based Message Authentication Code (CMAC) algorithms such as AES-CMAC. This level of security allows the following process to be performed securely, thereby mitigating concerns for service providers and payment account users that unscrupulous individuals may fraudulently compromise payment cards as described herein.

[0057] FIG. 4 is a flow chart illustrating an example of a process performed by a mobile device for use in a system such as that shown in FIG. 1. In one example, an e-ink display enabled card is compromised (e.g., fraudulent transactions are made using the payment card number) and the payment card needs to be reissued. Instead of replacing the payment card (110 in FIG. 1 or 200 in FIG. 2), the payment card of the disclosed embodiment may have the number of the payment card changed. In an embodiment, the payment card may be placed within the electric field of an NFC device mobile phone (e.g., "tap to phone") and information provided to authenticate the payment card. Based on authentication of the card and the mobile device, the mobile device is operable to pass new information: card number, card verification value (CVV), expiration date, service provider / issuer (e.g., VISA or MASTERCARD), all or some of which may be displayed. For example, when the e-ink display is changed and the payment card is removed from the NFC field of the mobile device, the e-ink display becomes stationary.

[0058] More specifically, process 400 may include the mobile device sending a request to update the card number of the payment card to be reissued (410). The request may include an indication that the card number presented on the display of the payment card and / or the card number encoded on the magnetic strip of the payment card is invalid and cannot be used to complete a transaction (e.g., purchasing goods or services, etc.). The payment card number may become invalid and unusable because the payment card number has been compromised due to identity theft, user negligence, etc. In some examples, an authentication message may be generated by a reissue application, such as 127 of FIG. 1, executing on the mobile device prior to sending the authorization request to reissue the payment card. The authentication message may include information related to the mobile device that is stored, for example, by an authentication server of the service provider. The authentication message may be included in the request along with the indication.

[0059] In response to the transmitted request, the mobile device 120 may receive (420) authorization to reissue the payment card and update the card number. For example, the mobile device 120 may receive authorization to reissue the payment card and update the card number based on an authorization message included in the request. For example, the authorization message included in the request may include information processed by the authentication server 150, such as an encrypted message. An authentication status message may be transmitted from the authentication server 150 to the payment account server 103, the application server 106, or both. In response to the authentication status message, the payment account server 103 or the application server 106 may retrieve and transmit information related to the updated card number and / or selected user preferences (described in more detail below).

[0060] In this example, the card number encoded on the magnetic strip of the payment card may not be updated. In response to the received authentication, the updated card number may be retrieved from a secure source of updated card numbers (430). In this example, the mobile device may retrieve the updated card number by retrieving the updated card number from a secure element of the mobile device. Upon retrieving the updated card number from the secure element, the mobile device may report the updated card number of the payment card to, for example, an issuer server associated with the issuer of the payment card or a financial institution associated with the payment card. The mobile device may remove the updated card number from the secure element or take some other action to ensure that the updated card number is not inadvertently reused. As shown in FIG. 1, the updated card number (CN) 129 may be stored in various locations and may be retrieved by the mobile device 120 in response to request and authentication by the respective sources. For example, the secure source of the updated card number may be one or more of a variety of sources, such as, for example, a secure element in the mobile device, a secure element in the payment card, a source in the service provider, a source in the issuer of the payment card, or another secure source. Instead of obtaining the updated card number in the secure element of the mobile device, the mobile device may obtain the updated card number from an issuer server associated with the issuer of the payment card, such as issuer server 108 of FIG. 1, when obtaining the updated card number from the secure source of the updated card number. In another example, the updated card number may be generated by the reissue application 127 of the mobile device based on data obtained from the payment card 110 of FIG. 1 using a cryptographic hash function. In another example, the processor 112 of the payment card 110 may be operable to generate the updated card number using, for example, a cryptographic hash function or other function and data maintained in a memory of the payment card, such as data from a counter 114, etc.In an embodiment, a cryptographic hash function or other function may be a secure source of the updated card number through the use of various encryption and other security techniques. Once payment card 110 of Figure 1 generates the updated card number, authentication server 150 of Figure 1 may be used to authenticate payment card 110 via mobile device 120. Once authenticated, payment card 110 itself may generate the updated card number.

[0061] In yet another example, when mobile device 120 obtains the updated card number from a secure source of the updated card number in step 430, it may obtain the updated card number from a secure element of the mobile device. Mobile device 120 may report the updated card number of the payment card to an issuer server associated with the issuer of the payment card and remove the updated card number from the secure element.

[0062] In response to a command signal from a signal generation component executing on the mobile device, an updated card number signal representing the updated card number may be output via a near field communication circuit or device within the mobile device (440). A near field communication device included in the reissued payment card may receive the updated card number signal while the payment card is within range of the near field communication circuit or device within the mobile device (450). As an example, the payment card may receive an authentication signal from the mobile device 120 via the payment card near field communication device. Logic on the payment device may verify that the mobile device 120 is associated with the payment card, e.g., using a cryptographic key or the like.

[0063] The payment card may use energy from the updated card number signal to power a microprocessor and respond to the received signal. For example, at 460, in response to receiving the updated card number signal and harvesting energy from the received signal, a visual display on the payment card may be changed to indicate the updated card number. In an example where the payment card has a rewritable magnetic strip, the microprocessor of the payment card may be operable to rewrite the rewritable magnetic strip with the updated card number. Conversely, in an example where the payment card does not have a rewritable magnetic strip, the updated card number is different from the card number represented by the magnetic strip of the reissued payment card. Additionally, the updated card number signal may include a value indicating that the magnetic strip is invalid and unusable for point of sale devices that continue to use swipe technology. The payment card may store a value indicating that the magnetic strip is invalid and unusable and provide information related to the value to the point of sale device. Alternatively, the updated card number itself may indicate that the magnetic strip is invalid, or the authentication server may be configured to provide an indication to the point of sale device that the magnetic strip is invalid and cannot be used.

[0064] In another example, the updated card number may be a temporary payment card number, such as a temporary virtual number that can be used for one transaction, a predefined period of time, etc. The temporary virtual number may be displayed for a limited time, such as for a single transaction, a predefined period of time, etc. In another example, the rewritable visual display may be used to display a one-time use "token," temporary virtual number, or dynamic credit card number, provided by either an application server or an authentication server and transmitted to the payment card, such as via NFC on the mobile device. An indication may be provided that the token, temporary virtual number, or dynamic credit card number is not a primary payment account number.

[0065] In some examples, process 400 may include enabling the mobile device to perform additional functions. These additional functions may, for example, increase the user's awareness of the monetary value associated with the payment card by providing additional information that may be time-consuming and inconvenient to obtain. For example, in response to a user's input, the mobile device may select an account display preference for displaying information about the payment card. In response to the selected account display preference, a signal generation component of the mobile device may modify signal parameters for rewriting the rewritable visual display according to the selected account display preference. The modified signal parameters may be used to transmit a user preference display signal to the payment card. The transmitted user preference display signal causes one or more of the following information to be presented on the visual display of the payment card: the last transaction amount, the rewards total amount, the account balance, the account limit, or an alert related to the account balance. Of course, other information may be provided. The presented information may be obtained from a service provider 105, such as from a payment account server 103 or an application server 106, for example.

[0066] A payment card, such as 110 of FIG. 1, may be operable to perform a process for authentication of the card to receive an updated card number. FIG. 5 is a flow chart illustrating an example of a process 500 performed by the payment card of the example system of FIG. 1. In an example, at 510, a processor of the payment card may generate an authentication signal including the payment card number currently displayed on a visual display of the payment card. In an example, a near field communication device of the payment card may transmit the generated authentication signal for receipt by a near field communication device of the mobile device. In this example, the transmitted authentication signal may include the payment card number currently displayed on the payment card. The transmitted authentication signal may be transmitted after the payment card is introduced into any portion of a near field communication field surrounding the mobile device. The transmitted authentication signal may acknowledge a request to change or reissue the card number currently displayed on the visual display of the payment card. In this example, the payment card may store an indication in a memory device within the payment card that the card number encoded on the magnetic strip of the payment card is invalid and cannot be used.

[0067] While the payment card remains within any portion of the near field surrounding the mobile device, the near field communication device of the payment card may receive an updated card number signal (520). In one example, the updated card number signal may be received from the mobile device and may include only the updated card number. In another example, the updated card number signal received from the mobile device may include other information in addition to the updated card number, such as information based on user selected preferences.

[0068] In a particular example, the updated card number signal may be related to provisioning of an EMV (Europay, Mastercard, Visa) profile. As an example, the EMV profile contains authentication keys used to verify chip-based and contactless payment transactions. These authentication keys may be transmitted encrypted with the card's symmetric master key (stored in the card's secure memory, such as a secure element) or may be transmitted by activating a backup "profile." A backup profile may be, for example, an inactive full set of EMV-compliant data on the payment card's chip, which may become the primary payment card number (i.e., the payment card number authorized to be used for transactions). Upon activation of each updated payment card number, the payment card may display the updated payment card number as the new Primary Account Number (PAN).

[0069] In response to receiving the update card number signal, the card number currently displayed on the visual display of the payment card may be replaced with the updated card number 530. For example, a processor or logic circuitry on the payment card may generate display drive signals to drive the visual display of the payment card to change the currently displayed card number in response to receiving the update card number signal by the near field communication device of the payment card.

[0070] The payment card may also receive an account status signal via the near field communication device of the mobile device at 540. In response to the account status signal, the visual display of the payment card may be altered to present at least one of the payment card account balance, the most recent transaction amount, the account annual percentage rate, reward points balance, payment due date, location-based discounts, or location-based rewards.

[0071] Process 500 may further include selecting an account display preference to modify information displayed on the payment card. For example, a signal generation component under control of the reissue application 127 may modify signal parameters according to the selected account display preference. A display preference signal based on the selected preference may be sent to the payment card prior to sending a signal representing the updated card number. The display preference signal may cause the payment card's e-ink display to display one or more of the last transaction amount, rewards total, account balance, account limit, and account balance warnings.

[0072] In other examples, the user preference display signal may include information related to a selected at least one of the selectable user preferences in addition to the updated card number. For example, the mobile device processor 124 of FIG. 1 may be operable to present a menu of selectable user preferences on the mobile device display 128 via a user interface provided by execution of the reissue application 127.

[0073] In an example, the menu of selectable user preferences may include one or more of a payment card account balance, a recent transaction amount, an account annual percentage rate, a reward points balance, a payment due date, a location-based discount, or a location-based reward. A selection of at least one of the selectable user preferences may be received by the mobile device 120 through at least one input device (e.g., a touch screen, a button, a keypad, etc.). The at least one selected user preference may be stored in memory. In one example, each selected user preference may be presented on the rewritable visual display 113 of the payment card 110 whenever the payment card 110 and the mobile device 120 communicate with each other, regardless of whether the payment card number is reissued. The mobile device processor 124 may be further operable to obtain information related to the selection of at least one of the selectable user preferences in response to verification that the mobile device 120 is associated with the payment card 110 via the reissue application 127. Information associated with the selected at least one of the selectable user preferences may be stored in memory 122 by other elements 189 or may be obtained via authentication server 150, payment account server 103, or application server 106, for example. Memory 122 may also be operable to store user associated numbers, information associated with users authorized to use the payment card, etc.

[0074] In another example, the payment account server 103 may be operable to retrieve an updated card number from the data store 101 in response to a request from the mobile device 120. The payment account server 103 may send the updated card number to a reissue application 127 executing on the mobile device.

[0075] In response to the account status signal, the visual display of the payment card may be altered (550) to present at least one of the payment card's account balance, most recent transaction amount, the account's annual percentage rate, reward points balance, payment due date, location-based discounts, or location-based rewards. In some examples, the prior transaction information may be stored in a memory such as 335 in FIG. 3A. When the payment card is placed in a near field, the payment card may harvest energy to present a portion of the prior transaction information.

[0076] In another example, the rewritable visual display might be used to display a one-time-use "token" or dynamic credit card number, provided by a server and transmitted to the card via NFC, perhaps with some indication that it is not a primary account number.

[0077] In addition to reissuing the payment card number for use in future transactions, the rewritable visual display may also be controlled to change the type of card. For example, the payment card may be changed entirely to another type of card, such as a prescription card, an authentication card, a debit card, etc. Of course, to accommodate such card type changes, a service provider, such as 105 in FIG. 1, may access or provide respective services related to prescription cards, authentication cards, debit cards, etc.

[0078] 6 illustrates an example of a computing architecture 600 suitable for implementing various examples as described above. In one example, computing architecture 600, if appropriately programmed, may incorporate elements that may be typically used to implement a server or network platform as part of system 100. In another example, computing architecture 600 may incorporate optional elements that may be typically used to implement a smart digital or computing device that may be implemented as part of system 100.

[0079] Computing architecture 600 may include various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing units, video cards, audio cards, multimedia input / output (I / O) components, power supplies, etc. However, the present embodiment is not limited to implementation by computing architecture 600.

[0080] 6, computing architecture 600 includes a processing unit 604, a system memory 606, and a system bus 608. Processing unit 604 can be any one or many of a variety of commercially available processors.

[0081] The system bus 608 provides an interface to the processing unit 604 for system components including, but not limited to, the system memory 606. The system bus 608 can be any of several types of bus structures that can be further interconnected to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. Interface adapters may connect to the system bus 608 via a slot architecture. Examples of slot architectures include, but are not limited to, Accelerated Graphics Port (AGP), CardBus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and the like.

[0082] Computing architecture 600 may include or be implemented in a variety of articles of manufacture. The articles of manufacture may include a computer-readable storage medium that stores logic. Examples of computer-readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and the like. Examples of logic may include executable computer program instructions implemented using any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. Also, may be implemented, at least in part, as instructions contained in or on a non-transitory computer-readable medium embodied in programming code that may be read and executed by one or more processors to enable execution of example operations described herein.

[0083] The system memory 606 may include various types of computer readable storage media in the form of one or more high speed memory units, such as read only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, Silicon-Oxide-Nitrid-Oxide-Silicon (SONOS) memory, magnetic or optical cards, device arrays such as Redundant Array of Independent Disks (RAID) drives, solid state memory devices (e.g., USB memory), Solid State Drives (SSD), and any type of storage medium suitable for storing information. In the exemplary embodiment shown in FIG. 6, the system memory 606 may include non-volatile memory 610 and / or volatile memory 612. The non-volatile memory 610 can store a Basic Input / Output System (BIOS).

[0084] The computer 602 may include various types of computer readable storage media in the form of one or more low speed memory units, including an internal hard disk drive (HDD) 614 (or, optionally, an external hard disk drive (HDD) 613), a magnetic floppy disk drive (FDD) 616 that reads from or writes to a removable magnetic disk 618, and an optical disk drive 620 that reads from or writes to a removable optical disk 622 (e.g., a CD-ROM or DVD). The HDD 614 or 613, FDD 616 and optical disk drive 620 can be connected to the system bus 608 by a HDD interface 624, a FDD interface 626 and an optical drive interface 628, respectively. The HDD interface 624 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies.

[0085] The drives and associated computer-readable media provide volatile and / or nonvolatile storage of data, data structures, computer-executable instructions, and the like. A number of computer program modules can be stored in the drives and memory 610, 612, including, for example, an operating system 630, one or more application programs 632, other program modules 634, and program data 636. In one example, the one or more application programs 632, other program modules 634, and program data 636 can include, for example, various applications and / or components of the computing architecture 600. At least one computer-readable storage medium may contain instructions that, when executed, cause the system to perform any of the computer-implemented methods and processes described herein.

[0086] Optionally, when configured as a mobile device, smart digital device, laptop, etc., the computing architecture 600 may include additional devices that allow data input and output to a user. For example, a user may input commands and information to the computer 602 via one or more optional wired / wireless input devices, e.g., a keypad 638 and a tactile input device, such as a touch screen 640. Other input devices may include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, a game pad, a stylus pen, a near field communication device, a dongle, a fingerprint reader, a glove, a graphic tablet, a joystick, a keyboard, a retina reader, a touch screen (e.g., capacitive, resistive, etc.), a track ball, a track pad, a sensor, a stylus, etc. These and other input devices are often connected to the processing unit 604 via an optional interface 642 coupled to the system bus 608, but may also be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.

[0087] Another optional element is a display 644, which may be an organic light emitting diode (OLED), light emitting display (LED), or other type of display device, which may also be connected to the system bus 608 via an interface, such as an optional video adapter 646. The display 644 may be internal or external to the computer 602. In addition to the display 644, computers typically include other peripheral output devices, such as speakers, printers, etc., which may also be coupled to the system bus 608 via an optional interface 642.

[0088] The computer 602 may operate in a networked environment using wired and / or wireless communication logical connections to one or more remote computers, such as a remote computer 648. The remote computer 648 can be a workstation, a server computer, a router, a personal computer, a portable computer, a microprocessor-based entertainment appliance, a peer device, or other common network node, and typically includes many or all of the elements described relative to the computer 602, although for simplicity, only a remote memory / storage device 659 is illustrated. The illustrated logical connections include wired / wireless connections to a local area network (LAN) 652 and / or larger networks, such as a wide area network (WAN) 654. Such LAN and WAN networking environments are commonplace in offices and businesses and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network, such as the Internet.

[0089] When used in a LAN networking environment, the computer 602 may be connected to the LAN 652 via a wired and / or wireless communication network interface or adapter 656. The adapter 656 may facilitate wired and / or wireless communication to the LAN 652 and may include a wireless access point disposed thereon for communicating with the wireless capabilities of the adapter 656.

[0090] When used in a WAN networking environment, the computer 602 may include a modem 658 or be connected to a communications server on the WAN 654 or have other means for establishing communications over the WAN 654, such as via the Internet. The modem 658, which may be internal or external and a wired and / or wireless device, connects to the system bus 608 via an interface 642. In a networked environment, program modules depicted relative to the computer 602, or portions thereof, may be stored in a remote memory / storage device 659. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

[0091] The computer 602 is operable to communicate with wired and wireless devices or entities using the IEEE 802 family of standards, such as wireless devices operatively arranged for wireless communication (e.g., IEEE 802.11 wireless modulation techniques). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth wireless technologies, among others. Thus, the communication may be of a predefined structure, such as a traditional network, or simply ad-hoc communication between at least two devices. A Wi-Fi network uses radio technologies called IEEE 802.11x (a, b, g, n, etc.) to provide secure, reliable, and high-speed wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (using IEEE 802.3 related media and functions). Wireless technology may be coupled to computer 602 via one or more transceivers (not shown) in optional interface 642 or communications interface 656 facilitating the use of wireless technologies such as, for example, Wi-Fi, WiMax, Bluetooth, as well as others.

[0092] The various elements of the apparatus as described above with reference to Figures 1-6 may include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include apparatus, logic devices, components, processors, microprocessors, circuits, processors, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, Application Specific Integrated Circuits (ASICs), Programmable Logic Devices (PLDs), Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), memory units, logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. However, the decision of whether to implement an example using hardware and / or software elements may vary depending on any number of factors, such as desired computational speeds, power levels, thermal tolerances, processing cycle budgets, input data rates, output data rates, memory resources, data bus speeds, and other design or performance constraints desired for a given implementation.

[0093] The terms "system," "component," and "unit" as used herein are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution, examples of which are described herein. For example, a component can be, but is not limited to, a process running on a processor, a processor, a hard disk drive, multiple storage drives (optical and / or magnetic storage media), an object, an executable, a thread of execution, a program, and / or a computer. By way of example, both an application running on a server and the server can be a component. One or more components can reside within a process and / or thread of execution, and a component can be localized on one computer and / or distributed between two or more computers.

[0094] Additionally, each component may be communicatively coupled to one another by various types of communication media to coordinate operations. The coordination may include unidirectional or bidirectional exchange of information. For example, the components may convey information in the form of signals communicated over the communication media. The information may be implemented as signals assigned to various signal lines. In such an assignment, each message is a signal. However, further examples may instead employ data messages. Such data messages may be transmitted over various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

[0095] Some embodiments may be described using the phrase "one embodiment" or "one embodiment" and its derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. The appearance of the phrase "in one embodiment" in various places in this specification does not necessarily all refer to the same embodiment. Moreover, unless otherwise noted, it is recognized that the features described above can be used together in any combination. Thus, any features discussed separately may be employed in combination with each other, unless it is indicated that the features are mutually exclusive.

[0096] Generally referring to the notation and nomenclature used herein, the detailed descriptions herein may be presented in terms of functional blocks or units that may be implemented as 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 substance of their work to others skilled in the art.

[0097] A procedure, process, or method is herein generally conceived to be a self-consistent sequence of operations leading to a desired result. These operations require physical 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 is sometimes convenient, 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 these quantities.

[0098] Further, the manipulations performed are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. 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 of the embodiments. Rather, the operations are machine operations. Useful machines for performing the operations of the various embodiments include general purpose digital computers or similar devices.

[0099] Some examples may be described using the terms "coupled" and "coupled," along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, some examples may be described using the terms "connected" and / or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements still cooperate or interact with each other even when they are not in direct contact with each other.

[0100] Various examples also relate to an apparatus or system for performing these operations. The apparatus may be specially constructed for the described purposes, or it may comprise a general-purpose computer as selectively activated or reconfigured by a computer program stored in the computer. The procedures or processes described herein are not inherently related to any particular computer or other apparatus. Various general-purpose machines may be used with programs written in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. A structure for these various machines will appear from the description given.

[0101] It is emphasized that the Summary of the Disclosure is provided to enable the reader to quickly grasp the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Additionally, in the foregoing detailed description, various features are grouped together in a single example for the purposes of streamlining the disclosure. Such disclosure method should not be interpreted as reflecting an intention that the claimed examples require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Accordingly, the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment. In the appended claims, the terms "including" and "in which" are used as the plain English equivalents of the respective terms "comprising" and "wherein." Additionally, the terms "first," "second," "third," etc. are used merely as labels and are not intended to impose numerical requirements on their subject matter.

[0102] The foregoing includes examples of the disclosed architecture. Of course, it is not possible to describe every conceivable combination of components and / or methodologies, but one of ordinary skill in the art will recognize that many more combinations and permutations are possible. Accordingly, the novel architecture is intended to embrace all such alterations, modifications, and variations that fall within the spirit and scope of the appended claims.

Claims

1. transmitting, via a mobile device, a request to update the card number of a reissued payment card, said request being presented on a display of said payment card and including an indication that the card number encoded on a magnetic strip of said payment card is invalid and cannot be used; receiving, by the mobile device, authorization to reissue the payment card and update the card number in response to the transmitted request; retrieving an updated card number from a secure source of updated card numbers in response to receiving said authorization; in response to a command signal from a signal generating component, outputting an updated card number signal, representing the updated card number, via a near field communication circuit of the mobile device; receiving, in response to the updated card number signal, via a near field communication circuit in the mobile device a signal indicating that the card number has been successfully updated; method.

2. receiving, by the mobile device, the authorization to reissue the payment card and update the card number; generating an authorization message to be included in the request with the indication prior to sending the request for approval to reissue the payment card; The authentication message comprises: including information stored by a service provider's authentication server relating to the mobile device; The method of claim 1.

3. Obtaining the updated card number from the secure source of updated card numbers includes: obtaining the updated card number from a secure element of the mobile device; reporting the updated card number of the payment card to an issuer server associated with an issuer of the payment card; and deleting the updated card number from the secure element. The method of claim 1.

4. Obtaining the updated card number from the secure source of updated card numbers includes: obtaining the updated card number from an issuer server associated with the payment card issuer; The method of claim 1.

5. selecting an account display preference in a user interface provided by the reissue application to display the payment card information; modifying, by the signal generation component, signal parameters in response to selected account display preferences provided by the reissue application; and transmitting a user preference indication signal that causes the visual display of the payment card to display one or more of a last transaction amount, a rewards total amount, an account balance, an account limit, and an account balance warning based on the modified signal parameters prior to transmitting the signal representing the updated card number. The method of claim 1.

6. transmitting an authentication signal by a near field communication device of the payment card for receipt by a near field communication device of the mobile device; Here, the authentication signal to be sent is a payment card number currently displayed on a visual display of said payment card; Dispatched after the payment card is introduced into any portion of a near field wireless communication field surrounding the mobile device; and an approval of a request to change the card number currently displayed on the visual display of the payment card; receiving, by a near field communication device of the payment card while the payment card remains within any portion of the near field communication field surrounding the mobile device, an updated card number signal, the updated card number signal including an updated card number; and in response to receiving the updated card number signal, replacing the card number currently displayed on the visual display of the payment card with an updated card number. method.

7. storing, in a memory device of the payment card, an indication that the payment card number encoded on the magnetic strip of the payment card is invalid and cannot be used. The method according to claim 6.

8. and generating, in response to receiving the updated card number signal by the near field communication device of the payment card, a display drive signal for driving the visual display of the payment card to change the currently displayed card number and display the updated card number. The method according to claim 6.

9. receiving an account status signal from the near field communication device of the mobile device; and modifying the visual display of the payment card in response to the account status signal to present at least one of the payment card account balance, a recent transaction amount, an annual percentage rate for an account, a reward points balance, a payment due date, a location-based discount, or a location-based reward. The method according to claim 6.

10. a payment card comprising a payment card near field communication device, a rewritable visual display operable to present a previously issued card number, a processor, and a memory; a reissue application on the mobile device executable by a processor of the mobile device and, when executed, operable to reissue a card number for the payment card; an authentication server operable to communicate with the reissue application; The reissue application, when executed, sending a request to the authentication server to verify that the reissue application is associated with the payment card; in response to verifying that the reissue application is associated with the payment card, obtaining an updated card number that is different from the previously issued card number; generating an updated card number signal including the updated card number and information related to at least one of a card verification value, an expiration date, and an issuer; further operable to output the renewal card number signal; The payment card, receiving the updated card number signal via a near field communication device of the payment card; and operable to drive the rewritable visual display based on the updated card number signal to present an updated card number in place of the previously issued card number. system.

11. The reissue application, when executed, Providing a user interface; receiving input via the user interface; presenting information via the user interface in response to a signal generated by the reissue application; presenting a menu of selectable user preferences via the user interface, where the selectable user preferences in the menu include one or more of a payment card account balance, a recent transaction amount, an account annual percentage rate, a reward points balance, a payment due date, a location-based discount, or a location-based reward; receiving, via the user interface, a selection of at least one selectable user preference from the menu of selectable user preferences; and further operable to store the at least one selected user preference. The system of claim 10.

12. When the reissue application is executed, in response to verifying that the reissue application is associated with the payment card, obtaining information related to the selected at least one of the selectable user preferences, the information being retrieved via the authentication server; generating a user preference display signal including said information related to said selected at least one of said selectable user preferences; and further operable to output the generated user preference display signal to a near field communication device of the payment card. The system of claim 11.

13. The payment card, receiving the user preference display signal output via a near field communication device of the payment card; Processing the user preference display signal; and further operable to transfer the processed user preference display signal to the rewritable visual display for output of the information related to the selected at least one of the selectable user preferences. The system of claim 12.

14. The reissue application, when executed, Providing a user interface; and further operable to provide, via the user interface, an indication of where the payment card is to be placed so as to exchange near field communication signals with a near field communication device of the payment card. The system of claim 10.

15. a payment account server coupled to the data storage device and communicatively coupled to the authentication server; The payment account server, Operable to store payment account information associated with the payment card; The payment account information is at least one of a payment account balance, a payment account limit, information related to the mobile device, user preference selections, transaction information, a payment card number history, a list of undeployed payment card numbers, and information related to users authorized to use the payment card; The system of claim 10.

16. a payment account server connected to a data storage device communicatively connected to the authentication server; The payment account server, retrieving the updated card number from the data storage device in response to a request from the reissue application; and operable to transmit the updated card number to the reissue application. The system of claim 10.

17. The reissue application, Detecting an authentication signal emitted from a near field communication device of the payment card; forwarding the authentication signal to the authentication server; and operable to receive, in response to transmitting the authentication signal, verification that the payment card is a valid payment card associated with the reissue application. The system of claim 10.

18. The rewritable visual display comprises: An electronic ink display, a near field communication device of the payment card; converting the updated card number signal into a voltage value suitable for driving the electronic ink display to replace the previously issued card number with the updated card number; The system of claim 10.

19. the payment card processor; When obtaining the updated card number, the method is operable to generate an updated card number using a cryptographic hash function and data held in memory of the payment card. The system of claim 10.

20. a publisher server communicatively connected to the reissue application; The reissue application, and when obtaining the updated card number, further operable to retrieve the updated card number from an issuer server associated with an issuer of the payment card. The system of claim 10.

Images