A system and method that enables mobile near-field wireless communication to update the display on a 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] This invention relates to a system and method that enable updating of the display on a payment card.

Background Art

[0002] Payment cards such as credit cards, gift cards, and debit cards have become the preferred means of payment in transactions. Transactions involving payment cards are increasing amazingly. Illegal transactions are also increasing amazingly. As a result, the number of payment cards that have to be replaced is also increasing similarly. Once payment cards were inexpensive, but currently, with the requirement for security functions, the cost of payment cards is not negligible. Especially for card-issuing companies, when multiplied by the number of card replacements that occur every year, it becomes a huge burden.

Summary of the Invention

[0003] A method is disclosed that includes the step of transmitting, via a mobile device, a request to update the card number of a reissued payment card. The request may be presented on the display of the payment card and may include a display indicating that the card number encoded on the magnetic strip of the payment card is invalid and unusable. In response to the transmitted request, the mobile device may reissue the card and receive approval to update the card number. In response to the received approval, the updated card number may be obtained from a secure source of the updated card number. In response to a command signal from a reissue application executed on the mobile device, an updated card number signal representing 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 that the update of the card number has been successful is received via a near-field communication circuit in the mobile device.

[0004] Other methods are disclosed, including the payment card's near-field communication device (NFM) transmitting an authentication signal for reception by the mobile device's NFM. The transmitted authentication signal includes the card number currently displayed on the payment card. The transmitted authentication signal may be transmitted after the payment card has been introduced into any portion of the NFM surrounding the mobile device. The transmitted authentication signal may be an approval of a request to change the card number currently displayed on the payment card's visual display. While the payment card remains within any portion of the NFM surrounding the mobile device, the method may include the payment card's NFM receiving an updated card number signal. The updated card number signal may include an updated card number. In response to the reception of the updated card number signal, the card number currently displayed on the payment card's visual display may be replaced with the updated card number.

[0005] An example of a system is disclosed, including a reissue application on a mobile device, an authentication server, and a payment card. The reissue application may be runnable by the mobile device's processor and, when runnable, can operate to reissue the card number of the payment card. The authentication server can operate 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 memory. The rewritable visual display of the payment card may operate to display the previously issued card number. When runnable, the reissue application may operate to send a request to the authentication server to verify that the reissue application is associated with the payment card. In response to verification 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 relating to at least one of the following: card verification value, expiration date, and issuer. The reissue application may output an updated card number signal. The payment card may be operable to receive the updated card number signal via a payment card near-field communication device. Based on the updated card number signal, a rewritable visual display may be driven to display the updated card number instead of the previously issued card number. [Brief explanation of the drawing]

[0006] [Figure 1] This is a block diagram of a system that can operate to reissue payment cards as an example. [Figure 2] Figure 1 shows an example of a contactless card suitable for use in the system example. [Figure 3A] Figure 2 is a block diagram showing an example of the components of a contactless card. [Figure 3B] To modify the rewritable visual display of the payment card example described with reference to Figures 2 and 3A, an example of a device that supplies power to the payment card is shown. [Figure 4] Figure 1 shows a flowchart illustrating an example of processing performed by a mobile device in a system like the one shown. [Figure 5] This flowchart shows an example of a process performed by one or more components of the system example in Figure 1. [Figure 6] This shows a computer architecture suitable for implementing one or more components of the system example in Figure 1. [Modes for carrying out the invention]

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

[0008] Various examples describe a system and method that enables updating the card number of a payment card and thereby reissuing the payment card using a mobile device associated with the payment card. The mobile device hosts a reissuance application, which is a mobile computer application running on the mobile device's processor and capable of communicating with a service provider that manages the payment card. The payment card includes processing circuitry and a rewritable visual display. Using cryptographic techniques, the mobile device and the payment card are authenticated by the service provider. Once authenticated, the updated card number is obtained from a secure source and provided to the payment card via near-field communication by the mobile device. In response to the updated payment card number received from the mobile device, the rewritable visual display on the payment card is updated with the updated card number. Other information may also be displayed on the rewritable visual display of the payment card based on user preference. The advantages of the disclosed embodiments include mobile reissuance of payment cards, reduced waiting time for receiving updated card numbers, improved security based on security features in both the mobile device and the payment card, and other advantages that may become apparent upon consideration of the disclosed embodiments.

[0009] In the described example, the payment card may be a credit card-dimension contactless card including an embedded integrated circuit, a memory device, and an interface that enables 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 example is described in U.S. Patent Application No. 16 / 205,119, filed November 29, 2018, by Osborn et al., titled “Systems and Methods for Cryptographic Authentication of Contactless Cards,” which is incorporated herein by reference in its entirety (hereinafter, Application 119).

[0010] Figure 1 is a block diagram of a system capable of reissuing a payment card according to one embodiment. The 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 payment account server 103, an application server 106, a service provider network 107, and a data storage device 101 coupled to the authentication server 150. The service provider 105 may, for example, be a business that provides computer-based services to clients via network 115. The combination of software and hardware that provides a particular service of the service provider to a 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 shown in Figure 1, the service provider 105 is depicted as including an application server 106 and an authentication server 150. Although each server is depicted as a separate device, it is understood that applications and servers may be distributed across the entire enterprise, or, in the case of distributed resources such as “cloud” resources, they may be distributed across the entire service provider network 107. The application server 106 may support one or more application services provided by the service provider 105, for example, an account management service. The authentication server 150 may, in one embodiment, be capable of providing either or both first-factor authentication and second-factor authentication using contactless cards, as will be disclosed in more detail below.

[0013] The data storage device 109 comprises data storage resources that can be used to store customer accounts, credentials, and other authentication information, including dynamic password data, for use by, for example, the application server 106 and the authentication server 150. The data storage device 109 may consist of combined data resources 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 communication network or the like, which 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 storage device 101 and may be communicably 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 related to other payment cards (not shown) as well as payment card 110 in the data storage device 101. For example, the payment account information 102 may include at least one of the following: payment account balance, payment account limit, information related to mobile device 120, user preference information such as user preference selection, transaction information, payment card number history, list of undeployed payment card numbers, information related to users authorized to use payment card 110, etc.

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

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

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

[0018] For example, the authentication server 150 may be configured to authenticate transactions using payment cards, as well as operations related to payment cards, such as the reissuance of payment card numbers and the updating of account information. For instance, the authentication server 150 may be configured to store information related to the service provider 105's clients, including a client information table (not shown). This information may be stored in a data storage device 101 and accessible to the payment account server 103. Such information may include, but is not limited to, the client's username, client's encryption key, and counters.

[0019] The mobile device 120 may include a mobile device processor 124, a memory 122 for storing the reissue application 127, a transceiver (XCVRS) 187, and a near-field communication (NFC) device 125. The mobile device 120 may optionally include a security element 185 that is operable to store the updated card number 129. The reissue application 127 hosts a signal generation component 121. In this example, the reissue application 127 may be operable when run by the mobile device processor 124 to cause the mobile device processor 124 to present a user interface 126 on the mobile device display 128 that provides information related to the payment card 110, including information that associates the payment card 110 with the reissue application 127 on the mobile device 120, and the reissue application may be able to respond to user input to the user interface 126.

[0020] More specifically, the reissue application 127 may allow the user to manage their payment account, including setting authorized users, setting spending limits, setting and responding to purchase confirmation notifications, and requesting the reissue of payment card numbers, which are maintained by the payment account server 103 in the data storage 101. For example, the reissue application 127 may be associated with the payment card 110 in the authentication server 150. The reissue application 127 may be provided, for example, by a service provider 105, and may be capable of linking to different services and servers, such as the application server 106 and the authentication server 150, as well as communicating 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 user interface 126 and mobile device display 128. Mobile device 120 may be a touch screen display suitable for providing user interface 126, which is operable to display information in response to signals generated by, for example, reissue application 127 executed on mobile device 120 processor. Mobile device 120 may further include mobile device display 128. Mobile device display 128 may be operable to display user interface 126, which presents information in response to signals generated by reissue application 127 executed on mobile device 120 processor.

[0022] Mobile device processor 124 may be operable to present, for example, via reissue application 127, via user interface 126 on mobile device display 128, an arrangement display of where to place the payment card with respect to mobile device 120. The arrangement instruction may indicate the arrangement of payment card 110 with respect to mobile device 120 where a near-field communication signal can be exchanged between mobile device short-range wireless communication device 125 and payment card short-range wireless communication device. The indicated arrangement may, for example, align the electric fields of the respective short-range wireless communication devices of mobile device 120 and payment card 110 for maximum near signal strength. The user preference display signal generation instruction may be information communicated between mobile device 120 and payment card 110. The user preference display signal generation instruction may be generated by signal generation component 121 based on, for example, information related to the selected user preference and output to payment card 110 as a user preference signal display by NFC device 125.

[0023] The signal generation component 121 may be hardware, software, firmware, or a combination thereof, capable of generating signals in response to instructions from a reissue application 127 running 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, for example, a transceiver 187 or a component of the mobile device 120 associated with the mobile device processor 124, which is utilized by the reissue application 127.

[0024] In some examples, the signal generation component 121 may be coupled to the mobile device processor 124 or may be part of the mobile device processor 124. In one example, the mobile device processor 124 may output a user preference display signal generation command to the signal generation component 121. The user preference display signal generation command 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 display signal in accordance with the user preference display signal generation instruction. The user preference display signal may include, for example, information related to at least one of the selected 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 display signal generation command for output as the user preference display signal. In one example, the signal generation component 121 receives an instruction from the mobile device processor 124 to generate a signal for output to a payment card or another device such as the issuer server 108 or an entity such as the service provider 105. When transmitting the instruction to the issuer server 108 or the service provider 105, the instruction may be output to each transceiver of the transceiver 187 for output by the mobile device 120 via the data network 130. The generated user preference display signal may be transferred to the mobile device short-range wireless communication device 125 for output from the mobile device 120.

[0025] In one example, the mobile device 120 may be capable of detecting an authentication signal transmitted from the payment card short-range wireless communication device 115 via the mobile device short-range wireless communication device 125. The authentication signal may be forwarded to the authentication server 150, and in response to forwarding the authentication signal, the mobile device 120 may receive verification or authentication that the payment card 110 is a valid payment card with an authenticated association with the mobile device 120. For example, as a result of the verification or authentication, the service provider indicates that the payment card 110 is valid for use in a transaction and that the association between the mobile device 120 and the payment card 110 has been verified and authenticated.

[0026] The mobile device 120 may include a security element 185. In some examples, the mobile device processor 124 may be operable to retrieve the updated card number 129 from the security element 185 of the mobile device when obtaining the updated card number 129. The mobile device processor 124 may report the updated card number of the payment card 110 to the issuer server 108 associated with the issuer of the payment card. In response to reporting the updated payment, the updated card number may be removed from the security element 185 of the mobile device 120.

[0027] The payment card 110 may be operable to receive a user preference indicator signal output by the NFC device of the mobile device 120 via the payment card NFC device 115. The user preference indicator signal may be processed by the microprocessor 112 of the payment card 110. The processed user preference indicator signal may be forwarded to the display driver 633 and the rewritable visual display 113 to output the updated card number. The payment card NFC 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 the card number, presented on the display with new text and / or graphics, such as the updated card number. The 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 memory 116. The rewritable visual display 113 of the payment card 110 may be coupled to a display driver 633 that can operate to display the card number. The rewritable visual display 113 may be, for example, an e-ink display. The memory 116 may store an applet 117 and other information 119. The applet 117 may include an instance of a reissue application, such as a reissue application 127, which may be obtained from the application server 106 of the service provider 105. In one example, the memory 116 may include a security element (not shown) within the other information 119. In some examples, the payment card processor 112 may be operable to obtain an updated card number 129 from the security element. The counter 114 may count the number of times the payment card 110 has been used in a transaction, etc.The count of counter 114 does not need to be shared outside the card, which makes it more difficult for eavesdropping devices to determine the count of counter 114. For more details on applet 117 and other information 119, please refer to the examples in Figures 2-5.

[0028] The payment card 110 may be a contactless card that communicates wirelessly with the mobile device 120, for example, via Near Field Communication (NFC). Through NFC interaction between the payment card 110 and the mobile device 120, the payment card 110 may harvest energy (more detailed with reference to the example in Figure 3B) from the NFC signal of the mobile device to perform functions as described herein. For example, the payment card 110 may include one or more chips, such as a radio frequency identification chip, that are operable to communicate via NFC or other short-range protocols. In other examples, the payment card 110 may communicate with the 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 mobile phone, a laptop, and / or a tablet. The payment card 110 may be operable to communicate with the mobile device 120 via NFC when the payment card 110 is within range of each mobile device. As will be described in more detail below, the payment card 110 may include username, encryption key, and counter information from a counter 114 that can be transformed using an encryption algorithm to generate a ciphergram containing a dynamic password that a service provider can use to authenticate a mobile device.

[0029] The system 100 may also include an issuer server 108. The issuer server 108 may be associated with the 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 a service provider 105 and a mobile device 120. The 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 the updated card number 129. The mobile device processor 124, via a reissue application (app) 127, may enable the mobile device 120 to retrieve the updated card number from the issuer server 108.

[0030] For more details on the operational examples, please refer to the examples in Figures 4 and 5. However, at this point, it is useful to briefly describe an operational example illustrating the interaction of each component of system 100 with reference to Figure 1. In this embodiment, the mobile device 120 may be operable to send a request to the authentication server 150 transmitted via the data network 130 by the reissue application 127. This 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 the verification 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 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 a data storage device 101. In one example, the updated card number 129 may be stored together with payment account information 102. The payment account information 102 may include information relating to each payment card account managed and provided by the service provider 105. Alternatively, the issuer server 108 may store a number of unused or unassigned payment card numbers that can be used as updated card numbers 129.

[0031] In this embodiment, the updated card number 129 is different from the card number displayed on the payment card 110 before the updated card number was issued. 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 relevant information such as the cryptographic key, authenticated username, card verification value, expiration date, and issuer name. In another example, the updated card number signal may not include the updated card number, but instead indicate 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, which can be used, for example, by the authentication server 150 to further confirm or verify that the payment card 110 is genuine, valid, or associated with a user who also possesses the mobile device 120. The updated card number signal may be output via the mobile device's near-field communication device 125. In this embodiment, the payment card 110 may be operable to receive an updated card number signal output by the mobile device short-range wireless communication device 125 via the payment card short-range wireless communication device 115. In response to receiving the updated card number signal, the microprocessor 112 may be operable to process the updated card number signal, and based on the updated card number signal, the rewritable visual display 113 may be driven (by the display driver 633) to present the updated card number in place of the displayed card number.

[0032] The payment card 110 may include numerous components, as shown in Figure 1, but a more detailed description of an example of a payment card will be given with reference to Figures 2 and 3A-B.

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

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

[0035] The rewritable visual display 207 may be an electronic ink display that responds to drive signals to set the state of the display, and in response to the removal of the drive signals, the electronic ink display rests in the state set by the last applied drive signal. For example, an example of a payment card number currently displayed or previously assigned may be "1234 5678 1234 5678" as shown on the rewritable visual display 207. The payment card 200 may include a magnetic strip or tape, which may be located on the back of the card (not shown). As illustrated in the following example, 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 the updated card number substantially simultaneously with the provision of the electronic ink display of the updated card number for use in future transactions.

[0037] The 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. The user identification information 215 (referred to as “cardholder name”) may be the user’s name or nickname. The contact pad 220 may be operable to establish contact with another communication device, such as a mobile device, smartphone, laptop, desktop, or tablet computer. The payment card 200 may also include processing circuits, antennas, and other components as shown in other examples. These components may be located behind the contact pad 220 or elsewhere on the circuit board 210.

[0038] As described above, the payment card 200 may be built on a software platform capable of operating on smart cards such as JavaCard, which consist of program code, processing power, and memory. In some examples, an applet like 117 in Figure 1 may be added to the contactless payment card to not only generate a request to reissue the card number, but also to provide other services such as issuing one-time passwords (OTPs) for multi-factor authentication (MFA) in various mobile application-based use cases. Thus, the functionality of the contactless payment card enables communication with a mobile device for reissuing the payment card number, as described below with reference to Figure 3A-5.

[0039] Figure 3A is a block diagram showing in more detail an example of the components of the contactless payment card shown in Figure 2.

[0040] As shown in Figure 3A, below (and coupled to) the contact pad 320, there may be a processing circuit 325 for processing and storing information, and one or more antennas 355. In addition to logic circuits and the like, it is understood that the processing circuit 325 may include additional components necessary to perform the functions described herein, such as a processor, memory, error and parity / CRC checker, data encoder, anti-collision algorithm, controller, command decoder, security primitive, tamper-proof hardware, etc.

[0041] One or more antennas 355 may be located inside the payment card and contact pad 320, and around the processing circuit of the contact pad 320. For example, one or more antennas 355 may be integrated with the processing circuit 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 outside the contact pad 320 and the processing circuit. Also, one or more antennas 355 may provide the inductance necessary to harvest power to drive, for example, the processing circuit 325, memory 335, the rewritable visual display 207 in Figure 2, etc. The processing circuit 325 may include a power management unit (not shown) capable of managing the power and storage of the payment card 200.

[0042] In an example of energy harvesting, Figure 3B shows an example of a device 360 ​​that supplies power to a payment card to change the rewritable visual display of the payment card example, as described with reference to Figures 2 and 3A-B. In the device 360 ​​of the example in Figure 3B, antenna 362 may be an NFC-compatible antenna configured to receive NFC signals. In the example in Figure 3B, antenna 362 may be operable to provide both communication and the inductance required for power harvesting. As described above, antenna 362 may be coupled to a communication interface (shown in the example in Figure 3A) that provides signals to processing circuits for signal processing (as described with reference to Figure 3A). For example, the power captured by antenna 362 may be obtained from, for example, a 13.56 MHz NFC signal that generates an alternating current within antenna 362. Of course, radio frequency signals of a different frequency than 13.56 MHz may be used. A matching circuit 363 may be part of antenna 362 and match to the incident magnetic field to obtain the maximum inductance. In this embodiment, the inductive-capacitive (LC) filter 364 may function as a low-pass filter to remove high-frequency components unnecessary for communication from the received signal. The communication output by the processing circuit is shown in Figure 3A.

[0043] The energy of the induced current and induced voltage is recovered by the energy harvesting component 361. The induced voltage may be approximately 0.1 volts (V). The voltage may be supplied to the power management unit 365 for rectification, smoothing, and other processing, or it may be distributed to other components such as a display driver 333 or NFC circuit 368, which may be controlled by a microprocessor (as shown in other embodiments). In this example, the induced voltage can 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 an increased number of coil turns or an increased permanent magnetic field. If the payment card is not reissued because power is only needed when the e-ink display is replaced, the payment card may harvest energy while in use with the NFC device and store the harvested energy in an energy storage device 367, which may be a battery, capacitor, supercapacitor, etc., to store power for future display replacements. In further examples, the power management unit 365 may include intermediate energy storage devices, such as capacitors, to smooth the voltage provided by the energy harvesting component 361.

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

[0045] Returning to the example in Figure 3A, memory 335 may be read-only memory, write-once read-multiple memory, or read / write memory, such as RAM, ROM, and EEPROM, and processing circuit 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 provides 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 also 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 identifiers 350. One or more applets 340 may be one or more software applications associated with one or more service provider applications (e.g., provided by service provider 105 in Figure 1) and operable to run on one or more payment cards, for example, an applet for a Java card. For example, an applet in applet 340 may be operable to respond to one or more requests, such as a Near Field Communication (NFC) reader's Near Field Data Exchange (NDEF) request, and generate an NDEF message consisting of a cryptographically secure OTP encoded as an NDEF text tag. In one example, each applet may store the username of a user associated with the payment card account for accessing the associated service provider application. In some examples, the counter 345, which is 1 or greater, may have a numerical counter sufficient to store an integer representing the number of times the payment card 200 has been used.

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

[0048] For example, referring to Figures 1 and 3, memory 335 may contain information for username 342, encryption key 343, and counter 345, which is used to generate an encryption key containing a dynamic password, which can be used by the service provider's authentication server 150 in Figure 1 to authenticate payment card 110, mobile device 120, user (not shown), or all three, using, for example, an encryption algorithm, and which is then translated by the microprocessor 330. For example, the microprocessor 330 may, in the cryptographic processing functions provided by the microprocessor 330, use values ​​from one of the payment card account identifier 350, encryption key 343, and counter 345, along with the username, to generate an encryption key containing a dynamic password, which can be used to authenticate the reissuance of payment card 110 and the provision of an updated card number 129 to payment card 110 via mobile device 120. In one example, the dynamic password is related to counter 345. In such an example, the dynamic password thus advantageously reflects the previous actions of the holder of payment card 110. For example, a counter-based dynamic password can reflect the number of times a user has used a payment card 110 to obtain a specific service from a service provider 105 (e.g., advance payment, transaction authorization), which is a knowledge element 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 the secure memory of the payment card as the value of a counter 345, and the value of the counter may be incremented each time the payment card is used for a transaction.

[0049] The microprocessor 330 and memory 335 elements in the exemplary embodiments described above have been described with reference to the contact pad 320, but the disclosure is not limited thereto. It is understood that these elements may be mounted outside the contact pad 320, or completely separately from the contact pad 320, or as additional elements in addition to the microprocessor 330 and memory 335 elements located within the contact pad 320.

[0050] Returning to Figures 2 and 3A-B, in some examples, the payment card 200 may include one or more antennas 355 positioned around the processing circuit 325 of the contact pad 320. For example, one or more antennas may be integrated with the processing circuit 325, or one or more antennas 355 may be used with an external booster coil. In another example, one or more antennas 355 may be outside the contact pad 320 and the processing circuit 325. As an example, one or more antennas 355 may extend around the area of ​​the card to enhance the power transfer characteristics of the antennas when placed in an electric field such as the 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, which is capable of communicating with a mobile device such as 120 in Figure 1, in accordance with ISO / IEC 14443, via one or more short-range wireless communication protocols such as Near Field Communication (NFC), Europay, Mastercard, Visa (EMV) standards. In some examples, the RFID chip 338 may also be called a payment card near-field communication device, such as 115 in Figure 1. Although NFC is used as an exemplary communication protocol, this 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, such as those shown in the example in Figure 3A.

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

[0053] For example, in reissuing payment card numbers, a passwordless authentication protocol may be used, which practically applies a contactless payment card cryptographic exchange protocol as a first-factor authentication mechanism to facilitate access to application services without sacrificing the security of those services.

[0054] The cryptographic exchange protocol for payment cards 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 using either the applet 340, the counter value from counter 345, the key value from cryptographic key 343, and the microprocessor 330.

[0055] To ensure valid authentication of payment accounts, mobile devices, and payment cards, these three are typically linked together by associating their digital authentication information with each other.

[0056] For example, a payment card may be registered with service provider 105 in order to receive a reissue request service. As part of the registration, a username such as 342 may be stored in a data storage device 109 connected to authentication server 150. In some examples, the username may be automatically generated by service provider 105, unknown to the mobile device, and loaded into both a user information table (not shown) stored in data storage device 109 and an applet 340 downloaded to payment card 110. As an example, a payment card is associated with a user and the user's payment account, which is maintained by payment account server 103 and stored in data storage device 101. The payment card number (e.g., 1234 5678), user information, and the user's payment account information (i.e., account number or other identifier) ​​may be maintained and stored by service provider 105 via payment account server 103. Payment account information 102 also includes information about the mobile device, payment card, and user payment account associated with the user. For example, payment account information 102 may include information about the mobile device 120, such as a unique identifier associated with the mobile device (e.g., a phone number, MEID (Mobile Equipment Identifier), IMEI (International Mobile Equipment Identity), IMSI (International Mobile Subscriber Identity), serial number, MAC (Media Access Control) address, and / or similar), application information related to the application used to capture the image (e.g., an identifier for the application instance, the application version, and / or similar), and / or similar.Once a payment card is registered with service provider 105 and bound to a mobile device, application authentication using the payment card's cryptographic algorithm is performed, enabling authentication of the payment card, mobile device, and user, which may allow for the reissuance of the payment card via a reissue application. Examples of cryptographic algorithms suitable for use in the disclosed examples include 3DES (Triple Data Encryption Algorithm), AES (Advanced Encryption Standard), 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 processes to be performed securely, thereby reducing concerns for service providers and users of payment accounts that malicious actors could fraudulently compromise payment cards as described herein.

[0057] Figure 4 is a flowchart illustrating an example of a process performed by a mobile device used in a system such as the one shown in Figure 1. In one example, an e-ink display-enabled card is compromised (e.g., a fraudulent transaction is made using the payment card number), and the payment card needs to be reissued. Instead of replacing the payment card (110 in Figure 1 or 200 in Figure 2), the payment card in the disclosed embodiment may allow the payment card number to be changed. In the embodiment, the payment card may be placed within the field of an NFC-enabled mobile phone (e.g., "tap to phone"), providing information to authenticate the payment card. Based on the authentication of the card and the mobile device, the mobile device can operate to pass new information such as the card number, card verification value (CVV), expiration date, and service provider / issuer (e.g., VISA or MASTERCARD), all or part 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 static.

[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 a display indicating that the card number displayed on the payment card and / or the card number encoded on the payment card's magnetic strip is invalid and unusable to complete a transaction (e.g., the purchase of goods or services). A payment card number may become invalid and unusable due to a breach of the payment card number, such as identity theft or user negligence. In some examples, an authentication message may be generated by a reissue application, such as 127 in Figure 1, running on the mobile device before sending an authorization request to reissue the payment card. The authentication message may include, for example, information related to the mobile device stored by a service provider's authentication server. The authentication message may be included in the request along with the display.

[0059] In response to a transmitted request, the mobile device 120 may receive authentication to reissue a payment card and update the card number (420). For example, the mobile device 120 may receive authentication to reissue a payment card and update the card number based on the authentication message included in the request. For example, the authentication message included in the request may contain information to be processed by the authentication server 150, such as an encrypted message. An authentication status message may be sent 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 send 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 payment card's magnetic strip does not need to be updated. In response to received authentication, the updated card number may be retrieved from a secure source of the updated card number (430). In this embodiment, the mobile device may obtain the updated card number by retrieving it from the security element of the mobile device. Upon retrieving the updated card number from the security element, the mobile device may report the updated card number of the payment card to, for example, an issuer server associated with the payment card issuer or a financial institution associated with the payment card. The mobile device may remove the updated card number from the security element or take any other action to prevent the updated card number from being inadvertently reused. As shown in Figure 1, the updated card number (CN) 129 may be stored in various locations and retrieved by the mobile device 120 in response to requests and authentication from each source. For example, the secure source of the updated card number may be one or more different sources, such as a secure element within the mobile device, a secure element within the payment card, a source within the service provider, a source within the payment card issuer, or another secure source. Instead of obtaining the updated card number from the secure element of the mobile device, the mobile device may obtain the updated card number from an issuer server associated with the payment card issuer, such as an issuer server like 108 in Figure 1, when obtaining the updated card number from a secure source of the updated card number. In another example, the updated card number may be generated by the mobile device's reissue application 127 using a cryptographic hash function based on data obtained from the payment card 110 in Figure 1. 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 held in the payment card's memory, such as data from a counter 114.In the embodiment, a cryptographic hash function or other function may be a secure source of the updated card number, using various cryptographic and other security techniques. Once the payment card 110 in Figure 1 generates the updated card number, the authentication server 150 in Figure 1 may be used to authenticate the payment card 110 via the mobile device 120. Once authenticated, the payment card 110 itself may generate the updated card number.

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

[0062] In response to a command signal from a signal generation component running 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 embedded 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). For example, the payment card may receive an authentication signal from the mobile device 120 via the payment card near-field communication device. A logic circuit on the payment device may verify that the mobile device 120 is associated with the payment card, for example, using an encryption key.

[0063] The payment card may use energy from the updated card number signal to power the microprocessor and respond to the received signal. For example, in 460, in response to receiving the updated card number signal and harvesting energy from the received signal, the visual display on the payment card may change to show the updated card number. In the example of a payment card with a rewritable magnetic strip, the payment card's microprocessor may be operable to rewrite the rewritable magnetic strip with the updated card number. Conversely, in the example where the payment card does not have a rewritable magnetic strip, the updated card number is different from the card number represented on the magnetic strip of the reissued payment card. Furthermore, 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 the point-of-sale device with information related to that value. Alternatively, the updated card number itself may indicate that the magnetic strip is invalid, or the authentication server may be configured to provide a display to the point of sale indicating that the magnetic strip is invalid and unusable.

[0064] In another example, the updated card number may be a temporary payment card number, such as a temporary virtual number usable for a single transaction or for a specified period. The temporary virtual number may be displayed for a limited time, such as during a single transaction or for a specified period. In yet another example, a rewritable visual display may be used to display a one-time use “token,” a temporary virtual number, or a dynamic credit card number. These are provided by either an application server or an authentication server and transmitted to the payment card via NFC or similar on a mobile device. A indication may be made that the token, temporary virtual number, or dynamic credit card number is not the 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, enhance 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 user 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, the signal generation component of the mobile device may modify signal parameters for rewriting a rewritable visual display according to the selected account display preference. The modified signal parameters may be used to send a user preference display signal to the payment card. The transmitted user preference display signal causes one or more pieces of information to be displayed on the payment card's visual display, including the last transaction amount, total reward amount, account balance, account limit, or warnings related to the account balance. Of course, other information may also be provided. The displayed information may be obtained from the service provider 105, for example, from a payment account server 103 or an application server 106.

[0066] A payment card, such as 110 in Figure 1, may be operable to perform a process for card authentication in order to receive an updated card number. Figure 5 is a flowchart of an example of a process 500 performed by the payment card in the system example of Figure 1. In the embodiment, at 510, the payment card processor may generate an authentication signal that includes the payment card number currently displayed on the payment card's visual display. In the embodiment, the payment card's near-field communication device may transmit the generated authentication signal for reception by the mobile device's near-field communication device. In this embodiment, 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 has been introduced into any part of the near-field communication field surrounding the mobile device. The transmitted authentication signal may approve a request to change or reissue the card number currently displayed on the payment card's visual display. In this embodiment, the payment card may store in a memory device within the payment card an indication that the card number encoded on the payment card's magnetic strip is invalid and unavailable.

[0067] While the payment card remains within any portion of the near-field wireless communication field surrounding the mobile device, the payment card's near-field wireless communication device 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 contain only the updated card number. In another example, the updated card number signal received from the mobile device may contain, in addition to the updated card number, other information such as information based on user-selected preferences.

[0068] In certain cases, the updated card number signal may be related to the provisioning of an EMV (Europay, Mastercard, Visa) profile. For example, an 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 they may be transmitted with a backup "profile" enabled. The backup profile is, for example, an EMV-compliant, inactive full set of data on the payment card's chip, which may be the primary payment card number (i.e., the payment card number authorized to be used for transactions). Once each updated payment card number is enabled, the payment card may display the updated payment card number as the new primary account number (PAN).

[0069] In response to receiving an updated card number signal, the card number currently displayed on the payment card's visual display may be replaced with the updated card number (530). For example, a processor or logic circuit on the payment card may generate a display drive signal to drive the payment card's visual display in order to change the currently displayed card number in response to receiving an updated card number signal from the payment card's near-field communication device.

[0070] Additionally, the payment card may receive an account status signal via a near-field communication device of a mobile device. In response to the account status signal, the payment card's visual display may be modified to show at least one of the following: the payment card's account balance, the most recent transaction amount, the account's annual interest rate, the reward points balance, the due date, location-based discounts, or location-based rewards.

[0071] Process 500 may further include selecting an account display preference to modify the information displayed on the payment card. For example, a signal generation component under the 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 before sending a signal representing the updated card number. The display preference signal may cause the e-ink display of the payment card to show one or more of the following: the last transaction amount, the total rewards amount, the account balance, the account limit, or a warning about the account balance.

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

[0073] In the example, the selectable user preferences in the menu may include one or more of the following: payment card account balance, most recent transaction amount, account annual interest rate, reward points balance, payment due date, location-based discounts, or location-based rewards. At least one selection of the selectable user preferences may be received by the mobile device 120 through at least one input device (such as a touchscreen, button, or keypad). 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 further operate via the reissue application 127 to retrieve information related to at least one selected user preference in response to verification that the mobile device 120 is associated with the payment card 110. Information related to at least one of the selectable user preferences may be stored in memory 122, for example, in other element 189, or retrieved via the authentication server 150, payment account server 103, or application server 106. Memory 122 may also be operable to store user-related numbers, information related to users authorized to use payment cards, and so on.

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

[0075] In response to an account status signal, the payment card's visual display may be modified to show at least one of the following: the payment card's account balance, the most recent transaction amount, the account's annual interest rate, the reward points balance, the due date, location-based discounts, or location-based rewards (550). In some examples, prior transaction information may be stored in memory as shown in 335 of Figure 3A. When the payment card is placed in a near-field wireless communication field, the payment card may harvest energy to display some of the prior transaction information.

[0076] In another example, a rewritable visual display could be used to show a one-time-use "token" or a dynamic credit card number. These are provided by a server and sent to the card via NFC. There would likely be some indication that it is not the primary account number.

[0077] In addition to reissuing payment card numbers for use in future transactions, the card type may be changed by controlling a rewritable visual display. For example, a payment card can be completely changed to another type of card, such as a prescription card, authentication card, or debit card. Of course, to provide such a change of card type, a service provider like 105 in Figure 1 may access or provide the respective services associated with prescription cards, authentication cards, debit cards, etc.

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

[0079] Computing architecture 600 includes a variety of common computing elements, such as one or more processors, multicore processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input / output (I / O) components, and power supplies. However, this embodiment is not limited to implementation using computing architecture 600.

[0080] As shown in Figure 6, the computing architecture 600 includes a processing unit 604, system memory 606, and a system bus 608. The processing unit 604 can be one or more of various commercially available processors.

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

[0082] Computing architecture 600 may include or implement various products. These products may include computer-readable storage media for storing logic. Examples of computer-readable storage media may include any tangible media capable of storing electronic data, such as volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, and writable or rewritable memory. Examples of logic may include executable computer program instructions implemented using any appropriate type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, and visual code. They may also be implemented, at least partially, as instructions contained in or on non-temporary computer-readable media embodied in programming code that can be read and executed by one or more processors to enable the execution of the operational examples 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), EEPROM (Electrically Erasable Programmable ROM), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase-change or ferroelectric memory, SONOS (Silicon-Oxide-Nitrid-Oxide-Silicon) memory, magnetic or optical cards, device arrays such as RAID (Redundant Array of Independent Disks) drives, solid-state memory devices (e.g., USB memory), SSDs (Solid State Drives), and any kind of storage medium suitable for storing information. In the exemplary embodiment shown in Figure 6, the system memory 606 may include non-volatile memory 610 and / or volatile memory 612. The BIOS (Basic Input / Output System) can be stored in the non-volatile memory 610.

[0084] 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 for reading from or writing to a removable magnetic disk 618, and an optical disk drive 620 for reading from or writing 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 HDD interface 624, FDD interface 626, and optical drive interface 628, respectively. The HDD interface 624 for external drive implementation may include at least one or both of the Universal Serial Bus (USB) and IEEE 1394 interface technologies.

[0085] The drives and associated computer-readable media provide volatile and / or non-volatile storage devices such as data, data structures, and computer-executable instructions. For example, a number of computer program modules, including an operating system 630, one or more application programs 632, other program modules 634, and program data 636, can be stored in the drives and memories 610, 612. In one example, the one or more application programs 632, other program modules 634, and program data 636 could include, for example, various applications and / or components of a 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 enable data input and output to the user. For example, the user may input commands and information to the computer 602 via one or more wired / wireless optional input devices, such as a keypad 638 and a tactile input device such as a touchscreen 640. Other input devices may include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, a gamepad, a stylus pen, a near-field communication device, a dongle, a fingerprint reader, a glove, a graphics tablet, a joystick, a keyboard, a retina reader, a touchscreen (e.g., capacitive, resistive, etc.), a trackball, a trackpad, 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 via other interfaces such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, or an IR interface.

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

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

[0089] When used in a LAN networking environment, computer 602 may be connected to LAN 652 via a wired and / or wireless network interface or adapter 656. Adapter 656 can facilitate wired and / or wireless communication to LAN 652 and may include a wireless access point placed on it to communicate with the wireless capabilities of adapter 656.

[0090] When used in a WAN networking environment, computer 602 may include a modem 658, or be connected to a communication server on WAN 654, or have other means for establishing communication on WAN 654, such as via the Internet. The modem 658, which may be internal or external and may be wired and / or wireless, connects to the system bus 608 via interface 642. In a network environment, program modules, or parts thereof, written in relation to computer 602 may be stored in remote memory / storage 659. The network connections shown are illustrative, and it is understood that other means can be used to establish communication links between computers.

[0091] Computer 602 is capable of communicating with wired and wireless devices or entities using the IEEE 802 standard family, such as wireless devices configured to operate wirelessly (e.g., IEEE 802.11 wireless modulation technology). This includes, among other things, wireless technologies such as Wi-Fi (or Wireless Fidelity), WiMAX, and Bluetooth®. Thus, communication may be a predefined structure, like a conventional network, or it may be simply ad-hoc communication between at least two devices. Wi-Fi networks provide secure, reliable, and high-speed wireless connectivity using wireless technologies called IEEE 802.11x (a, b, g, n, etc.). Wi-Fi networks can be used to connect computers to each other, to the Internet, and to wired networks (those using IEEE 802.3 related media and functions). Wireless technology can be connected to the computer 602 via one or more transceivers (not shown) in optional interface 642 or communication interface 656, which facilitates the use of wireless technologies such as Wi-Fi, WiMax, and Bluetooth, as well as others.

[0092] The various elements of the device, as previously described with reference to Figures 1-6, may include various hardware elements, software elements, or combinations of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processors, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, ASICs (Application Specific Integrated Circuits), PLDs (Programmable Logic Devices), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), 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 programming 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 the example using hardware and / or software elements may vary depending on any number of factors desired for a given implementation, such as the desired computation speed, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints.

[0093] As used in this Application, the terms “system,” “component,” and “unit” are intended to refer to computer-related entities that are either hardware, a combination of hardware and software, software, or running software, 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 (of optical and / or magnetic storage media), an object, an executable, an execution thread, a program, and / or a computer. For example, both an application running on a server and the server itself can be components. One or more components may reside within a process and / or an execution thread, and components may be localized on one computer and / or distributed across two or more computers.

[0094] Furthermore, each component may be coupled to communicate with one another by various types of communication media to coordinate operations. Coordination may include unidirectional or bidirectional information exchange. For example, components may transmit information in the form of signals communicated over a communication medium. Information can be implemented as signals assigned to various signal lines. In such an assignment, each message becomes a signal. However, in further examples, data messages may be employed instead. Such data messages may be transmitted over various connections. Illustrative connections include parallel interfaces, serial interfaces, and bus interfaces.

[0095] Some embodiments may be described using the expression "one embodiment" or its derivatives. These terms mean that a particular feature, structure, or characteristic described in relation to an embodiment is included in at least one embodiment. The expression "in one (embodiment)" appears in various places in this specification, but not all of them necessarily refer to the same example. Furthermore, unless otherwise noted, the features described above are considered to be usable together in any combination. Thus, any features discussed separately may be adopted in combination with each other unless it is pointed out that the features are incompatible with each other.

[0096] Referring generally 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 a network of computers. These procedural descriptions and expressions are used to most effectively convey the nature of the work to those skilled in the art.

[0097] A procedure, process, or method is generally considered here to be a self-consistent set of operations that lead to a desired outcome. These operations require the physical manipulation of physical quantities. While not always the case, these quantities usually take the form of electrical, magnetic, or optical signals that can be stored, transferred, combined, compared, and other manipulated. It can be convenient to refer to these signals as bits, values, elements, symbols, letters, terms, numbers, etc., primarily for reasons of common usage. However, it should be noted that all these terms and similar terms are related to the appropriate physical quantities and are merely convenient labels applied to those quantities.

[0098] Furthermore, the operations performed are often referred to in terms such as addition and comparison, which are generally associated with mental operations performed by human operators. In none of the operations described herein that form part of one or more embodiments is such a capability of a human operator required, nor is it desirable in most cases. Rather, the operations are mechanical operations. Machines useful for performing the operations of various embodiments include general-purpose digital computers or similar devices.

[0099] In some examples, the terms "joined" and "linked" are used, along with their derivatives. These terms are not necessarily intended to be synonymous with each other. For example, some examples may use the terms "connected" and / or "joined" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "joined" can also mean that two or more elements cooperate or interact with each other even if they are not in direct contact.

[0100] Various examples also relate to apparatus or systems for performing these operations. This apparatus may be specifically constructed for the purposes described, or it may consist of a general-purpose computer that is selectively activated or reconfigured by a computer program stored within it. 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 be convenient to construct more specialized apparatus to perform the required method steps. The structures for these various machines will appear in the given description.

[0101] The gist of this disclosure is provided to emphasize that it is intended to allow readers to quickly grasp the nature of the technical disclosure. It is submitted with the understanding that it is not intended to be used to interpret or limit the claims or their meaning. Furthermore, in the preceding detailed description, various features are grouped into a single example in order to streamline the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed example requires more features than those explicitly stated in each claim. Rather, as the following claims demonstrate, the inventive subject matter lies in fewer features than all the features of a single disclosed embodiment. Accordingly, the following claims are incorporated herein into the detailed description, with each claim standing independently as a separate embodiment. In the attached claims, the terms “including” and “in which” are used as plain English equivalents of the terms “comprising” and “wherein,” respectively. Furthermore, terms such as “first,” “second,” and “third” are used merely as labels and are not intended to impose numerical requirements on their subject matter.

[0102] The above description includes examples of the disclosed architecture. Of course, it is impossible to describe all possible combinations of components and / or methodologies, but those skilled in the art will recognize that many more combinations and permutations are possible. Therefore, novel architectures are intended to encompass all such changes, modifications, and variations that fall within the spirit and scope of the attached claims.

Claims

1. A computer execution method performed by a computer, An application running on the processor of a mobile device sends a request to a server to reissue the card number of a contactless card associated with the mobile device, wherein the card number is displayed on the contactless card's display. The application receives authentication of the request from the server, The application receives the updated card number based on the authentication, The application includes transmitting the updated card number to the contactless card. The request includes information associated with the mobile device, The server approves the request based on the determination that the contactless card is associated with information associated with the mobile device. Computer execution method.

2. The aforementioned computer execution method further, The application receives a display indicating that the contactless card has updated its card number with the updated card number. A computer execution method according to claim 1, including the following:

3. The information includes encrypted data, The computer execution method according to claim 1.

4. The aforementioned computer execution method further, Before updating the card number, the application receives verification from the server that the contactless card is a valid card associated with the application. A computer execution method according to claim 1, including the following:

5. The updated card number is provided to the contactless card via near-field communication (NFC). The computer execution method according to claim 1.

6. The application receives an updated card number from either the server or the secure element of the mobile device. The computer execution method according to claim 1.

7. The request further includes an indication that the contactless card is unusable. The computer execution method according to claim 1.

8. A non-temporary computer-readable storage medium, The computer-readable storage medium includes a predetermined instruction that the processor of the mobile device executes when it is executed by the processor of the mobile device, and the instruction is: An application running on the processor sends a request to a server to reissue the card number of the contactless card associated with the mobile device, Receiving the card number displayed on the contactless card's display, The application receives authentication of the request from the server, The application receives the updated card number based on the authentication, The application includes transmitting the updated card number to the contactless card, The request includes information associated with the mobile device, The server approves the request based on the determination that the contactless card is associated with information associated with the mobile device. Computer-readable storage medium.

9. The aforementioned instruction further tells the processor: The application receives a display indicating that the contactless card has updated its card number with the updated card number. A computer-readable storage medium according to claim 8, which allows execution.

10. The information includes encrypted data, The computer-readable storage medium according to claim 8.

11. The updated card number is provided to the contactless card via near-field communication (NFC). The computer-readable storage medium according to claim 8.

12. A computer execution method performed by a computer, An application running on the device's processor sends a request to a server to update the card number of the contactless card associated with the device, A request to update the card number displayed on the contactless card's display, which includes transmitting a request for the contactless card to be reissued. The aforementioned application receives authentication for the request from the server, The application receives the updated card number based on the authentication, The application includes transmitting the updated card number to the contactless card, The request includes information associated with the device, The server approves the request based on the determination that the contactless card is associated with information associated with the device. Computer execution method.

13. The aforementioned computer execution method further, The application receives a display indicating that the contactless card has updated its card number with the updated card number. The computer execution method according to claim 12, including the method described in claim 12.

14. The information includes encrypted data, The computer execution method according to claim 12.

Images