Source: https://patents.google.com/patent/US10127533B2/en
Timestamp: 2019-04-24 10:44:05+00:00

Document:
Managing user devices associated with a digital wallet account comprises associating, using one or more computing devices, one or more user computing devices with a digital wallet account of a user, each of the associated one or more user computing devices being activated to conduct financial transactions with a merchant utilizing the digital wallet account; presenting the associated user computing devices in a list of associated user computing devices; receiving a request to deactivate a particular user computing device from the list of associated user computing devices; deactivating the particular user computing device, the deactivation being sufficient to prevent the user computing device from conducting transactions with a merchant utilizing the digital wallet account; and presenting a deactivated status of the particular user computing device.
This patent application claims priority to U.S. Provisional Patent Application No. 61/678,089, filed Jul. 31, 2012 and entitled “Proxy Card System.” The entire disclosure of the above-identified priority application is hereby fully incorporated herein by reference.
The present disclosure relates generally to digital wallet transactions, and more particularly to managing devices associated with a digital wallet account.
Digital wallet accounts can be configured by a user for transactions with merchants. The transactions can be conducted online or offline. Digital wallet accounts can be used for online purchases via the Internet with a user computing device. A digital wallet application module can be installed on a mobile computing device for use in offline purchases. For example, the user can utilize a digital wallet application module on a user computing device to make purchases at a merchant location via near field communication (“NFC”), BLUETOOTH, Wi-Fi, or other proximity communication technologies.
The digital wallet account can be associated with a proxy card account. Proxy card payment systems enable users to utilize a single card to access multiple financial accounts maintained by multiple issuers. The user receives a proxy card from the proxy card system and either creates a new proxy card system account or associates the proxy card with the user's digital wallet account already maintained by the proxy card system. The user then associates one or more financial card accounts with the proxy account. For example, the user can associate with the user's proxy card account multiple debit/credit cards maintained by multiple issuers (including the proxy card system operating as an issuer), stored value cards (for example, gift cards, prepaid cards, re-loadable transaction cards, exchange cards, and other forms of non-credit based value cards), loyalty cards or store rewards cards, value added service accounts (for example, coupons, vouchers for prepaid offers, redemption offers, and other forms of offers), peer-to-peer transaction accounts, bank accounts and/or other forms of financial card accounts.
In a conventional digital wallet application, the user is not able to disable a digital wallet application module on a different mobile user device or other user device. For example, a user might lose a mobile phone that has a digital wallet application module installed or have that cell phone stolen. The user does not have a manner of conveniently disabling or removing the user device from the list of authorized digital wallet devices.
Techniques herein provide a computer-implemented method to manage user devices associated with a digital wallet account. A payment system employs a server configured for associating, using one or more computing devices, one or more user computing devices with a digital wallet account of a user, each of the associated one or more user computing devices being activated to conduct financial transactions with a merchant utilizing the digital wallet account; presenting the associated user computing devices in a list of associated user computing devices; receiving a request to deactivate a particular user computing device from the list of associated user computing devices; deactivating the particular user computing device, the deactivation being sufficient to prevent the user computing device from conducting transactions with a merchant utilizing the digital wallet account; and presenting a deactivated status of the particular user computing device.
Another aspect of the example embodiments described herein provides a computer program product that is installed on a server to manage user devices associated with a digital wallet account. The computer program product includes a non-transitory computer-readable storage device having computer-readable program instructions stored therein. The computer-readable program instructions include computer program instructions for associating each of the associated one or more user computing devices being activated to conduct financial transactions with a merchant utilizing the digital wallet account; presenting the associated user computing devices in a list of associated user computing devices; receiving a request to deactivate a particular user computing device from the list of associated user computing devices; and deactivating the particular user computing device, the deactivation being sufficient to prevent the user computing device from conducting transactions with a merchant utilizing the digital wallet account.
FIG. 1 is a block diagram depicting a system for managing devices associated with a digital wallet account, in accordance with certain example embodiments.
FIG. 2 is a block flow diagram depicting a method for adding a user device to a digital wallet account, in accordance with certain example embodiments.
FIG. 3 is a block flow diagram depicting a method for disabling or removing a user device from a digital wallet account, in accordance with certain example embodiments.
FIG. 4 is a block flow diagram depicting a computing machine and a module, in accordance with certain example embodiments.
The example embodiments provide a digital wallet account and one or more user devices utilized to make transactions with the digital wallet account. To receive the benefits of the techniques described herein, in certain embodiments, the user will install an application, use a particular service, or otherwise engage in the techniques herein. In the example embodiment, a digital wallet account includes specified information for one or more financial accounts, including, but not limited to debit cards, credit cards, stored value cards, loyalty/rewards cards, bank accounts, peer-to-peer transaction accounts, stored value accounts, and coupons (including purchased offers and other offers), each accessible by a digital wallet application module or other embodiment of the digital wallet account. In an example embodiment, the user can access the digital wallet account using an application operating on a mobile communications device or other device equipped with a web browser or other communication module and connected to the Internet. The digital wallet account can be hosted by a payment processing system or any other suitable system.
In an example embodiment, the digital wallet account can utilize or represent a proxy card account. The digital wallet account can store the proxy card account or any suitable representation or operations of the proxy card account. The proxy card account can be a function of the digital wallet account or can represent the system by which the digital wallet account operates. Alternatively, a proxy card account can be just one of multiple accounts managed and utilized by the digital wallet application module.
In an example embodiment, a front-end “kill-switch” provides an interface for users to display, monitor, and de-activate their wireless and physical proxy card devices on a per-device basis. This implementation provides security and control to payment processing system users.
Wireless devices and other user devices are added to a digital wallet account when the user device sends a request to the payment processing system to add the user device. User devices added to the digital wallet account can include any computing device available to a user including a desktop computer, laptop computer, tablet computer, a television with one or more processors embedded therein and/or coupled thereto, smart phone, handheld computer, personal digital assistant (“PDA”), or any other wired or wireless, processor-driven device. The digital wallet account may be represented on a device as a digital wallet application module, a digital wallet application module operating on a website or server, a representation on a user interface of the payment processing system, or any other suitable embodiment of the digital wallet account.
Additionally or alternatively, the digital wallet account may include a physical payment card, including a proxy card, or other physical tool for conducting transactions, such as a magnetic stripe card, smartcard, RFID device, or other suitable tools. Throughout the specification, “digital wallet application module” will be intended to encompass all embodiments of the digital wallet account on user devices, including physical cards. Additionally, “user devices” will be intended to encompass all suitable devices used to host a digital wallet account embodiment, including physical cards.
In an example embodiment, a request for adding a user device is required when a digital wallet application module is first installed and after each reset. Thus, the first activation is when the application is first set up on the user device. A subsequent reset and re-activation of the application will be considered a new activation. In an example embodiment, re-activation of a deactivated device is performed by reinstalling and setting up the digital wallet application module on the user's mobile communication device. In an example embodiment, the user may be required to re-enter their financial payment card information.
In an example embodiment, a page on a user interface associated with a digital wallet account provides a listing of user devices associated with the digital wallet account. The device listing will indicate the enabled user devices that the user owns and the activation state of each device. The device list contains all of the information required to render a virtual representation of the device to the user. For example, the device list may show information indicating the device status such as the device name, the activation date, the last time a transaction was initiated, the activation status, a device image, an option to deactivate any active devices, an option to retry a deactivation if a previous attempt did not complete, and any other suitable displays or options.
In an example embodiment, the user can access the digital wallet account by logging onto the payment processing system website online, using a digital wallet application module on a user mobile communication device such as a user device, or by using any other suitable user interface system. The user may retrieve the status of all devices linked to the digital wallet account.
The user can select a user device to add to the digital wallet account by adding the user device details into a user interface of the digital wallet account. For example, the user can enter the phone number to a mobile user device and the digital wallet account can locate the appropriate user device over the network, via email, over a wired network, or via any other suitable manner. The user can select the device from a list of devices associated with the user. The user can select a device from a list of inactive devices. Any other suitable manner of selecting user devices to add to the digital wallet account can be employed.
The user can install the digital wallet application module on the user device. In an example embodiment, the payment system can transmit the digital wallet application module to the user device. In another example, the user device can locate the digital wallet application module on the Internet and download the application for the digital wallet application module. In another example, the user device can download the digital wallet application module from a website of the payment processing system. The user can install the digital wallet account in any other suitable manner.
In an alternative embodiment, the user device has installed a digital wallet application module before the user device is added to the device list of the digital wallet account. Additionally or alternatively, the user can use the digital wallet application module to add the device to the device list. For example, the user can open the digital wallet application and input the digital wallet account credentials to enter the digital wallet account. From the user device, the user can add the user device to the digital wallet account. For the purposes of fraud prevention, the user would be required to authenticate the addition of the user device.
When a user adds a user device to the device list on the digital wallet account, the digital wallet application module on the user device transmits a setup request to the payment processing system. If not previously authorized, the user can enter security information to authorize the addition.
The user device can then be added to the device list on the digital wallet account. The device list can display the user device on the list with any additional identification or visual representations of the user device that are configured by the user or the digital wallet account. For example, the device list can display the user device phone number, serial number, username, or any suitable alias or identification provided by the user or others. The device list can display a picture or other representation of the user device, such as a picture of the model of the device based on provided model numbers. Any other suitable display or identification can be used to represent the user device on the device list.
The device list can display the status of the user device as active or any suitable description of the status.
The user may desire to remove a user device from the digital wallet account. The user may desire to disable a digital wallet application module from a particular user device if that user device is stolen, lost, or otherwise has the security of the user device compromised. The user may desire to remove a user device if the user device is being traded, sold, or replaced. The user may desire to remove a user device if the user device is no longer going to be used for digital transactions or for any other suitable reason.
The user can open the device list on a user interface of the digital wallet account in the manner employed to add a device. The user can access the digital wallet account by logging onto the payment processing system website online, using a digital wallet application module on a mobile communication device, or by using any other suitable user interface system.
The user can select a user device to remove from the list. The user can identify the desired user device by selecting the representation of the user device from the list. For example, the user can click on a picture of the user device on the user interface. The user can tap a username or identifier of the user device on the user interface. The user can state a verbal identification of the device to select the user device. Any other suitable manner of selecting the user device from the list can be employed.
When deactivation is initiated, the digital wallet user interface being utilized transmits the deactivation request to the payment processing system and the user device that is being deactivated. The payment processing system can receive the request and deactivate the user device from a list of active devices within the payment processing system. The payment processing system will no longer honor requests for transactions from the digital wallet application module operating on the deactivated user device.
In an example embodiment, the user device that is being deactivated on the device list is not contacted to disable the digital wallet application module because it is not currently connected to a communication network. The deactivation can occur when the user device next achieves network access. That is, when the user device is again turned on, returned to a service area, or otherwise achieves a network connection, the instructions can be transmitted at that time to the device to be deactivated. If the user device successfully communicates with the payment processing system server, then the digital wallet application module on the user device is deactivated and the digital wallet application module can no longer be utilized for transactions using the digital wallet account of the user. In an alternate embodiment, the digital wallet user interface being utilized for the deactivation or the payment processing system transmits the deactivation request directly to the user device that is being deactivated.
The digital wallet application module also can be removed from a user device that has been deactivated from the digital wallet account. In an example embodiment, the digital wallet account can transmit instructions to the user device to delete the digital wallet application module, to delete the digital wallet account information, to delete financial account information from the user device, or to delete any other suitable information that could be used to make the digital wallet application module operable with the digital wallet account of the user. Additionally or alternatively, the user can manually delete the digital wallet application module or other information from the user device.
When deactivation is initiated, the user interface will provide a clear indication to the user of what is happening, and what, if any, further action must be taken. The user interface displays to the user that the deactivation is successful or if the deactivation is in progress. For example, the user interface can display that a device is partially disabled.
In certain instances, a partially disabled state can be created when the payment processing system can be updated, but not the user device. When the digital wallet account is unable to contact the user device, the digital wallet application module on the user device cannot be deleted or disabled. Moreover, if the user has a stored value card on a user device that is partially disabled, then the user may still be vulnerable to charges on the stored value card, and the user will need to contact the issuer of the stored value card to disable the card. The user interface will display to the user that the digital wallet account will retry the deactivation button until a complete deactivation is achieved or the digital wallet account is requested to discontinue the deactivation.
If a user device has been deactivated on the digital wallet account at the payment processing system but the digital wallet application module on the user device has not been deactivated, a transaction might be attempted by a person in possession of the user device. For example, if a user device is stolen, the person with the stolen device may attempt a transaction. The payment processing system is notified of the transaction request. However, the payment processing system determines that the user requested to have the user device deactivated on the user device list. The payment processing system declines the transaction and attempts again to deactivate the digital wallet application module on the user device.
The user interface also can allow the user to remove any deactivated devices from the list of devices, or the removal can occur automatically. Devices that have been deactivated can appear in the list in a disabled state until the user manually deletes them. Additionally or alternatively, the user can leave the deactivated devices on the list of devices or store the deactivated devices in a list of deactivated or unused devices.
Additionally or alternatively, the deactivated device can remain on the list of devices but remain hidden from view until the user requests that hidden devices be displayed. In an example embodiment, devices that are marked hidden will not be shown, except when showing a historic device view is requested.
FIG. 1 is a block diagram depicting a system for managing devices associated with a digital wallet account, in accordance with certain example embodiments. As depicted in FIG. 1, the system 100 includes network devices 110 and 140 that are configured to communicate with one another via one or more networks 105.
Each network 105 includes a wired or wireless telecommunication means by which network devices (including devices 110 and 140) can exchange data. For example, each network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, a mobile telephone network, or any combination thereof. Throughout the discussion of example embodiments, it should be understood that the terms “data” and “information” are used interchangeably herein to refer to text, images, audio, video, or any other form of information that can exist in a computer-based environment.
Each network device 110 and 140 includes a device having a communication module capable of transmitting and receiving data over the network 105. For example, each network device 110 and 140 can include a server, desktop computer, laptop computer, tablet computer, a television with one or more processors embedded therein and/or coupled thereto, smart phone, handheld computer, personal digital assistant (“PDA”), or any other wired or wireless, processor-driven device. In the example embodiment depicted in FIG. 1, the network devices 110 and 140 are operated by end-users or consumers on user devices and payment processing system operators respectively.
The user 101 can use the communication application 112 on a user mobile device 110, such as a web browser application or a stand-alone application, to view, download, upload, or otherwise access documents or web pages via a distributed network 105. The network 105 includes a wired or wireless telecommunication system or device by which network devices (including devices 110 and 140) can exchange data. For example, the network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, storage area network (SAN), personal area network (PAN), a metropolitan area network (MAN), a wireless local area network (WLAN), a virtual private network (VPN), a cellular or other mobile communication network, Bluetooth, NFC, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages.
The communication applications 112 can interact with web servers or other computing devices connected to the network 105, including the point of sale terminal of the merchant system (not shown), the merchant server of a merchant system, the web server 141 of the payment processing system 140.
The user mobile device 110 may include a digital wallet application module 111. The digital wallet application module 111 can encompass any application, hardware, software, or process the user devices 110 can employ to assist the user 101 in completing a purchase. A digital wallet application module 111 can interact with a communication application 112 or can be embodied as a companion application of the communication application 112. As a companion application, a digital wallet application module 111 executes within a communication application 112. That is, a digital wallet application module 111 may be an application program embedded in a communication application 112.
The user mobile device 110 also includes a data storage unit 113 accessible by the digital wallet application module 111 and the communication application 112. The example data storage unit 113 can include one or more tangible computer-readable storage devices. The data storage unit 113 can be stored on the user mobile device 110 or can be logically coupled to the user mobile device 110. For example, the data storage unit 113 can include on-board flash memory and/or one or more removable memory cards or removable flash memory.
A user 101 can employ physical payment instrument 120 to initiate a transaction employing the digital wallet account 121, a proxy card account on the digital wallet account 121, a specified payment instrument operating on the digital wallet account 121, or any other payment instrument embodiment. In an example embodiment, a physical payment instrument 120 looks and/or functions in the same manner as a standard credit or debit card. For example, a physical payment instrument 120 may have the name of the user 101 and/or the account number of the user 101 listed on the front of the card. An example physical payment instrument 120 can include a magnetic stripe encoding the physical payment instrument account information of the user 101. In an example embodiment, the account information encoded in the magnetic stripe routes payment requests to the payment processing system 140 for processing.
In an alternative example embodiment, the physical payment instrument 120 can be a smartcard, RFID transmitter device, or any other suitable physical device capable of initiating a transaction with the digital wallet account of the user.
The user 101 may use the user mobile device 110 or user computing device to register the digital wallet application module 111, or the digital wallet account 121 and/or access the digital wallet account 121 account of the user 101. The user mobile device 110 may comprise appropriate technology that includes or is coupled to a web server (for example, a web browser application, or other suitable application for interacting with web page files).
The user 101 can use a web server 141 on the payment processing system 140 to view, register, download, upload, or otherwise access the payment processing system 140 via a website 142 and a communication network 105. The user 101 associates one or more registered payment instruments, including bank account debit cards, credit cards, gift cards, loyalty cards, coupons, offers, prepaid offers, peer-to-peer transaction accounts, store rewards cards, or other type of payment instrument that can be used to make a purchase or redeem value-added services with a digital wallet account 121 of the user 101. The payment processing system 140 also may function as the issuer for the associated financial payment instrument. The user's registration information is provided to the payment processing system 140. The user 101 also may use the web server 141 to define payment rules.
The user 101 may request a purchase from the merchant system (not pictured). In an example embodiment, the purchase is initiated by a wireless “tap” of the mobile device 110 with the POS terminal. In an alternative example embodiment, the purchase is initiated when the user 101 enters an account identification number at the POS terminal or in the user device 110. In another alternative example embodiment, the purchase is initiated online with the merchant server. The purchase may be initiated via the merchant website. In yet another alternative example embodiment, the purchase is initiated by use of a permanent/temporary virtual/physical token, QR code, bar code, or other suitable machine-readable medium captured by the terminal reader. The merchant's POS terminal can interact with an acquirer (or other third party payment processing companies), the card network, the proxy card system 140, and the payment instrument issuer.
The components of the example operating environment 100 are described hereinafter with reference to the example methods illustrated in FIGS. 2-3.
FIG. 2 is a block flow diagram depicting a method 200 for adding a user device 110 to a digital wallet account 121, in accordance with certain example embodiments.
In block 205, the user 101 selects a user device to add to a digital wallet account. User devices 110 that the user 101 may desire to add to the digital wallet account 121 can include any of the user devices 110 describe previously including, desktop computer, laptop computer, tablet computer, a television with one or more processors embedded therein and/or coupled thereto, smart phone, handheld computer, personal digital assistant (“PDA”), or any other wired or wireless, processor-driven device. The digital wallet account 121 may be represented on a user device 110 as a digital wallet application module 111, a digital wallet application operating on a website or server, a representation on a user interface of the payment processing system 140, or any other suitable embodiment of the digital wallet account 121.
Additionally or alternatively, the user 101 selects a physical payment instrument 120 or other physical tool for conducting transactions, such as a smartcard, RFID device, to add to a digital wallet account. For example, the physical payment instrument 120 may be card for accessing a proxy card account of the user 101. Throughout the specification, “digital wallet application module 111” will be intended to encompass all embodiments of the digital wallet account on user devices 110, including physical payment instruments 102. Additionally, “user devices 110” will be intended to encompass all suitable devices used to host a digital wallet account 121 embodiment, including physical payment instruments 102.
In block 210, the user installs a digital wallet application module 111 on a user device 110. The digital wallet application module 111 can be downloaded from a web server such as the web server 141 of the payment processing system 140. The digital wallet application module 111 may come installed on a new user device 110. The digital wallet application module 111 can be obtained from any other suitable source, such as a website on the Internet or a portable storage device such as a flash drive.
In block 215, the user device 110 transmits a setup request to the payment processing system 140. A request for adding a user device 110 is required when a digital wallet application module 111 is first installed and after each reset. Thus, the first activation is when the digital wallet application module 111 is first set up on the user device 110. A subsequent reset and re-activation of the digital wallet application module 111 will be considered a new activation. In an example embodiment, re-activation of a deactivated device 110 is performed by reinstalling and setting up the digital wallet application module 111 on the user device 110. In an example embodiment, the user 101 may be required to re-enter financial payment card information.
The digital wallet application module 111 can be installed on a user device 110 before being associated with a digital wallet account 121.
In block 220, the digital wallet application module 111 on the user device 110 is authorized by the user 101. In an example embodiment the user 101 must enter an authorization for the setup to be initiated by the payment processing system 140. That is, the payment processing system 140 can require a username and password, or other suitable authorization protocol, to begin the setup process for the digital wallet application module 111. In alternate example embodiments, the authorization of the user 101 can be required at any point of the setup process, such as before the installation of the digital wallet application module 111 or after the setup process has begun.
In block 225, the user device 110 is added to the list of devices on the digital wallet account 121. In an example embodiment, a page on a user interface of the digital wallet account 121 provides a listing of user devices associated with the digital wallet account 121. The device listing will indicate the enabled user devices 110 that the user owns and the activation state of each user device 110. The device list contains all of the information required to render a virtual representation of the user device 110 to the user 101. For example, the device list may show information indicating the device status such as the device 110 name, the activation date, the last time a transaction was initiated, the activation status, a device image, an option to deactivate any active devices 110, an option to retry a deactivation if a previous attempt did not complete, and any other suitable displays or options.
In an example embodiment, the user 101 can access the digital wallet account 121 by logging onto the payment processing system website 142 online, using a digital wallet application module 111 on a mobile user communication device such as a user device 110, or by using any other suitable user interface system. The user 101 may retrieve the status of all devices linked to the digital wallet account.
The user 101 can select a user device 110 to add to the digital wallet account 121 by adding the user device 110 details into a user interface on the digital wallet account 121. For example, the user 101 can enter the phone number to a mobile user device 110 and the digital wallet account 121 can locate the appropriate user device 110 over the network 105, via email, over a wired network, or via any other suitable manner. The user 101 can select the user device 110 from a list of devices associated with the user 101. The user 101 can select a user device 110 from a list of inactive devices. Any other suitable manner of selecting user devices to add to the digital wallet account can be employed.
If the digital wallet account 121 attempts to set up a new user device 110 that has not had the digital wallet application module 111 installed, then the digital wallet 121 can initiate installation. For example, the digital wallet account 121 can transmit the digital wallet application module to the user device. In another example, the user device can locate the digital wallet application on the Internet and download the application. Any other method can be utilized to install the digital wallet application module 111.
The device list can display the user device 110 with any additional identification or visual representations of the user device 110 that are configured by the user 101 or the digital wallet account 121. For example, the device list can display the user device phone number, serial number, username, or any suitable alias or identification provided by the user or others. The device list can display a picture or other representation of the user device 110, such as a picture of the model of the user device 110 based on provided model numbers. Any other suitable display or identification can be used to represent the user device on the device list.
FIG. 3 is a block flow diagram depicting a method 300 for removing a user device 110 from a digital wallet account 121, in accordance with certain example embodiments.
The user 101 can select a user device 110 that the user 101 no longer wants to have associated with the digital wallet account 121. The user can desire to remove a user 110 device if the device is stolen, lost, or otherwise has the security of the user device 110 compromised. The user 101 can desire to remove a user device 110 if the user device 110 is being traded, sold, or replaced. The user 101 can desire to remove a user device 110 if the user device 110 is no longer going to be used for digital transactions or for any other suitable reason.
In block 310, the user 101 can open the device list on a user interface of the digital wallet account 121 in the manner employed to add a user device 110. The user can access the digital wallet account 121 by logging onto the payment processing system website 142 online, using a digital wallet application module 111 on a user device 110, or by using any other suitable user interface system associated with the digital wallet account 121.
In block 315, the user 101 can select a user device 110 to remove from the device list. The user 101 can identify the desired user device 110 by selecting the representation of the user device 110 from the list. For example, the user 101 can click on a picture of the user device 110 on the user interface. The user 101 can tap a username or identifier of the user device 110 on the user interface. The user 101 can state a verbal identification of the user device 110 to select the device. Any other suitable manner of selecting the user device 110 from the list can be employed.
In block 320, the digital wallet account 121 deactivates the user device 110. When deactivation is initiated, the digital wallet account 121 user interface being utilized transmits the deactivation request to the payment processing system 140 and the user device 110 that is being deactivated. The payment processing system 140 can receive the request and deactivate the user device 110. The payment processing system 140 will no longer honor requests for transactions from the digital wallet application module 111 operating on the user device.
In an example, a transaction is attempted with the digital wallet application module 111 of a user device 110 that has been deactivated on the payment processing system 140. The payment processing system 140 can receive a transaction request and recognize that the user device 110 being used in the transaction has been deactivated by the user 101. The payment processing system 140 can recognize an identity of the user device 110 or other identifier included in the transaction details. When the payment processing system 140 recognizes an identity of a deactivated user device 110, the payment processing system 140 can refuse the transaction. The payment processing system 140 can additionally alert the user 101, the digital wallet account 121, or other party of the attempted transaction for the purposes of fraud prevention.
The digital wallet account 121 user interface being utilized to deactivate a user device 110 transmits the deactivation request to the user device 110 that is being deactivated. If the user device 110 is successfully contacted, then the user device 110 is deactivated and the digital wallet application module 111 can no longer be utilized for transactions using the digital wallet account 121 of the user 101.
In block 325, the digital wallet application module 111 is removed from the user device 110 that has been deactivated. Upon receiving the deactivation request from the digital wallet account 121, the digital wallet application module 111 can disable the account of the user on the digital wallet application module 111 by executing the instructions provided by the digital wallet account 121. Additionally or alternatively, the digital wallet application module 111 can be removed from a user device 110 that has been deactivated from the digital wallet account 121 by executing the instructions provided by the digital wallet account 121. In an example embodiment, the digital wallet account 121 can transmit instructions to the user device 110 to delete the digital wallet application module 111, to delete the digital wallet account information, to delete financial account information from the user device 110, or to delete any other suitable information that can be used to make the digital wallet application module 111 operable with the digital wallet account 121 of the user. Upon receipt, the digital wallet application module 111 can execute the instructions. Additionally or alternatively, the user 101 can manually delete the digital wallet application module 111 or other information from the user device 110.
If the digital wallet account 121 is unable to contact the user device 110 at the time of deactivation, then the deactivation can occur when the user device 110 next achieves network access. That is, when the user device 110 is again turned on, returned to a service area, or otherwise achieves a network connection, the instructions can be transmitted at that time.
In certain instances, the user device 110 may be partially disabled. A partially disabled state can be created when the payment processing system 140 can be updated, but not the user device 110. When the digital wallet account 121 is unable to contact the user device 110, the digital wallet application module 111 on the user device cannot be deleted or disabled. Moreover, if the user 101 has a stored value card on a user device 110 that is partially disabled, then the user 101 may still vulnerable to charges on the stored value card, and the user 101 will need to contact the issuer of the stored value card to disable the card. The user interface will display to the user 101 that the digital wallet account 121 will retry the deactivation button until a complete deactivation is achieved or the digital wallet account 121 is requested to discontinue the deactivation.
In block 330, the user interface shows the status of the deactivation of the user device 110. The user interface will provide a clear indication to the user of what is happening, and what, if any, further action must be taken. The user interface displays to the user that the deactivation is successful, if the deactivation is in progress, if the user device 110 has been partially disabled, or any other suitable status.
The user interface will also allow the user 101 to remove any deactivated user devices 110 from the list of devices, or the removal can occur automatically. User devices 110 that have been deactivated can appear in the list in a disabled state until the user 101 manually deletes them. Additionally or alternatively, the user 101 can leave the deactivated devices on the list of devices or store the deactivated user device 110 in a list of deactivated or unused devices.
Additionally or alternatively, the deactivated user device 110 can remain on the list of devices but remain hidden from view until the user 101 requests that hidden devices be displayed. In an example embodiment, user devices 110 that are marked hidden will not be shown, except when showing a historic device view is requested.
If a user device 110 has been deactivated on the digital wallet account 121 at the payment processing system 140 but not the digital wallet application module 111 on the user device 110 has not been deactivated, a transaction can be attempted by a person in possession of the user device 110. For example, if a user device 110 is stolen, the person with the stolen user device 110 may attempt a transaction. The payment processing system 140 is notified of the transaction request. However, the payment processing system 140 determines that the user 101 requested to have the user device 110 deactivated on the user device list. The payment processing system 140 declines the transaction and attempts again to deactivate the digital wallet application module 111 on the user device.
in response to receiving the transaction request from the particular mobile computing device and in response to determining that the particular mobile computing device is deactivated, instructing, using the one or more computing devices and to the particular mobile computing device, the particular mobile computing device to delete an application associated with the digital wallet account on the particular mobile computing device.
2. The computer-implemented method of claim 1, wherein the list of associated mobile computing devices is presented via a user interface of an application executing on a mobile computing device.
3. The computer-implemented method of claim 1, wherein the deactivated mobile computing device is removed from the list of associated mobile computing devices.
4. The computer-implemented method of claim 1, wherein the particular mobile computing device comprises a magnetic stripe card, an RFID device, a smartcard, or an account identifier capable of being scanned.
5. The computer-implemented method of claim 1, wherein the digital wallet account is managed by a payment processing computing system.
computer-readable program instructions to communicate to the particular user computing device, in response to receiving the transaction request and determining that the particular user computing device is deactivated, instructions instructing the particular user computing device to delete an application associated with the digital wallet account on the particular user computing device.
7. The computer program product of claim 6, wherein the deactivating of the particular user computing device comprises logging the particular user computing device as deactivated such that the transaction request comprising an identification of the particular user computing device will be rejected.
8. The computer program product of claim 6, wherein the list of associated user computing devices is presented via a user interface of an application on a user computing device.
9. The computer program product of claim 6, further comprising computer-readable program instructions to present, at a time after deactivating the particular user computing device, a deactivated status of the particular user computing device.
10. The computer program product of claim 6, wherein the particular user computing device comprises a mobile computing device, a magnetic stripe card, an RFID device, a smartcard, or an account identifier capable of being scanned.
communicate, to the particular user computing device, in response to receiving the transaction request and determining that the particular user computing device is deactivated, instructions instructing the particular user computing device to delete an application associated with the digital wallet account on the particular user computing device.
12. The system of claim 11, wherein the processor is further configured to execute application code instructions to cause the system to present, at a time after deactivating the particular user computing device, a deactivated status of the particular user computing device.
13. The system of claim 11, wherein the deactivating of the particular user computing device comprises logging the particular user computing device as deactivated such that a payment authorization request comprising an identification of the particular user computing device will be rejected.
"Chinese Office Action issued in Chinese Application No. 201380050257.1", dated Oct. 31, 2017, 06 pages of English Translation and 06 pages of Chinese Office Action.
"Chinese Office Action issued in Chinese Application No. 201480035608.6", dated Aug. 14, 2017, 6 pages of English Translation and 6 pages of Chinese Office Action.
"Chinese Office Action issued in Chinese Application No. 201480035608.6", dated Feb. 11, 2018, 5 pages of English Translation and 4 pages of Chinese Office Action.
"International Preliminary Report on Patentability and Written Opinion Received for PCT Patent Application No. PCT/US2012/060442, dated May 15, 2014,", 18 pages.
"International Preliminary Report on Patentability and Written Opinion Received for PCT Patent Application No. PCT/US2012/060445, dated May 15, 2014,", 14 pages.
"International Preliminary Report on Patentability and Written Opinion Received for PCT Patent Application No. PCT/US2013/060189, dated Apr. 2, 2015," 14 pages.
"International Search Report and Written Opinion of the International Searching Authority for International Pat. Application No. PCT/US2013/028697, dated May 23, 2013," 8 pages.
"International Search Report and Written Opinion of the International Searching Authority for International Patent Application No. PCT/US2013/033467, dated Jul. 4, 2013," 8 pages.
"International Search Report and Written Opinion of the International Searching Authority for International Patent Application No. PCT/US2013/035406, dated Jul. 19, 2013," 8 pages.
"International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/060442, dated Jan. 28, 2013,", 11 pages.
"International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/060445, dated Jan. 28, 2013," 10 pages.
"International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/060189, dated Nov. 22, 2013," 9 pages.
"Notice of Allowance received for Japanese Patent Application No. 2014-538836, dated Apr. 20, 2015," 3 pages Japanese NOA only.
"Notice of Allowance received for U.S. Appl. No. 13/653,145, dated Aug. 19, 2014," 8 pages.
Aconyte Smart Solutions, "Mobile Application Management", May 1, 2012, XP055050399, 6 pages.
Author: Campen, K., Title: Office Action issued in copending U.S. Appl. No. 13/545,702, filed Jul. 10, 2012, pp. 1-14, dated Jun. 17, 2013.
Author: Colbert, E., Title: Office Action issued in copending U.S. Appl. No. 13/759,003, filed Feb. 4, 2013, pp. 1-24, dated Jun. 6, 2013.
Author: Johnson, G., Title: Office Action issued in copending U.S. Appl. No. 13/717,295, filed Dec. 17, 2012, pp. 1-13, dated Feb. 28, 2013.
Author: Kim, T., Title: International Search Report and Written Opinion issued in International Application No. PCT/US2013/052708, pp. 1-10, dated Nov. 19, 2013.
Author: Nguyen, L., Title: Office Action issued in copending U.S. Appl. No. 13/784,808, filed Mar. 4, 2013, pp. 1-20, dated Jul. 15, 2013.
Author: Quittner, Jeremy, Title: PayPal Seeks to Cut Out Card Companies with New Plastic, Publ: Bank Technology News , pp. 2, date Oct. 18, 2011.
Author: Shaikh, M., Title: Office Action issued in copending U.S. Appl. No. 13/802,705, filed Mar. 13, 2013, pp. 1-11, dated Jul. 18, 2013.
Author: Ziegle, S. Title: Office Action issued in copending U.S. Appl. No. 13/658,783, filed Oct. 23, 2012, pp. 1-14, dated Jul. 11, 2013.
Author: Ziegle, S., Title: Office Action issued in copending U.S. Appl. No. 13/658,783, filed Oct. 23, 2012, pp. 1-14, dated Mar. 5, 2013.
Bai, "International Preliminary Report on Patentability issued in International Application No. PCT/US2013/052708", dated Feb. 12, 2015, 7 pages.
De Pol, "Australian Office Action issued in Australian Application No. 2016203535", dated Mar. 15, 2017 2 pages.
Feng, "Chinese Office Action issued in Chinese Application No. 201280059706.4", dated Jun. 24, 2016, 3 pages of English Translation and 5 pages of Chinese Office Action.
Finextra Research, "Aconite launches Mobile Application Management", Oct. 26, 2011, XP055050391, 2 pages.
Gee, "U.S. Notice of Allowance issued in copending U.S. Appl. No. 14/487,433, filed Sep. 16, 2014", dated Dec. 9, 2015, 9 pages.
Gee, "U.S. Office Action issued in copending U.S. Appl. No. 14/487,433, filed Sep. 16, 2014, dated Aug. 17, 2015", 19 pages.
Gee, "U.S. Office Action issued in copending U.S. Appl. No. 14/487,433, filed Sep. 16, 2014, dated May 8, 2015", 14 pages.
Gee, "U.S. Office Action issued in copending U.S. Appl. No. 15/073,064, filed Mar. 10, 2015", dated Apr. 3, 2017, 17 pages.
Global Platform Inc., "Global Platform-Card Specification," Global Platform Inc., version 2.1.1, Mar. 2003, pp. 1-237.
Global Platform Inc., "Global Platform's Proposition for NFC Mobile: Secure Element Management and Messaging," GlobaiPiatform Inc., Apr. 2009, pp. 1-36.
Global Platform Inc., "Global Platform—Card Specification," Global Platform Inc., version 2.1.1, Mar. 2003, pp. 1-237.
GlobalPlatform Inc., "GlobalPlatform Card Contactless Services Card Specification v2.2-Amendment C", GlobalPlatform Inc., version 1.0., Feb. 2010, pp. 1-77.
GlobalPlatform Inc., "GlobalPlatform-Card Specification," GlobalPlatform Inc., version 2.2, Mar. 2006, pp. 1-375.
GlobalPlatform Inc., "GlobalPlatform Card Contactless Services Card Specification v2.2—Amendment C", GlobalPlatform Inc., version 1.0., Feb. 2010, pp. 1-77.
GlobalPlatform Inc., "GlobalPlatform—Card Specification," GlobalPlatform Inc., version 2.2, Mar. 2006, pp. 1-375.
Kim, "Korean Office Action issued in Korean Application No. 10-2014-7014377 dated Sep. 24, 2014", 3 pages of English Translation and 3 pages of Korean Office Action.
Lau, "Canada Office Action issued in Canada Application No. 2854276 dated Aug. 26, 2015", 4 pages.
Lau, "Canada Office Action issued in Canada Application No. 2854277 dated Nov. 21, 2014", 5 pages.
Lau, "Canada Office Action received for Canada Patent Application No. 2,854,276", dated Feb. 13, 2018, 4 pages.
Lee, "Korean Office Action issued in Korean Application No. 10-2014-7035460, dated Jul. 30, 2015", 6 pages of Korean Office Action only.
Louie, "U.S. Office Action issued in copending U.S. Appl. No. 13/653,145, filed Oct. 16, 2012, dated Jun. 17, 2013", 7 pages.
Louie, "U.S. Office Action issued in copending U.S. Appl. No. 13/653,145, filed Oct. 16, 2012, dated May 2, 2014", 9 pages.
Louie, "U.S. Office Action issued in copending U.S. Appl. No. 13/653,145, filed Oct. 16, 2012, dated Oct. 25, 2013", 8 pages.
McCosker, "Australian Office Action issued in Australian Application No. 2012332956 dated Apr. 20, 2015", 3 pages.
MX/A/2014/005180, "Office Action received for Mexican Patent Application No. MX/a/2014/005180, dated Jul. 10, 2015,", 2 pages.
Nakazato, "apanese Office Action issued in Japanese Application No. 2014-538837 dated Apr. 27, 2015", 12 pages of English Translation and 11 pages of Japanese Office Action.
Nakazato, "Japanese Office Action issued in Japanese Application No. 2014-538837 dated Oct. 5, 2015", 6 pages of English Translation and 6 pages of Japanese Office Action.
Nega, "U.S. Office Action issued in copending U.S. Appl. No. 13/653,160, filed Oct. 16, 2012, dated Oct. 21, 2014", 10 pages.
Ng, "Australian Office Action issued in Australian Application No. 2015234304 dated Nov. 17, 2015", 3 pages.
Nora, "International Preliminary Report on Patentability issued in International Application No. PCT/US2014/016922", dated Dec. 3, 2015, 7 pages.
Notice of Allowance received for Korean Patent Application No. 10-2014-7014377, dated Jan. 22, 2015, 1 pages of English Translation and 2 pages of Korean NOA.
Omogbenigun, "Australian Office Action issued in Australian Application No. 2013318245 dated Aug. 14, 2015", 3 pages.
Omogbenigun, "Australian Office Action issued in Australian Application No. 2013318245 dated Jul. 8, 2015", 3 pages.
Roberti, "Extended European Search Report issued in European Application No. 14800349.4", dated Dec. 15, 2016, 9 pages.
Shingles, "U.S. Office Action issued in copending U.S. Appl. No. 14/029,463, filed Sep. 17, 2013", dated Dec. 3, 2015, 8 pages.
Tsujimoto, "Japanese Office Action issued in Japanese Application No. 2014-538837", dated Sep. 25, 2017, 03 pages of English Translation and 03 pages of Japanese Office Action.
U.S. Appl. No. 13/545,702 to Weksler filed Jul. 10, 2012.
U.S. Appl. No. 13/658,783 to Mizhen et al. filed Oct. 23, 2012.
U.S. Appl. No. 13/717,295 to Kunz et al. filed Dec. 17, 2012.
U.S. Appl. No. 13/728,619 to Kunz et al. filed Dec. 27, 2012.
U.S. Appl. No. 13/759,003 to Andrews et al. filed Feb. 4, 2013.
U.S. Appl. No. 13/784,808 to Blandina et al. filed Mar. 4, 2013.
Vergas, "Mexican Office Action issued in Mexican Application No. MX/a/2014/005181", dated May 20, 2016, 2 pages of English Translation and 2 pages of Mexican Office Action.
Weidmann, "Extended European Search Report issued in European Application No. 13825094.9", dated Dec. 9, 2015, 8 pages.
Woldemariam, "U.S. Office Action issued in copending U.S. App. No. 15/279,975, filed Sep. 29, 2016", dated Aug. 10, 2017, 15 pages.
Woldemariam, "U.S. Office Action issued in copending U.S. Appl. No. 14/183,137, filed Feb. 18, 2014", dated Nov. 4, 2015, 10 pages.
Woldemariam, "U.S. Office Action issued in copending U.S. Appl. No. 15/279,975, filed Sep. 29, 2016", dated Jan. 23, 2018, 12 pages.
Woldemariam, "U.S. Office Action issued in copending U.S. Appl. No. 15/481,420, filed Apr. 6, 2017", dated Aug. 23, 2017, 12 pages.
Woldemariam, "U.S. Office Action issued in copending U.S. Appl. No. 15/481,420, filed Apr. 6, 2017", dated Jan. 24, 2018, 10 pages.
Yang, "International Search Report and Written Opinion issued in International Application No. PCT/US2014/016922", dated Jun. 24, 2014, 8 pages.
Yliuntinen, "3rd Party TSM Management of SIM Cards", [online], Sep. 12, 2011, 4 pages.
Yoon, "Korean Office Action issued in Korean Application No. 10-2017-7021176", dated Aug. 21, 2017, 4 pages of English Translation and 3 pages of Korean Office Action.
Zhou, "Chinese Office Action issued in Chinese Application No. 201380050257.1", dated Mar. 1, 2017, 9 pages of English Translation and 8 pages of Chinese Office Action.

References: Application No. 61
 Application No. 201380050257
 Application No. 201480035608
 Application No. 201480035608
 Application No. 2014
 Application No. 2016203535
 Application No. 201280059706
 Application No. 10
 Application No. 2854276
 Application No. 2854277
 Application No. 2
 Application No. 10
 Application No. 2012332956
 Application No. 2014
 Application No. 2014
 Application No. 2015234304
 Application No. 10
 Application No. 2013318245
 Application No. 2013318245
 Application No. 14800349
 Application No. 2014
 Application No. 13825094
 Application No. 10
 Application No. 201380050257