Synchronous interfacing with unaffiliated networked systems to alter functionality of sets of electronic assets

Description

TECHNICAL FIELD

Embodiments of the present disclosure relate to systems and methods for transforming functionality of sets of electronic assets via interface calls using corresponding sets of networked computing interfaces.

BACKGROUND

A person may carry—in a wallet, purse, bag, or other “carrier”—a collection of many different kinds of electronic “assets” (e.g., several credit and debit cards, remote access keys such as radio-frequency identification (RFID) cards, gift cards, fobs, and other identifications). In some instances, the assets are serviced by many different issuers (e.g., several unaffiliated banks, businesses, and organizations). If the person loses the carrier, he/she may wish to deactivate all the assets in that carrier while he/she looks for the carrier to avoid fraudulent or otherwise unauthorized use of the electronic assets. This is normally achieved by contacting each individual third-party issuer of the electronic assets, such as by using a website or application of each issuer or contacting each issuer by telephone. Additionally, each issuer may have its own process for preventing fraudulent use of the asset that is different from other issuers, making this a relatively slow and cumbersome process at a time when the person is already distraught from the loss of the carrier. Moreover, a person may not remember exactly what assets were in the particular carrier when it was lost, making the process even more frustrating.

SUMMARY

Various embodiments relate to a method that includes providing, by a processor of a computing system through a telecommunications network, to a remote user computing device that includes an input device configured to detect at least one of biometric data, alphanumeric entries, or icon selections, a portal with a network security access control. The method includes receiving, by the processor, via the network security access control of the portal, login credentials detected using the input device of the user computing device, and in response to receiving the login credentials, determining, by the processor, that the login credentials are associated with a set of electronic assets corresponding to a plurality of third-party computing systems with application programming interface (API) gateways, where each of the API gateways is configured to accept an API call directed to changes in functionality of the electronic assets. The method includes presenting, by the processor, via the portal, a virtual icon configured to be selectable using the input device to identify a coordinated action with respect to all electronic assets in the set of electronic assets. The method further includes accepting, by the processor, via the portal, selection of the virtual icon detected using the input device of the user computing device, and in response to accepting the selection via the portal, executing, by the processor, a set of API calls that include an asset-specific API call to each third-party computing system in the plurality of third-party computing systems to implement the coordinated action on all electronic assets in the set of electronic assets.

Various embodiments relate to a computing system having a processor and a memory storing executable code. The executable code causes the computing system, when executed, to (i) provide, via an internet connection, to a user computing device that includes an input device configured to detect at least one of biometric data, alphanumeric entries, or icon selections, a portal with a network security access control; (ii) receive, via the network security access control of the portal, login credentials detected using the input device of the user computing device; (iii) in response to receiving the login credentials, determine that the login credentials are associated with a set of electronic assets corresponding to a plurality of third-party computing systems with application programming interface (API) gateways configured to accept API calls directed to changes in functionality of the electronic assets, (iv) present, via the portal, a virtual icon configured to be selectable using the input device to identify a coordinated action with respect to all electronic assets in the set of electronic assets; (v) accept, via the portal, selection of the virtual icon detected using the input device of the user computing device; and (vi) in response to accepting the selection via the portal, execute a set of API calls including an asset-specific API call to each third-party computing system in the plurality of third-party computing systems to implement the coordinated action on each corresponding electronic asset in the set of electronic assets.

Various embodiments relate to a method that includes presenting, on a display of a mobile device, a graphical user interface (GUI), where the mobile device includes an input device configured to detect at least one of alphanumeric entries, icon selections, or image data. The method also includes receiving, by a processor from the input device, a plurality of asset definitions for a set of electronic assets, each asset definition including a third-party identifier that is indicative of a respective one of a plurality of third-party computing systems. The method also includes identifying, via the processor, the plurality of third-party computing systems based on the plurality of third-party identifiers, and presenting, by the display, via the GUI, a virtual icon configured to be selectable using the input device to identify a coordinated action with respect to all electronic assets in the set of electronic assets. The method further includes receiving, by the processor, selection of the virtual icon from the input device, and in response to the selection, transmitting, via a transceiver of the mobile device, the selection to a remote computing system to implement the coordinated action on each corresponding electronic asset in the set of electronic assets.

These and other features, together with the organization and manner of operation thereof, will become apparent from the following detailed description when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of an electronic asset management system, according to an example embodiment.

FIG. 2 is a block diagram of a user computing device, according to an example embodiment.

FIG. 3 is a flow diagram of a method of managing a set of electronic assets, according to an example embodiment.

FIG. 4 is an example interface for a user computing device, according to an example embodiment.

FIG. 5 is a flow diagram of a method of populating a set of electronic assets into an electronic asset management system, according to an example embodiment.

FIGS. 6 and 7 are example interfaces for a user computing device, according to various example embodiments.

FIG. 8 is a flow diagram of a method of implementing a coordinated action on a set of electronic assets based on a travel plan, according to an example embodiment.

FIG. 9 is an example interface for a user computing device, according to another example embodiment.

DETAILED DESCRIPTION

Referring to the figures generally, systems, methods, and apparatuses for managing groupings of electronic assets synchronously and from a single location (e.g., a central location, portal, etc.) are described. In particular, systems, methods, and apparatuses for taking specific coordinated action across a grouping of assets consisting of assets that are independently managed through multiple unaffiliated networked systems are described.

Existing third-party issuers of electronic identification cards and other electronic assets, such as government entities and financial institutions (e.g., banks), require clients to connect with them directly when changes to the operating status of the asset is desired. For example, in a situation where a person loses their wallet or purse, the person may wish to freeze and/or cancel any electronic access or identification cards that were carried in the purse to prevent fraudulent transactions. This process requires the person to notify each individual third-party issuer to take the required action. If the wallet or purse is ultimately deemed permanently lost, the person may wish to receive replacement assets. In that case, the cumbersome process of notifying each individual issuer needs to be repeated (if the assets were previously deactivated), or started anew (if assets were not previously deactivated, making the cumbersome process unavoidable). This process may be further complicated by different security protocols or procedures used by the various, unaffiliated third-party issuers that are responsible for the electronic assets. If a person is away from home or traveling internationally, the process of connecting with each issuer may be logistically complicated by differing communications networks. While some third-party issuers offer services to cancel and/or freeze cards over the internet, none offer a secure and efficient system for synchronously controlling sets and/or groupings of electronic assets from multiple unaffiliated networked systems from a single location.

In other situations, a person may wish to engage in some activity that affects multiple electronic assets from different third-party issuers at the same time, such as travel. In these situations, the person may only want to impose restrictions on (e.g., deactivate or limit usability thereof), remove restrictions from (e.g., authorize international transactions), or otherwise alter the functionality of, a grouping of assets because of their travel plans.

Referring generally to the figures, a system for managing sets and/or groupings of electronic assets from multiple, unaffiliated third-party issuers is described. In particular, the system provides a selection tool that allows a user to alter the functionality of all of the assets within a single grouping synchronously (e.g., in parallel, simultaneously, at the same time, etc.). The electronic assets may be payment items such as credit cards, debit cards, gift cards, or non-payment items such as identification cards and electronic access keys. The assets may be grouped within the system based on how they are physically carried. For example, a single grouping of assets may be contained within the same physical carrier (e.g., purse, wallet, etc.). A first grouping of electronic assets may be a grouping of credit cards, debit cards, RFID cards, and other electronically managed identification cards that are contained within a person's wallet. A second grouping of electronic assets may a grouping of credit cards, gift cards, and other electronically managed identification cards that are contained within the person's money clip that is used separately from the wallet or purse (e.g., for different occasions, under different circumstances, etc.). The wallet and the money clip may include different groupings of credit cards, and/or identification cards. When the person is using their wallet, he/she can use the system to quickly deactivate, freeze, or otherwise restrict the use of the second grouping of electronic assets (in the money clip) to protect the assets when not in use, without having to engage with multiple third-party issuers. In the event that the wallet and/or money clip becomes lost, the person can use the system to identify which electronic assets are affected by the loss, and to deactivate, restrict, or otherwise alter all of the electronic assets within the first or second groupings at the same time (and with a single selection). Actions may be performed in a “single click” fashion to simplify control over multiple assets.

In one embodiment, the system uses a set of application programming interfaces (APIs) to communicate the desired changes in functionality to the different, unaffiliated third-party issuers. For example, each third-party issuer may be provided with its own API to allow it to implement different functions for the assets they support. Upon receiving a selection to modify the functionality of a grouping of assets, the system executes an asset-specific API call to each of the third-party computing systems to implement the desired change. Among other benefits, the use of multiple APIs allows the system to adapt to different policies that may be used between different third-party issuers (e.g., different policies for altering the functionality of electronic assets in the same way). Additionally, the use of multiple APIs that can be executed in parallel is more efficient that other methods of coordinated control.

The system is also configured to facilitate recognition and grouping of the electronic assets. For example, the system can be configured to scan each of the electronic assets (e.g., cards, etc.) using a sensor of a mobile device, and to automatically recognize and the third-party issuer that supports (e.g., manages, funds, etc.) the asset. In particular, in various embodiments, the system may be configured to convert image data that is obtained from the scan to machine readable text, and match the text with the API that corresponds to the asset. In certain embodiments, the sensor is a magnetic reader, or another form of integrated sensor/reader. In various embodiments, the system is configured to identify at least one electronic asset through wireless communications between the mobile device 200 and the electronic asset. Each API, electronic assets, mobile device, etc., may have a corresponding unique identifier (e.g., an API identifier, an asset identifier, a device identifier) that is generated or obtained by the system, and identifiers may be linked or paired so as to associate the identifiers and indicate that the corresponding API, asset, device, etc. correspond to each other. Among other benefits, the automated recognition and integration of electronic assets from different third-party issuers greatly reduces the time required to input different electronic assets into the system, and reduces the risk of pairing electronic assets with incorrect APIs.

In one embodiment, the system serves, provides, or otherwise includes a portal (e.g., an internet portal that is accessible via an internet browser, an application running on a mobile device, etc.) that is configured to maintain asset information, and to facilitate user control of groupings of electronic assets. The portal may include a network security access control to prevent fraudulent access to the groupings of assets. The portal may allow the user to take a set of actions, in batch, on a grouping of assets (e.g., turn off and replace all electronic assets grouped in “wallet”). The portal may also provide notifications from other third-party issuers, prompting the user to take any additional steps that are needed with individual third-party issuers to implement the requested actions. In one embodiment, the portal may automatically redirect the user to other applications (e.g., sponsored by one or more third-party issuers) to complete the requested actions.

In one embodiment, the portal may be implemented as part of the operating system of a user's mobile device to facilitate more rapid selection of the desired actions. For example, a selection tool may be integrated into a shortcuts screen or through interaction with an application icon that corresponds to the portal. For example, in order to select a certain action with respect to a grouping of electronic assets, the user may select and hold the application icon (e.g., on a touchscreen display) for a threshold period and/or make a selection from a shortcut menu that opens after pressing the application icon for the threshold period.

The system can also perform other more complex actions with respect to one or more groupings of electronic assets. For example, the portal may include a travel planner that allows the user to enter information on locations, dates, and other travel-related information to selectively control pre-defined groupings of assets (e.g., to identify a set of actions, pre-authorizations, or restrictions to be taken with respect to the pre-defined grouping of assets). In this way, a user can notify the third-party issuers about anticipated travel plans, to reduce the risk of the third-party issuers inadvertently locking/freezing funds or other electronic assets used due to use of the assets outside of the area where the user resides.

As used herein, the term “electronic asset” or “asset” refers to any form of user and/or user account identification that can be remotely activated, deactivated, restricted, or otherwise altered. For example, electronic assets may refer to payment items/vehicles such as payment cards (e.g., credit cards, charge cards, ATM cards, debit cards, stored-value cards such as gift cards, fleet cards, etc.), checks, and money orders. Additionally, electronic assets may refer to non-payment items such as electronic identification cards, security access devices (e.g., key cards, RFID access cards, etc.), and the like.

Referring to FIG. 1, a view of an electronic asset management system 100 is shown according to an example embodiment. As described below in further detail, the electronic asset management system 100 facilitates the sharing and management of groupings/sets of electronic assets associated with a user. The system 100 includes a primary institution 102, at least one third-party computing system 104, and at least one user computing device 106. The electronic asset information can include asset definitions that identify the asset (e.g., account numbers, labels/identifiers for third-party issuers, etc.), transaction and/or use history of the electronic asset (e.g., account balances, transaction information, bill due dates, etc.), and grouping definitions that include asset definitions for all electronics assets contained within a single carrier. The electronic asset information may also include user personal information stored by the primary institution 102 and/or used by the third-party computing systems 104 for security purposes (e.g., identity information, authentication information, etc.).

The user may be a customer or an account holder of the primary institution 102. The primary institution 102 includes a remote computing system 108. The remote computing system 108 maintains information about electronic assets held by the user and groupings of electronic assets. In one embodiment, the remote computing system 108 also maintains accounts held with the primary institution 102 and facilitates the movement of funds into and out of the accounts, or between the accounts in the primary institution 102 and other third-party issuers. For example, the primary institution 102 may be a financial institution that maintains at least one financial account of the user. Additionally, the remote computing system 108 facilitates the sharing of and the provision of access to information associated with user accounts to the user, to user computing devices 106, and to third-party computing systems 104. The remote computing system 108 includes a network interface 110. The network interface 110 is structured to facilitate data communication with other computing systems (e.g., the user computing devices 106, the third-party computing systems 104, etc.) via a network 112. The network interface 110 includes hardware and program logic that facilitates connection of the remote computing system 108 to the network 112. For example, the network interface 110 may include a wireless network transceiver (e.g., a cellular modem, a Bluetooth transceiver, a WiFi transceiver, etc.) and/or a wired network transceiver (e.g., an Ethernet transceiver). In some arrangements, the network interface 110 includes the hardware and programming logic sufficient to support communication over multiple channels of data communication (e.g., the Internet and an internal primary institution network). Further, in some arrangements, the network interface 110 is structured to encrypt data sent over the network 112 and decrypt received encrypted data.

The remote computing system 108 includes a processing circuit 114 having a processor 116 and memory 118. The processor 116 may be implemented as a general-purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a digital signal processor (DSP), a group of processing components, or other suitable electronic processing components. The memory 118 includes one or more memory devices (e.g., RAM, NVRAM, ROM, Flash Memory, hard disk storage, etc.) that store data and/or computer code for facilitating the various processes described herein. Moreover, the memory 118 may be or include tangible, non-transient volatile memory or non-volatile memory.

As shown in FIG. 1, the remote computing system 108 includes an access control circuit 120 and an electronic asset management circuit 122. Although shown as separate circuits in FIG. 1, in some arrangements, the access control circuit 120 and/or the electronic asset management circuit 122 are part of the processing circuit 114. Other arrangements may include more or less circuits without departing from the spirit and scope of the present disclosure. Further, some arrangements may combine the activities of one circuit with another circuit to form a single circuit. Therefore, those of ordinary skill in the art will appreciate that the present arrangement is not meant to be limiting. The access control circuit 120 is structured to manage the sharing and provision of customer information to third-party computing systems 104 and to user computing devices 106 based on permissions and preferences of the user. The electronic asset management circuit 122 is structured to perform various electronic asset management functions for groupings of electronic assets, including maintaining an electronic asset database 124, sharing electronic asset information between the user computing devices 106 and third-party computing systems 104, analyzing asset definitions, selecting third-party API calls based on asset definitions, and synchronously routing commands/selections from the user computing devices to the third-party computing systems 104 using the API calls.

The remote computing system 108 includes the electronic asset database 124. In some arrangements, the electronic asset database 124 is part of the memory 118. The electronic asset database 124 is structured to hold, store, categorize, and otherwise serve as a repository for electronic asset information, groupings of assets, user selections, and APIs. For example, the electronic asset database 124 may store asset definitions that identify the electronic assets such as account numbers, third-party identifiers that are indicative of a respective one of the plurality of third-party computing systems 104, grouping definitions including lists of electronic assets that are contained within different carriers, and the like. The electronic asset database 124 may also include information related to use of each grouping of electronic assets, or individual electronic assets within each grouping (e.g., account balances, use/transaction information, account ownership information, and the like). The electronic asset database 124 is structured to selectively provide access to information relating to groupings of electronic assets (e.g., to the user via the user computing devices 106). In some arrangements, the remote computing system 108 includes other databases, such as customer document and information databases structured to store non-asset related information or other documents associated with the user for distribution to third-party computing systems 104 at the approval of the user.

Still referring to FIG. 1, the electronic asset management system 100 includes at least one third-party computing system 104. The third-party computing system 104 may be unaffiliated with the remote computing system 108 and/or may have separate security protocols from the remote computing system 108. Additionally, in embodiments with multiple third-party computing systems 104, at least two of the third-party computing systems 104 are unaffiliated with one another. In other words, each third-party computing system 104 is affiliated with a separate (e.g., different, etc.) third-party issuer that maintains, sponsors, or otherwise services at least one electronic asset. As used herein, the term “unaffiliated” means that at least two recipient computing systems are those of separate unrelated entities and/or institutions that have separate security protocols. The third-party computing systems 104 are communicably coupled to the primary institution 102 through remote computing system 108 and can be authorized by the user to access information associated with the user that is stored, generated, maintained, and/or controlled in part by the primary institution 102. For example, the third-party computing systems 104 may be affiliated with any combination of merchants (e.g., brick-and-mortar retailers, e-commerce merchants, etc.), payment networks (e.g., payment networks affiliated with credit cards offered by the primary institution 102 and/or third-party issuers that are not affiliated with the primary institution 102), governments, businesses (e.g., employers), or the like. As described in further detail below, the user can submit requests to manage electronic assets that are affiliated with the third-party issuers through the remote computing system 108.

The user is associated with various user computing devices 106. The user computing devices 106 may include, for example, desktop computers or mobile devices such as smartphones, tablet computers, laptop computers, wearables (e.g., smart watches, smart glasses, fitness trackers, etc.), and/or internet of things (“IOT”) devices (e.g., Amazon Echo®, smart appliances, etc.). The user computing devices 106 provide access to information associated with the user (e.g., information regarding groupings of assets, etc.) that is stored, generated, maintained, and/or controlled in part by the primary institution 102.

The devices of the system 100 communicate via the network 112. The network 112 may include any combination of the Internet and an internal private network (e.g., any combination of wired and/or wireless networks, telecommunications networks, etc.). Through data communication over the network 112, the remote computing system 108 can coordinate requests from the user computing devices 106 to the third-party issuers (e.g., third-party computing systems 104) to change the functionality of different groupings of electronic assets.

As shown in FIG. 1, the remote computing system 108 includes user device APIs 126 that define how the remote computing system 108 communicates electronic asset information with the user computing devices 106. The user device APIs facilitate the sharing of and access to the electronic asset information stored at the remote computing system 108 based on permissions and preferences provided by the user. The user device APIs also facilitate the transmission of commands/selections from the user computing devices 106 to the remote computing system 108 to control functionality of groupings of assets.

The remote computing system 108 also includes third-party APIs 128 that define how the remote computing system 108 shares electronic asset information with the third-party computing systems 104. The third-party APIs 128 may facilitate the sharing of and access to information related to one or more electronic assets within a grouping of electronic assets (e.g., electronic assets that are supported, serviced, or otherwise controlled by a third-party issuer that is associated with the third-party APIs 128). The third-party APIs also facilitate the transmission of commands/selections from the remote computing system 108 to the third-party computing systems 104 to synchronously control the functionality of groupings of assets. As used herein, the term “synchronously” refers to the substantially coordinated control of assets that are supported by multiple, unaffiliated third-party computing systems 104. For example, synchronous control may refer to the transmission of API calls to each of the third-party computing system in parallel (e.g., at the same time), or in a controlled sequence (e.g., not necessarily at the same time) to reduce the average time required to activate, deactivate, restrict, or otherwise manage each asset from the grouping of assets. In one embodiment, the third-party APIs 128 are specifically configured to transmit requests/commands/selections through third-party API gateways 130 of the third-party computing systems 104. For example, the primary institution 102 may have arrangements with third-party issuers, and may have APIs 128 that are specific to each issuer, and that conform to the specific procedural requirements that each issuer has for changing the functionality of electronic assets that are managed by the third-party issuer. API calls (requests, commands, selections from the remote computing system 108) are routed by the third-party API gateways 130. Each API may require APIs calls that follow specific protocols, such as what data (e.g., security or access tokens, identifiers, etc.) is required with the API call, formatting of data provided, encryption, etc. The third-party API gateways 130 are management tools that accept (e.g., receive, authenticate, verify, analyze, decipher, decrypt, etc.) all API calls from the remote computing system 108, aggregate the various services required to fulfill them, and take the appropriate action through the third-party computing systems 104. The APIs 128 may include encryption to ensure the secure transfer of information between the remote computing system 108 and the third-party computing systems 104.

The access control circuit 120 controls access to the electronic asset information by the user computing devices 106 via the user device APIs 126. The access control circuit 120 may form part of a network security access control that prevents unauthorized viewing of electronic asset information. In some arrangements, the remote computing system 108 provisions requested electronic asset information to a given user computing device 106 for local storage on the user computing device 106. For example, the remote computing system 108 can provision grouping definitions that indicate which assets are associated with which carriers (e.g., which credit cards, RFID cards, gift cards, etc. are contained within a user's purse or another carrier), asset definitions such as third-party issuer identifiers that are indicative of the third-party issuer that is associated with each electronic asset, and other electronic asset information (e.g., transaction history for groupings of electronic assets or individual electronic assets from within one or more groupings, etc.). In other arrangements, the remote computing system 108 provides access to remotely display, present, or analyze electronic asset information stored at the remote computing system 108 while the remote computing system 108 retains control over the electronic asset information. For example, the remote computing system 108 can provide access to an internet server to present designated electronic asset information through a website for the primary institution 102, when the internet server requests the information, without directly transmitting the data to the internet server.

Referring now to FIG. 2, a more detailed view of a user computing device 106 is shown, according to an example embodiment. The user computing device 106 shown in FIG. 2 is a mobile device 200. The mobile device 200 is structured to exchange data over the network 112, execute software applications, access websites, generate graphical user interfaces, and perform other operations described herein. The mobile device 200 may include one or more of a smartphone or other cellular device, a wearable computing device (e.g., eyewear, a watch or bracelet, etc.), a tablet, a portable gaming device, a laptop, and other portable computing devices.

In the example shown, the mobile device 200 includes a network interface 202 (e.g., a transceiver) enabling the mobile device 200 to communicate via the network 112. The mobile device 200 also includes a user interface 204 (an input output (I/O) device, etc.), and a processing circuit 206 including a memory 208 and a processor 210. As shown in FIG. 2, the user interface 204 includes hardware and associated logics configured to exchange information with a user. An input aspect of the user interface 204 allows the user to provide information to the mobile device 200, and may include, for example, a mechanical keyboard, a touchscreen, a microphone, a camera, biometric scanner to receive biometric data such as a fingerprint scanner, any user input device that is engageable to the mobile device 200 via a USB, serial cable, Ethernet cable, and so on. As shown in FIG. 2, the mobile device 200 includes a sensor 212 that is configured to capture image data. The sensor 212 may be a camera or another optical sensor that is built into the mobile device 200. An output aspect of the user interface 204 allows the user to receive information from the mobile device 200, and may include, for example, a digital display 214 (e.g., a touchscreen display, an LCD display, and other monitor types), a speaker, illuminating icons, LEDs, and so on.

The user portal 216 (e.g., user portal circuit, etc.) is structured to provide the user with access to services offered by the primary institution 102 (e.g., the remote computing system 108). The user portal 216 may be, or may be accessed via, a software application that may be provided by or associated with the primary institution 102 (via the remote computing system 108). As such, the user portal 216 may be hard coded onto the memory of the mobile device 200. In another embodiment, the user portal 216 may be one or more web-based interface applications that are supported by a separate computing system comprising one or more servers, processors, network interface circuits, or the like, that transmit the application to the mobile device 200, and where the user has to log onto or access the web-based interface before usage.

The user portal 216 is structured to provide displays to the mobile device 200 that enable the user to view and manage groupings of electronic assets through the remote computing system 108. Accordingly, the user portal 216 is communicably coupled to the remote computing system 108 (e.g., the access control circuit 120 and the electronic asset management circuit 122).

Further, via the user portal 216, the mobile device 200 is configured to receive and display various datasets from the remote computing system 108 to facilitate management and control of the groupings of electronic assets (and individual electronic assets within each grouping). The mobile device 200, via the user portal 216, is configured to render such datasets into the GUI of the user portal 216. As described herein, through such GUIs, the user is able to modify the functionality of certain groupings of electronic assets.

In some embodiments, the mobile device 200 is configured (e.g., via the user portal 216) to perform various operations described herein as being performed by the remote computing system 108. For example, in one embodiment, the user portal 216 includes APIs structured to facilitate exchange of information between the mobile device 200 and the various third-party computing systems 104 independently or at least partially independently from the remote computing system 108.

In some embodiments, the user portal 216 is a separate software application implemented on the mobile device 200. The user portal 216 may be downloaded by the mobile device 200 prior to its usage, hard coded into the memory 208 of the mobile device 200, or be a web-based interface application such that the mobile device 200 may provide a web browser to the application, which may be executed remotely from the mobile device 200. In the latter instance, the user may have to log onto or access the web-based interface before usage of the applications. Further, and in this regard, the user portal 216 may be supported by a separate computing system including one or more servers, processors, network interface circuits, or the like that transmit applications for use to the mobile device 200.

It should be understood that other user computing devices 106 (e.g., user computing devices 106 other than a mobile device 200) may include applications that are similar to the user portal 216 discussed above. For example, a smart appliance may include an application associated with the primary institution 102 that enables the user to exchange information with the remote computing system 108 and/or third-party computing systems 104 to manage groupings of electronic assets. In another example, a smart speaker may include an application through which the user may modify the functionality of at least one grouping of electronic assets via voice commands. In certain embodiments, a user may speak a command, such as “deactivate,” “turn off,” “restrict,” etc., followed by an identification of a set of electronic assets (such as the name of a carrier) to be altered. In some embodiments, the system may verify the voice signature as being that of an owner or other authorized user, decipher the audio in the spoken command to interpret the spoken words as commanding an action upon a specified grouping of electronic assets, and alter the electronic assets in the specified grouping of electronic assets according to the command. In certain embodiments, authenticating the command may require detection of a spoken passcode or sound signature, alternatively or additionally to verification of a voice signature as being that of the owner or authorized user.

Referring to FIG. 3, a flow diagram of a method 300 of managing groupings of electronic assets is shown, according to an example embodiment. Method 300 may be implemented using the system 100 of FIG. 1, and particularly, by the remote computing system 108 (e.g., by the processor 116 of the remote computing system 108). As such, reference will be made to the system 100 when describing method 300. In another embodiment, at least portions of method 300 may be performed by the user computing device 106. In another embodiment, additional, fewer, and/or different operations may be performed. It will be appreciated that the order or flow of operations indicated by the flow diagrams and arrows with respect to the methods described herein is not meant to be limiting. For example, in one embodiment, two or more of the operations of method 300 may be performed simultaneously.

At operation 302, a portal is provided with a network security access control. The portal 216 may be, or may be accessed through, a software application that is provided by a remote computing system 108 to the user computing device 106. For example, the portal 216 may be provided by the remote computing system 108 as a mobile app that is downloaded and installed onto the user computing device 106. In another embodiment, the portal 216 may be hosted at the remote computing system 108 (e.g., via a server, etc.) and may be accessed by the user computing device 106, for example, through a web-browser via an internet connection (e.g., through the network interface 202). The network security access control may be an interface of the portal 216 that prompts an individual to enter login credentials such as biometric data, alphanumeric entries, icon selections, and the like to identify the individual to the remote computing system 108.

The method 300 may further include receiving an authentication request from the user computing device 106 through the network security access control. The authentication request indicates that an individual purporting to be a customer, employee, or other authorized individual is attempting to access the portal 216 to view electronic asset information and/or to control the functionality of groupings of electronic assets. At operation 304, the remote computing system 108 receives login credentials from the user computing device 106. Operation 304 may include receiving, by the user computing device 106, inputs from the user interface 204 (e.g., login credentials that are detected using an input device of the user interface). For example, operation 304 may include receiving biometric data such as fingerprint data from a fingerprint scanner, or image data from a user-facing camera. In another embodiment, operation 304 may include receiving combinations of alphanumeric characters (e.g., a pin, password, etc.), or some combination of different types of user inputs through the user interface 204.

At operation 306, the remote computing system 108 determines that the login credentials are associated with a set of electronic assets, or with an individual who is authorized to manage functionality of the set of electronic assets. The electronic assets may correspond to a plurality of different third-party computing systems 104. The third-party computing systems 104 may include API gateways 130 that are configured to accept API calls directed to changes in the usability (e.g., functionality, operability, etc.) of the electronic assets. Operation 306 may include comparing the login credentials to a list of login credentials stored in the electronic asset database 124 of the remote computing system 108, including login credentials associated with various third-party issuers. Operation 306 may include confirming the login credentials are valid by identifying the login credentials from the list of login credentials to prevent fraudulent access to electronic asset information and control tools.

At operation 308, the remote computing system 108 presents, via the portal 216, a virtual icon. The virtual icon is selectable using the user interface 204 of the user computing device 106 to identify a coordinated action with respect to all electronic assets in the set of electronic assets. The coordinated action may be a change in functionality of all of the assets within a single physical carrier such as activation, deactivation, or other use restrictions. Examples of use restrictions include restrictions on an amount of funds that can be accessed through the electronic asset, transaction limits, a number of transactions, locations where the electronic asset may be used (e.g., geographical locations, certain lists of merchants or businesses, etc.), the types of products that may be purchased or otherwise accessed using the electronic asset, physical or virtual locations which may be accessed via an electronic key, and the like. Other examples of use restrictions include requiring pre-approval of transactions (e.g., requiring confirmation by an account owner before a transaction can be processed, etc.) or restrictions that require notifications to the asset owner each time the asset is used. Yet another example of a coordinated action is ordering a replacement of all of the assets within a set of electronic assets (e.g., submitting a request to have new electronic assets mailed or otherwise delivered to the asset owner, etc.). The virtual icon may be a selectable interface (e.g., toggle, indicator, etc.) that is accessible from within the portal 216, and that allows a user to toggle between different functionalities that are available for the set of electronic assets. In another embodiment, the portal 216 is at least partially integrated with and forms part of an operating system of the user computing device 106. In this way, the virtual icon may be presented on an interface of the operating system (e.g., a home screen, desktop view, etc.) of, for example the mobile device.

Referring to FIG. 4, an example display 400 of a mobile device (e.g., mobile device 200) is shown, according to an example embodiment. The example display 400 presents a home screen 402 of the mobile device from which the user may access different applications. The home screen 402 forms part of a GUI of the operating system that presents tiles 404, with each tile 404 corresponding with an application that is installed (or installable) on the mobile device. In the example of FIG. 4, the home screen 402 of the mobile device provides for a tile overlay mode, or shortcut access mode that is initiated upon detection of a certain gesture or other input, such as a press and hold gesture, a double tap or triple tap on the tile 404, and/or other gestures or inputs that differ from the gestures or inputs used to indicate application launch or tile movement. The tile overlay mode may allow the user to make selections of virtual icons and perform operations to affect the usability of one or more sets of assets with a minimal number of gestures (e.g., without launching the application, etc.). In another embodiment, the tile 404 itself is the virtual icon, which is selected by a specific gesture or input (e.g., a triple tap, which automatically selects the virtual icon to enable/disable or otherwise modify the functionality of a specific set of assets).

As shown in FIG. 4, the tile overlay mode generates a GUI (e.g., shortcuts menu, selection pane, etc.) that is configured to present selection options (e.g., virtual icons) to the user. A first example selection GUI 406 is shown toward the lower end of the display 214 of the mobile device in FIG. 4. The first selection GUI 406 includes a list. A first column (e.g., leftmost column as shown in FIG. 4) includes a listing of identifiers 408 for each set/grouping of electronic assets. In the example of FIG. 4, the identifiers 408 are the names of individual carriers (e.g., yellow bag, wallet, jacket, etc.) in which the set of electronic assets is physically contained. A second column (e.g., rightmost column as shown in FIG. 4) includes a listing of selections (e.g., coordinated actions) for each set of electronic assets. In the first selection GUI 406, the selection for each set of assets is a toggle 408 that can be selected, through the user interface 204, to enable or disable (e.g., freeze or otherwise restrict the use of) all of the electronic assets within each carrier. In this way, the coordinated action can be taken across all assets in a set of electronic assets with a single click, rather than having to individually specify the desired change in functionality for each individual asset. The first selection GUI 406 also shows the current status of each set of assets by the current position of the toggle 408.

In another embodiment, the number of selections and selection options presented for each set of electronic assets may be different. For example, FIG. 4 also shows a second selection GUI 407, in which multiple options are provided for modifying the functionality of each set of electronic assets. Selections are made by touching the desired selection container 409 in the second selection GUI 407 (e.g., by a single tap on the selection container 409 on a touchscreen display, etc.). Options include enabling or disabling (e.g., freezing) each set of electronic assets, and canceling each set of electronic assets (e.g., permanently deactivating and/or ordering new electronic assets). In other embodiments, the types of coordinated actions that may be selected from the GUIs may be different. For example, selections may include a limited operability mode and/or restricted access mode, which permits only certain transactions to be performed by the electronic assets (e.g., only being used within a certain geographical area, at only certain stores or on only certain types of products, only during certain times of day, limited transaction amounts, etc.). Such functionality is particularly useful when a user has provided one of his/her carriers to a relative or another trusted individual (e.g., a child, etc.) for temporary use. In another embodiment, the virtual icon may be accessible from a different GUI that is separate from the mobile app tile 404. For example the virtual icon may be accessed from a drop-down menu of the operating system on the mobile device (e.g., when the user swipes downward from the top of the touchscreen display from the home screen, etc.). In various embodiments, any available changes (e.g., alterations to the functionality) to the electronic assets may be presented as options, and the changes may be predefined as “modes” (e.g., user defined modes for the assets that may be presented in place of, or in addition to, “enable” and “disable”), such as “daytime” mode to restrict the electronic assets to usability during a predefined time period (e.g., as 7 am to 7 pm, or between sunrise and sunset times for the physical location of the electronic assets, which may be determined, e.g., via a GPS of the electronic asset, via a device to which the electronic asset is presented, and/or via a device which otherwise detects the electronic asset when physically nearby).

Returning to FIG. 3, operation 308 may further include accepting, by the remote computing system 108, via the portal 216, selection of the virtual icon that is detected from the user interface 204. Operation 308 may include receiving, via the network interface 110, a signal from the user computing device 106 that indicates the desired selection, and confirming the selection by comparing the selection to a list of available coordinated actions stored in the electronic asset database 124.

At operation 310, the remote computing system 108, in response to accepting the selection via the portal 216, executes a set of API calls to each third-party computing system 104 to synchronously, or substantially synchronously implement the coordinated action across all of the electronic assets that are contained within a single carrier. Operation 310 may include identifying a list of asset-specific API calls that correspond with the required procedures for different, unaffiliated third-party computing systems 104 (e.g., third-party computing systems 104 having different security protocols, third-party computing systems 104 associated with separate unrelated entities and/or institutions). For example, operation 310 may include matching the selection with a set of asset-specific API calls stored in the electronic asset database 124 using a selection engine, or by crawling through the electronic asset database 124 to match the selection with an appropriate identifier that corresponds with the selection. Operation 310 may include transmitting, by the network interface 110, via the API calls, the coordinated action for each asset in the set of electronic assets to a corresponding one of the third-party computing systems 104 (e.g., via API gateways 130 of the third-party computing systems 104). In one embodiment, the remote computing system 108 is configured to transmit the asset-specific API calls in parallel, which reduces the time required to perform the coordinated action across all of the assets within the set of electronic assets. In other embodiments, the remote computing system 108 is configured to transmit the asset-specific API calls in a controlled sequence to reduce the average time required to activate, deactivate, restrict, or otherwise control each electronic asset of the set of electronic assets. For example, the remote computing system 108 may be configured to transmit API calls in a prescribed sequence to control the functionality of assets with less robust/complex security protocols first, to focus processing power on those assets before transmitting API calls to third-party computing systems 104 with more robust and/or complex security protocols. In some embodiments, a prescribed sequence may be based on the characteristics of the electronic assets (such as vulnerability to security breach) or other factors such as, for example, time of day, season, physical location, etc. (e.g., certain assets may me more vulnerable to security breach at certain times, and/or may less computationally demanding to alter at certain times, and such assets may be prioritized over relatively less vulnerable assets or relatively more computationally demanding assets depending on when the command to alter the electronic assets is received). In various embodiments, such a prescribed sequencing for effecting alterations to the functionality of a set of electronic assets may maximize or otherwise enhance efficiency by, for example, altering the functionality of the largest number of electronic assets (at least electronic assets of certain types) in the shortest amount of time. Operation 310 may include transmitting information associated with the user (e.g., login credentials, user information, etc.) to confirm the identity of the user to the third-party computing systems 104, along with the selection.

Operation 310 may further include operations performed by the third-party computing systems 104 to implement the coordinated action. For example, the third-party computing systems 104 may determine whether the information transmitted via the third-party APIs 128 is sufficient to complete the coordinated action. In the event that further information is required, the third-party computing systems 104 may transmit notifications, via the network 112 to one, or a combination of, the remote computing system 108 and the user computing device 106. The notifications may include a prompt that requests additional user information to complete the requested action. For example, the prompt (e.g., text, pop-up, etc.) may be a notification on the user computing device 106 to confirm that they requested the coordinated action.

Referring to FIG. 5, a flow diagram of a method 500 of populating a set of electronic assets into an electronic asset management system is shown, according to an example embodiment. Method 500 may be implemented using the system 100 of FIG. 1, and particularly, the mobile device 200 of FIG. 2 (e.g., the processor 210 of the mobile device 200). As such, reference will be made to the mobile device 200 of FIG. 2. However, it will be appreciated that in other embodiments, a different user computing device 106 may be used (e.g., a desktop computer, an IoT device, etc.). In another embodiment, additional, fewer, and/or different operations may be performed.

At operation 502, the mobile device 200 presents, on the display of the mobile device 200, a GUI. Operation 502 may include receiving a selection of a software app that corresponds to the portal 216 from the home screen of the mobile device 200, or receiving a command to navigate to the portal 216 from a web-browser installed on the mobile device 200. Operation 502 may also include receiving login credentials from the user interface 204 of the mobile device 200 to access the portal 216.

At operation 504, the mobile device 200 receives, from the user interface 204, a plurality of asset definitions for a set of electronic assets. Each asset definition may include a third-party identifier that is indicative of a respective one of the plurality of third-party issuers (e.g., third-party computing systems 104). The third-party identifier may be a name of one of the third-party issuers. In other embodiments, the third-party identifier may be a logo that is associated with the third-party issuer. The asset definitions may also include other information regarding the electronic assets, such as an account number associated with the asset, expiration information, security codes, and/or identifying information for the user (e.g., user name, date of birth, etc.). The asset definitions together may form a carrier definition that identifies all of the assets within a single group (e.g., a group representative of a single physical carrier, etc.). Operation 504 may include receiving manual entry of the asset definitions from the user interface 204 (e.g., via a keyboard, etc.). In other embodiments, the asset definition may include one or more images or scans of the electronic asset (e.g., taking a picture of the electronic asset, reading a magnetic strip on the back of the asset, etc.), and/or communications with the electronic assets (through, e.g., near-field communications with embedded microchips in the electronic assets, an RFID tag, or another contactless card identification technique) as will be further described.

FIGS. 6 and 7 show example interfaces that may be presented in the portal 216 to facilitate entry of asset definitions. In particular, FIG. 6 shows an interface 600 that is used to present carrier and asset definitions to a user. As shown in FIG. 6, the interface 600 includes a header label 602 that identifies the selected carrier and the electronic assets contained within the carrier. The header label 602 also includes a status indicator that shows the current operability of the set of electronic assets (e.g., whether the electronic assets are enabled, or disabled, deactivated, or otherwise restricted). The header label 602 also includes a virtual icon 604 that can be used to select coordinated actions, or to access a listing of virtual icons that correspond to different coordinated actions. The set of electronic assets are represented in FIG. 6 by a plurality of asset labels 603. Additional information regarding each individual asset from the set of electronic assets may be accessed by selecting a corresponding one of the asset labels 603. The asset labels 603 may also provide user access to a modifications interface that can be used to modify/edit electronic asset information (e.g., asset definitions) through the user interface 204. Additionally, a selection pane 606 at the bottom of the interface 600 allows a user to add or delete assets from the defined set of electronic assets.

In some embodiments, the portal 216 includes a scan tool that provides automated entry of asset definitions, and which significantly reduces the required amount of user interaction with the portal 216. The scan tool may be configured to exchange information with one or more user interfaces 204. For example, FIG. 7 shows an example scan tool interface 700 that is configured to exchange information with a sensor 212 of the user interface 204. In particular, the scan tool interface 700 is configured to exchange information with and control operation of a camera or other optical sensor onboard the mobile device 200. As shown in FIG. 7, the scan tool interface 700 includes a window 702 that provides real-time image data from the camera. In this example, the camera is facing a credit card 704 that is positioned behind the mobile device 200. The window 702 may include various alignment indicators 706 and/or other features to facilitate user interaction with the scan tool and to improve feature recognition of the credit card or other electronic asset. For example, the alignment indicators 706 may include a cross-hatch pattern on the center of the window 702, which may change color depending on the how well the electronic asset is aligned with the window 702 or encompassed by the window 702. The scan tool interface 700 may be configured to control the camera (e.g., to refocus the camera, to modify lighting provided by an external LED or other illuminating device, etc.) to improve recognition of image data captured by the camera. The scan tool interface 700 may also include a capture button 708 to take a snapshot of the real-time image data for further processing by the portal 216, which may be performed onboard the mobile device 200 and/or remotely (e.g., by the remote computing system 108).

In various embodiments, other (e.g., contactless) asset identification techniques may be employed to obtain information regarding the electronic assets. For example, the portal 216 may be configured to interface with a magnetic card reader that is connected to the user computing device 200, to identify the asset by reading a magnetic strip integrated into the asset (e.g., by swiping a credit card through a magnetic reader, etc.). The portal 216 may be configured to receive the information regarding the electronic asset through the reader, and/or another form of scanner/reading hardware. In another embodiment, at least one electronic asset may be identified through wireless (e.g., radio frequency) communications between the mobile device 200 and the electronic asset. For example, the electronic asset may include a radio chip, antennae, RFID tag, or another near-field communication technology to transmit information regarding the electronic asset. The portal 216 may be configured to receive the information regarding the electronic asset through the network interface 202 (e.g., a transceiver) of the mobile device 200, and/or another wireless communications interface. For example, the portal 216 may be configured to wirelessly communicate with the electronic asset and receive a data packet from the electronic asset (e.g., the third party identifier) when the electronic asset is placed near the mobile device 200. The data packet may include the information regarding the electronic asset, which may be encrypted to prevent fraudulent duplication of the electronic asset. In one embodiment, the portal 216 may be configured to receive information regarding the entire set of electronic assets simultaneously; for example, from any carrier that is placed near the mobile device 200 that contains multiple electronic assets using near-field technology. In various potential embodiments, one or more electronic assets and/or devices with which the electronic assets interface may employ “EMV” standards (managed by EMVCo). EMV specifications include, for example, encrypted data exchange standards for cards via either microchip insert or contactless functions. EMV specifications and standards relate to contact, contactless, mobile, payment tokenization, QR code, secure remote commerce, and 3-D secure technologies.

Returning to FIG. 5, the method 500 further includes identifying a plurality of third-party computing systems based on the plurality of asset definitions, at 506. Operation 506 may include analyzing the image data, retrieved from the camera, to determine an API identifier that corresponds with one of the plurality of third-party issuers (e.g., third-party computing systems 104). For example, operation 506 may include using optical character recognition to convert portions of the image data into machine-readable text. The portion of the image data may correspond with a logo 710 including a name of the third-party issuer or a symbol that is synonymous with the identity of the third-party issuer. Operation 506 may further include matching the machine-readable text to an API identifier of a plurality of API identifiers (e.g., from a list of API identifiers stored in memory). Operation 506 may include using one or more neural network models (e.g., convolutional neural networks, etc.) to facilitate identification of the API identifier. In one embodiment, operation 506 includes extracting pixel features from the image data, analyzing the features (e.g., color depth of each pixel, etc.), and comparing the features and their arrangement with known logos 710 (e.g., logos stored in the electronic asset database 124) to determine the API identifier.

In an embodiment where at least one electronic asset includes a wireless communication device, operation 506 may include analyzing the signal received from the electronic asset to determine the API identifier. Operation 506 may include decrypting the signal (e.g., data packet) from the electronic asset using a key or other data decryption methodology employed by a respective one of the third-party issuers. The key may be provided by the third-party issuer, and may be selected by the processor based on the signal (e.g., the type of signal, content of the signal, etc.) that is received from the electronic asset (e.g., from a list stored in memory). In another embodiment, operation 506 may include transmitting the signal to at least one of the third-party computing systems 104 for further processing and dissemination. In other words, the remote computing system 108 may be configured to query the third-party computing systems 104 for data/information related to the electronic asset by transmitting the signals associated with the electronic assets.

At operation 508, the mobile device 200 presents, through the display 214, via the portal 216, a virtual icon that is selectable to identify a coordinated action with respect to all of the assets within a set of electronic assets. The virtual icon may be the same or similar to the virtual icon described with reference to FIG. 4. For example, the virtual icon may be presented by the display 214 as a selectable tile on a home screen of the mobile device 200. In another embodiment, the virtual icon may be a selectable toggle from within the portal 216. At operation 510, the mobile device 200 receives a selection of the virtual icon from a user interface of the mobile device 200. Operation 510 may include receiving a command signal from a keyboard, touchscreen, and/or microphone of the mobile device 200 that is indicative of user interaction with the virtual icon. At operation 512, the mobile device 200 transmits the selection of the virtual icon to the remote computing system 108 to implement the coordinated action on all assets in the set of electronic assets, as described in detail with reference to the method 300 of FIG. 3.

Referring to FIG. 8, a flow diagram of a method 800 of implementing a coordinated action on a set of electronic assets based on a travel plan is shown, according to an example embodiment. As with other methods described herein, method 800 may be implemented using the system 100 of FIG. 1 (e.g., via a user computing device such as the mobile device 200, a different user computing device 106, the remote computing device 108, or some combination thereof). As such reference will be made to elements of the system 100 and mobile device 200 when describing method 800. In another embodiment, the method 800 may include additional, fewer, and/or different operations.

At operation 802, the mobile device 200 presents, on the display 214 of the mobile device 200, a travel planner for a grouping of electronic assets. The grouping may be the set of electronic assets for at least one carrier, or some combination of individual assets from multiple carriers. The grouping may include electronic assets that will be carried with the user while travelling. In another embodiment, the grouping may include electronic assets that will remain behind, and are to be frozen or disabled during travel to prevent fraudulent use. Operation 802 may include receiving a selection, via the user interface 204, of a software app corresponding to the portal 216 from the home screen of the mobile device 200, or receiving a command to navigate to the portal 216 from a web-browser installed on the mobile device 200. Operation 802 may further include navigating through the portal 216 to the travel planner.

FIG. 9 shows an example travel planner 900 that may be accessed through the portal 216 by the mobile device 200, according to an embodiment. The travel planner 900 is selectable by the user interface 204 of the mobile device 200 to identify a set of travel parameters. The travel parameters may include travel actions to be taken with respect to a grouping of electronic assets, and a travel selection indicative of at least one of a location of travel and/or a date of travel. The travel actions may be one or more coordinated actions to apply to a grouping of electronic assets. For example, the travel actions may be coordinated actions that enable the use of the grouping of electronic assets in different geographical areas (e.g., areas outside of the range of typical use, in different states and/or countries than where the user resides). In another embodiment, the travel actions may be coordinated actions that increase a transaction limit, account balance, or number of transactions to thereby accommodate the needs of the user during travel. For example, the user may need access to additional funds from their credit card during travel to accommodate stays in hotels, food, and related purchases. In the embodiment of FIG. 9, the travel planner 900 includes a travel actions button 902 to facilitate the selection of travel actions. The travel actions button 902 may generate a separate selection window with a listing of the different groupings of assets and virtual icons with different coordinated actions for each grouping.

The travel selection may be a combination of information that informs the remote computing system 108 about where the user will travel (e.g., the state, country, etc.) and when the travel will occur (i.e., the dates of travel). As shown in FIG. 9, the travel planner includes a calendar interface 904 to facilitate the assignment of travel dates and times. Commands received by the portal 216, via the user interface 204, are used to add, delete, or otherwise manipulate events 906 on the calendar. A separate travel location button 908 is provided by the travel planner 900 to facilitate the selection of geographical areas at which the grouping of assets will be used.

Returning to FIG. 8, the method 800 additionally includes receiving a selection of travel parameters from the user interface 204, including the travel actions and the travel selection, at 804. Operation 804 may further include transmitting the travel parameters, via the network interface 202 of the mobile device 200, to the remote computing device 108. Operation 804 may further include storing the travel parameters in the electronic asset database 124 for monitoring and future use. In one embodiment, operation 804 includes initializing a transmission delay to prevent the travel actions from being transmitted to the third-party computing systems 104 until the date of travel, or some threshold period in advance of the date of travel.

At operation 806, the remote computing device 108, in response to accepting the selection of travel parameters via the portal 216 (prior to or at the beginning of travel), executes a set of API calls to implement the selection of travel parameters on the grouping(s) of electronic assets. In one embodiment, operation 806 includes executing the set of API calls to the third-party computing systems 104 after the transmission delay has elapsed.

It is noted that any of the features, selectors, icons, functionalities, information, elements, or other aspects of any one interface or figure may be combined or swapped with or applied to any of the features, selectors, icons, functionalities, information, elements, or other aspects of any other interface or figure.

The embodiments described herein have been described with reference to drawings. The drawings illustrate certain details of specific embodiments that implement the systems, methods and programs described herein. However, describing the embodiments with drawings should not be construed as imposing on the disclosure any limitations that may be present in the drawings.

It should be understood that no claim element herein is to be construed under the provisions of 35 U.S.C. § 112(f), unless the element is expressly recited using the phrase “means for.”

As used herein, the term “circuit” may include hardware structured to execute the functions described herein. In some embodiments, each respective “circuit” may include machine-readable media for configuring the hardware to execute the functions described herein. The circuit may be embodied as one or more circuitry components including, but not limited to, processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, etc. In some embodiments, a circuit may take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (IC), discrete circuits, system on a chip (SOCs) circuits, etc.), telecommunication circuits, hybrid circuits, and any other type of “circuit.” In this regard, the “circuit” may include any type of component for accomplishing or facilitating achievement of the operations described herein. For example, a circuit as described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, and so on).

The “circuit” may also include one or more dedicated processors communicatively coupled to one or more dedicated memory or memory devices. In this regard, the one or more dedicated processors may execute instructions stored in the dedicated memory or may execute instructions otherwise accessible to the one or more dedicated processors. In some embodiments, the one or more dedicated processors may be embodied in various ways. The one or more dedicated processors may be constructed in a manner sufficient to perform at least the operations described herein. In some embodiments, the one or more dedicated processors may be shared by multiple circuits (e.g., circuit A and circuit B may comprise or otherwise share the same processor which, in some example embodiments, may execute instructions stored, or otherwise accessed, via different areas of memory). Alternatively or additionally, the one or more dedicated processors may be structured to perform or otherwise execute certain operations independent of one or more co-processors. In other example embodiments, two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multi-threaded instruction execution. Each processor may be implemented as one or more general-purpose processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components structured to execute instructions provided by memory. The one or more dedicated processors may take the form of a single core processor, multi-core processor (e.g., a dual core processor, triple core processor, quad core processor, etc.), microprocessor, etc.

Any foregoing references to currency or funds are intended to include fiat currencies, non-fiat currencies (e.g., precious metals), and math-based currencies (often referred to as cryptocurrencies). Examples of math-based currencies include Bitcoin, Litecoin, Dogecoin, and the like.

It should be noted that although the diagrams herein may show a specific order and composition of method steps, it is understood that the order of these steps may differ from what is depicted. For example, two or more steps may be performed concurrently or with partial concurrence. Also, some method steps that are performed as discrete steps may be combined, steps being performed as a combined step may be separated into discrete steps, the sequence of certain processes may be reversed or otherwise varied, and the nature or number of discrete processes may be altered or varied. The order or sequence of any element or apparatus may be varied or substituted according to alternative embodiments. Accordingly, all such modifications are intended to be included within the scope of the present disclosure as defined in the appended claims.

The foregoing description of embodiments has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from this disclosure. The embodiments were chosen and described in order to explain the principals of the disclosure and its practical application to enable one skilled in the art to utilize the various embodiments and with various modifications as are suited to the particular use contemplated. Other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the embodiments without departing from the scope of the present disclosure as expressed in the appended claims.

Claims

1. A method comprising: providing, by a processor of a computing system through a telecommunications network, to a remote user computing device comprising an input device configured to detect at least one of biometric data, alphanumeric entries, or icon selections, a portal with a network security access control;receiving via the portal, by the processor, for the network security access control, login credentials detected using the input device of the user computing device, and verifying that the login credentials grant access to the portal;determining, by the processor, that the login credentials are associated with a set of electronic assets corresponding to a plurality of third-party computing systems with application programming interface (API) gateways configured to accept API calls directed to changes in functionality of the electronic assets;receiving, by the processor, via the portal, a selection of a coordinated action with respect to all electronic assets in the set of electronic assets, the selection detected via the input device of the remote user computing device; andexecuting, by the processor, based on the selection, a set of API calls comprising an asset-specific API call to each third-party computing system in the plurality of third-party computing systems to implement the coordinated action on all electronic assets in the set of electronic assets.
2. The method of claim 1, further comprising: determining, by the processor, an asset definition for each of the set of electronic assets, each asset definition comprising a third-party identifier that is indicative of a respective one of the plurality of third-party computing systems; andidentifying, via the processor, the plurality of third-party computing systems based on the plurality of third-party identifiers.
3. The method of claim 2, wherein determining the asset definition for at least one electronic asset of the set of electronic assets comprises: presenting, by the processor, via the portal, a scan tool configured to interface with an optical sensor of the user computing device and capture an image using the optical sensor;receiving, by the processor, the image of the electronic asset captured using the optical sensor; andanalyzing, by the processor, the image to determine the third-party identifier.
4. The method of claim 2, wherein determining the asset definition for at least one electronic asset of the set of electronic assets comprises: presenting, by the processor, via the portal, a scan tool configured to interface with a transceiver of the user computing device and wirelessly communicate through near-field communications with the at least one electronic asset to acquire a data packet therefrom;receiving, by the processor, the data packet acquired via the transceiver; andanalyzing, by the processor, the data packet to determine the third-party identifier.
5. The method of claim 2, wherein the asset definitions together form a carrier definition, further comprising receiving, by the processor from the user computing device, a plurality of carrier definitions, each carrier definition of the plurality of carrier definitions associated with a different carrier.
6. The method of claim 2, wherein the third-party identifier comprises a logo, and wherein identifying each one of the plurality of third-party computing systems comprises: using optical character recognition to convert the logo to machine-readable text; andmatching the machine-readable text to one of a plurality of API identifiers corresponding to the asset-specific API call.
7. The method of claim 2, wherein the third-party identifier comprises a logo, and wherein identifying each one of the plurality of third-party computing systems comprises associating the logo with one of a plurality of API identifiers corresponding to the asset-specific API call.
8. The method of claim 1, further comprising: presenting, by the processor, via the portal, a travel planner configured to be selectable using the input device to identify a set of travel actions to be taken with respect to a grouping of electronic assets, and a travel selection indicative of at least one of a location of travel or a date of travel, the grouping of electronic assets comprising at least one electronic asset from the set of electronic assets;receiving, by the processor, via the portal, selection of the set of travel actions and the travel selection; andexecuting, by the processor, based on the selection, the set of API calls to implement the selection of the set of travel actions on the grouping of electronic assets.
9. The method of claim 1, wherein the portal forms part of an operating system of the user computing device, and wherein the selection is presented from one of a shortcuts screen or an application tile that corresponds to a provider application for one of the electronic assets.
10. The method of claim 1, wherein the set of electronic assets comprises a non-payment item.
11. The method of claim 1, wherein the coordinated action imposes restrictions on the use of each one of the set of electronic assets.
12. The method of claim 1, wherein the coordinated action is ordering replacements of each one of the set of electronic assets.
13. A computing system having a processor and a memory storing executable code which causes the computing system, when executed, to: provide, via an internet connection, to a user computing device comprising an input device configured to detect at least one of biometric data, alphanumeric entries, or icon selections, a portal with a network security access control;receive, via the portal, login credentials detected using the input device of the user computing device and verify that the login credentials grant access to the portal;determine that the login credentials are associated with a set of electronic assets corresponding to a plurality of third-party computing systems with application programming interface (API) gateways configured to accept API calls directed to changes in functionality of the electronic assets;receive, via the portal, a selection of a coordinated action with respect to all electronic assets in the set of electronic assets, the selection detected via the input device of the remote user computing device; andexecute, based on the selection, a set of API calls comprising an asset-specific API call to each third-party computing system in the plurality of third-party computing systems to implement the coordinated action on each corresponding electronic asset in the set of electronic assets.
14. The computing system of claim 13, wherein the executable code further causes the computing system, when executed, to: determine, via the portal, an asset definition for each of the set of electronic assets, each asset definition comprising a third-party identifier that is indicative of a respective one of the plurality of third-party computing systems; andidentify the plurality of third-party computing systems based on the plurality of third-party identifiers.
15. The computing system of claim 14, wherein determining the asset definition for at least one electronic asset of the set of electronic assets comprises: presenting, via the portal, a scan tool configured to interface with an optical sensor of the user computing device and capture an image using the optical sensor; andreceiving, via the portal, the image of the electronic asset captured using the electronic sensor; andanalyzing, by the processor, the image to determine the third-party identifier.
16. The computing system of claim 13, wherein the third-party identifier comprises a logo, and wherein identifying each one of the plurality of third-party computing systems comprises: using optical character recognition to convert the logo to machine-readable text; andmatching the machine-readable text to one of a plurality of API identifiers corresponding to the asset-specific API call.
17. The computing system of claim 13, wherein the executable code further causes the computing system, when executed, to: present, via the portal, a travel planner configured to be selectable using the input device to identify a set of travel actions to be taken with respect to a grouping of electronic assets, and a travel selection indicative of at least one of a location of travel or a date of travel, the grouping of electronic assets comprising at least one electronic asset from the set of electronic assets;receive, via the portal, selection of the set of travel actions and the travel selection; andexecuting, based on the selection, the set of API calls to implement the selection of the set of travel actions on the grouping of electronic assets.
18. A method, comprising: presenting, on a display of a mobile device, a graphical user interface (GUI), the mobile device comprising an input device configured to detect at least one of alphanumeric entries, icon selections, or image data;receiving, by a processor from the input device, a plurality of asset definitions for a set of electronic assets, each asset definition comprising a third-party identifier that is indicative of a respective one of a plurality of third-party computing systems;identifying, via the processor, the plurality of third-party computing systems based on the plurality of third-party identifiers;presenting, by the display, via the GUI, a virtual icon configured to be selectable using the input device to identify a coordinated action with respect to all electronic assets in the set of electronic assets;detecting, by the processor, via the input device, a selection of the virtual icon from the input device; andtransmitting, based on the selection, via a transceiver of the mobile device, an indication of the selection to a remote computing system to implement the coordinated action on all electronic assets in the set of electronic assets.
19. The method of claim 18, wherein the GUI comprises a scan tool, and wherein receiving the asset definition for at least one electronic asset of the set of electronic assets comprises: capturing, via the input device, using the scan tool, image data of the electronic asset; andanalyzing the image data to identify the third-party identifier.
20. The method of claim 18, wherein the third-party identifier comprises a logo, and wherein identifying each one of the plurality of third-party computing systems comprises: using optical character recognition to convert the logo to machine-readable text;matching the machine-readable text to an API identifier of a plurality of API identifiers corresponding to one of the plurality of third-party computing systems; andtransmitting, via the transceiver, the API identifier to the remote computing system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/240,730, filed Apr. 26, 2021, which is a continuation of U.S. patent application Ser. No. 17/013,193, filed on Sep. 4, 2020, titled “Synchronous Interfacing with Unaffiliated Networked Systems to Alter Functionality of Sets of Electronic Assets,” all of which are incorporated herein by reference in its entireties.

US Referenced Citations (547)

Number	Name	Date	Kind
5485510	Colbert	Jan 1996	A
5573457	Watts et al.	Nov 1996	A
5737423	Manduley	Apr 1998	A
5999978	Angal et al.	Dec 1999	A
6047268	Bartoli et al.	Apr 2000	A
6105006	Davis et al.	Aug 2000	A
6188309	Levine	Feb 2001	B1
6193152	Fernando et al.	Feb 2001	B1
6408330	Delahuerga	Jun 2002	B1
6422462	Cohen	Jul 2002	B1
6494367	Zacharias	Dec 2002	B1
6575361	Graves et al.	Jun 2003	B1
6717592	Gusler et al.	Apr 2004	B2
6845906	Royer et al.	Jan 2005	B2
6865547	Brake et al.	Mar 2005	B1
6879965	Fung et al.	Apr 2005	B2
6910021	Brown et al.	Jun 2005	B2
6931382	Laage et al.	Aug 2005	B2
6980969	Tuchler et al.	Dec 2005	B1
7014107	Singer et al.	Mar 2006	B2
7016877	Steele et al.	Mar 2006	B1
7107243	McDonald et al.	Sep 2006	B1
7219833	Cantini et al.	May 2007	B2
7225156	Fisher et al.	May 2007	B2
7249099	Ling	Jul 2007	B2
7264154	Harris	Sep 2007	B2
7319986	Praisner et al.	Jan 2008	B2
7331518	Rable	Feb 2008	B2
7347361	Lovett	Mar 2008	B2
7359880	Abel et al.	Apr 2008	B2
7383988	Slonecker, Jr.	Jun 2008	B2
7392224	Bauer et al.	Jun 2008	B1
7398248	Phillips et al.	Jul 2008	B2
7401731	Pletz et al.	Jul 2008	B1
7413113	Zhu	Aug 2008	B1
7451395	Brants et al.	Nov 2008	B2
7512563	Likourezos et al.	Mar 2009	B2
7552088	Malcolm	Jun 2009	B2
7571142	Flitcroft et al.	Aug 2009	B1
7587365	Malik et al.	Sep 2009	B2
7653597	Stevanovski et al.	Jan 2010	B1
7685037	Reiners et al.	Mar 2010	B2
7689502	Lilly et al.	Mar 2010	B2
7698221	Blinn et al.	Apr 2010	B2
7707082	Lapstun et al.	Apr 2010	B1
7712655	Wong	May 2010	B2
7740170	Singh et al.	Jun 2010	B2
7753265	Harris	Jul 2010	B2
7778932	Yan	Aug 2010	B2
7818319	Henkin et al.	Oct 2010	B2
7873573	Realini	Jan 2011	B2
7937325	Kumar et al.	May 2011	B2
7941534	De La Huerga	May 2011	B2
7949572	Perrochon et al.	May 2011	B2
7954704	Gephart et al.	Jun 2011	B1
8090346	Cai	Jan 2012	B2
8099109	Altman et al.	Jan 2012	B2
8127982	Casey et al.	Mar 2012	B1
8160933	Nguyen et al.	Apr 2012	B2
8175938	Olliphant et al.	May 2012	B2
8196131	Von Behren et al.	Jun 2012	B1
8245909	Pletz et al.	Aug 2012	B2
8249983	Dilip et al.	Aug 2012	B2
8255323	Casey et al.	Aug 2012	B1
8266031	Norris et al.	Sep 2012	B2
8266205	Hammad et al.	Sep 2012	B2
8280786	Weiss et al.	Oct 2012	B1
8280788	Perlman	Oct 2012	B2
8296228	Kloor	Oct 2012	B1
8297502	Mcghie et al.	Oct 2012	B1
8301566	Mears	Oct 2012	B2
8332294	Thearling	Dec 2012	B1
8359531	Grandison et al.	Jan 2013	B2
8360952	Wissman et al.	Jan 2013	B2
8364556	Nguyen et al.	Jan 2013	B2
8396808	Greenspan	Mar 2013	B2
8407136	Bard et al.	Mar 2013	B2
8407142	Griggs	Mar 2013	B1
8423349	Huynh et al.	Apr 2013	B1
8473394	Marshall	Jun 2013	B2
8489761	Pope et al.	Jul 2013	B2
8489894	Comrie et al.	Jul 2013	B2
8543506	Grandcolas et al.	Sep 2013	B2
8589335	Smith et al.	Nov 2013	B2
8595074	Sharma et al.	Nov 2013	B2
8595098	Starai et al.	Nov 2013	B2
8625838	Song et al.	Jan 2014	B2
8630952	Menon	Jan 2014	B2
8635687	Binder	Jan 2014	B2
8639629	Hoffman	Jan 2014	B1
8655310	Katzer et al.	Feb 2014	B1
8655719	Li et al.	Feb 2014	B1
8660926	Wehunt et al.	Feb 2014	B1
8666411	Tokgoz et al.	Mar 2014	B2
8682753	Kulathungam	Mar 2014	B2
8682802	Kannanari	Mar 2014	B1
8700729	Dua	Apr 2014	B2
8706625	Vicente et al.	Apr 2014	B2
8712839	Steinert et al.	Apr 2014	B2
8725601	Ledbetter et al.	May 2014	B2
8762211	Killian et al.	Jun 2014	B2
8762237	Monasterio et al.	Jun 2014	B2
8768838	Hoffman	Jul 2014	B1
8781957	Jackson et al.	Jul 2014	B2
8781963	Feng et al.	Jul 2014	B1
8793190	Johns et al.	Jul 2014	B2
8794972	Lopucki	Aug 2014	B2
8851369	Bishop et al.	Oct 2014	B2
8868458	Starbuck et al.	Oct 2014	B1
8880047	Konicek et al.	Nov 2014	B2
8887997	Barret et al.	Nov 2014	B2
8924288	Easley et al.	Dec 2014	B1
8954839	Sharma et al.	Feb 2015	B2
9076134	Grovit et al.	Jul 2015	B2
9105021	Tobin	Aug 2015	B2
9195984	Spector et al.	Nov 2015	B1
9256871	Anderson et al.	Feb 2016	B2
9256904	Haller et al.	Feb 2016	B1
9305155	Vo et al.	Apr 2016	B1
9372849	Gluck et al.	Jun 2016	B2
9390417	Song et al.	Jul 2016	B2
9396491	Isaacson et al.	Jul 2016	B2
9444824	Balazs et al.	Sep 2016	B1
9489694	Haller et al.	Nov 2016	B2
9514456	England et al.	Dec 2016	B2
9519934	Calman et al.	Dec 2016	B2
9558478	Zhao	Jan 2017	B2
9569473	Holenstein et al.	Feb 2017	B1
9569766	Kneen	Feb 2017	B2
9576318	Caldwell	Feb 2017	B2
9646300	Zhou et al.	May 2017	B1
9647855	Deibert et al.	May 2017	B2
9690621	Kim et al.	Jun 2017	B2
9699610	Chicoine et al.	Jul 2017	B1
9740543	Savage et al.	Aug 2017	B1
9792636	Milne	Oct 2017	B2
9792648	Haller et al.	Oct 2017	B1
9849364	Tran et al.	Dec 2017	B2
9853959	Kapczynski et al.	Dec 2017	B1
9858576	Song et al.	Jan 2018	B2
9978046	Lefebvre et al.	May 2018	B2
10032146	Caldwell	Jul 2018	B2
10044501	Bradley et al.	Aug 2018	B1
10044647	Karp	Aug 2018	B1
10050779	Alness et al.	Aug 2018	B2
10055747	Sherman et al.	Aug 2018	B1
10115155	Haller et al.	Oct 2018	B1
10152756	Isaacson et al.	Dec 2018	B2
10157420	Narayana et al.	Dec 2018	B2
10187483	Golub et al.	Jan 2019	B2
10216548	Zhang et al.	Feb 2019	B1
10275602	Bjorn et al.	Apr 2019	B2
10359915	Asai	Jul 2019	B2
10402817	Benkreira et al.	Sep 2019	B1
10402818	Zarakas et al.	Sep 2019	B2
10417396	Bawa et al.	Sep 2019	B2
10423948	Wilson et al.	Sep 2019	B1
10445152	Zhang et al.	Oct 2019	B1
10460395	Grassadonia	Oct 2019	B2
10521798	Song et al.	Dec 2019	B2
10592882	Viswanath et al.	Mar 2020	B1
10650448	Haller et al.	May 2020	B1
10657503	Ebersole et al.	May 2020	B1
10867298	Duke et al.	Dec 2020	B1
10872005	Killis	Dec 2020	B1
10878496	Duong et al.	Dec 2020	B1
10963589	Fakhraie et al.	Mar 2021	B1
10984482	Thangarajah et al.	Apr 2021	B1
10992679	Fakhraie et al.	Apr 2021	B1
11107561	Matthieu et al.	Aug 2021	B2
11144903	Ready et al.	Oct 2021	B2
20010001856	Gould et al.	May 2001	A1
20010032183	Landry	Oct 2001	A1
20010051920	Joao et al.	Dec 2001	A1
20010056398	Scheirer	Dec 2001	A1
20020016749	Borecki et al.	Feb 2002	A1
20020035539	O'Connell	Mar 2002	A1
20020038289	Lawlor et al.	Mar 2002	A1
20020062249	Iannacci	May 2002	A1
20020095386	Maritzen et al.	Jul 2002	A1
20020143655	Elston et al.	Oct 2002	A1
20020169720	Wilson et al.	Nov 2002	A1
20030046246	Klumpp et al.	Mar 2003	A1
20030061163	Durfield	Mar 2003	A1
20030097331	Cohen	May 2003	A1
20030172040	Kemper et al.	Sep 2003	A1
20030195847	Felger	Oct 2003	A1
20030200179	Kwan	Oct 2003	A1
20030216997	Cohen	Nov 2003	A1
20030217001	McQuaide et al.	Nov 2003	A1
20040054564	Fonseca et al.	Mar 2004	A1
20040054591	Spaeth et al.	Mar 2004	A1
20040073903	Melchione et al.	Apr 2004	A1
20040078325	O'Connor	Apr 2004	A1
20040090825	Nam et al.	May 2004	A1
20040128243	Kavanagh et al.	Jul 2004	A1
20040143632	McCarty	Jul 2004	A1
20040148259	Reiners et al.	Jul 2004	A1
20040178907	Cordoba	Sep 2004	A1
20040225606	Nguyen et al.	Nov 2004	A1
20040249710	Smith et al.	Dec 2004	A1
20040249753	Blinn et al.	Dec 2004	A1
20040263901	Critelli et al.	Dec 2004	A1
20050010483	Ling	Jan 2005	A1
20050014705	Cheng et al.	Jan 2005	A1
20050039041	Shaw et al.	Feb 2005	A1
20050060233	Bonalle et al.	Mar 2005	A1
20050114705	Reshef et al.	May 2005	A1
20050131815	Fung et al.	Jun 2005	A1
20050199714	Brandt et al.	Sep 2005	A1
20050224587	Shin et al.	Oct 2005	A1
20050228750	Olliphant et al.	Oct 2005	A1
20050273431	Abel et al.	Dec 2005	A1
20060046745	Davidson	Mar 2006	A1
20060059110	Madhok et al.	Mar 2006	A1
20060178986	Giordano et al.	Aug 2006	A1
20060184456	De Janasz	Aug 2006	A1
20060190374	Sher	Aug 2006	A1
20060202012	Grano et al.	Sep 2006	A1
20060206912	Klarfeld et al.	Sep 2006	A1
20060235795	Johnson et al.	Oct 2006	A1
20060278698	Lovett	Dec 2006	A1
20070083463	Kraft	Apr 2007	A1
20070100773	Wallach	May 2007	A1
20070112673	Protti	May 2007	A1
20070123305	Chen et al.	May 2007	A1
20070143831	Pearson et al.	Jun 2007	A1
20070203836	Dodin	Aug 2007	A1
20070226086	Bauman et al.	Sep 2007	A1
20070255653	Tumminaro et al.	Nov 2007	A1
20070266257	Camaisa et al.	Nov 2007	A1
20080000052	Hong et al.	Jan 2008	A1
20080005037	Hammad et al.	Jan 2008	A1
20080017702	Little et al.	Jan 2008	A1
20080021787	Mackouse	Jan 2008	A1
20080029608	Kellum et al.	Feb 2008	A1
20080052226	Agarwal et al.	Feb 2008	A1
20080086398	Parlotto	Apr 2008	A1
20080115104	Quinn	May 2008	A1
20080149706	Brown et al.	Jun 2008	A1
20080154772	Carlson	Jun 2008	A1
20080170156	Kim	Jul 2008	A1
20080191878	Abraham	Aug 2008	A1
20080208726	Tsantes et al.	Aug 2008	A1
20080229383	Buss et al.	Sep 2008	A1
20080244724	Choe et al.	Oct 2008	A1
20080260119	Marathe et al.	Oct 2008	A1
20080283590	Oder et al.	Nov 2008	A1
20080301043	Unbehagen	Dec 2008	A1
20090005269	Martin et al.	Jan 2009	A1
20090007231	Kaiser et al.	Jan 2009	A1
20090055269	Baron	Feb 2009	A1
20090055642	Myers et al.	Feb 2009	A1
20090112763	Scipioni et al.	Apr 2009	A1
20090132351	Gibson	May 2009	A1
20090164324	Bishop et al.	Jun 2009	A1
20090205014	Doman et al.	Aug 2009	A1
20090228381	Mik et al.	Sep 2009	A1
20090287603	Lamar et al.	Nov 2009	A1
20090319638	Faith et al.	Dec 2009	A1
20100036769	Winters et al.	Feb 2010	A1
20100036906	Song et al.	Feb 2010	A1
20100063906	Nelsen et al.	Mar 2010	A1
20100082445	Hodge et al.	Apr 2010	A1
20100082487	Nelsen	Apr 2010	A1
20100094735	Reynolds et al.	Apr 2010	A1
20100100470	Buchanan et al.	Apr 2010	A1
20100114768	Duke et al.	May 2010	A1
20100132049	Vernal et al.	May 2010	A1
20100199098	King	Aug 2010	A1
20100228671	Patterson	Sep 2010	A1
20100274691	Hammad et al.	Oct 2010	A1
20100312700	Coulter et al.	Dec 2010	A1
20110023129	Vernal et al.	Jan 2011	A1
20110035318	Hargrove et al.	Feb 2011	A1
20110035596	Attia et al.	Feb 2011	A1
20110078010	Postrel	Mar 2011	A1
20110106698	Isaacson et al.	May 2011	A1
20110162057	Gottumukkala et al.	Jun 2011	A1
20110176010	Houjou et al.	Jul 2011	A1
20110178929	Durkin et al.	Jul 2011	A1
20110191177	Blackhurst et al.	Aug 2011	A1
20110191239	Blackhurst et al.	Aug 2011	A1
20110196791	Dominguez	Aug 2011	A1
20110202462	Keenan	Aug 2011	A1
20110218849	Rutigliano et al.	Sep 2011	A1
20110247055	Guo et al.	Oct 2011	A1
20110276479	Thomas	Nov 2011	A1
20110307826	Rivera et al.	Dec 2011	A1
20110320246	Tietzen et al.	Dec 2011	A1
20120024946	Tullis et al.	Feb 2012	A1
20120030109	Dooley Maley et al.	Feb 2012	A1
20120041881	Basu et al.	Feb 2012	A1
20120046994	Reisman	Feb 2012	A1
20120047072	Larkin	Feb 2012	A1
20120096534	Boulos et al.	Apr 2012	A1
20120099780	Smith et al.	Apr 2012	A1
20120101938	Kasower	Apr 2012	A1
20120123841	Taveau et al.	May 2012	A1
20120123933	Abel et al.	May 2012	A1
20120124658	Brudnicki et al.	May 2012	A1
20120158590	Salonen	Jun 2012	A1
20120197691	Grigg et al.	Aug 2012	A1
20120214577	Petersen et al.	Aug 2012	A1
20120227094	Begen et al.	Sep 2012	A1
20120239417	Pourfallah et al.	Sep 2012	A1
20120239670	Horn et al.	Sep 2012	A1
20120240235	Moore	Sep 2012	A1
20120246122	Short et al.	Sep 2012	A1
20120254038	Mullen	Oct 2012	A1
20120259782	Hammad	Oct 2012	A1
20120265682	Menon	Oct 2012	A1
20120265685	Brudnicki et al.	Oct 2012	A1
20120270522	Laudermilch et al.	Oct 2012	A1
20120296725	Dessert et al.	Nov 2012	A1
20120296831	Carrott	Nov 2012	A1
20120317036	Bower et al.	Dec 2012	A1
20130006847	Hammad et al.	Jan 2013	A1
20130031006	Mccullagh et al.	Jan 2013	A1
20130046690	Calman et al.	Feb 2013	A1
20130055378	Chang et al.	Feb 2013	A1
20130080219	Royyuru et al.	Mar 2013	A1
20130091452	Sorden et al.	Apr 2013	A1
20130103391	Millmore et al.	Apr 2013	A1
20130117696	Robertson et al.	May 2013	A1
20130132854	Raleigh et al.	May 2013	A1
20130151405	Head et al.	Jun 2013	A1
20130173402	Young et al.	Jul 2013	A1
20130174244	Taveau et al.	Jul 2013	A1
20130212666	Mattsson et al.	Aug 2013	A1
20130218649	Beal	Aug 2013	A1
20130218758	Koenigsbrueck et al.	Aug 2013	A1
20130226813	Voltz	Aug 2013	A1
20130240618	Hall	Sep 2013	A1
20130246258	Dessert	Sep 2013	A1
20130246272	Kirsch	Sep 2013	A1
20130254079	Murali	Sep 2013	A1
20130254115	Pasa et al.	Sep 2013	A1
20130339124	Postrel	Dec 2013	A1
20130346302	Purves et al.	Dec 2013	A1
20130346306	Kopp	Dec 2013	A1
20130346310	Burger et al.	Dec 2013	A1
20140006209	Groarke	Jan 2014	A1
20140019352	Shrivastava	Jan 2014	A1
20140026193	Saxman et al.	Jan 2014	A1
20140032419	Anderson et al.	Jan 2014	A1
20140032723	Nema	Jan 2014	A1
20140040144	Plomske et al.	Feb 2014	A1
20140046827	Hochstatter et al.	Feb 2014	A1
20140053069	Yan	Feb 2014	A1
20140067503	Ebarle Grecsek et al.	Mar 2014	A1
20140067683	Varadarajan	Mar 2014	A1
20140076967	Pushkin et al.	Mar 2014	A1
20140108260	Poole et al.	Apr 2014	A1
20140108263	Ortiz et al.	Apr 2014	A1
20140114780	Menefee et al.	Apr 2014	A1
20140114855	Bajaj et al.	Apr 2014	A1
20140122328	Grigg	May 2014	A1
20140123312	Marcotte	May 2014	A1
20140129357	Goodwin	May 2014	A1
20140129448	Aiglstorfer	May 2014	A1
20140143886	Eversoll et al.	May 2014	A1
20140149198	Kim et al.	May 2014	A1
20140149368	Lee et al.	May 2014	A1
20140162598	Villa-Real	Jun 2014	A1
20140164220	Desai et al.	Jun 2014	A1
20140172576	Spears et al.	Jun 2014	A1
20140172707	Kuntagod et al.	Jun 2014	A1
20140180854	Bryant, II	Jun 2014	A1
20140198054	Sharma et al.	Jul 2014	A1
20140200957	Biggs	Jul 2014	A1
20140207672	Kelley	Jul 2014	A1
20140237236	Kalinichenko et al.	Aug 2014	A1
20140248852	Raleigh et al.	Sep 2014	A1
20140250002	Isaacson et al.	Sep 2014	A1
20140258104	Harnisch	Sep 2014	A1
20140258110	Davis et al.	Sep 2014	A1
20140279309	Cowen et al.	Sep 2014	A1
20140279474	Evans et al.	Sep 2014	A1
20140279559	Smith et al.	Sep 2014	A1
20140282852	Vestevich	Sep 2014	A1
20140297438	Dua	Oct 2014	A1
20140306833	Ricci	Oct 2014	A1
20140324527	Kulkarni et al.	Oct 2014	A1
20140337188	Bennett et al.	Nov 2014	A1
20140344149	Campos	Nov 2014	A1
20140344153	Raj et al.	Nov 2014	A1
20140344877	Ohmata et al.	Nov 2014	A1
20140357233	Maximo et al.	Dec 2014	A1
20140365291	Shvarts	Dec 2014	A1
20140372308	Sheets	Dec 2014	A1
20140379575	Rogan	Dec 2014	A1
20150019443	Sheets et al.	Jan 2015	A1
20150019944	Kalgi	Jan 2015	A1
20150026026	Calman et al.	Jan 2015	A1
20150026049	Theurer et al.	Jan 2015	A1
20150026057	Calman et al.	Jan 2015	A1
20150032625	Dill et al.	Jan 2015	A1
20150032626	Dill et al.	Jan 2015	A1
20150032627	Dill et al.	Jan 2015	A1
20150039457	Jacobs et al.	Feb 2015	A1
20150046338	Laxminarayanan et al.	Feb 2015	A1
20150046339	Wong et al.	Feb 2015	A1
20150066768	Williamson et al.	Mar 2015	A1
20150079932	Zelinka et al.	Mar 2015	A1
20150082042	Hoornaert et al.	Mar 2015	A1
20150088756	Makhotin et al.	Mar 2015	A1
20150095238	Khan et al.	Apr 2015	A1
20150096039	Mattsson et al.	Apr 2015	A1
20150100477	Salama et al.	Apr 2015	A1
20150100495	Salama et al.	Apr 2015	A1
20150106239	Gaddam et al.	Apr 2015	A1
20150112870	Nagasundaram et al.	Apr 2015	A1
20150121500	Venkatanaranappa et al.	Apr 2015	A1
20150127524	Jacobs et al.	May 2015	A1
20150127547	Powell et al.	May 2015	A1
20150132984	Kim et al.	May 2015	A1
20150134700	Macklem et al.	May 2015	A1
20150142673	Nelsen et al.	May 2015	A1
20150149357	Ioannidis et al.	May 2015	A1
20150154595	Collinge et al.	Jun 2015	A1
20150178724	Ngo et al.	Jun 2015	A1
20150180836	Wong et al.	Jun 2015	A1
20150186856	Weiss et al.	Jul 2015	A1
20150193639	Esposito et al.	Jul 2015	A1
20150193764	Haggerty et al.	Jul 2015	A1
20150193866	Van Heerden et al.	Jul 2015	A1
20150199679	Palanisamy et al.	Jul 2015	A1
20150199689	Kumnick et al.	Jul 2015	A1
20150200495	Yu et al.	Jul 2015	A1
20150213435	Douglas et al.	Jul 2015	A1
20150220999	Thornton et al.	Aug 2015	A1
20150221149	Main et al.	Aug 2015	A1
20150229622	Grigg et al.	Aug 2015	A1
20150242853	Powell	Aug 2015	A1
20150248405	Rudich et al.	Sep 2015	A1
20150254635	Bondesen et al.	Sep 2015	A1
20150254646	Harkey et al.	Sep 2015	A1
20150254647	Bondesen et al.	Sep 2015	A1
20150254655	Bondesen et al.	Sep 2015	A1
20150254656	Bondesen et al.	Sep 2015	A1
20150269566	Gaddam et al.	Sep 2015	A1
20150286834	Ohtani et al.	Oct 2015	A1
20150287133	Marlov et al.	Oct 2015	A1
20150295906	Ufford et al.	Oct 2015	A1
20150312038	Palanisamy	Oct 2015	A1
20150319158	Kumnick	Nov 2015	A1
20150319198	Gupta et al.	Nov 2015	A1
20150324592	Dutta	Nov 2015	A1
20150332067	Gorod	Nov 2015	A1
20150339663	Lopreiato et al.	Nov 2015	A1
20150339664	Wong et al.	Nov 2015	A1
20150379508	Van	Dec 2015	A1
20160026997	Tsui et al.	Jan 2016	A1
20160028550	Gaddam et al.	Jan 2016	A1
20160028735	Francis et al.	Jan 2016	A1
20160036790	Shastry et al.	Feb 2016	A1
20160042381	Braine et al.	Feb 2016	A1
20160063497	Grant, IV	Mar 2016	A1
20160065370	Le Saint et al.	Mar 2016	A1
20160078428	Moser et al.	Mar 2016	A1
20160080403	Cunningham et al.	Mar 2016	A1
20160092696	Guglani et al.	Mar 2016	A1
20160092870	Salama et al.	Mar 2016	A1
20160092872	Prakash et al.	Mar 2016	A1
20160092874	O'Regan et al.	Mar 2016	A1
20160098577	Lacey et al.	Apr 2016	A1
20160098692	Johnson et al.	Apr 2016	A1
20160109954	Harris et al.	Apr 2016	A1
20160119296	Laxminarayanan et al.	Apr 2016	A1
20160125405	Alterman et al.	May 2016	A1
20160125409	Meredith et al.	May 2016	A1
20160127892	Huang et al.	May 2016	A1
20160140221	Park et al.	May 2016	A1
20160149875	Li et al.	May 2016	A1
20160155156	Gopal et al.	Jun 2016	A1
20160171483	Luoma et al.	Jun 2016	A1
20160173483	Wong et al.	Jun 2016	A1
20160180302	Bagot, Jr.	Jun 2016	A1
20160189121	Best et al.	Jun 2016	A1
20160217461	Gaddam et al.	Jul 2016	A1
20160232600	Purves	Aug 2016	A1
20160239437	Le et al.	Aug 2016	A1
20160239835	Marsyla	Aug 2016	A1
20160239840	Preibisch	Aug 2016	A1
20160260084	Main et al.	Sep 2016	A1
20160260176	Bernard et al.	Sep 2016	A1
20160267467	Rutherford et al.	Sep 2016	A1
20160267480	Metral	Sep 2016	A1
20160292673	Chandrasekaran	Oct 2016	A1
20160294879	Kirsch	Oct 2016	A1
20160314458	Douglas et al.	Oct 2016	A1
20160321669	Beck et al.	Nov 2016	A1
20160328522	Howley	Nov 2016	A1
20160358163	Kumar et al.	Dec 2016	A1
20160371471	Patton et al.	Dec 2016	A1
20160379211	Hoyos et al.	Dec 2016	A1
20170004506	Steinman et al.	Jan 2017	A1
20170011215	Poiesz et al.	Jan 2017	A1
20170011389	Mccandless et al.	Jan 2017	A1
20170024393	Choksi et al.	Jan 2017	A1
20170068954	Hockey et al.	Mar 2017	A1
20170078299	Castinado et al.	Mar 2017	A1
20170078303	Wu	Mar 2017	A1
20170091759	Selfridge et al.	Mar 2017	A1
20170132633	Whitehouse	May 2017	A1
20170147631	Nair et al.	May 2017	A1
20170161724	Lau	Jun 2017	A1
20170249478	Lovin	Aug 2017	A1
20170344991	Mark et al.	Nov 2017	A1
20170352028	Vridhachalam et al.	Dec 2017	A1
20170364898	Ach et al.	Dec 2017	A1
20180005323	Grassadonia	Jan 2018	A1
20180006821	Kinagi	Jan 2018	A1
20180025145	Morgner et al.	Jan 2018	A1
20180053200	Cronin et al.	Feb 2018	A1
20180088909	Baratta et al.	Mar 2018	A1
20180158137	Tsantes et al.	Jun 2018	A1
20180270363	Guday	Sep 2018	A1
20180276628	Radiotis et al.	Sep 2018	A1
20180349922	Carlson et al.	Dec 2018	A1
20180357440	Brady et al.	Dec 2018	A1
20190007381	Isaacson et al.	Jan 2019	A1
20190171831	Xin	Jun 2019	A1
20190197501	Senci et al.	Jun 2019	A1
20190220834	Moshal et al.	Jul 2019	A1
20190228173	Gupta et al.	Jul 2019	A1
20190228428	Bruner et al.	Jul 2019	A1
20190228430	Givol et al.	Jul 2019	A1
20190318122	Hockey et al.	Oct 2019	A1
20190325161	Zavesky et al.	Oct 2019	A1
20190332802	Barday et al.	Oct 2019	A1
20190333061	Jackson et al.	Oct 2019	A1
20190347442	Marlin et al.	Nov 2019	A1
20190354979	Crawford	Nov 2019	A1
20190356641	Isaacson et al.	Nov 2019	A1
20190362069	Park et al.	Nov 2019	A1
20190369845	Rucker	Dec 2019	A1
20190370798	Hu et al.	Dec 2019	A1
20190392443	Piparsaniya et al.	Dec 2019	A1
20200005347	Boal	Jan 2020	A1
20200074552	Shier et al.	Mar 2020	A1
20200090179	Song et al.	Mar 2020	A1
20200118114	Benkreira et al.	Apr 2020	A1
20200118133	Schmidt et al.	Apr 2020	A1
20200286057	Desai	Sep 2020	A1
20210303335	Foreman et al.	Sep 2021	A1

Foreign Referenced Citations (19)

Number	Date	Country
1 259 947	Nov 2002	EP
1 770 628	Apr 2007	EP
2 441 156	Feb 2008	GB
2 441 156	Feb 2008	GB
20160015375	Feb 2016	KR
WO-9013096	Nov 1990	WO
WO-0072245	Nov 2000	WO
WO-0072245	Nov 2000	WO
WO-03038551	May 2003	WO
WO-03038551	May 2003	WO
WO-2004081893	Sep 2004	WO
WO-2004090825	Oct 2004	WO
WO-2009151839	Dec 2009	WO
WO-2012054148	Apr 2012	WO
WO-2015103443	Jul 2015	WO
WO-2015135131	Sep 2015	WO
WO-2016015054	Jan 2016	WO
WO-2017035399	Mar 2017	WO
WO-2018005635	Jan 2018	WO

Non-Patent Literature Citations (28)

Entry
ASB, “How to command your cards with ASB Card Control” Apr. 20, 2015, https://www.youtube.com/watch?v=O1sfxvVUL74 (Year: 2015).
Authorize.Net. Authorize.Net Mobile Application: iOS User Guide. Sep. 2015. Authorize.Net LLC. Ver.2.0, 1-23. https://www.authorize.net/content/dam/anet-redesign/documents/iosuserguide.pdf (Year: 2015).
CO-OP THINK, Rachna Ahlawat at CO-OP THINK—Evolution Sessions from THINK14, Dec. 22, 2014, 26:22. https://www.youtube.com/watch?v=yEp-qfZoPhl (Year: 2014).
Demiriz et al. “Using Location Aware Business Rules for Preventing Retail Banking Frauds” Jan. 15, 2015, IEEE (Year: 2015).
Fiserv. CardValet: Mobile Application Training. Fiserv, Inc. 1-93. https://www.westernbanks.com/media/1664/ cardvalet-application .pdf (Year: 2015).
Notre Dame FCU “Irish Card Shield: How to Control Transaction Types” Jan. 15, 2016, 0:27, https://youtube.com/watch?v=0eZG1c6Bn38 (Year: 2016).
PCM Credit Union, “CardValet Tutorial” Jun. 24, 2015, https://www.youtube.com/watch?v=uGPh9Htw0Wc (Year: 2015).
Purchasing charges ahead. (1994). Electronic Buyers' News,, 68. Retrieved from https://dialog.proquest.com/professional/docview/681599288?accountid=131444 on Nov. 13, 2020 (Year: 1994).
U.S. Office Action on U.S. Appl. No. 16/719,419 dated May 12, 2021.
Austin Telco Federal Credit Union, “Lost or Stolen Cards”, www.atfcu.org/lost-stolen-cards.htm; Apr. 9, 2004. 6 pages.
BancFirst, “Lost Card”, https://www.bancfirst.com/contact.aspx, Oct. 28, 2003. 1 page.
CM/ECF, “CM/ECF Internet Credit Card Payment Guide”, https://www.vaeb.uscourts.gov/wordpress/?page_id=340, Mar. 16, 2005. 12 pages.
Cronian, Darrin “Credit card companies Freeze Spending whilst Abroad”, published Jun. 9, 2007, Available at: http://www.travel-rants.com/2007/06/09/credit-card-companies-freeze-spending-whilst-abroad/.
Fort Knox Federal Credit Union, “Lost or Stolen VISA Card”, http://www.fortknoxfcu.org/loststolen.html, Feb. 1, 2001. 2 pages.
IEEE Xplore; 2009 First Asian Himalayas International Conference on Internet: Emergence of Payment Systems in the age of Electronic Commerce.; The state off Art. Author S Singh Nov. 1, 2009 pp. 1-18 (Year: 2009).
Ip.com Search Query; May 5, 2020 (Year: 2020).
Konsko: “Credit Card Tokenization: Here's What You Need to Know”, Credit Card Basics, Credit Card—Advertisement Nerdwallet (Year: 2014).
Merrick Bank, “Reporting Lost or Stolen Card Help Return to the Cardholder Center FAQs”, http://www.merrickbank.com/Frequent-Asked-Questions/Report-Stolen-Card.aspx, Aug. 9, 2004. 1 page.
Microsoft, “Automatically summarize a document”, 2016. 3 pages.
Notice of Allowance on U.S. Appl. No. 15/360,343 dated Sep. 23, 2020.
RBC Royal Bank, “If Your Card is Lost or Stolen”, http://www.rblbank.com/pdfs/CreditCard/FAQs.pdf, Oct. 1, 2002. 2 pages.
State Employees Credit Union, “Lost or Stolen Account Info”, https://www.secumd.org/advice-planning/money-and-credit/privacy-fraud-protection/lost-or-stolen-account-info.aspx, May 20, 2005. 2 pages.
Transaction aggregation as a strategy for credit card fraud detection. file:///C:/Users/eoussir/Downloads/Transaction_aggregation_as_a_strategy for credit_c. pdf (Year: 2009).
Union Bank & Trust, “Report Lost or Stolen Card”, http://www.ubt.com/security-fraud/report-lost-or-stolen-cards, Jul. 10, 2005. 13 pages.
Using location aware business rules for preventing retail banking frauds. https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=7351936 (Year: 2015).
Smartphones as Practical and Secure Location Verification Tokens for Payments. file:///C:/Users/eoussir/Documents/e-Red% 20 Folder/15496961 /N PL_ Smartphones %20as %20 Practical %20and %20Secu re %20 Location %20Verification %20Tokens %20for% 20Payments.pdf (Year: 2014).
Urein et al.: “A breakthrough for prepaid payment: End to end token exchange and management using secure SSL channels created by EAP-TLS smart cards”, 2011 International Conference on Collaboration Technologies and Systems (CTS) (Year: 2011).
Yang MH. Security enhanced EMV-based mobile payment protocol. Scientific World Journal. 2014.https://www.ncbi.nlm.nih.gov/ pmc/articles/PMC4181509/ (Year: 2014).

Continuations (2)

	Number	Date	Country
Parent	17240730	Apr 2021	US
Child	17558469		US
Parent	17013193	Sep 2020	US
Child	17240730		US

Synchronous interfacing with unaffiliated networked systems to alter functionality of sets of electronic assets

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer