System and method for enabling mobile near field communication to update a display on a payment card

Abstract

A system and method are disclosed that enable updating a payment card's card number and thereby reissuing the payment card with a reissue application associated with the payment card. The reissue application, when executed, communicates with a service provider that manages the payment card. The payment card includes processing circuitry and a rewritable visual display. Using cryptographic techniques, the reissue application and the payment card are authenticated to the service provider. Upon verification, an updated card number is obtained and provided to the payment card via near field communication. In response to the updated payment card number received from the reissue application, the rewritable visual display on the payment card is updated with the updated card number. Other information can also be presented on the rewritable visual display of the payment card based on user preferences.

Description

[0001] Related applications

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

[0003] Payment cards, such as credit cards, gift cards, and debit cards, have become the preferred payment method for transactions. The number of transactions involving payment cards is growing at an alarming rate. The number of fraudulent transactions is also growing at an incredible rate. As a result, the number of payment cards that must be replaced is also increasing. Payment cards may have once been inexpensive items, but due to the security features required today, their cost is not negligible. When multiplied by the numerous card replacements that occur each year, the cost is particularly high for card issuers. Summary of the Invention

[0004] A method is disclosed, comprising the steps of: sending a request via a mobile device for updating the card number on a reissued payment card. The request may include an indication, displayed on the payment card's display and encoded on the payment card's magnetic stripe, that the card number is invalid and unusable. In response to the sent request, the mobile device may receive authorization for reissue of the payment card and updating the card number. In response to the received authorization, 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 running 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 successful card number update may be received via the near-field communication circuit in the mobile device.

[0005] Another method is disclosed that includes transmitting, by a payment card's near field communication device, an authentication signal that is received by a mobile device's near field communication device. The transmitted authentication signal includes a card number currently displayed on the payment card. The transmitted authentication signal can be transmitted after the payment card is introduced into any portion of a near field communication electric field surrounding the mobile device. The transmitted authentication signal can permit 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 near field communication electric field surrounding the mobile device, the method can include receiving, by the payment card's near field communication device, an updated card number signal. The updated card number signal can contain an updated card number. In response to receiving the updated card number signal, the card number currently displayed on the payment card's visual display can be replaced with the updated card number.

[0006] 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 is executable by a processor of the mobile device and, when executed, is operable to reissue a card number of the payment card. The authentication server is operable to communicate with the reissue application. The payment card can 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 is operable to present a previously issued card number. The reissue application, when executed, is operable 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 can 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 can also include information related to at least one of: a card verification value, an expiration date, or an issuer. The reissue application can cause the updated card number signal to be output. The payment card is operable to receive the updated card number signal via the payment card near field communication device. Based on the updated card number signal, the rewritable visual display can be driven to present the updated card number in place of the previously issued card number. BRIEF DESCRIPTION OF DRAWINGS

[0007] Figure 1 is a block diagram of a system operable to reissue a payment card according to an example;

[0008] Figure 2 is an example of a contactless card suitable for use in Figure 1 a system example;

[0009] Figure 3A is a block diagram illustrating components of a contactless card of Figure 2 an example;

[0010] Figure 3B illustrates power supplied to a payment card for use in modifying aFigure 2 and Figure 3A Examples of apparatuses for re-writable visual displays of payment card instances;

[0011] Figure 4 are examples of processes performed by mobile devices used in systems such as Figure 1 are examples of processes performed by mobile devices used in systems such as

[0012] Figure 5 are examples of processes performed by mobile devices used in systems such as Figure 1 are examples of processes performed by mobile devices used in systems such as

[0013] Figure 6 illustrate computer architectures suitable for implementing one or more components of system examples such as Figure 1 DETAILED DESCRIPTION

[0014] Various examples describe a system and method that enables updating of a card number of a payment card and thereby re-issuing the payment card with a mobile device associated with the payment card. The mobile device hosts a re-issuing application that is a mobile computer application executing on a processor of the mobile device that is operable to communicate with a service provider that manages the payment card. The payment card includes processing circuitry and a re-writable visual display. Using cryptographic techniques, the mobile device and the payment card are authenticated to the service provider. Upon verification, an updated card number is obtained from a secure source and provided by the mobile device to the payment card via near field communication. In response to the updated payment card number received from the mobile device, the re-writable visual display on the payment card is updated with the updated card number. Other information can also be presented on the re-writable visual display of the payment card based on user preferences. Benefits of the disclosed examples include: mobile re-issuance of payment cards, reduced wait time for receiving an updated card number, increased security based on security features of both the mobile device and the payment card, and other benefits that can be apparent upon review and consideration of the disclosed examples.

[0015] ​In the described examples, the payment card can be a credit card sized contactless card including an embedded integrated circuit, a storage device, and an interface that allows the card to communicate with a receiving device using a near field communication (NFC) protocol. Examples of contactless cards that can be used in the disclosed examples are described in Osborn et al., U.S. Patent Application Serial No. 16 / 205,119, entitled “Systems and Methods for Cryptographic Authentication of Contactless Cards,” filed November 29, 2018, which is incorporated by reference herein in its entirety (hereinafter the ‘119 application).

[0016] Figure 1 is a block diagram of a system operable to reissue a payment card according to an example. The system 100 can include a service provider 105, a mobile device 120, a data network 130, and a payment card 110.

[0017] The data network 130 can 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 can include a data storage device 101 coupled to a payment account server 103, an application server 106, a service provider network 107, and an authentication server 150. In one example, the service provider 105 can be a company that provides computer-based services to clients over a 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 servers can communicate over a private network of the service provider, often referred to as the service provider network 107. The service provider network 107 can include a wireless network, a wired network, or any combination of wireless and wired networks as described above with respect to the data network 130.

[0018] In Figure 1 the system of the service provider 105 is shown to include an application server 106 and an authentication server 150. While each server is shown as a discrete device, it should be understood that the applications and servers can be distributed throughout the enterprise, or in the case of distributed resources such as “cloud” resources, throughout the service provider network 107. The application server 106 can support one or more application services provided by the service provider 105, such as an account management service. According to one aspect, the authentication server 150 can be operable to provide one or both of first factor authentication and second factor authentication using a contactless card, as disclosed in greater detail below.

[0019] The data storage device 109 includes data storage resources that can be used, for example, to store customer accounts, credentials, and other authentication information, including dynamic password data for use by the application server 106 and the authentication server 150. The data storage device 109 can be comprised of coupled data resources including any combination of local storage, distributed data center storage, or cloud-based storage.

[0020] The service provider network 107 can be a wide area data communication network or the like that enables various components of the service provider 105 to communicate with another component within the service provider 105, as well as the data network 130 outside of the service provider 105. The payment account server 103 can be coupled to the data storage device 101 and communicatively coupled to the data network 130 and the authentication server 150. The payment account server 103 can operate to store payment account information 102 related to the payment card 110 and other payment cards (not shown) in the data storage device 101. For example, the payment account information 102 can include at least one of a payment account balance, a payment account limit, information related to the mobile device 120, user preference information such as user preference selections, transaction information, payment card number history, a list of un-deployed payment card numbers, information related to a user authorized to use the payment card 110, or the like.

[0021] In some examples, the payment account server 103 can operate to store the updated card number 129. For example, in response to a request from the mobile device 120, the payment account server 103 can operate to retrieve the updated card number 129 from the data storage device 101 and transmit the updated card number 129 to the reissue application 127 executing on the mobile device 120.

[0022] The application server 106 can operate to manage the operation and delivery of different applications (i.e., computer applications or programming code) such as the reissue application 127 that can be executed by a processor on a mobile device, server, or another computing device. For example, a user can select an icon, link, or other mechanism provided as part of the reissue application 127 to launch the application on the mobile device 120 for accessing a payment card number reissue service. The application server 106 can maintain user preferences, user names, or similar information in a data storage (not shown) that can be similar to the data storage device 101.

[0023] Authentication server 150 can include hardware and software for performing various authentication processes. Authentication server 150 can be operable to communicate with payment account server 103 and application server 106 within service provider 105. For example, authentication server 150 can provide authentication status regarding a payment card having a card number that is reissued in response to a request from payment account server 103 or application server 106. Additionally, mobile device 120 and data network 130 can be operable to exchange communications between mobile device 120 and authentication server 150.

[0024] In an example, authentication server 150 can be operable to authenticate transactions conducted with a payment card and operations related to a payment card, such as reissuing a payment card number, authenticating account information updates, or the like. For example, authentication server 150 can be operable to store information related to clients of service provider 105, including a client information table (not shown). This information can also be stored in data storage 101 and be accessible to payment account server 103. Such information can include, but is not limited to, a client username, a client password key, and a counter.

[0025] Mobile device 120 can include a mobile device processor 124, a memory 122 storing a reissue application 127, a transceiver (XCVRS) 187, and a near field communication (NFC) device 125. Mobile device 120 can include a secure element 185 that is operable to optionally store an updated card number 129. Reissue application 127 hosts a signal generation component 121. In an example, reissue application 127, when executed by mobile device processor 124, can cause mobile device processor 124 to be operable to cause mobile device display 128 to present 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 enable the reissue application to respond to user input to user interface 126.

[0026] In more detail, the reissue application 127 can enable a user to manage a payment account maintained by the payment account server 103 in the data storage device 101, such as setting authorized users, setting spending limits, setting and responding to purchase verification notifications, requesting reissuance of a payment card number, and the like. In an example, the reissue application 127 can be associated with the payment card 110 at the authentication server 150. The reissue application 127 can be provided, for example, by the service provider 105, and can operate 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 can include a signal generation component 121 that generates signals, such as command signals, for output to other devices, such as the service provider 105, the payment card 110, and the like.

[0027] The mobile device 120 can include at least one input device (shown in later examples) coupled to the user interface 126 and the mobile device display 128. The mobile device 120 can also include the mobile device display 128, which can be, for example, a touch screen display adapted to provide the user interface 126 that is operable to display information in response to signals generated by the reissue application 127 executing on the mobile device 120 processor. The mobile device display 128 can be operable to display the user interface 126 that presents information in response to signals generated by the reissue application 127 executing on the mobile device 120 processor.

[0028] For example, the mobile device processor 124 can operate via the reissue application 127 to present, via the user interface 126, a placement indication on the mobile device display 128 of a position at which the payment card is to be placed with respect to the mobile device 120. The placement indication can indicate a placement of the payment card 110 with respect to the mobile device 120 that enables 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 can, for example, align respective electric fields of the respective near field communication devices of the mobile device 120 and the payment card 110 to obtain near maximum signal strength. The user preference display signal generation instructions can be information communicated between the mobile device 120 and the payment card 110. The user preference display signal generation instructions can be generated by the signal generation component 121 as a signal, for example, based on information related to the selected user preference; and can be output as a user preference signal display by the NFC device 125 to the payment card 110.

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

[0030] In some examples, the signal generation component 121 can be coupled to or part of the mobile device processor 124. In examples, the mobile device processor 124 can output user preference display signal generation instructions to the signal generation component 121. The user preference display signal generation instructions can include user reference information to be output by the re- writable visual display 113 of the payment card 110. The signal generation component 121 can be operable to generate a user preference display signal in accordance with the user preference display signal generation instructions. For example, the user preference display signal can include information related to at least one of the selected user preferences. In examples, the signal generation component can include programmed code executed by the mobile device processor 124 to process the user preference display signal generation instructions for output as the user preference display signal. In examples, the signal generation component 121 receives instructions from the mobile device processor 124 to generate a signal for output to the payment card or another device, such as the issuer server 108, or entity, such as the service provider 105. In the case where the instructions are to be sent to the issuer server 108 or the service provider 105, the instructions can be output to a corresponding transceiver in the transceiver 187 for output by the mobile device 120 via the data network 130. The generated user preference display signal can be forwarded to the mobile device near field communication device 125 for output from the mobile device 120.

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

[0032] The mobile device 120 can include a secure element 185. In some examples, the mobile device processor 124, when obtaining the updated card number 129, can be operative to retrieve the updated card number 129 from the secure element 185 of the mobile device. The mobile device processor 124 can 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 can be deleted from the secure element 185 of the mobile device 120.

[0033] The payment card 110 can be operative to receive a user preference display signal output by the mobile device 120 near field communication device via the payment card near field communication device 115. The user preference display signal can be processed by the microprocessor 112 of the payment card 110. The processed user preference display signal can be forwarded to the display driver 633 and the rewritable visual display 113 for outputting the updated card number. The payment card near field communication device 115 can be operative to convert the updated card number signal output by the mobile device NFC device 125 into voltage values suitable for driving the rewritable visual display 113 (i.e., an e-ink display in the present 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 can 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. The rewritable visual display 113 of the payment card 110 can be coupled to the display driver 633, which can be operative to present the card number. The rewritable visual display 113 can be, for example, an e-ink display. The memory 116 can store one or more applets 117 and other information 119. The applets 117 can include an instance of a reissue application (such as the reissue application 127) that can be obtained from the application server 106 of the service provider 105. In examples, the memory 116 can include a secure element (not shown) within the other information 119. In some examples, the payment card processor 112 can be operative to retrieve the updated card number 129 from the secure element. The counter 114 can record the number of times the payment card 110 is used in transactions or the like. The count of the counter 114 cannot be shared outside the card, which makes it difficult for a skimming device to determine the count of the counter 114. Details of the applets 117 and the other information 119 are explained in more detail with reference to the examples of Figures 2-5

[0034] The payment card 110 can be a contactless card that wirelessly communicates (e.g., near field communication (NFC)) with the mobile device 120. Via NFC interaction between the payment card 110 and the mobile device 120, the payment card 110 can harvest energy from the NFC signal of the mobile device. The payment card 110 can be operative to receive a user preference display signal output by the mobile device 120 near field communication device via the payment card near field communication device 115. The user preference display signal can be processed by the microprocessor 112 of the payment card 110. The processed user preference display signal can be forwarded to the display driver 633 and the rewritable visual display 113 for outputting the updated card number. The payment card near field communication device 115 can be operative to convert the updated card number signal output by the mobile device NFC device 125 into voltage values suitable for driving the rewritable visual display 113 (i.e., an e-ink display in the present 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 can 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. The rewritable visual display 113 of the payment card 110 can be coupled to the display driver 633, which can be operative to present the card number. The rewritable visual display 113 can be, for example, an e-ink display. The memory 116 can store one or more applets 117 and other information 119. The applets 117 can include an instance of a reissue application (such as the reissue application 127) that can be obtained from the application server 106 of the service provider 105. In examples, the memory 116 can include a secure element (not shown) within the other information 119. In some examples, the payment card processor 112 can be operative to retrieve the updated card number 129 from the secure element. The counter 114 can record the number of times the payment card 110 is used in transactions or the like. The count of the counter 114 cannot be shared outside the card, which makes it difficult for a skimming device to determine the count of the counter 114. Details of the applets 117 and the other information 119 are explained in more detail with reference to the examples of​Figure 3B The payment card 110 can include one or more chips (described in more detail with respect to the examples of FIGS. 1A-1C) operable to perform functions as described herein. For example, the payment card 110 can include one or more chips, such as a radio frequency identification chip operable to communicate via NFC or other short-range protocol. In other examples, the payment card 110 can communicate with the mobile device 120 by other means, including but not limited to Bluetooth, satellite, and / or Wi-Fi. In some examples, the mobile device can be, for example, a card reader terminal, a cellular phone, a laptop, and / or a tablet. The payment card 110 can be operable to communicate with the mobile device 120 via NFC when the payment card 110 is within range of the respective mobile device. As described in more detail below, the payment card 110 can include a user name, an encryption key, and counter information from the counter 114, which can be transformed using a cryptographic algorithm to generate ciphertext including a dynamic password that can be used by a service provider to authenticate the mobile device.

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

[0036] Referring to Figure 4 and Figure 5 Details of the operational examples are described in more detail with respect to the examples of FIGS. 1A-1C. However, it can be beneficial at this time to refer to Figure 1A brief description explains the operation of an example of the interaction of the respective components of system 100. In the example, mobile device 120 can operate to send a request by reissue application 127 to authentication server 150, the request being sent via data network 130. The request can be made to authentication server 150 to verify that mobile device 120 is associated with payment card 110. In response to the verification that mobile device 120 is associated with payment card 110, mobile device 120 can obtain updated card number (CN) 129. As shown, the updated card number can be stored in a number of different locations within system 100. For example, updated card number 129 can be stored by service provider 105 in a secure location in a payment account server coupled to data storage device 101. In the example, updated card number 129 can be stored with payment account information 102. Payment account information 102 can include information related to each payment card account managed and serviced by service provider 105. Alternatively, issuer server 108 can store a number of unused or unassigned payment card numbers that can be used as updated card number 129.

[0037] In the example, updated card number 129 is different than the card number displayed on payment card 110 prior to issuance of the updated card number. Signal generation component 121 can operate to generate an updated card number signal. The updated card number signal may, for example, include the updated card number and other related information such as an encryption key, one or more authorized user names, a card verification value, an expiration date, an issuer name, etc. In another example, the updated card number signal can be a signal without the updated card number, the signal instead indicating that the updated card number is to be generated by a device receiving the updated card number signal, such as a payment card, an issuer server, etc. In another example, the card verification value can be another identifier related to payment card 110, such as a hash value, etc., that can be used by, for example, authentication server 150 to further confirm or verify that payment card 110 is authentic or is associated with the same user that also possesses mobile device 120. The updated card number signal can be output via mobile device near field communication device 125. In the example, payment card 110 can operate to receive the updated card number signal output by mobile device near field communication device 125 via payment card near field communication device 115. In response to receiving the updated card number signal, microprocessor 112 can operate to process the updated card number signal, and based on the updated card number signal, re-writeable visual display 113 can be driven (by display driver 633) to display the updated card number in place of the displayed card number.

[0038] Payment card 110 can include a number of components, such as Figure 1 those shown, but reference is made to Figure 2 and 3A- B provides a more detailed discussion of example payment cards.

[0039] Figure 2 A front view of an example of a payment card 200 suitable for use in the example processes described herein is provided. The payment card 200 can operate as a payment card issued by a service provider / issuer, such as a credit card, debit card, or gift card, with the name 205 of the service provider / issuer displayed on the front (or back, in some examples) of the payment card 200. The contactless payment card 200 can also include user identification information 215 displayed on the front 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.

[0040] The payment card 200 can include a substrate 210, which can include a single layer or one or more laminates composed of plastic, metal, and other materials. Examples of materials that can 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, and the like. In some examples, the payment card 200 can have physical characteristics that conform to the ID-1 format of the ISO / IEC 7810 standard, and the payment card 200 can additionally conform to the ISO / IEC 14443 standard. However, it should be understood that payment cards 200 according to the present disclosure can have different characteristics.

[0041] The rewritable visual display 207 can be an electronic ink display that responds to a drive signal to set a state of the display, and the electronic ink display remains static in the state set by the last applied drive signal in response to the drive signal being removed. For example, an example of a currently displayed or previously assigned payment card number can be “1234 5678 12345678,” as shown by the rewritable visual display 207. The payment card 200 can also include a magnetic stripe or tape, which can be located on the back of the card (not shown). As described in the examples below, the currently displayed or previously assigned payment card number “1234 5678 12345678” can be overwritten with an updated card number, such as “09876543 2109 8765.” As a result, the payment card with the updated card number can be reissued and used in future transactions.

[0042] In an example, the payment card 200 can include a rewritable magnetic stripe that is substantially overwritten with the updated card number at the same time that the updated card number is provided to the electronic ink display for use in future transactions.

[0043] The payment card 200 can also include identification information 215 displayed on the front and / or back of the card, as well as a contact pad 220. The user identification information 215 (shown as "Cardholder Name") can be the name or nickname of the user. The contact pad 220 can operate to establish contact with another communication device, such as a mobile device, smart phone, laptop, desktop, tablet, and the like. The payment card 200 can also include processing circuitry, antennas, and other components not shown in other examples. These components can be located behind the contact pad 220 or in other locations on the substrate 210.

[0044] As explained above, the payment card 200 can be built on a software platform operable on a smart card or other device including program code, processing power, and memory, such as Java Card. In some examples, such as Figure 1 Applets of the 117 can be added to the contactless payment card to generate requests for reissuing card numbers as well as 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 to reissue payment card numbers, as described below with reference to Figures 3A-5 .

[0045] Figure 3A is a block diagram of example components of the contactless payment card of Figure 2 .

[0046] As shown in Figure 3A , the bottom face of the contact pad 320 (and coupled thereto) can include processing circuitry 325 for storing and processing information, as well as one or more antennas 355. In addition to logic circuitry and the like, it is understood that the processing circuitry 325 can contain, for example, additional components necessary to perform the functions described herein, including processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, tamper-resistant hardware, and the like.

[0047] The one or more antennas 355 can be placed within the payment card, underneath the contact pad 320 and around the processing circuitry of the contact pad 320. For example, one or more antennas 355 can be integral with the processing circuitry 325, while another of the one or more antennas can be used with an external boost coil. In another example, the one or more antennas 355 can be external to the contact pad 320 and processing circuitry. The one or more antennas 355 can also provide the required inductance to collect power for driving, for example, the processing circuitry 325, memory 335, Figure 2The rewritable visual display 207 and similar power supplies. The processing circuitry system 325 may include a power management unit (not shown) that can operate to manage the power supply and storage devices for the payment card 200.

[0048] In the example of energy harvesting, Figure 3B The diagram illustrates powering the payment card for modification as shown in the reference. Figure 2 and 3A -3B describes an example of a device 360 ​​for a rewritable visual display of a payment card. Figure 3B In example device 360, antenna 362 can be an NFC-compatible antenna configured to receive NFC signals. Figure 3B In the example, antenna 362 can operate to provide both communication and inductance required for power harvesting. As mentioned above, antenna 362 can be coupled to a communication interface (in... Figure 3A As shown in the example, this communication interface provides signals to the processing circuitry system for signal processing (as shown in the example). Figure 3A (As described above). For example, the power captured by antenna 362 can be obtained, for instance, from a 13.56MHz NFC signal that generates alternating current within antenna 362. Of course, a radio frequency signal at a different frequency than 13.56MHz can also be used. Matching circuitry 363 can be part of antenna 362, which is matched to the incoming magnetic field to generate maximum inductance. In the example, inductor-capacitor (LC) type filter 364 can act as a low-pass filter, filtering out high-frequency components from the received signal that are unnecessary for communication. This communication is handled by processing circuitry (in... Figure 3A (The output is shown in the image.)

[0049] Energy from the induced current and induced voltage is harvested by energy harvesting component 361. The induced voltage can be approximately 0.1 volts (V). This voltage can be provided to power management unit 365 for rectification, smoothing, and other processing, as well as for distribution to other components such as display driver 333 or NFC circuitry 368, which can be controlled by a microprocessor (shown in other examples). In this example, the induced voltage can power changes in a rewritable visual display, such as an e-ink display. If the induced voltage is too low, additional circuitry and techniques can be used to increase it, such as using a transformer with more coil turns or an enhanced permanent magnetic field. When the payment card is not reissued because the e-ink display only needs power when changed, the payment card can harvest energy while being used with an NFC device and store the harvested energy in energy storage device 367 (which can be a battery, capacitor, supercapacitor, etc.) to store power for future display changes. In other examples, power management unit 365 may include an intermediate energy storage device (such as a capacitor) to smooth the voltage provided by energy harvesting component 361.

[0050] In the example, the signal received via NFC antenna 362 can be used to directly power NFC circuitry 368, or the power can be captured via energy harvesting component 361 to drive display driver 333, under the control of processor, to update the payment card number and present other information by means of changes to an electronic ink display as described in other examples.

[0051] return Figure 3A For example, memory 335 can be read-only memory, write-once-read-many memory, or read / write memory, such as RAM, ROM, and EEPROM, and processing circuitry system 325 can include one or more of these memories. For instance, read-only memory can be manufacturer-programmable read-only memory or one-time programmable memory. One-time programmability provides the opportunity to write once and then read many times. Write-once / read-many memory can be programmed at some point after the memory chip has left the factory. Once the memory is programmed, it cannot be rewritten but can be read multiple times. Read / write memory can be programmed and reprogrammed multiple times after leaving the factory. Read / write memory can also be read multiple times.

[0052] The memory 335 is operable to store one or more applets 340, one or more counters 345, and (multiple) payment card account identifiers 350. The one or more applets 340, one or more counters 345, and payment card account identifiers 350 may include: apps that work with corresponding one or more service provider applications (e.g., by...). Figure 1 The service provider 105 provides one or more associated software applications, such as Java Card applets, that are operable on one or more contactless cards. For example, one or more applets 340 may operate to respond to one or more requests (such as Near Field Communication (NFC) readers) from a reader and generate an NDEF message including an encrypted secure OTP encoded as an NDEF text tag. According to the example, each applet may store the username of a user associated with the payment card account to access the associated service provider application. One or more counters 345 may include a digital counter sufficient to store an integer, in some examples, representing the number of times the payment card 200 has been used.

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

[0054] For example, with reference to Figure 1 and FIG. 3, the memory 335 can include a username 342, encryption keys 343, and counter 345 information that can be used by the microprocessor 330, for example, in cryptographic algorithms to generate encryption keys that include dynamic passwords that can be used by Figure 1 the authentication server 150 of the service provider of the service provider 105 to authenticate the payment card 110, the mobile device 120, the user (not shown), or all three. For example, in cryptographic processing functions provided by the microprocessor 330, the microprocessor 330 can use the payment card account identifier(s) 350, the encryption keys 343, and a value from one of the counters 345 to generate encryption keys that include dynamic passwords that can be used with the username to authenticate the reissuance of the payment card 110 and provide the updated card number 129 to the payment card 110 via the mobile device 120. In one example, the dynamic password is related to the counter 345. In such an example, the dynamic password thus advantageously reflects prior behavior of the cardholder of the payment card 110. For example, a counter-based dynamic password can reflect the number of times the user has used the payment card 110 to obtain a particular service of the service provider 105 (e.g., a prepayment, a transaction authorization, or the like), which is a knowledge factor that a malicious third party would not actually be able to determine. For example, the number of times the payment card 110 is used can be stored as a counter 345 value in the secure memory of the payment card, and the value of the counter is incremented each time the payment card is used in a transaction.

[0055] The microprocessor 330 and memory 335 elements of the foregoing example examples are described with reference to the contact pad 320, but the present disclosure is not so limited. It should be understood that these elements can be outside of the contact pad 320 or completely separate therefrom, or implemented as other elements in addition to the microprocessor 330 and memory 335 elements located within the contact pad 320.

[0056] Returning to Figure 2 and Figures 3A-3BIn some examples, the payment card 200 can include one or more antennas 355 placed around the processing circuitry 325 of the contact pad 320. For example, the one or more antennas can be integral with the processing circuitry 325, or the one or more antennas 355 can be used with an external boost coil. As another example, the one or more antennas 355 can be external to the contact pad 320 and the processing circuitry 325. In examples, the one or more antennas 355 can extend around a region of the card to enhance the power transfer characteristics of the antenna when the antenna is placed in an electric field, such as an NFC field of a mobile device.

[0057] The processing circuitry 325 can include one or more communication interfaces 337, such as a radio frequency identification (RFID) chip 338, coupled to the one or more antennas 355, which are operable to communicate with a mobile device, such as the 120) via one or more short-range wireless communication protocols, such as near field communication (NFC), Europay, Mastercard, Visa (EMV) standards, and the like, and in compliance with ISO / IEC 14443. In some examples, the RFID chip 338 can also be referred to as a payment card near field communication device, such as the 115). While NFC is used as an example 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 can include additional components, such as those shown in the example of Figure 1 Figure 1 While NFC is used as an example 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 can include additional components, such as those shown in the example of Figure 3A

[0058] The payment card account identifier(s) 350 can include a unique alphanumeric identifier assigned to a user of the payment card 200, and / or one or more encryption keys 343, which together can be used to distinguish the payment card user from other payment card users. In some examples, the payment card account identifier(s) 350 can include both an identification of a customer and an account assigned to that customer, and can further identify a payment card (i.e., payment card number) associated with that customer’s account. According to some aspects, the username 342 can be derived from a combination of one or more of the payment card account identifiers 350 and / or one or more encryption keys 343.

[0059] In examples, the reissuance of a payment card number can utilize a password-less authentication protocol that effectively applies a contactless payment card cryptographic exchange protocol as a first factor authentication mechanism to facilitate application service access without sacrificing application service security.

[0060] ​​The payment card cryptogram exchange protocol includes registering a payment card to an application service client, binding a contactless card to the client, and performing first factor, second factor, and / or other authentication of a client access request using the cryptogram exchange protocol with one of the applet(s) 340, a counter value from the counter 345, a key value from the encryption key 343, and the microprocessor 330.

[0061] To ensure valid authentication of the payment account, mobile device, and payment card, the three are typically bound to one another by correlating digital certificates of the payment account, mobile device, and payment card to one another.

[0062] For example, a payment card can register with the service provider 105 to receive a reissue application service. As part of the registration, a username, such as 342, can be stored in a data store 109 coupled to the authentication server 150. In some examples, the username can be automatically generated by the service provider 105, the username is not known to the mobile device, and is loaded to a user information table (not shown) stored in the data store 109 and the applet(s) 340 downloaded on the payment card 110. As an example, the payment card is associated with a user and a user 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 user payment account information (i.e., account number or other identifier) can be maintained and stored by the service provider 105 via the payment account server 103. The payment account information 102 also includes information about the mobile device associated with the user, payment card, and user payment account. For example, the payment account information 102 can include mobile device 120 information 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 an application used to capture the image (e.g., an identifier of an instance of the application, an application version of the application, and / or the like), and / or the like. Once the payment card is registered with the service provider 105 and bound to the mobile device, application authentication using a payment card cryptographic algorithm can be performed to enable authentication of the payment card, the mobile device, and the user, which enables reissuance of the payment card via the reissue application. Examples of cryptographic algorithms suitable for use with the disclosed examples include: 3DES (Triple Data Encryption Algorithm), Advanced Encryption Standard (AES); a symmetric hash-based message authentication (HMAC) algorithm such as HMAC-SHA-256; and a symmetric cipher-based message authentication code (CMAC) algorithm such as AES-CMAC, or the like. This level of security enables the following processes to be securely performed, mitigating the service provider's or the payment account user's concern of a rogue fraudulent disclosure of a payment card such as that described herein.

[0063] Figure 4 is an example process executed by a mobile device used in a system such as that shown in Figure 1 In the example, a card supporting an electronic ink display has been compromised (e.g., a fraudulent transaction has been made using the payment card number), and the payment card needs to be reissued. Instead of replacing the payment card (e.g., 110 or 120) with a new payment card (e.g., 110 or 120), the payment card can be reissued by the service provider 105 using the reissue application 340. Figure 1 Figure 2 ​In the disclosed examples, the payment card can cause the card number on the payment card to change. In an example, the payment card can be placed within the electric field of the NFC device of the mobile phone (e.g., "tap the phone") and provide information to authenticate the payment card. Based on the authentication of the card and the mobile device, the mobile device can be operative to communicate the following new information: card number, card verification value (CVV), expiration date, service provider / issuer (e.g., VISA or MASTERCARD), all or a portion of which can be displayed. For example, the e-ink display is modified and the e-ink display remains static when the payment card is removed from the NFC field of the mobile device.

[0064] In more detail, the process 400 can include the mobile device sending a request to update a card number on a reissued payment card (410). The request can include an indication that the card number presented on the display of the payment card and / or encoded on the magnetic stripe of the payment card is invalid and unusable to complete a transaction (e.g., purchase of goods or services, etc.). The payment card number can become invalid and unusable because the payment card number has been compromised due to identity theft, user negligence, or the like. In some examples, an authentication message can be generated by a reissue application executing on the mobile device, such as the reissue application 202 of FIG. 2, prior to sending the request to authorize the reissued payment card. The authentication message can include, for example, information related to the mobile device that is stored by an authentication server of the service provider. The authentication message can be included in the request with the indication. Figure 1

[0065] In response to the sent request, the mobile device 120 can receive authorization to reissue the payment card and update the card number (420). For example, the mobile device 120 can receive authorization to reissue the 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 can have information processed by the authentication server 150, such as an encrypted message. An authentication status message can 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 can obtain and send the updated card number and / or information associated with the selected user preferences (described in more detail below).

[0066] ​In this example, the card number encoded on the magnetic stripe of the payment card may not be updated. In response to received authorization, the updated card number can be obtained from a secure source of the updated card number (430). In this example, the mobile device can obtain the updated card number by retrieving it from the mobile device's secure element. After retrieving the updated card number from the secure element, the mobile device can report the updated card number to, for example, an issuer server associated with the payment card's issuer or a financial institution associated with the payment card. The mobile device can delete the updated card number from the secure element or take other actions to ensure that the updated card number is not unintentionally reused. Figure 1 As shown, the updated card number (CN) 129 can be stored in various locations and can be obtained by the mobile device 120 when requested and authorized by the appropriate source. For example, the security source of the updated card number can be one or more of several various sources, such as a security element within the mobile device, a security element within the payment card, a source within the service provider, a source within the payment card issuer, or another security source. Instead of obtaining the updated card number from the security element of the mobile device, when obtaining the updated card number from the security source of the updated card number, the mobile device can obtain it from an issuer server (such as an issuer server, etc.) associated with the issuer of the payment card. Figure 1 In example 108), the updated card number is retrieved. In other examples, the updated card number can be used by the mobile device's reissue application 127 based on... Figure 1 The updated card number is generated by a cryptographic hash function on the data retrieved by payment card 110. In another example, the processor 112 of payment card 110 can be operated to generate the updated card number, for example, by using a cryptographic hash function or some other function and data maintained in the payment card memory (such as data from counter 114). In the example, the cryptographic hash function or other function can be a secure source of the updated card number using various cryptographic and other security technologies. Figure 1 When the payment card 110 generates an updated card number, Figure 1 The authentication server 150 can be used to authenticate the payment card 110 via the mobile device 120. Once authenticated, the payment card 110 itself can generate an updated card number.

[0067] In another example, at step 430, when mobile device 120 obtains the updated card number from a secure source, it can retrieve the updated card number from the secure element of the mobile device. Mobile device 120 can report the updated card number of the payment card to the issuer server associated with the payment card issuer and delete the updated card number from the secure element.

[0068] In response to the command signal from the signal generation component executing on the mobile device, an updated card number signal representing the updated card number can be output via the near field communication circuit or device in the mobile device (440). As the payment card is within range of the near field communication circuit or device in the mobile device, the near field communication device embedded in the payment card to be reissued can receive the updated card number signal (450). In an example, the payment card can also receive an authentication signal from the mobile device 120 via the payment card near field communication device. The logic circuit on the payment device can verify that the mobile device 120 is associated with the payment card, for example, with an encryption key or the like.

[0069] The payment card can power the microprocessor with energy from the updated card number signal in response to the received signal. For example, at 460, in response to receiving the updated card number signal and harvesting energy from the received signal, the visual display on the payment card can be modified to indicate the updated card number. In an example of a payment card equipped with a rewritable magnetic stripe, the payment card microprocessor can operate to rewrite the rewritable magnetic stripe with the updated card number. Conversely, in an example of a payment card not equipped with a rewritable magnetic stripe, the updated card number is different from the card number represented by the magnetic stripe of the payment card to be reissued. Additionally, the updated card number signal can include a value indicating that the magnetic stripe is invalid and unusable for continued use of the payment card with point of sale devices using swipe technology. The payment card can store the value indicating that the magnetic stripe is invalid and unusable and provide information related to the value to point of sale devices. Alternatively, the updated card number itself can indicate that the magnetic stripe is invalid, or the authentication server can have a setting to provide point of sale devices with an indication that the magnetic stripe is invalid and unusable.

[0070] In another example, the updated card number can be a temporary payment card number (such as a temporary virtual card number) that can be used for a single transaction, a predetermined time period, and the like. The temporary virtual card number can be displayed for a limited time, such as the duration of a single transaction, a predetermined time period, and the like. In another example, the rewritable visual display can be used to display a one-time use "token," a temporary virtual card number, or a dynamic credit card number. These would be provided by the application server or the authentication server and communicated to the payment card via NFC or the like of the mobile device. The display can present an indication that the token, temporary virtual card number, or dynamic credit card number is not the primary payment account number.

[0071] In some examples, the process 400 can include enabling the mobile device to perform additional functions. For example, these additional functions improve the user's awareness of the monetary value associated with their payment card by providing additional information that can be time consuming and inconvenient to obtain. For example, in response to a user input, the mobile device can select an account display preference for displaying information on the payment card. In response to the selected account display preference, the signal generating component of the mobile device can modify the signal parameters for overwriting the rewritable visual display in accordance with the selected account display preference. The modified signal parameters can be used to transmit a user preference display signal to the payment card. The transmitted user preference display signal causes information such as one or more of the following to be presented on the visual display of the payment card: a recent transaction amount, a total amount of reward points, an account balance, an account limit, or a warning related to the account balance. Of course, other information can also be provided. The presented information can be obtained from the service provider 105, e.g., from the payment account server 103, the application server 106, or the like.

[0072] The payment card (such as Figure 5 The payment card 110) can operate to perform a process for authenticating the card to receive an updated card number. Figure 1 is a flowchart illustrating an example of a process 500 performed by a system example of a payment card. Figure 1 The payment card 110) can operate to perform a process for authenticating the card to receive an updated card number. Figure 1 is a flowchart illustrating an example of a process 500 performed by a system example of a payment card. Figure 1 The payment card 110) can operate to perform a process for authenticating the card to receive an updated card number. Figure 1 is a flowchart illustrating an example of a process 500 performed by a system example of a payment card.

[0073] The payment card 110) can operate to perform a process for authenticating the card to receive an updated card number. Figure 1 is a flowchart illustrating an example of a process 500 performed by a system example of a payment card.

[0074] In a particular example, the updated card number signal can be related to the provisioning of a Europay, Mastercard, Visa (EMV) profile. In an example, the EMV profile contains authentication keys for verifying chip-based and contactless payment transactions. These authentication keys can be encrypted with the card's symmetric primary key (stored in the card's secure memory, such as a secure element) and sent, or completed by activating a backup "profile." The backup profile can be, for example, an inactive, complete EMV-compliant data set on the chip of the payment card that would become the primary payment card number (i.e., the payment card number authorized for use in transactions). Upon activation of the corresponding updated payment card number, the payment card can display the updated payment card number as the new primary account number (PAN).

[0075] In response to receiving the updated card number signal, the card number currently displayed on the visual display of the payment card can be replaced with the updated card number (530). For example, a processor or logic circuit on the payment card, in response to the payment card's near field communication device receiving the updated card number signal, can generate a display driving signal for driving the visual display of the payment card to alter the currently displayed card number.

[0076] At 540, the payment card can also receive an account status signal, which can be received via the mobile device's near field communication device. In response to the account status signal, the visual display of the payment card can be modified to present at least one of: a payment card account balance, a recent transaction amount, an account annual percentage rate, a rewards points balance, a payment due date, a location-based discount, or a location-based reward.

[0077] The process 500 can also include selecting an account display preference for modifying information displayed on the payment card. For example, under the control of the reissue application 127, the signal generation component can modify the signal parameters in response to the selected account display preference. Prior to transmitting the signal representing the updated card number, a display preference signal based on the selected preference can be transmitted to the payment card. The display preference signal can cause one or more of the following to be displayed on the payment card electronic ink display: a recent transaction amount, a rewards points total, an account balance, an account limit, or a warning related to the account balance.

[0078] In other examples, in addition to the updated card number, the user preference display signal can include information related to at least one of the selected selectable user preferences. For example, Figure 3A The mobile device processor 124 can operate 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.

[0079] In an example, the selectable user preferences in the menu can include one or more of: a payment card account balance, a recent transaction amount, an account annual interest rate, a rewards points balance, a payment due date, a location-based discount, or a location-based reward. The mobile device 120 can receive a selection of at least one of the selectable user preferences via at least one input device, such as a touch screen, buttons, a keyboard, etc. The at least one selected user preference can be stored in the memory. In an example, each selected user preference can be presented on the rewritable visual display 113 of the payment card 110 each time the payment card 110 and the mobile device 120 communicate with each other, regardless of whether the payment card number is to be reissued. The mobile device processor 124 can also operate to obtain information related to at least one of the selected selectable user preferences via the reissue application 127 in response to authentication of the mobile device 120 in association with the payment card 110. The information related to at least one of the selected selectable user preferences can be stored in the memory 122, e.g., in other elements 189, or retrieved via the authentication server 150, the payment account server 103, or the application server 106. The memory 122 can also operate to store user-related numbers, information related to the user authorized to use the payment card, or the like.

[0080] In another example, the payment account server 103 can operate to retrieve the updated card number from the data store 101 in response to a request from the mobile device 120. The payment account server 103 can transmit the updated card number to the reissue application 127 executing on the mobile device.

[0081] In response to the account status signal, the visual display of the payment card can be modified to present at least one of: a payment card account balance, a recent transaction amount, an account annual interest rate, a rewards points balance, a payment due date, a location-based discount, or a location-based reward (550). In some examples, previous transaction information can be stored in memory (such as, for example, the 335) of the payment card. When the payment card is placed in a near field communication electric field, the payment card can collect energy to present a portion of the previous transaction information. Figure 1

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

[0083] In addition to reissuing a payment card number for future transactions, the rewritable visual display can be controlled to change the type of card. For example, the payment card can be completely changed to another card, such as a prescription card, an identification card, a debit card, etc. Of course, to provide for such a change in card type, the service provider (such as, for example, the payment account server 103) can be required to have access to the card type information.​Figure 6 of 105) can access or provide respective services related to prescription cards, identification cards, debit cards, and the like.

[0084] Figure 6 An example of a computing architecture 600 suitable for implementing various examples as previously described is shown. In one example, the computing architecture 600 can include elements that can be typically used to implement a server or a network platform (as part of the system 100, if appropriately programmed). In another example, the computing architecture 600 can include optional elements that can be typically used to implement a smart digital device or a computing device (which can be implemented as part of the system 100).

[0085] The computing architecture 600 includes various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input / output (I / O) components, power supplies, and so forth. However, examples are not limited to implementation by the computing architecture 600.

[0086] As shown in Figure 6 The computing architecture 600 includes a processing unit 604, a system memory 606, and a system bus 608. The processing unit 604 can be any of various available processors, or multiple processors, of any kind, typically supplied by a single vendor.

[0087] The system bus 608 provides an interface for system components including, but not limited to, the system memory 606, to the processing unit 604. The system bus 608 can be any of several types of bus structures including, but not limited 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 can connect to the system bus 608 via an appropriate interface. Example interface adapters include, but are not limited to, sound cards, video cards, bus master

[0088] The computing architecture 600 can include or implement various articles of manufacture. An article of manufacture can include a computer-readable storage medium. Examples of a computer-readable storage medium can include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of logic can 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. Examples can also be implemented as hardware logic with

[0089] The system memory 606 can include various types of computer-readable storage media in the form of one or more higher 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-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, an array of devices such as Redundant Array of Independent Disks (RAID) drives, solid state drives (e.g., USB memory, SSDs), and any other suitable type of memory or other computer-readable storage medium. Figures 1-6 In the illustrated example, the system memory 606 can include non-volatile memory 610 and / or volatile memory 612. A basic input / output system (BIOS) can be stored in non-volatile memory 610.

[0090] The computer 602 can include various types of computer-readable storage media in the form of one or more lower storage units, including an internal hard disk drive (HDD) 614 (or an external hard disk drive (HDD) 613), a magnetic floppy disk drive (FDD) 616 to read from or write to a removable magnetic floppy disk 618, and an optical disk drive 620 to read from or write to a removable optical disk 622 such as 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, an FDD interface 626 and an optical drive interface 628, respectively. The HDD interface 624 for an external drive implementation can include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies.

[0091] The drives and associated computer-readable media provide volatile and / or nonvolatile storage of data, data structures, computer-executable instructions, and so forth. 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 memory 610, 612. 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 can include instructions that, when executed, cause the system to perform any of the computer-implemented methods and processes described herein.

[0092] Optionally, the computing architecture 600 can include additional devices that enable data to be input to and output from the user, such as a smart digital device, laptop, or the like, when configured as such. For example, a user can enter commands and information into the computer 602 through one or more wire / wireless optional input devices, e.g., a keyboard 638 and a touch input device such as a touch screen 640. Other input devices can include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, a game pad, a stylus, a near field communication device, a dongle, a fingerprint reader, a glove, a head mounted display, a headset, a joystick, a keyboard, a retina reader, a touch screen (e.g., capacitive, resistive, etc.), a trackball, a trackpad, a sensor, a stylus, and / or the like. These and other input devices are often connected to the processing unit 604 through an optional interface 642 that is coupled to the system bus 608, but can be connected by other interfaces such as a parallel port, IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.

[0093] Another optional element that can be included is a display 644, which can be an organic light emitting diode (OLED), a light emitting display (LED), or some other type of display device that can be configured to present graphics, application icons, and other information to a user via an interface, such as optional video adapter 646. Display 644 can be internal or external to computer 602. In addition to display 644, a computer typically also includes other peripheral output devices, such as speakers, printers, and so forth, which can also be coupled to system bus 608 via optional interface 642.

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

[0095] When used in a LAN networking environment, computer 602 can be connected to the LAN 652 through a wired and / or wireless communication network interface or adapter 656. The adapter 656 can facilitate wired / wireless communications to the LAN 652, which can also include a wireless access point disposed thereon for communicating with the adapter 656.

[0096] When used in a WAN networking environment, computer 602 can include a modem 658, or other means for establishing communications over the WAN 654, such as by way of the Internet. The modem 658, which can be internal or external, can be connected to the system bus 608 via the interface 642, in a wired or wireless manner. In a networked environment, program modules depicted relative to computer 602, or portions thereof, can be stored in the 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 can be used.

[0097] The computer 602 is operable to communicate with wirelessly and wireline devices or entities using the IEEE 802 family of standards (such as wireless devices operable in accordance with a Wireless Fidelity (Wi-Fi) or Wireless LAN (WLAN) standard such as IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ah, 802.1 lad, 802.1 lay, 802.1 lax, or 802.1 lay, or any implementation of the IEEE 802.15 standard, or the Bluetooth® wireless personal area networks, or WiMax, or the LTE) or to communicate using other mechanisms of using the IEEE 802 family of standards. This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ personal area networks. The computer 602 can communicate with the wireless devices or entities through a communications interface 656 using the wireless techniques described above, and using the associated wireless communications interface 656 (e.g., the radio 648 can use multiple antennas for TM wireless communications). The communications interface 656 (and / or portions thereof) can facilitate wired or wireless communications for the transfer of data to and from the computer 602. The communications interface 656 can include one or more interfaces common across various devices or platforms, and can be configured to facilitate the communications of information between these devices or platforms. The communications interface 656 can include one or more wired or wireless interfaces that can be used to receive input, provide output, both receive and provide output, or the like. The communications interface 656 can be configured to use various protocols of the TCP / IP family to communicate over the World Wide Web, via a variety of devices and technologies, including the Internet, intranets, Extranets, LAN, WAN, etc. Use of the TCP / IP family of protocols is not intended to be a limitation on the scope or the disclosure given above. In fact, any of a variety of protocols can be used, including but not limited to protocols that are proprietary to a particular device or platform.

[0098] As previously noted, various components of the devices described previously Assembly with reference to FIG. 6 can include various hardware elements, software elements, or a combination of both. Examples of hardware elements can include devices, logic devices, components, processors, microprocessors, circuitry, processing circuitry, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), 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 device, chips, microchips, chip sets, and so forth. Examples of software elements can include software ​ , 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, determining whether an example is implemented using hardware elements and / or software elements can vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given implementation.

[0099] As used in this application, the terms "system," "component," and "unit" 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 being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (optical and / or magnetic storage medium), an object, an executable, a thread of execution, a program, and / or a computer. By way of illustration, 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.

[0100] Further, these components can be coupled by various types of communications media to coordinate operations. The coordination can involve the uni-directional or bi-directional exchange of information. For instance, the components can communicate in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. In other examples, alternative technologies to signals can be present. Such alternative technologies use data messages. Such data messages can be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

[0101] Some examples can use the expression "one or more" along with the term "each" in the discussions of examples. This usage should not be construed in means that there is one or more of each; but instead that there are one or more of the members in at least one example. The same should be understood for "each" when it is used in conjunction with the term "at least one" or a like term. Also, as used in the description herein and the appended claims, the singular forms "a," "an" and "the" include plural referents unless the context clearly dictates otherwise.

[0102] With primary reference to notations and nomenclature used herein, the detailed description herein can be presented in terms of functional blocks or units that can be implemented as program processes executing on a computer or computer network. These process- based descriptions and representations can be realized as the structural description set forth herein in terms of the functions, operations and / or procedures performed by the structural components and / or units.

[0103] Processes, procedures, or methods here generally are conceived to be self-consistent sequences of operations leading to a desired result. The operations are those requiring 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 proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities.

[0104] Furthermore, the performed manipulations are often referred to in terminology such as adding or comparing, which often is associated with mental operations performed by a human operator. In any of the operations described herein forming part of one or more of the examples, such capability of a human operator is not necessary, or in most cases desirable. Rather, the operations are machine operations. Useful machines for performing the operations of various examples include general purpose digital computers or similar devices.

[0105] Some examples can be described using the expression "coupled" and "connected" along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, some examples can 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. The term "coupled," however, can also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

[0106] Various examples also relate to apparatus or systems for performing these operations. This apparatus can be specially constructed for the required purposes, or it can comprise a general purpose computer as selectively activated or reconfigured by a computer program stored in the computer. The processes presented herein are not inherently related to a particular computer or other apparatus. Various general purpose machines can be used with programs in accordance with the teachings herein, or it can prove convenient to construct more specialized apparatus to perform the required method steps. The structure for a variety of these machines will appear from the description given.

[0107] It is to be appreciated that the Abstract is provided herein for convenience and for allowing a quick initial appreciation of a purpose of the disclosure. Submissions to the USPTO are made pursuant to 37 C.F.R. § 1.72(b). Submissions under 37 C.F.R. § 1.72(b) are not admitted to be prior art against the present disclosure. Additionally, in the preceding detailed description, various features are grouped together in single examples for the purpose of streamlining the disclosure. The methods of the present disclosure are not to be interpreted as reflecting an intention that the claimed examples require more features than are explicitly recited in each claim. Rather, as the claims below reflect, inventive subject matter lies in fewer than all features of a single disclosed example. Thus, the following claims are hereby incorporated into the detailed description, where each claim can stand on its own as a separate example. In the appended claims, the terms "including," "containing," "having," and "wherein" are used as synonyms for each other, in an attempt to employ the

[0108] What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and / or methodologies, but one of ordinary skill in the art could recognize that many other 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. A computer-implemented method, comprising: The mobile device sends a request to the service provider system to update an account on a contactless card, wherein the request includes an indication that the account on the contactless card is invalid and information related to the mobile device stored by the service provider system. The mobile device receives authorization from the service provider system for updating the account, wherein the authorization is based on valid authentication of the contactless card linked to the payment account; The mobile device requests the updated account from the service provider's system; The updated account is received by the mobile device from the service provider's system; The contactless card is detected by the mobile device based on wireless communication signals; and The updated account is transmitted from the mobile device to the contactless card.

2. The computer-implemented method according to claim 1, comprising receiving a signal from the mobile device indicating that the account has been successfully updated using the updated account.

3. The computer-implemented method according to claim 1, wherein, The mobile device includes an application for performing operations to update the account, the operations including sending the request, receiving the authorization, requesting the updated account, receiving the updated account, detecting the contactless card, and transmitting the updated account.

4. The computer-implemented method of claim 3, further comprising sending a verification request to the service provider system to verify that the mobile device, the application, or both the mobile device and the application are associated with the contactless card before requesting an updated account.

5. The computer-implemented method according to claim 3, comprising: The application provides a user interface. as well as The application receives an input request via the user interface to update the account on the contactless card.

6. The computer-implemented method according to claim 3, comprising: The mobile device detects the authentication signal emitted from the contactless card; The authentication signal is forwarded from the mobile device to the service provider system; as well as Before updating the account, receiving the contactless card is verification of a valid payment card associated with the mobile device, the application, or both the mobile device and the application.

7. A computing device, comprising: processor; and A memory storing instructions that, when executed by the processor, cause the processor to: Send a request to the service provider system to update the account on the contactless card, wherein the request includes an indication that the account on the contactless card is invalid and information related to the computing device stored by the service provider system; Receive authorization for updating the account from the service provider system, wherein the authorization is based on valid authentication of the contactless card linked to the payment account; Request an updated account from the service provider's system; Receive the updated account from the service provider's system; The contactless card is detected based on wireless communication signals; as well as The updated account is transmitted to the contactless card.

8. The computing device of claim 7, further comprising causing the processor to receive a signal indicating that the account has been successfully updated using the updated account.

9. The computing device according to claim 7, wherein, The mobile device includes an application for performing operations to update the account, the operations including sending the request, receiving the authorization, requesting the updated account, receiving the updated account, detecting the contactless card, and transmitting the updated account.

10. The computing device according to claim 9, wherein, The application also includes instructions to send a verification request to the service provider system before requesting an updated account to verify that the mobile device, the application, or both the mobile device and the application are associated with the contactless card.

11. The computing device according to claim 9, wherein, The application also includes instructions for the following operations: Provide a user interface; and Process input requests for updating an account on the contactless card via the user interface.

12. The computing device according to claim 9, wherein, The application also includes instructions for the following operations: Detect the authentication signal emitted from the contactless card; The authentication signal is forwarded to the service provider system; as well as Before updating the account, receiving the contactless card is verification of a valid payment card associated with the mobile device, the application, or both the mobile device and the application.

13. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor of a mobile device, cause the processor to: Send a request to the service provider system to update the account on the contactless card, wherein the request includes an indication that the account on the contactless card is invalid and information related to the mobile device stored by the service provider system; Receive authorization for updating the account from the service provider system, wherein the authorization is based on valid authentication of the contactless card linked to the payment account; Request an updated account from the service provider's system; Receive the updated account from the service provider's system; The contactless card is detected based on wireless communication signals; as well as The updated account is transmitted to the contactless card.

14. The computer-readable storage medium of claim 13, further comprising the processor receiving an instruction indicating that the account has been successfully updated using the updated account.

15. The computer-readable storage medium according to claim 13, wherein, The instructions are included in an application for performing operations to update the account, the operations including sending the request, receiving the authorization, requesting the updated account, receiving the updated account, detecting the contactless card, and transmitting the updated account.

16. The computer-readable storage medium of claim 15, further comprising instructions that the processor is configured to send an authentication request to the service provider system to verify that the mobile device, the application, or both the mobile device and the application are associated with the contactless card before requesting an updated account.

17. The computer-readable storage medium of claim 15, wherein the processor is configured to: The application provides a user interface; and The application receives an input request via the user interface to update the account on the contactless card.

18. The computer-readable storage medium of claim 15, wherein the processor is configured to: Detect the authentication signal emitted from the contactless card; Forward the authentication signal to the service provider system; and Before updating the account, receiving the contactless card is verification of a valid payment card associated with the mobile device, the application, or both the mobile device and the application.

Images