Dynamic utilization of alternative resources based on token association

Information

  • Patent Grant
  • 10986541
  • Patent Number
    10,986,541
  • Date Filed
    Monday, December 23, 2019
    4 years ago
  • Date Issued
    Tuesday, April 20, 2021
    3 years ago
Abstract
Embodiments of the present invention provide a system for dynamic utilization of alternative resources based on token association. The system is typically configured for receiving a request from a user to generate a generic token for a digital wallet located on a mobile device of the user, generating the generic token and associating one or more resource credentials of the user with the generic token, transmitting the generic token to the mobile device of the user and storing the generic token in the digital wallet, receiving an interaction request from an authorization network to route an interaction, and routing the interaction to complete the interaction by selecting at least one resource credential from the one or more resource credentials associated with the generic token and transmitting the at least one resource credential to the authorization network.
Description
BACKGROUND

The present invention relates to associating a token with alternative resources of a user and completing interactions by dynamically utilizing the alternative resources based on token association.


Sending notifications to users requires large quantities of data storage and large amounts of processing capacity. When an entity sends targeted notifications to users, there is a greater likelihood that the users actually take an action associated with the notification, and it reduces the amount of data storage and processing capacity required when compared to non-targeted notification. By sending notifications to a subset of users from a plurality of users (excluding other users), an entity reduce the data and storage and processing capacity without affecting the actions taken on such notifications. Therefore, there is a need for a system to more accurately and efficiently provide notifications.


SUMMARY

The following presents a simplified summary of one or more embodiments of the present invention, in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments of the present invention in a simplified form as a prelude to the more detailed description that is presented later.


Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for dynamic utilization of alternative resources. The system embodiments may comprise one or more memory devices having computer readable program code stored thereon, a communication device, and one or more processing devices operatively coupled to the one or more memory devices, wherein the one or more processing devices are configured to receiving a request from a user via a user application to generate a generic token for a digital wallet, wherein the user application and the digital wallet are located on a mobile device of the user. Upon receiving the request the one or more processing devices generate the generic token in response to receiving the request from the user and retrieve information associated with the mobile device of the user, wherein the information comprises at least identification code of the digital wallet located on the mobile device of the user. The one or more processing devices are further configured to transmit control signals to cause the mobile device to display a user interface for prompting the user to select one or more resource credentials to associate with the generic token and receive selection of the one or more resource credentials from the mobile device of the user. The retrieved identification code and the one or more resource credentials of the user are associated with the generic token and the generic token is transmitted to the mobile device of the user and stored the generic token in the digital wallet. Additionally, the generic token is transmitted to one or more authorization networks.


In some embodiments, the system receives an interaction request comprising the generic token from the one or more authorization networks to route an interaction, wherein the interaction request is associated with the interaction initiated by the user via the digital wallet. The system upon receiving the interaction request routes the interaction for completing the interaction by determining the one or more resource credentials associated with the generic token, selecting at least one resource credential from the one or more resource credentials associated with the generic token, and transmitting the at least one resource credential to the one or more authorization networks.


In some embodiments, selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on type of the interaction and the type of the interaction is determined based on the merchant associated with the interaction.


In some embodiments, selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on location of the interaction.


In some embodiments, selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on supplemental resources associated with the one or more resource credentials.


In some embodiments, the system prompts the user on the mobile device, via the user interface, to customize usage of the one or more resource credentials, receives user preferences from the mobile device of the user associated with the usage of the one or more resource credentials, and associates the user preferences with the generic token and store the user preferences in a data store.


In some embodiments, selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on the user preferences stored in the data store.


The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.





BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, where:



FIG. 1 is a flowchart illustrating a general process flow for implementing rule-based notification association, in accordance with embodiments of the present invention.



FIG. 2 is a flowchart illustrating a general process flow for queuing input information for performing rule-based notification association, in accordance with embodiments of the present invention.



FIG. 3 is a flowchart illustrating a general process flow for creation of generic token for a wallet of a user, in accordance with embodiments of the present invention.



FIG. 4 is a flowchart illustrating a general process flow for using the generic token to complete an interaction via an artificial intelligence engine, in accordance with embodiments of the present invention.



FIG. 5 is a flowchart illustrating a general process flow for using the generic token to complete an interaction based on user preferences, in accordance with embodiments of the present invention.





DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more embodiments. It may be evident; however, that such embodiment(s) may be practiced without these specific details. Like numbers refer to like elements throughout.


In accordance with embodiments of the invention, the terms “resource entity system” and “authentication networks” may include any organization that processes financial transactions including, but not limited to, banks, credit unions, savings and loan associations, card associations, settlement associations, investment companies, stock brokerages, resource management firms, insurance companies and the like. Furthermore, embodiments of the present invention use the term “user” or “customer.” It will be appreciated by someone with ordinary skill in the art that the user or customer may be a customer of the financial institution or a potential customer of the financial institution or an employee of the financial institution.


In accordance with embodiments of the invention, an “account” or “resource credential” is the relationship that a customer has with an entity, such as a financial institution. Examples of accounts include a deposit account, such as a transactional account (e.g., a banking account), a savings account, an investment account, a money market account, a time deposit, a demand deposit, a pre-paid account, a credit account, a debit/deposit account, a non-monetary user datafile that includes information associated with the user, or the like. The account is associated with and/or maintained by the entity.


In accordance with embodiments of the invention, an “interaction” may be a transaction, transfer of funds, transfer of resources, and may refer to any activities or communication between a user and an entity, between an entity and a third party system, activities or communication between multiple entities, communication between technology application and the like. Transfer of resources may refer to a payment, processing of funds, international transfer of funds, purchase of goods or services, a return of goods or services, a payment transaction, a credit transaction, or other interactions involving user's resource or account. Unless specifically limited by the context, a “transaction”, a “transfer of funds”, a “record” may refer to any activity initiated between a user and a resource entity or a third party system, or any combination thereof. Typical financial transactions include point of sale (POS) transactions, automated teller machine (ATM) transactions, person to person (p2p) transfers, internet transactions, online shopping, electronic funds transfers between accounts, transactions with a financial institution teller, personal electronic checks, conducting purchases using loyalty/reward points etc. When discussing the resource transfers or transactions are evaluated it could mean that the transactions has already occurred, is in the process of occurring or being processed, or it has yet to be processed/posted by one or more financial institutions. In accordance with embodiments of the invention, a “generic token” may be a unique identifier generated by the entity system to represent one or more resource credentials of the user in a digital wallet.


Many of the example embodiments and implementations described herein contemplate interactions engaged in by a user with a computing device and/or one or more communication devices and/or secondary communication devices. A “user”, as referenced herein, may refer to an entity or individual that has the ability and/or authorization to access and use one or more resources or portions of a resource. Furthermore, as used herein, the term “user computing device” or “mobile device” may refer to mobile phones, personal computing devices, tablet computers, wearable devices, smart devices and/or any portable electronic device capable of receiving and/or storing data therein.


A “user interface” is any device or software that allows a user to input information, such as commands or data, into a device, or that allows the device to output information to the user. For example, the user interface include a graphical user interface (GUI) or an interface to input computer-executable instructions that direct a processing device to carry out specific functions. The user interface typically employs certain input and output devices to input data received from a user second user or output data to a user. These input and output devices may include a display, mouse, keyboard, button, touchpad, touch screen, microphone, speaker, LED, light, joystick, switch, buzzer, bell, and/or other user input/output device for communicating with one or more users.


A “system environment”, as used herein, may refer to any information technology platform of an enterprise (e.g., a national or multi-national corporation) and may include a multitude of servers, machines, mainframes, personal computers, network devices, front and back end systems, database system and/or the like.


Systems, methods, and computer program products are herein disclosed that provide for dynamic utilization of alternative resources based on token association. The present systems do not have the capability of allowing the user to evaluate what interactions are associated with which digital wallets. A user may have multiple digital wallets and multiple resource credentials in each of the digital wallets. With increase in the use of digital wallets, it may be very difficult to track interactions performed via the digital wallets or control the use of resource credentials in digital wallets. The present invention solves the technical problem by providing a system which generates a generic token for a digital wallet and associates digital wallet identification code and one or more resource credentials of the user with the generic token, thereby allowing the user to track interactions and dynamically control the usage of resource credentials associated with the generic token. The system interacts with multiple systems such as mobile device of the user, merchant acquiring network, authorization systems, and/or the like to enable the feature of tracking interactions and dynamically controlling the usage of one or more resource credentials. Additionally, performing interactions via the generic token provide an additional layer of security by preventing misappropriation of resource credentials.



FIG. 1 illustrates a supplemental resource system environment 100, in accordance with embodiments of the invention. As illustrated in FIG. 1, one or more resource entity systems 10 are operatively coupled, via a network 2, to one or more user computer systems 20, one or more interaction entity systems 30, one or more third-party systems 40, and/or one or more other systems (not illustrated). In this way, the user 4 (e.g., one or more associates, employees, agents, contractors, sub-contractors, third-party representatives, customers, or the like), through a user application 27 (e.g., web browser, dedicated or specialized application, or the like), may access resource entity applications 17 (e.g., website, dedicated or specialized application, or the like) of the resource entity systems 10 to receive supplemental resources for interactions with interaction entities and request the resource entity system to generate generic tokens for digital wallets and associate one or more resource credentials of the user with the generic token. The resource entity system performs the process flows described in the present application.


The network 2 may be a global area network (GAN), such as the Internet, a wide area network (WAN), a local area network (LAN), or any other type of network or combination of networks. The network 2 may provide for wireline, wireless, or a combination of wireline and wireless communication between systems, services, components, and/or devices on the network 2.


As illustrated in FIG. 1, the resource entity systems 10 generally comprise one or more communication components 12, one or more processing components 14, and one or more memory components 16. The one or more processing components 14 are operatively coupled to the one or more communication components 12 and the one or more memory components 16. As used herein, the term “processing component” generally includes circuitry used for implementing the communication and/or logic functions of a particular system. For example, a processing component 14 may include a digital signal processor component, a microprocessor component, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations of the foregoing. Control and signal processing functions of the system are allocated between these processing components according to their respective capabilities. The one or more processing components 14 may include functionality to operate one or more software programs based on computer-readable instructions 18 thereof, which may be stored in the one or more memory components 16.


The one or more processing components 14 use the one or more communication components 12 to communicate with the network 2 and other components on the network 2, such as, but not limited to, the components of the user computer systems 20, the interaction entity systems 30, authorization network systems 40, or other systems. As such, the one or more communication components 12 generally comprise a wireless transceiver, modem, server, electrical connection, electrical circuit, or other component for communicating with other components on the network 2. The one or more communication components 12 may further include an interface that accepts one or more network interface cards, ports for connection of network components, Universal Serial Bus (USB) connectors and the like.


As further illustrated in FIG. 1, the resource entity systems 10 comprise computer-readable instructions 18 stored in the memory component 16, which in one embodiment includes the computer-readable instructions 18 of the resource entity application 17 (e.g., website application, dedicated application, or the like). In some embodiments, the one or more memory components 16 include one or more data stores 19 for storing data related to the resource entity systems 10, including, but not limited to, data created, accessed, and/or used by the resource entity application 17. The resource entity application 17 may be utilized to provide and/or store not only resources for the user 4, but also supplemental resources for the user, and apply such supplemental resources to the interactions of the user 4. The resource entity application


As illustrated in FIG. 1, users 4 may access the resource entity application 17, or other applications, through a user computer system 20. The user computer system 20 may be a desktop, mobile device (e.g., laptop, smartphone device, PDA, tablet, or other mobile device), or any other type of computer that generally comprises one or more communication components 22, one or more processing components 24, and one or more memory components 26.


The one or more processing components 24 are operatively coupled to the one or more communication components 22, the one or more image capture components 25, and the one or more memory components 26. The one or more processing components 24 use the one or more communication components 22 to communicate with the network 2 and other components on the network 2, such as, but not limited to, the resource entity systems 10, the interaction entity systems 30, authorization network systems 40, and/or other systems. As such, the one or more communication components 22 generally comprise a wireless transceiver, modem, server, electrical connection, or other component for communicating with other components on the network 2. The one or more communication components 22 may further include an interface that accepts one or more network interface cards, ports for connection of network components, Universal Serial Bus (USB) connectors and the like. Moreover, the one or more communication components 22 may include a keypad, keyboard, touch-screen, touchpad, microphone, mouse, joystick, other pointer component, button, soft key, and/or other input/output component(s) for communicating with the users 4.


As illustrated in FIG. 1, the user computer systems 20 may have computer-readable instructions 28 stored in the one or more memory components 26, which in one embodiment includes the computer-readable instructions 28 for user applications 27, such as dedicated applications (e.g., apps, applet, or the like), portions of dedicated applications, a web browser or other apps that allow the user 4 to take various actions, including allowing the user 4 to access applications located on other systems, or the like. In some embodiments, the user 4 utilizes the user applications 27, through the user computer systems 20, to access the resource entity applications 17 to accept supplemental resources. Moreover, in some embodiments the user 4 may also utilize the user applications 27, through the user computer systems 20, to enter into interactions with the interaction entity, through the interaction entity applications 37 and/or interaction entity systems 30.


As illustrated in FIG. 1, one or more interaction entity systems 30 may communicate with the resource entity systems 10 and/or user computer systems 20 to provide supplemental resources to the resource entity and/or to engage in interactions with the user 4. As such, the interaction entity systems 30 are operatively coupled, via a network 2, to the one or more resource entity systems 10, the user computer systems 20, the authorization network systems 40, and/or other systems. The interaction entity systems 30 generally comprise one or more communication components 32, one or more processing components 34, and one or more memory components 36.


The one or more processing components 34 are operatively coupled to the one or more communication components 32, and the one or more memory components 36. The one or more processing components 34 use the one or more communication components 32 to communicate with the network 2 and other components on the network 2, such as, but not limited to, the components of the resource entity systems 10, the user computer systems 20, the authorization network systems 40, and/or other systems. As such, the one or more communication components 32 generally comprise a wireless transceiver, modem, server, electrical connection, or other component for communicating with other components on the network 2. The one or more communication components 32 may further include an interface that accepts one or more network interface cards, ports for connection of network components, Universal Serial Bus (USB) connectors and the like.


As illustrated in FIG. 1, the interaction entity systems 30 may have computer-readable instructions 38 stored in the one or more memory components 36, which in one embodiment includes the computer-readable instructions 38 of interaction entity applications 37 that allow for the interactions with the user 4 and/or the resource entity regarding supplemental resources, as will be described herein.


Moreover, as illustrated in FIG. 1, authorization network systems 40, and/or other like systems are operatively coupled to the resource entity systems 10, the user computer systems 20, and/or the interaction entity systems 30, through the network 2. The authorization network systems 40 and/or other like systems have components the same as or similar to the components described with respect to the resource entity systems 10, the user computer systems 20, and/or the interaction entity systems 30 (e.g., one or more communication components, one or more processing components, and one or more memory devices with computer-readable instructions of one or more applications, one or more datastores, or the like). Thus, the authorization network systems 40 and/or other like systems communicate with the resource entity systems 10, the user computer systems 20, the interaction entity systems 30, and/or each other in same or similar way as previously described with respect to the resource entity systems 10, the user computer systems 20, and/or the interaction entity systems 30. The authorization network system may be any payment processing systems.


An embodiment of the present invention relates generally to a resource entity providing a notification to a user that results in the user being able to take an action, such that a user may enter into a future interaction using user's resources from a resource pool and supplemental resources related to the notification and/or action. In some embodiments, the resource entity may be a financial institution and the interaction entity may be a merchant, but it should be understood that the entities may be another third party entity acting on its own or as a third-party for the resource entity or interaction entity. In some embodiments, the resource entity or the interaction entity may be acting on behalf of one another. The notification may relate to supplemental resources (e.g., and offer, discount, rebate, or the like) that the user may utilize for a product (e.g., good or service) during an interaction (e.g., transaction, or the like) with an interaction entity. The notification may be presented to the user via various channels, such as through the user's online resource pool (e.g., online banking account, or the like), social network account, email, text message, or other like channel. In some embodiments, the user action may be the acceptance of the notification (e.g., acceptance of the supplemental resources). When the user accepts the supplemental resources, the supplemental resources are activated so that if the user uses eligible resources from an eligible resource pool (e.g., as determined by the resource entity, the interaction entity, third party entity, or the like) to enter into the interaction, the user receives the benefit associated with the supplemental resources. In other embodiments, the supplemental resources may be automatically activated if the user has previously chosen to automatically activate supplemental resources associated with particular interactions (e.g., associated with particular interaction entities or products). In some embodiments, the resource entity may determine that a user may choose among multiple eligible resources pools in order to enter into an interaction associated with the supplemental resources.


As will be described herein in further detail later, in some embodiments the present invention provides a targeted integrated interface that integrates information related to interactions that the user 4 has with interaction entities with resources used from the resource entities, and provides targeted supplemental resources to the user 4 through the targeted integrated interface. The present invention provides at least two different improvements to the technological environment of interactions that occurs over a network 2, such as the Internet. First, the present invention presents a targeted integrated interface that presents targeted supplemental resources to the user 4 in order to keep the user 4 within the resource entity systems 10 and to make the user 4 more likely to use the resources of the resource entity by providing supplemental resources to the user 4 for future interactions with various interaction entity systems 30. Secondly, the present invention reduces the storage and processing capacity required by the resource entity systems 10 to present the targeted supplemental resources to the users 4. Because the targeted integrated interface is utilized to present the targeted supplemental resources to the user 4, the number of notifications presented to the user 4 is greatly reduced because the notifications are specified to the user 4 and the user 4 can select the targeted supplemented resources that the user 4 wants to use.


Referring now to FIG. 2, a general process flow 200 is provided for implementing rule-based supplemental resource association. At block 210, the method comprises receiving at least one rule, the at least one rule comprising at least one of a user rule or an entity rule (e.g., a filtering rule that excludes or allows the user access to supplemental resources based on the user and/or the entities). As used herein, a user rule is a rule that determines the users 4 that can access or that are excluded from the supplemental resources (e.g., allows or excludes some users from receiving and/or using the supplemental resources). In some embodiments, the at least one user rule may comprise an affinity rule. Therefore, if the user 4 and interaction entity already have an existing relationship (e.g., for providing and/or using supplemental resources), these users may be allowed or excluded from receiving the supplemental resources through the resource entity. The affinity rule comprises at least one of a full affinity rule or a partial affinity rule. When the affinity rule comprises a full affinity rule, the user is completely allowed or excluded from receiving supplemental resources if the interaction entity already has an existing relationship with the user 4. When the affinity rule comprises a partial affinity rule, the user 4 is allowed to or excluded from receiving supplemental resources associated with a particular product, category of products, an entity, industry, or the like associated with a particular interaction entity that already has an existing relationship with the user 4 for the particular product, category of products, entity, industry, or the like; however, the user 4 may receive supplemental resources associated with other products, categories of products, entities, industries, or the like associated with the particular entity. Additionally or alternatively, the user 4 may be allowed to or excluded from receiving supplemental resources associated with a competitor of a particular interaction entity if that particular interaction entity already has an existing relationship with the user 4.


In some embodiments, an entity rule is a rule that allows or excludes some interaction entities from providing supplemental resources to users 4 associated with an interaction entity. In some embodiment, the at least one entity rule comprises a category code rule. Therefore, an interaction entity associated with a predetermined category code is allowed to or excluded from providing supplemental resources. However, the resource entity managing the resource pool of the user 4 may set up a list of interaction entities that trigger exceptions. Interaction entities that trigger exceptions can provide supplemental resources even if these entities are associated with the excluded category codes.


It should be understood that specific user rules and/or entity rules have been described herein; however, any user rules or entity rules may be utilized to determine what users 4 have access to supplemental resources.


At block 220, the method comprises receiving user information associated with a user 4, the user information may comprise resource pool information associated with the user's resource pool. In some embodiments, resource pool information, as used herein, refers to information associated with the user's resource pool managed by one or more resource entities. In some embodiments, the resource pool information comprises an interaction history (e.g., a transaction history, or the like) associated with the user's resource pool. The interaction history includes the types of interactions, frequency of interactions, resources used for the interactions, entities involved in the interactions, resource balance history, or the like. As used herein, an interaction, may be a transaction such as a purchase, a deposit, a withdrawal, a credit, a debit, or the like associated with a resource pool.


In some embodiments, the user information comprises other information as well. For example, in some embodiments, the user information comprises personal information (e.g., salary information, contact information (mailing address, email address, phone number, or the like), residence address history, education information, job information, or the like) associated with the user. In some embodiments, the personal information further comprises social network information associated with the user's social network account or other non-account related information associated with the user. In some embodiments, the user information further comprises user information (e.g., personal information, account information, or the like) associated with the user's immediate or extended family members or contacts (e.g., as determined from social network information).


At block 230, the method comprises determining whether to allow a user access to supplemental resources based on the at least one rule and/or based on the received user information. It should be understood that the resource entity may have agreements with interaction entities to for providing supplemental resources to the user 4 if the user 4 enters into interactions with the interaction entities. The supplemental resources enable the user 4 to apply the supplemental resources to an interaction with an interaction entity in order to reduce the resources the user 4 uses from the user's resource pool to complete the interaction. As such, using the at least one rule and the received user information, the resource entity determines the targeted supplemental resources to present to the user 4. By using targeted supplemental resources, the resource entity can identify the users 4 most likely to use the supplemental resources in order to keep the users from leaving the resource entity applications 17 and keep the user's using the resources of the resource entity for the interactions with the interaction entities, and also reduces the storage capacity and processing capacity required to present the supplemental resources to the users 4 (e.g., because the supplemental resources are targeted to specific users 4).


At block 240 in FIG. 2, when a user 4 qualifies for supplemental resources the resource entity may provide a notification to a user 4 regarding the supplemental resources. It should be understood that the user may receive a notification regarding the targeted supplemental resources from the resource entity. For example, the notification of the supplemental resources may be presented to the user 4 through the resource entity application 17 (e.g., user's online account accessed through the user computer systems 20), the social networking account of the user 4, electronic communication with the user 4 (e.g., user's e-mail, text message, sms message, other messaging channel, or the like), or the like, as will be described in further detail later.


As illustrated by block 250, regardless of how the supplemental resources are presented, an indication of an action is received regarding the one or more supplement resources accepted by or for the user 4. The user 4 may take an action by accepting one or more of the supplemental resources presented to the user 4. In other embodiments of the invention, one or more of the plurality of supplemental resources may be added automatically based on the one or more supplemental resources determined for the use as previously discussed with respect to block 230 (e.g., all of the supplemental resources for the user 4 are automatically added, or the like).


At block 240 an indication is received that a user 4 has entered into an interaction with an interaction entity using the user's resources from the resource pool of the user 4 at the resource entity. The indication may include the product associated with the interaction, the amount of the interaction, and/or the resource pool used by the user 4 to enter into the interaction. Should the interaction be allowed (e.g., there are no interaction limits on the user preventing the interaction, the interaction entity is allowed, the user's resource pool can cover the balance, or the like) resources from the user's resource pool are allocated for the interaction.


At block 250 as will be described, in some embodiments, the supplemental resources may be applied at a point of time in the future when the interaction that qualifies for the supplemental resources is processed.


In some embodiments, when an interaction is processed by the resource entity at a time in the future (e.g., at settlement time or processing time after the interaction is entered), the system determines whether the supplemental resources are still active and whether the supplemental resources are still valid with respect to both the user 4 and the interaction entity interacting with the user 4. This post-transaction process may be referred to as a supplemental resource reconciliation process. The supplemental resources are still active if the supplemental resources have not been revoked by at least one of the resource entity or the interaction entity, and/or if the supplemental resources have not expired.


The supplemental resources are valid with respect to the interaction entity if the interaction entity is not excluded under any entity rules. In some embodiments, in order for the supplemental resources to be valid, the interaction entity cannot be excluded under any entity rules that were in force at the time of the interaction. Additionally or alternatively, in some embodiments, in order for the supplemental resources to remain valid, the interaction entity cannot be excluded under any entity rules that are in force at the time of settlement of the interaction. Therefore, in some embodiments, the interaction entity cannot be excluded under any new entity rules that have been introduced since the interaction.


The supplemental interactions are valid for the user 4 if the user 4 is not excluded under any user rules. In some embodiments, in order for the supplemental resources to be valid, the user 4 cannot be excluded under any user rules that were in force at the time of the interaction. Additionally or alternatively, in some embodiments, in order for the supplemental resources to remain valid, the user cannot be excluded under any user rules that are in force at the time of settlement of the interaction. Therefore, in some embodiments, the user cannot be excluded under any new user rules that have been introduced since the purchase transaction.


In still other embodiments of the invention, the supplemental resources may also meet specific interaction rules regarding the interaction of the user with the interaction entity. The interaction rules may be set by the interaction entity and/or the resource entity. For example, the interaction rules may require the user 4 to enter the interaction at a specific date, time of day, location, interaction channel (e.g., in person, over the Internet, over a telephone, or the like), for a specific amount of resources, or the like. Moreover, the interaction rules may require the user 4 to use resources from specific resource pools.


If the user rules, interaction entity rules, and/or the interaction rules are met at the time of the interaction and/or time of settlement, the supplemental resources are still valid and the resource entity applies the amount of supplemental resources to the user's resource pool and/or reduces the resources provided to the interaction entity by the amount of the supplemental resources. In some embodiments, if at least one of the user rules, interaction entity rules, and/or the interaction rules are not met at the time of the interaction and/or settlement, the supplemental resources are invalid and the resource entity does not apply the amount of supplemental resources to the user's resource pool and/or applies the full amount of resources to the interaction entity. In alternate embodiments, even if at least one of the user rules, interaction entity rules, and/or interaction rules are not met at the time of settlement, the supplemental resources remain valid as long as the all of the rules were met at the time of the interaction, and consequently the resource entity applies the supplemental resources to the user's resource pool and reduces the resources provided to the interaction entity by the amount of the supplemental resources.


In some embodiments, the supplemental resources (e.g., a notification of the access to the supplemental resources) are presented via at least one of a targeted integrated interface associated with the user's resource pool (e.g., online banking account, mobile banking account on a portable mobile communication device, or the like), via a targeted integrated interface associated with the user's social network account, or the like. In some embodiments, a notification of the supplemental resources are inserted into or presented alongside (e.g., on the right, left, top, bottom side of an electronic interfaces related to an interaction with an interaction entity) the interaction history that is presented on the user's online resource pool interactions (e.g., online interaction account. Therefore, for example, if ten interactions are listed in the interaction history list, the notification of the supplemental resources may be presented between the fourth and fifth interactions on the list. In some embodiments, the notification of the supplemental resources may be related to the transaction which the offer is presented alongside (e.g., the fourth and/or fifth transaction in the above example). For example, if the fourth interaction is a transaction for product ‘A’ from interaction entity ‘A,’ the supplemental resources are for a transaction for product ‘A’ (e.g., from any interaction entity) or for a transaction from interaction entity ‘A’ (e.g., for any product) or for a transaction of product ‘A’ from interaction entity ‘A.’ Alternatively, the supplemental resources may be for a transaction of a substitute product ‘A’ (e.g., from interaction entity ‘A’ or from any other interaction entity).


In other embodiments of the invention, the supplemental resources may be provided as an alert within the resource entity application 17 (e.g., online interaction account), which when selected may provide a targeted integrated interface with a plurality of supplemental resources for which the user 4 qualifies. In some embodiments, the notification for the supplemental resources is transmitted to the user's email account. In other embodiments, the notification for the supplemental resources is transmitted, via text message or the like, to the user's mobile device.


In some embodiments, the presented supplemental resources are related to at least one of an interaction previously entered by the user (e.g., a previous transaction associated with the user's financial institution account), an interaction from an interaction entity from which the user previously entered into an interaction, an alternative to the interaction previously entered into by the user, or an alternative to the interaction from the interaction entity from which the user previously entered into an interaction. The alternative to the interaction may be determined based on interaction histories associated with a plurality of resource pools associated with multiple users.


In some embodiments, the presented notification for the supplemental resources relates to a new product related to a previous product interaction made by the user. For example, if the user previously bought a stove, the supplemental resources may be related to a dishwasher or a stove maintenance service.


In some embodiments, a notification of supplemental resources sent to or presented on a resource pool associated with a first member of a family may be used by a second member of the family. In some embodiments, the second member of the family may use the supplemental resources even if the second member is not associated with the resource pool associated with the first member. For example, the supplemental resources associated with a particular interaction entity may be transmitted to (or linked to) a resource pool associated with a first family member. When the second member of the family enters an interaction that qualifies for the supplemental resources using the second member's resource pool (e.g., any qualifying payment method), the second member receives the allocation of the supplemental resources after entering into the interaction. The resource entity may have access to information that indicates that the second member is a family member of the first member even if the second member is not listed as being associated with the resource pool associated with the first member.


Additionally, in some embodiments, as part of the previously described supplemental resources reconciliation process at the time of settlement of the supplemental resources, the system determines whether the resource pool information substantially matches the supplemental resources information. If the resource pool information has changed since the interaction such that the resource pool information no longer substantially matches the supplemental resources information, the supplemental resources may be deemed to be invalid and the resource entity does not provide allocation of the supplemental resources to the user's resource pool. However, in other embodiments, even if the resource pool information has changed since the interaction, the offer remains valid and the financial institution provides a rebate to the user's financial institution account.


Referring now to FIG. 3, a general process flow 300 is provided for creating a generic token for a digital wallet of the user. As shown in block 305, the system receives a request from a user via a user application to generate a generic token for a digital wallet, wherein the user application and the digital wallet are located on a mobile device of the user. For example, the user may sign into the online banking application and may send a request to the system to provide a generic token to represent a digital wallet located on the mobile of the user. The generic token described herein may be a unique identifier to represent the digital wallet of the user. In some embodiments, the generic token may be wallet specific. For example, a user may have multiple wallets and each wallet may have a unique generic token. In some embodiments, the generic token may be customer specific. For example, a customer may have only one generic token, wherein the generic token may any digit unique identifier representing the customer identity. In some embodiments, the generic token may be a sixteen digit identifier created by the resource entity system. In some embodiments, the generic token may be a device identification number of the mobile device comprising the digital wallet. The user application described in block 305 may be an online banking application provided by the resource entity system, wherein the resource entity system is a financial institution system maintaining one or more accounts of the user. The one or more accounts may include savings account, checking account, credit account, investment account, and/or the like. In some embodiments, the digital wallet application may be provided by the resource entity system. In alternate embodiments, the digital wallet application may be provided by a third party.


As shown in block 310, the system generates the generic token in response to receiving the request from the user. The generic token may be any digit unique identifier specific to the user or a digital wallet of the user. In some embodiments, the system may use a random generator algorithm to generate a unique number and may combine it with any information from the user datafile to generate the generic token. For example, the system may generate a unique ten digit number and may combine it with first name, initials of the user, date of birth of birth of the user. In some embodiments, the system may choose the generic token from a pre-created list of generic tokens. The pre-created list may be created by the system or by a third party entity.


As shown in block 315, the system retrieves information associated with the mobile device of the user, wherein the information comprises at least identification code of the digital wallet located on the mobile device of the user. The identification code may be any digit code which is allocated by digital wallet provider. For example, if the digital wallet is provided by a third party entity, the identification code is created and assigned to the digital wallet by the third party entity.


As shown in block 320, the system transmits control signals to cause the mobile device to display a user interface for prompting the user to select one or more resource credentials to associate with the generic token. The system may extract all resource credentials associated with the user and may display all the resource credentials on the user interface of the mobile device of the user. The user interface may be displayed to the user within the online banking application interface from where the user initiates the request. For example, the user may have multiple accounts such as checking account, savings account, credit account, and/or the like. In some instances, the user may use only checking account and credit account for daily transactions via the digital wallet and may like checking account and credit account to be associated with the generic token. The system displays user interface on the mobile device of the user to provide an option to the user to select at least one account from the one or more accounts to associate with the generic token.


As shown in block 325, the system receives selection of the one or more resource credentials from the mobile device of the user. For example, once the user selects at least one account from one or more accounts and submits the selected one or more resource credentials via the online banking application, the system receives the selection of one or more resource credentials to be associated with the generic token generated by the system. As shown in block 330, the system associates the generic token with the identification code and the one or more resource credentials of the user. The generic token is associated with the identification code and the one or more resource credentials of the user to allow the user track the interactions. For example, the user may have multiple digital wallets and multiple device. The user may prefer to track the transactions based on devices or digital wallets. By associating the generic token with identification code of the digital wallet A, the user may track all the transactions performed using digital wallet A. By associating one or more resource credentials of the user with the generic token, the user may restrict the use of resource credentials with the generic token. For example, if there are three accounts associated with the user, the user may choose to associate only two accounts with the generic token, thereby restricting the use of third account to perform transactions via the generic token. Additionally, associating the identification code with the generic token may restrict the use of generic token to particular digital wallet on a particular device.


As shown in block 335, the system transmits the generic token to the one or more authorization networks. The one or more authorization networks store the generic token in a data store, wherein the stored generic token is used to route the transactions. The authorization networks described herein may be any payment processing, authorizing, or routing networks. For example, once the user enters into a transaction at a merchant point of sale device, the payments are managed or routed via payment processing networks. These payment processing networks are responsible for communication between merchant acquiring entity (interaction entity) and user's issuing entity (resource entity). Transmitting the generic token to the one or more authorization networks helps with the process of routing the interactions. For example, the one or more authorization networks after receiving payment information (generic token) from the merchant acquiring entity route the payment to the user's issuing entity based on recognizing the generic token.


As shown in block 340, the system transmits the generic token to the mobile device of the user and stores the generic token in the digital wallet. The user may then use the generic token stored in the digital wallet to perform or initiate interactions. For example, the user may approach a point of sale device and enter into a transaction using the generic token stored in the digital wallet via Near Field Communication of the mobile device as opposed to using one or more resource credentials (account numbers). This method of using the generic token to enter into transactions instead of account numbers will provide an extra layer of security by masking account numbers to prevent misappropriation of account numbers. In some embodiments, in response to receiving the generic token from the system, the user may manually store the generic token in the digital wallet.


Referring to FIG. 4, a general process flow 400 is provided for illustrating the use of generic token for completing an interaction. As shown in block 410, the system receives an interaction request from the one or more authorization networks to route an interaction, wherein the interaction request is associated with the interaction initiated by the user via the digital wallet, wherein the interaction request comprises at least the generic token. In an exemplary embodiment, the user approaches a point of sale device of merchant A and initiates an interaction using the generic token stored in the digital wallet. The generic token is then received by the merchant acquiring entity and transferred to one or more authorization networks for further processing. The one or more authorization networks compare the generic token with all generic tokens stored in the data store to find a match. Upon finding a match, the one or more authorization networks determine the issuing entity associated with the generic token and send an interaction request to the issuing entity system to route the interaction. In some embodiments, the one or more authorization networks also transfer other information such as merchant name, merchant code, location of interaction, identification code of the user's digital wallet used for initiating the interaction, and/or the like.


As shown in block 440, the system automatically selects at least one resource credential from the one or more resource credentials associated with the generic token based at least on the type of the interaction or the location of the interaction. In one embodiment of the present invention, the system uses an artificial intelligence engine to automatically select the at least one resource credential from the one or more resource credentials associated with the generic token, wherein the artificial intelligence engine may use one or more rules to make the selection. In some embodiments, the artificial intelligence engine utilized by the system may automatically select the at least one resource credential based on determining the type of the interaction. For example, if credit card account ‘A’, credit card account ‘B’, credit card account ‘C’ are associated with the generic token and credit card account A may have a reward such as ten percent cash back on travel related transactions, credit card account ‘B’ may have a reward an such as five percent cash back on retail purchases, and credit card account ‘C’ may have a reward such as 15 percent cash back on purchases associated with groceries. The artificial intelligence engine utilized by the system may determine that the interaction request received from the one or more authorization networks is associated with a retail interaction based on the merchant code and the merchant name and may select credit card account B for completing the transaction. In some embodiments, the artificial intelligence engine utilized by the system may automatically select the at least one resource credential based on determining the location of the interaction. For example, if the user has a debit account and credit account associated with the generic token and the debit account may not have any foreign transaction payment, whereas the credit card may have a two percent foreign transaction payment. The artificial intelligence engine utilized by the system may determine that the location of the interaction is outside the country associated with the accounts of the user and may select the debit account for completing the transaction, thereby avoiding the foreign transaction payment. In some embodiments, the artificial intelligence engine utilized by the system may automatically select the at least one resource credential based on supplemental resources associated with the one or more resource credentials. For example, if credit card account ‘A’, credit card account ‘B’, credit card account ‘C’ are associated with the generic token and credit card B has supplemental resources added to it at some point before or after the initiation of the interaction, wherein the supplemental resources may be specific to a merchant ‘A’. The artificial intelligence engine utilized by the system may determine that the interaction is associated with merchant ‘A’ and may select credit card ‘B’ for completing the transaction. In some embodiments, the artificial intelligence engine utilized by the system may select the at least one resource credential based on resources available in the one or more resource credentials, thereby avoiding loading of the one or more resource credentials. For example, if credit card A has twenty percent funds available for interactions and credit card ‘B’ has more than twenty percent funds available for interactions, the artificial intelligence engine may select credit card B′ for completing the interaction.


As shown in block 450, the system routes the interaction by transmitting the at least one resource credential information selected by the artificial intelligence machine to the authorization network to complete the interaction. The one or more authorization networks upon receiving the at least one resource credential information may complete the interaction using the resource credential information. In some embodiments, the one or more authorization networks may transfer the at least one resource credential to card associations associated with the resource credential for completing the transaction. The card associations may be any clearing houses.


Referring to FIG. 5, a general process flow 500 is provided for illustrating the use of generic token for completing an interaction based on user preferences. As shown in block 510, the system prompts the user on the mobile device, via the user interface, to customize usage of the one or more resource credentials. In some embodiments, the system prompts the user to customize usage of the one or more resource credentials after receiving the selection of the one or more resource credentials from the user in block 325. In some embodiments, the user may customize the usage of the one or more resource credentials based on the type of interactions and/or the like. For example, the user may choose credit card account A for retail category transactions and debit card account B for travel category transactions. The type of interactions are determined by the system based on the merchant name or merchant code received from the one or more authorization networks. In some embodiments, the user may customize the usage of the one or more credentials based on supplemental resources associated with the one or more resource credentials. For example, if the user has added any supplemental resources using the process flow described in FIG. 2, the user may customize the usage of the resource credential associated with the supplemental resources based on merchant name or merchant code.


As shown in block 520, the system receives user preferences from the mobile device of the user associated with the usage of the one or more resource credentials. For example, once the user customizes the usage of the one or more accounts and submits the customized user preferences via the online banking application, the system receives the user preferences. As shown in block 530, the system associated the user preferences with the generic token and store the user preferences in the data store of the system. In some embodiments, the steps described in blocks 510-530 may be performed any time while performing the steps described in blocks 320-330 of FIG. 3.


As shown in block 540, the system receives an interaction request from the one or more authorization networks to route an interaction, wherein the interaction request is associated with the interaction initiated by the user via the digital wallet, wherein the interaction request comprises at least the generic token. In an exemplary embodiment, the user approaches a point of sale device of merchant A and initiates an interaction using the generic token stored in the digital wallet. The generic token is then received by the merchant acquiring entity and transferred to one or more authorization networks for further processing. The one or more authorization networks compare the generic token with all generic tokens stored in the data store to find a match. Upon finding a match, the one or more authorization networks determine the issuing entity associated with the generic token and send an interaction request to the issuing entity system to route the interaction. In some embodiments, the one or more authorization networks also transfer other information such as merchant name, merchant code, location of interaction, identification code of the user's digital wallet used for initiating the interaction, and/or the like.


As shown in block 550, the system determines the one or more resource credentials associated with the generic token upon receiving the request. For example, the system determines all accounts which are associated with the generic token. These accounts associated with the generic token are chosen by the user in blocks 320 and 325. As shown in block 560, the system selects a least one resource credential from the one or more resource credentials associated with the generic token based on the user preferences stored in the data store. For example, when the user preferences are based on the type of the interaction, the system determines that the interaction associated with the interaction request received from the one or more authorization networks is a retail interaction and selects the resource credential selected by the user for retail interactions.


As shown in block 570, As shown in block 450, the system routes the interaction by transmitting the at least one resource credential information selected by the artificial intelligence machine to the authorization network to complete the interaction. The one or more authorization networks upon receiving the at least one resource credential information may complete the interaction using the resource credential information. In some embodiments, the one or more authorization networks may transfer the at least one resource credential to card associations associated with the resource credential for completing the transaction. The card associations may be any clearing houses.


In one embodiment of the present invention, the user may use generic token to secure his accounts by only allowing interactions for the one or more resource credentials that are performed via the generic token. Additionally, dynamic utilization of one or more resource credentials associated with the user via the generic token may avoid loading of the one or more resource credentials of the user. In an exemplary embodiment, a resource credential associated with the user may be a shared resource credential. The user may control the usage of the resource credential by placing one or more limits. The one or more limits may be based on the type of interactions. The one or more limits may be placed while performing the process described in step 520. In other words, if the user is a primary user of the resource credential, the user may restrict the secondary user by not permitting the use of resource credential for retail transactions and may allow the secondary user to use the resource credential only for travel related transactions. In some embodiments of the present invention, the one or more resource credentials may include gift cards. In some other embodiments of the present invention, the generic token may be used for processes described in the U.S. Patent Applications, which are hereby incorporated by reference in its entirety.


Referring generally to the embodiments of the invention, supplement resources may be offers for discounts, rebates, and/or coupons (e.g., reverse couponing) that are applied to the user's resource pool retroactively after the interaction has been made. As such, the system enables transmission of individualized or personalized offers to users. For example, an offer associated with a merchant may be a 10% discount on a purchase made from that merchant. As an example, the activated offer may be a rebate of $5 on a purchase of $20 from a department store. The user may decide to use the offer by visiting the department store and making a purchase of $20. In some embodiments, at the point of sale, the user pays $20 for the user's purchase using an eligible payment method determined by the financial institution or the merchant (e.g., payment card, mobile device payment, check, or the like). When the transaction is processed by the financial institution at a predetermined settlement time in the future (e.g., as part of a periodic batch processing operation to generate monthly account statements), the financial institution provides a rebate of $5 to the user's financial institution account. Therefore, the department store, at the point of sale, may have no knowledge that the user will receive a rebate at some point in the future. In some embodiments, even the user may not be aware of the rebate at the point of sale (e.g., if the offer was automatically activated). In other embodiments, the point of sale terminal may provide an indication to at least one of the department store or the user that the user will receive a rebate at some point in the future.


Although many embodiments of the present invention have just been described above, the present invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Also, it will be understood that, where possible, any of the advantages, features, functions, devices, and/or operational aspects of any of the embodiments of the present invention described and/or contemplated herein may be included in any of the other embodiments of the present invention described and/or contemplated herein, and/or vice versa. In addition, where possible, any terms expressed in the singular form herein are meant to also include the plural form and/or vice versa, unless explicitly stated otherwise. Accordingly, the terms “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein. Like numbers refer to like elements throughout.


As will be appreciated by one of ordinary skill in the art in view of this disclosure, the present invention may include and/or be embodied as an apparatus (including, for example, a system, machine, device, computer program product, and/or the like), as a method (including, for example, a business method, computer-implemented process, and/or the like), or as any combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely business method embodiment, an entirely software embodiment (including firmware, resident software, micro-code, stored procedures in a database, or the like), an entirely hardware embodiment, or an embodiment combining business method, software, and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product that includes a computer-readable storage medium having one or more computer-executable program code portions stored therein. As used herein, a processor, which may include one or more processors, may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing one or more computer-executable program code portions embodied in a computer-readable medium, and/or by having one or more application-specific circuits perform the function.


It will be understood that any suitable computer-readable medium may be utilized. The computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, electromagnetic, infrared, and/or semiconductor system, device, and/or other apparatus. For example, in some embodiments, the non-transitory computer-readable medium includes a tangible medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), and/or some other tangible optical and/or magnetic storage device. In other embodiments of the present invention, however, the computer-readable medium may be transitory, such as, for example, a propagation signal including computer-executable program code portions embodied therein. In some embodiments, memory may include volatile memory, such as volatile random access memory (RAM) having a cache area for the temporary storage of information. Memory may also include non-volatile memory, which may be embedded and/or may be removable. The non-volatile memory may additionally or alternatively include an EEPROM, flash memory, and/or the like. The memory may store any one or more of pieces of information and data used by the system in which it resides to implement the functions of that system.


One or more computer-executable program code portions for carrying out operations of the present invention may include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript, and/or the like. In some embodiments, the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages. The computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F#.


Some embodiments of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of apparatus and/or methods. It will be understood that each block included in the flowchart illustrations and/or block diagrams, and/or combinations of blocks included in the flowchart illustrations and/or block diagrams, may be implemented by one or more computer-executable program code portions. These one or more computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer-executable program code portions, which execute via the processor of the computer and/or other programmable data processing apparatus, create mechanisms for implementing the steps and/or functions represented by the flowchart(s) and/or block diagram block(s).


The one or more computer-executable program code portions may be stored in a transitory and/or non-transitory computer-readable medium (e.g., a memory or the like) that can direct, instruct, and/or cause a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s).


The one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus. In some embodiments, this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s). Alternatively, computer-implemented steps may be combined with, and/or replaced with, operator- and/or human-implemented steps in order to carry out an embodiment of the present invention.


While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations, modifications, and combinations of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.


INCORPORATION BY REFERENCE

To supplement the present disclosure, this application further incorporates entirely by reference the following commonly assigned patent applications:














U.S. Patent




Application Ser.
Title
Filed On







U.S. patent application No.
SYSTEM FOR LINKING
Jun. 22, 2017


15/630,381 now
ALTERNATE RESOURCES



published as
TO RESOURCE POOLS AND



2018/0373569
ALLOCATING LINKED




ALTERNATIVE




RESOURCES TO A




RESOURCE INTERACTION



U.S. patent application No.
PROACTIVE RESOURCE
Jun. 22, 2017


15/630,284 now
ACQUISITION BASED ON



published as
ANTICIPATED NEED



2018/0375794




U.S. patent application No.
DATA TRANSMISSION TO
Jun. 22, 2017


15/630,289 now
A NETWORKED



published as
RESOURCE BASED ON



2018/0375859
CONTEXTUAL




INFORMATION



U.S. patent application No.
DATA TRANSMISSION
Jun. 22, 2017


15/630,355 now U.S.
BETWEEN NETWORKED



Pat. No.
RESOURCES



10.313,480 B2








Claims
  • 1. A system for dynamic utilization of alternative resources, the system comprising: a memory device with computer-readable program code stored thereon;a communication device;a processing device operatively coupled to the memory device and the communication device, wherein the processing device is configured to execute the computer-readable program code to: receive a request from a user via a user application to generate a generic token for a digital wallet, wherein the user application and the digital wallet are located on a mobile device of the user;identify a device identifier associated with the mobile device;generate the generic token using the device identifier of the mobile device in response to receiving the request from the user;retrieve information associated with the mobile device of the user, wherein the information comprises at least identification code of the digital wallet located on the mobile device of the user;transmit control signals to cause the mobile device to display a user interface for prompting the user to select one or more resource credentials to associate with the generic token;receive selection of the one or more resource credentials from the mobile device of the user;associate the generic token with the identification code and the one or more resource credentials of the user;transmit the generic token to the mobile device of the user and store the generic token in the digital wallet; andreceive an interaction request from one or more authorization networks to route an interaction, wherein the interaction request is associated with the interaction initiated by the user via the digital wallet, wherein the interaction request comprises at least the generic token; androute the interaction for completing the interaction by: determining the one or more resource credentials associated with the generic token;determining resource amounts associated with the one or more resource credentials;determining a type of the interaction and selecting at least one resource credential from the one or more resource credentials associated with the generic token based on the type of the interaction and the resource amounts associated with the one or more resource credentials; andtransmitting the at least one resource credential to the one or more authorization networks.
  • 2. The system of claim 1, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on location of the interaction.
  • 3. The system of claim 1, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on supplemental resources associated with the one or more resource credentials.
  • 4. The system of claim 3, wherein the supplemental resources are offers accepted by the user.
  • 5. The system of claim 1, wherein the processing device is further configured to: prompt the user on the mobile device, via the user interface, to customize usage of the one or more resource credentials;receive user preferences from the mobile device of the user associated with the usage of the one or more resource credentials; andassociate the user preferences with the generic token and store the user preferences in a data store.
  • 6. The system of claim 5, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on the user preferences stored in the data store.
  • 7. The system of claim 1, wherein the type of the interaction is determined based on a merchant associated with the interaction.
  • 8. A non-transitory computer readable medium comprising computer readable instructions for: receiving a request from a user via a user application to generate a generic token for a digital wallet, wherein the user application and the digital wallet are located on a mobile device of the user;identifying a device identifier associated with the mobile device;generating the generic token using the device identifier of the mobile device in response to receiving the request from the user;retrieving information associated with the mobile device of the user, wherein the information comprises at least identification code of the digital wallet located on the mobile device of the user;transmitting control signals to cause the mobile device to display a user interface for prompting the user to select one or more resource credentials to associate with the generic token;receiving selection of the one or more resource credentials from the mobile device of the user;associating the generic token with the identification code and the one or more resource credentials of the user;transmitting the generic token to the mobile device of the user and store the generic token in the digital wallet; andreceiving an interaction request from one or more authorization networks to route an interaction, wherein the interaction request is associated with the interaction initiated by the user via the digital wallet, wherein the interaction request comprises at least the generic token; androuting the interaction for completing the interaction by: determining the one or more resource credentials associated with the generic token;determining resource amounts associated with the one or more resource credentials;determining a type of the interaction and selecting at least one resource credential from the one or more resource credentials associated with the generic token based on the type of the interaction and the resource amounts associated with the one or more resource credentials; andtransmitting the at least one resource credential to the one or more authorization networks.
  • 9. The non-transitory computer readable medium of claim 8, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on location of the interaction.
  • 10. The non-transitory computer readable medium of claim 8, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on supplemental resources associated with the one or more resource credentials.
  • 11. The non-transitory computer readable medium of claim 10, wherein the supplemental resources are offers accepted by the user.
  • 12. The non-transitory computer readable medium of claim 8, wherein the at least one non-transitory computer readable medium comprises computer readable instructions for: prompting the user on the mobile device, via the user interface, to customize usage of the one or more resource credentials;receiving user preferences from the mobile device of the user associated with the usage of the one or more resource credentials; andassociating the user preferences with the generic token and store the user preferences in a data store.
  • 13. The non-transitory computer readable medium of claim 12, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on the user preferences stored in the data store.
  • 14. The non-transitory computer readable medium of claim 8, wherein the type of the interaction is determined based on a merchant associated with the interaction.
  • 15. A computer-implemented method implemented in hardware for dynamic utilization of alternative resources, the computer-implemented method comprises: receiving a request from a user via a user application to generate a generic token for a digital wallet, wherein the user application and the digital wallet are located on a mobile device of the user;identifying a device identifier associated with the mobile device;generating the generic token using the device identifier of the mobile device in response to receiving the request from the user;retrieving information associated with the mobile device of the user, wherein the information comprises at least identification code of the digital wallet located on the mobile device of the user;transmitting control signals to cause the mobile device to display a user interface for prompting the user to select one or more resource credentials to associate with the generic token;receiving selection of the one or more resource credentials from the mobile device of the user;associating the generic token with the identification code and the one or more resource credentials of the user;transmitting the generic token to the mobile device of the user and store the generic token in the digital wallet; andreceiving an interaction request from one or more authorization networks to route an interaction, wherein the interaction request is associated with the interaction initiated by the user via the digital wallet, wherein the interaction request comprises at least the generic token; androuting the interaction for completing the interaction by: determining the one or more resource credentials associated with the generic token;determining resource amounts associated with the one or more resource credentials;determining a type of the interaction and selecting at least one resource credential from the one or more resource credentials associated with the generic token based on the type of the interaction and the resource amounts associated with the one or more resource credentials; andtransmitting the at least one resource credential to the one or more authorization networks.
  • 16. The computer-implemented method of claim 15, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on location of the interaction.
  • 17. The computer-implemented method of claim 15, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on supplemental resources associated with the one or more resource credentials.
  • 18. The computer-implemented method of claim 15, wherein the computer-implemented method further comprises: prompting the user on the mobile device, via the user interface, to customize usage of the one or more resource credentials;receiving user preferences from the mobile device of the user associated with the usage of the one or more resource credentials; andassociating the user preferences with the generic token and store the user preferences in a data store.
  • 19. The computer-implemented method of claim 18, wherein selecting the at least one resource credential from the one or more resource credentials for routing the interaction is based on the user preferences stored in the data store.
  • 20. The computer-implemented method of claim 15, wherein the type of the interaction is determined based on a merchant associated with the interaction.
CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority from allowed, co-pending U.S. patent application Ser. No. 15/630,270, filed on Jun. 22, 2017 and entitled “DYNAMIC UTILIZATION OF ALTERNATIVE RESOURCES BASED ON TOKEN ASSOCIATION,” the entire disclosure of which is hereby incorporated herein by reference.

US Referenced Citations (1081)
Number Name Date Kind
3119103 Fertig Jan 1964 A
3254000 Chibret May 1966 A
3256670 Tersigni Jun 1966 A
3307412 Granqvist Mar 1967 A
3330546 Bryan Jul 1967 A
3352730 Murch, Jr. Nov 1967 A
3516056 Matthews Jun 1970 A
3658393 Luthi Apr 1972 A
3718328 Comstock Feb 1973 A
4766293 Boston Aug 1988 A
5041851 Nelson Aug 1991 A
5176224 Spector Jan 1993 A
5192854 Counts Mar 1993 A
5201010 Deaton et al. Apr 1993 A
5202826 McCarthy Apr 1993 A
5227874 Von Kohorn Jul 1993 A
5239165 Novak Aug 1993 A
5245533 Marshall Sep 1993 A
5250789 Johnsen Oct 1993 A
5256863 Ferguson et al. Oct 1993 A
5265008 Benton et al. Nov 1993 A
5283734 Von Kohorn Feb 1994 A
5285278 Holman Feb 1994 A
5287181 Holman Feb 1994 A
5305196 Deaton et al. Apr 1994 A
5353218 De Lapa et al. Oct 1994 A
5368129 Von Kohorn Nov 1994 A
5373440 Cohen et al. Dec 1994 A
5388165 Deaton et al. Feb 1995 A
5398326 Lee Mar 1995 A
5398932 Eberhardt et al. Mar 1995 A
5417424 Snowden et al. May 1995 A
5420606 Begum et al. May 1995 A
5430644 Deaton et al. Jul 1995 A
5438186 Nair et al. Aug 1995 A
5448471 Deaton et al. Sep 1995 A
5470079 LeStrange et al. Nov 1995 A
5471669 Lidman Nov 1995 A
5484998 Bejnar et al. Jan 1996 A
5491326 Marceau et al. Feb 1996 A
5492370 Chatwin et al. Feb 1996 A
5497314 Novak Mar 1996 A
5501491 Thompson Mar 1996 A
5508731 Kohom Apr 1996 A
5517015 Curry et al. May 1996 A
5523794 Mankovitz et al. Jun 1996 A
5537314 Kanter Jul 1996 A
5539450 Handelman Jul 1996 A
5557516 Hogan Sep 1996 A
5570465 Tsakanikas Oct 1996 A
5588649 Blumberg et al. Dec 1996 A
5592212 Handelman Jan 1997 A
5592376 Hodroff Jan 1997 A
5592560 Deaton et al. Jan 1997 A
5603078 Henderson et al. Feb 1997 A
5612527 Ovadia Mar 1997 A
5612868 Off et al. Mar 1997 A
5613012 Hoffman et al. Mar 1997 A
5619066 Curry et al. Apr 1997 A
5620079 Molbak Apr 1997 A
5621812 Deaton et al. Apr 1997 A
5638457 Deaton et al. Jun 1997 A
5644723 Deaton et al. Jul 1997 A
5649114 Deaton et al. Jul 1997 A
5650604 Marcous et al. Jul 1997 A
5651168 Tung et al. Jul 1997 A
5659469 Deaton et al. Aug 1997 A
5659740 Ezaki et al. Aug 1997 A
5675662 Deaton et al. Oct 1997 A
5687322 Deaton et al. Nov 1997 A
5689100 Carrithers et al. Nov 1997 A
5703795 Mankovitz Dec 1997 A
5708782 Larson et al. Jan 1998 A
5710886 Christensen et al. Jan 1998 A
5715448 Suzuki et al. Feb 1998 A
5731980 Dolan et al. Mar 1998 A
5732398 Tagawa Mar 1998 A
5734838 Robinson et al. Mar 1998 A
5736721 Swartz Apr 1998 A
5739512 Tognazzini Apr 1998 A
5745555 Mark Apr 1998 A
5759101 Von Kohorn Jun 1998 A
5767896 Nemirofsky Jun 1998 A
5789732 McMahon et al. Aug 1998 A
5791991 Small Aug 1998 A
5799767 Molbak Sep 1998 A
5805719 Pare, Jr. et al. Sep 1998 A
5806044 Powell Sep 1998 A
5819239 Berson et al. Oct 1998 A
5821512 Ohagan et al. Oct 1998 A
5822735 De Lapa et al. Oct 1998 A
5822744 Kesel Oct 1998 A
5832457 Obrien et al. Nov 1998 A
5832458 Jones Nov 1998 A
5838812 Pare, Jr. et al. Nov 1998 A
5841870 Fieres et al. Nov 1998 A
5845259 West et al. Dec 1998 A
5845265 Woolston Dec 1998 A
5852813 Guenther et al. Dec 1998 A
5855007 Jovicic et al. Dec 1998 A
5855369 Lieberman Jan 1999 A
5855514 Kamille Jan 1999 A
5857175 Day et al. Jan 1999 A
5859414 Grimes et al. Jan 1999 A
5865470 Thompson Feb 1999 A
5870723 Pare, Jr. et al. Feb 1999 A
5873069 Reuhl et al. Feb 1999 A
5880449 Teicher et al. Mar 1999 A
5884278 Powell Mar 1999 A
5887271 Powell Mar 1999 A
5892827 Beach et al. Apr 1999 A
5895902 Ziarno Apr 1999 A
5905246 Fajkowski May 1999 A
5907350 Nemirofsky May 1999 A
5916024 Von Kohorn Jun 1999 A
5917168 Nakamura et al. Jun 1999 A
5918213 Bernard et al. Jun 1999 A
5923016 Fredregill et al. Jul 1999 A
5924080 Johnson Jul 1999 A
5926795 Williams Jul 1999 A
5926796 Walker et al. Jul 1999 A
5931467 Kamille Aug 1999 A
5943424 Berger et al. Aug 1999 A
5948040 DeLorme et al. Sep 1999 A
5950173 Perkowski Sep 1999 A
5953047 Nemirofsky Sep 1999 A
5953705 Oneda Sep 1999 A
5956695 Carrithers et al. Sep 1999 A
5967844 Doutrich et al. Oct 1999 A
5970469 Scroggie et al. Oct 1999 A
5970470 Walker et al. Oct 1999 A
5973102 McCloskey et al. Oct 1999 A
5974396 Anderson et al. Oct 1999 A
5978013 Jones et al. Nov 1999 A
5979757 Tracy et al. Nov 1999 A
5988346 Tedesco et al. Nov 1999 A
5992570 Walter et al. Nov 1999 A
5992888 North et al. Nov 1999 A
6000608 Dorf Dec 1999 A
6009411 Kepecs Dec 1999 A
6012038 Powell Jan 2000 A
6012039 Hoffman et al. Jan 2000 A
6014634 Scroggie et al. Jan 2000 A
6016255 Bolan et al. Jan 2000 A
6021362 Maggard et al. Feb 2000 A
6023688 Ramachandran et al. Feb 2000 A
6024288 Gottlich et al. Feb 2000 A
6026387 Kesel Feb 2000 A
6028920 Carson Feb 2000 A
6032127 Schkolnick et al. Feb 2000 A
6035280 Christensen Mar 2000 A
6038549 Davis et al. Mar 2000 A
6039244 Finsterwald Mar 2000 A
6048271 Barcelou Apr 2000 A
6055513 Katz et al. Apr 2000 A
6076068 DeLapa et al. Jun 2000 A
6105013 Curry et al. Aug 2000 A
6110041 Walker et al. Aug 2000 A
6116402 Beach et al. Sep 2000 A
6116505 Withrow Sep 2000 A
6119103 Basch et al. Sep 2000 A
6125349 Maher Sep 2000 A
6129346 Zorn Oct 2000 A
6138105 Walker et al. Oct 2000 A
6138911 Fredregill et al. Oct 2000 A
6161059 Tedesco et al. Dec 2000 A
6185545 Resnick et al. Feb 2001 B1
6189787 Dorf Feb 2001 B1
6199753 Tracy et al. Mar 2001 B1
6230143 Simons et al. May 2001 B1
6233564 Schulze, Jr. May 2001 B1
6237145 Narasimhan et al. May 2001 B1
6251017 Leason et al. Jun 2001 B1
6254000 Degen et al. Jul 2001 B1
6256670 Davies Jul 2001 B1
6266647 Fernandez Jul 2001 B1
6276724 Zorn Aug 2001 B1
6292785 McEvoy et al. Sep 2001 B1
6292786 Deaton et al. Sep 2001 B1
6306035 Kelly et al. Oct 2001 B1
6308893 Waxelbaum et al. Oct 2001 B1
6311896 Mulla et al. Nov 2001 B1
6314519 Davis et al. Nov 2001 B1
6321208 Barnett et al. Nov 2001 B1
6327594 Van Huben et al. Dec 2001 B1
6330543 Kepecs Dec 2001 B1
6330546 Gopinathan et al. Dec 2001 B1
6332128 Nicholson Dec 2001 B1
6334108 Deaton et al. Dec 2001 B1
6336099 Bamett et al. Jan 2002 B1
6351735 Deaton et al. Feb 2002 B1
6356877 Schulden et al. Mar 2002 B1
6363351 Moro Mar 2002 B1
6366682 Hoffman et al. Apr 2002 B1
6377935 Deaton et al. Apr 2002 B1
6386323 Ramachandran et al. May 2002 B1
6394341 Mäkipää et al. May 2002 B1
6394907 Rowe May 2002 B1
6397198 Hoffman et al. May 2002 B1
6402030 Summers et al. Jun 2002 B1
6408286 Heiden Jun 2002 B1
6422462 Cohen Jul 2002 B1
6424949 Deaton et al. Jul 2002 B1
6456980 Powell Sep 2002 B1
6466921 Cordery et al. Oct 2002 B1
6467684 Fite et al. Oct 2002 B2
6467686 Guthrie et al. Oct 2002 B1
6487540 Smith et al. Nov 2002 B1
6493110 Roberts Dec 2002 B1
6493724 Cusack et al. Dec 2002 B1
6496804 McEvoy et al. Dec 2002 B2
6497360 Schulze, Jr. Dec 2002 B1
6508398 Estes Jan 2003 B1
6516056 Justice et al. Feb 2003 B1
6651168 Kao et al. Nov 2003 B1
6658393 Basch et al. Dec 2003 B1
6718328 Norris Apr 2004 B1
6722473 Ramachandran et al. Apr 2004 B1
6748365 Quinlan et al. Jun 2004 B1
6748367 Lee Jun 2004 B1
6749240 Burr et al. Jun 2004 B1
6758393 Luciano et al. Jul 2004 B1
6766301 Daniel et al. Jul 2004 B1
6769010 Knapp et al. Jul 2004 B1
6778967 Nicholson Aug 2004 B1
6779772 De Leon Aug 2004 B2
6795707 Martin et al. Sep 2004 B2
6810385 Brady et al. Oct 2004 B1
6829596 Frazee Dec 2004 B1
6837436 Swartz et al. Jan 2005 B2
6850901 Hunter et al. Feb 2005 B1
6852031 Rowe Feb 2005 B1
6862575 Anttila et al. Mar 2005 B1
6865546 Song Mar 2005 B1
6868406 Ogg et al. Mar 2005 B1
6876978 Walker et al. Apr 2005 B1
6882442 Roberts Apr 2005 B2
6885994 Scroggie et al. Apr 2005 B1
6886748 Moore May 2005 B1
6892180 Pointeau et al. May 2005 B1
6898598 Himmel et al. May 2005 B2
6901374 Himes May 2005 B1
6901436 Schneider May 2005 B1
6915271 Meyer et al. Jul 2005 B1
6925441 Jones, III et al. Aug 2005 B1
6932270 Fajkowski Aug 2005 B1
6937995 Kepecs Aug 2005 B1
6954732 DeLapa et al. Oct 2005 B1
6957186 Guheen et al. Oct 2005 B1
6959286 Perkowski Oct 2005 B2
6961712 Perkowski Nov 2005 B1
6961713 Perkowski Nov 2005 B2
6965872 Grdina Nov 2005 B1
6969318 Packes, Jr. et al. Nov 2005 B1
6970852 Sendo et al. Nov 2005 B1
6975937 Kantarjiev et al. Dec 2005 B1
6978380 Husain et al. Dec 2005 B1
6980670 Hoffman et al. Dec 2005 B1
6985452 Marshall et al. Jan 2006 B2
6985608 Hoffman et al. Jan 2006 B2
6993498 Deaton et al. Jan 2006 B1
6999943 Johnson et al. Feb 2006 B1
7003495 Burger et al. Feb 2006 B1
7003500 Driessen Feb 2006 B1
7006983 Packes, Jr. et al. Feb 2006 B1
7010498 Berstis Mar 2006 B1
7013286 Aggarwal et al. Mar 2006 B1
7013290 Ananian Mar 2006 B2
7016532 Boncyk et al. Mar 2006 B2
7016860 Modani et al. Mar 2006 B2
7016862 Vassigh et al. Mar 2006 B1
7024374 Day et al. Apr 2006 B1
7031945 Donner Apr 2006 B1
7043441 Maher May 2006 B1
7047205 Hale et al. May 2006 B2
7052393 Schoen May 2006 B1
7054830 Eggleston et al. May 2006 B1
7054837 Hoffman et al. May 2006 B2
7058596 Wojcik et al. Jun 2006 B1
7058806 Smeets et al. Jun 2006 B2
7063263 Swartz et al. Jun 2006 B2
7065559 Weiss Jun 2006 B1
7068382 Silverbrook et al. Jun 2006 B1
7072862 Wilson Jul 2006 B1
7085818 Brown et al. Aug 2006 B2
7089199 Perkowski Aug 2006 B2
7089322 Stallmann Aug 2006 B1
7107221 Tracy et al. Sep 2006 B1
7107231 Hall et al. Sep 2006 B1
7111323 Bhatia et al. Sep 2006 B1
7117183 Blair et al. Oct 2006 B2
7120596 Hoffman et al. Oct 2006 B2
7120607 Bolle et al. Oct 2006 B2
7124101 Mikurak Oct 2006 B1
7127236 Khan et al. Oct 2006 B2
7127414 Awadallah et al. Oct 2006 B1
7130807 Mikurak Oct 2006 B1
7136835 Flitcroft et al. Nov 2006 B1
7143055 Perkowski Nov 2006 B1
7150028 Ranta Dec 2006 B1
7152040 Hawthorne et al. Dec 2006 B1
7155228 Rappaport et al. Dec 2006 B2
7158948 Rodriguez et al. Jan 2007 B1
7162454 Donner et al. Jan 2007 B1
7165041 Guheen et al. Jan 2007 B1
7168617 Walker et al. Jan 2007 B2
7177838 Ling Feb 2007 B1
7178720 Strubbe et al. Feb 2007 B1
7185809 Barton et al. Mar 2007 B2
7188138 Schneider Mar 2007 B1
7203665 Donner Apr 2007 B2
7213754 Eglen et al. May 2007 B2
7216109 Donner May 2007 B1
7216110 Ogg et al. May 2007 B1
7231357 Shanman et al. Jun 2007 B1
7233913 Scroggie et al. Jun 2007 B2
7236956 Ogg et al. Jun 2007 B1
7240023 Powell Jul 2007 B1
7240037 Bussell Jul 2007 B1
7246158 Kitada et al. Jul 2007 B2
7248719 Hoffman et al. Jul 2007 B2
7249096 Lasater et al. Jul 2007 B1
7257545 Hung Aug 2007 B1
7263507 Brake, Jr. et al. Aug 2007 B1
7267614 Jorasch et al. Sep 2007 B1
7277866 Or-Bach et al. Oct 2007 B1
7280975 Donner Oct 2007 B1
7280979 Katz et al. Oct 2007 B1
7283650 Sharma et al. Oct 2007 B1
7283974 Katz et al. Oct 2007 B2
7292999 Hobson et al. Nov 2007 B2
7296282 Koplar et al. Nov 2007 B1
7306141 Schwarz, Jr. Dec 2007 B1
7308254 Rissanen Dec 2007 B1
7311244 Schwarz, Jr. Dec 2007 B1
7315826 Guheen et al. Jan 2008 B1
7318041 Walker et al. Jan 2008 B2
7319987 Hoffman et al. Jan 2008 B1
7328189 Ling Feb 2008 B2
7330974 Silverbrook et al. Feb 2008 B1
7334728 Williams Feb 2008 B2
7337144 Blinn et al. Feb 2008 B1
7340439 Burger et al. Mar 2008 B2
7343350 Donner Mar 2008 B1
7349668 Ilan et al. Mar 2008 B2
7357311 Silverbrook et al. Apr 2008 B2
7357312 Gangi Apr 2008 B2
7364068 Strubbe et al. Apr 2008 B1
7364086 Mesaros Apr 2008 B2
7367500 Fajkowski May 2008 B2
7376580 Walker et al. May 2008 B1
7376591 Owens May 2008 B2
7377421 Rhoads May 2008 B2
7379891 Donner et al. May 2008 B1
7380709 Silverbrook et al. Jun 2008 B2
7386485 Mussman et al. Jun 2008 B1
7386517 Donner Jun 2008 B1
7396281 Mendelsohn et al. Jul 2008 B2
7398225 Voltmer et al. Jul 2008 B2
7398250 Blinn et al. Jul 2008 B2
7400932 Ackley et al. Jul 2008 B2
7403652 Boncyk et al. Jul 2008 B2
7403796 Silverbrook et al. Jul 2008 B2
7406436 Reisman Jul 2008 B1
7407092 Silverbrook et al. Aug 2008 B2
7412081 Doi Aug 2008 B2
7412409 Aliabadi et al. Aug 2008 B2
7415424 Donner Aug 2008 B1
7415443 Hobson et al. Aug 2008 B2
7424303 Al-Sarawi Sep 2008 B2
7428498 Voltmer et al. Sep 2008 B2
7428986 Silverbrook et al. Sep 2008 B2
7438215 Silverbrook et al. Oct 2008 B2
7441697 Fletcher Oct 2008 B2
7441710 Perkowski Oct 2008 B2
7441712 Silverbrook et al. Oct 2008 B2
7448538 Fletcher Nov 2008 B2
7455586 Nguyen et al. Nov 2008 B2
7464050 Deaton et al. Dec 2008 B1
7469829 Silverbrook et al. Dec 2008 B2
7472827 Fletcher Jan 2009 B2
7477780 Boncyk et al. Jan 2009 B2
7487912 Seifert et al. Feb 2009 B2
7490065 Ogg et al. Feb 2009 B1
7496524 Voltmer et al. Feb 2009 B2
7496527 Silverstein et al. Feb 2009 B2
7506168 Silverbrook et al. Mar 2009 B2
7515914 Herrod et al. Apr 2009 B2
7516886 Gangi Apr 2009 B2
7526280 Jung et al. Apr 2009 B2
7529688 Prakash May 2009 B2
7529713 Donner May 2009 B1
7533810 Walker et al. May 2009 B2
7534169 Amaitis et al. May 2009 B2
7536034 Rhoads et al. May 2009 B2
7537153 Hurwitz et al. May 2009 B2
7540408 Levine et al. Jun 2009 B2
7546257 Hoffman et al. Jun 2009 B2
7548889 Bhambri et al. Jun 2009 B2
7562028 Donner Jul 2009 B1
7562051 Donner Jul 2009 B1
7564469 Cohen Jul 2009 B2
7565008 Boncyk et al. Jul 2009 B2
7565328 Donner Jul 2009 B1
7567940 Engelberg et al. Jul 2009 B1
7575172 Silverbrook et al. Aug 2009 B2
7577575 Donner et al. Aug 2009 B1
7577619 Donner et al. Aug 2009 B1
7577620 Donner Aug 2009 B1
7580856 Pliha Aug 2009 B1
7584133 Horowitz Sep 2009 B2
7584134 Horowitz Sep 2009 B2
7584139 Goodwin et al. Sep 2009 B2
7590589 Hoffberg Sep 2009 B2
7591724 Baerlocher Sep 2009 B2
7593871 Mesaros Sep 2009 B1
7593883 Horowitz Sep 2009 B2
7596530 Glasberg Sep 2009 B1
7597250 Finn Oct 2009 B2
7599857 Bishop et al. Oct 2009 B2
7606560 Labrou et al. Oct 2009 B2
7606730 Antonucci Oct 2009 B2
7606741 King et al. Oct 2009 B2
7610040 Cantini et al. Oct 2009 B2
7613628 Ariff et al. Nov 2009 B2
7617159 Donner Nov 2009 B1
7620475 Bottazzi et al. Nov 2009 B1
7621442 Silverbrook et al. Nov 2009 B2
7627499 Hahn-Carlson Dec 2009 B2
7627505 Yoshida et al. Dec 2009 B2
7637810 Amaitis et al. Dec 2009 B2
7646503 Silverbrook et al. Jan 2010 B2
7657489 Stambaugh Feb 2010 B2
7658327 Tuchman et al. Feb 2010 B2
7658674 Walker et al. Feb 2010 B2
7660581 Ramer et al. Feb 2010 B2
7663789 Silverbrook et al. Feb 2010 B2
7673315 Wong et al. Mar 2010 B1
7677445 Silverbrook et al. Mar 2010 B2
7680324 Boncyk et al. Mar 2010 B2
7681800 Silverbrook et al. Mar 2010 B2
7685083 Fairweather Mar 2010 B2
7689302 Schlottmann et al. Mar 2010 B2
7689473 Borom et al. Mar 2010 B2
7693766 Horowitz Apr 2010 B2
7693771 Zimmerman et al. Apr 2010 B1
7698221 Blinn et al. Apr 2010 B2
7698443 Yaffe et al. Apr 2010 B2
7702318 Ramer et al. Apr 2010 B2
7702918 Tattan et al. Apr 2010 B2
7706838 Atsmon et al. Apr 2010 B2
7711598 Perkowski May 2010 B2
7716077 Mikurak May 2010 B1
7716080 Postrel May 2010 B2
7720718 Hale et al. May 2010 B2
7729925 Maritzen et al. Jun 2010 B2
7729945 Katz et al. Jun 2010 B1
7735726 Bjoraker et al. Jun 2010 B2
7739162 Pettay et al. Jun 2010 B1
7739169 Hammad Jun 2010 B2
7742755 Silverbrook et al. Jun 2010 B2
7742967 Keresman, III et al. Jun 2010 B1
7742989 Schultz Jun 2010 B2
7747280 Silverbrook et al. Jun 2010 B2
7752141 Ogg et al. Jul 2010 B1
7753259 Taylor et al. Jul 2010 B1
7753264 Shafer et al. Jul 2010 B2
7761338 Schneider et al. Jul 2010 B1
7762470 Finn et al. Jul 2010 B2
7762885 Kelly et al. Jul 2010 B2
7765124 Postrel Jul 2010 B2
7771271 Walker et al. Aug 2010 B2
7774231 Pond et al. Aug 2010 B2
7774274 Jones et al. Aug 2010 B2
7775437 Cohen Aug 2010 B2
7778769 Boss et al. Aug 2010 B2
7778920 Zarin et al. Aug 2010 B2
7780526 Nguyen et al. Aug 2010 B2
7783281 Cook et al. Aug 2010 B1
7783515 Kumar et al. Aug 2010 B1
7783532 Hsu et al. Aug 2010 B2
7783542 Horowitz Aug 2010 B2
7783543 Horowitz Aug 2010 B2
7783544 Horowitz Aug 2010 B2
7783566 Armes et al. Aug 2010 B2
7784681 Silverbrook et al. Aug 2010 B2
7784682 Taylor et al. Aug 2010 B2
7784684 Labrou et al. Aug 2010 B2
7788129 Antonucci et al. Aug 2010 B2
7788188 Kramer Aug 2010 B2
7792298 Silverbrook et al. Sep 2010 B2
7792518 Trioano et al. Sep 2010 B2
7792539 Inselberg Sep 2010 B2
7792702 Katz et al. Sep 2010 B1
7792738 Channell Sep 2010 B2
7796162 Ortiz Sep 2010 B2
7796640 Giroux et al. Sep 2010 B2
7797005 Inselberg Sep 2010 B2
7797021 Silverbrook et al. Sep 2010 B2
7797192 Mitchell et al. Sep 2010 B2
7798397 Henry et al. Sep 2010 B2
7801629 Hale et al. Sep 2010 B2
7812935 Cowburn et al. Oct 2010 B2
7813955 Ariff et al. Oct 2010 B2
7815114 Mesaros Oct 2010 B2
7818215 King et al. Oct 2010 B2
7818392 Martino et al. Oct 2010 B1
7818415 Jhanji Oct 2010 B2
7822635 Brown et al. Oct 2010 B1
7822647 Mussman et al. Oct 2010 B1
7828208 Gangi Nov 2010 B2
7833101 Lutnick et al. Nov 2010 B2
7835960 Breck et al. Nov 2010 B2
7840485 Warren et al. Nov 2010 B1
7843595 Silverbrook et al. Nov 2010 B2
7843596 Silverbrook et al. Nov 2010 B2
7844492 Perkowski et al. Nov 2010 B2
7845555 Walker et al. Dec 2010 B2
7848980 Carlson Dec 2010 B2
7853241 Harrison Dec 2010 B1
7854386 Silverbrook et al. Dec 2010 B2
7855805 Silverbrook et al. Dec 2010 B2
7856360 Kramer et al. Dec 2010 B2
7856368 Avallone et al. Dec 2010 B2
7856377 Cohagan et al. Dec 2010 B2
7856414 Zee Dec 2010 B2
7860871 Ramer et al. Dec 2010 B2
7865187 Ramer et al. Jan 2011 B2
7865447 Rosenhaft et al. Jan 2011 B2
7870022 Bous et al. Jan 2011 B2
7873547 Borom et al. Jan 2011 B2
7873579 Hobson et al. Jan 2011 B2
7873580 Hobson et al. Jan 2011 B2
7881529 Boncyk et al. Feb 2011 B2
7881965 Bowles et al. Feb 2011 B2
7882032 Hoffman Feb 2011 B1
7890367 Senghore et al. Feb 2011 B2
7895120 Walker et al. Feb 2011 B2
7899243 Boncyk et al. Mar 2011 B2
7899252 Boncyk et al. Mar 2011 B2
7899710 Walker et al. Mar 2011 B1
7903029 Dupray Mar 2011 B2
7907940 Ramer et al. Mar 2011 B2
7908237 Angell et al. Mar 2011 B2
7970648 Galley et al. Jun 2011 B2
7970669 Santos Jun 2011 B1
7992779 Phillips et al. Aug 2011 B2
8012219 Mendez et al. Sep 2011 B2
8015076 Owens Sep 2011 B2
8032932 Speyer et al. Oct 2011 B2
8065201 Perkowski Nov 2011 B2
8073460 Scofield et al. Dec 2011 B1
8099360 Walker et al. Jan 2012 B2
8138930 Heath Mar 2012 B1
8160929 Park et al. Apr 2012 B1
8167199 Voutour May 2012 B1
8171531 Buer May 2012 B2
8180706 Bishop et al. May 2012 B2
8209229 Weiss et al. Jun 2012 B1
8249805 de Silva et al. Aug 2012 B2
8260663 Ranka et al. Sep 2012 B1
8261093 Dhesi et al. Sep 2012 B1
8271344 Channakeshava et al. Sep 2012 B1
8307413 Smadja et al. Nov 2012 B2
8311893 Schoettle Nov 2012 B2
8327428 Bailey et al. Dec 2012 B2
8327429 Speyer et al. Dec 2012 B2
8340981 Cave Dec 2012 B1
8346666 Lindelsee et al. Jan 2013 B2
8352323 Fisher Jan 2013 B2
8380177 Laracey Feb 2013 B2
8386309 Thibedeau et al. Feb 2013 B2
8395242 Oliver et al. Mar 2013 B2
8407142 Griggs Mar 2013 B1
8423466 Lanc Apr 2013 B2
8426884 Mizutani et al. Apr 2013 B2
8452705 Boal May 2013 B2
8489456 Burgess et al. Jul 2013 B2
8494915 Mesaros Jul 2013 B2
8498940 Pelegero et al. Jul 2013 B2
8522039 Hyndman et al. Aug 2013 B2
8560389 Burgess et al. Oct 2013 B2
8571983 Blackhurst et al. Oct 2013 B1
8572689 Radhakrishnan Oct 2013 B2
8577804 Bacastow Nov 2013 B1
8583498 Fried et al. Nov 2013 B2
8584251 McGuire et al. Nov 2013 B2
8589271 Evans Nov 2013 B2
8590008 Ellmore Nov 2013 B1
8590785 Mesaros Nov 2013 B1
8595812 Bomar et al. Nov 2013 B2
8606629 Bous et al. Dec 2013 B2
8620790 Priebatsch Dec 2013 B2
8637133 Vagliardo Jan 2014 B2
8650072 Mason et al. Feb 2014 B2
8650757 Rode Feb 2014 B2
8660951 Calman et al. Feb 2014 B2
8660965 Bickerstaff Feb 2014 B1
8665991 Zhu et al. Mar 2014 B2
8666660 Sartipi et al. Mar 2014 B2
8682802 Kannanari Mar 2014 B1
8683571 Zapata et al. Mar 2014 B2
8700472 Gray Apr 2014 B2
8732814 Radhakrishnan et al. May 2014 B2
8733637 Cedeno May 2014 B1
8751298 Giordano et al. Jun 2014 B1
8768838 Hoffman Jul 2014 B1
8775243 Gillenson et al. Jul 2014 B2
8781894 Walker et al. Jul 2014 B2
8788333 Alba et al. Jul 2014 B2
8788429 Tieken Jul 2014 B2
8789162 Radhakrishnan Jul 2014 B2
8799060 Gillenson et al. Aug 2014 B2
8799087 Martin et al. Aug 2014 B2
8825523 Gillenson et al. Sep 2014 B2
8839383 Van Horn Sep 2014 B2
8850575 Magi Shaashua et al. Sep 2014 B1
8909771 Heath Dec 2014 B2
8930271 Ellis et al. Jan 2015 B1
8943574 Bailey et al. Jan 2015 B2
8966423 Jain et al. Feb 2015 B2
8973102 Jakobsson Mar 2015 B2
8973819 Blackhurst et al. Mar 2015 B2
8985442 Zhou et al. Mar 2015 B1
8996423 Johnson et al. Mar 2015 B2
8997215 Guriappa Srinivas et al. Mar 2015 B2
9002924 Saretto et al. Apr 2015 B2
9053514 Bennett et al. Jun 2015 B2
9055053 Radhakrishnan et al. Jun 2015 B2
9069943 Radhakrishnan et al. Jun 2015 B2
9082153 Bennett et al. Jul 2015 B2
9098879 Bennett et al. Aug 2015 B2
9100795 Sartipi et al. Aug 2015 B2
9105059 Gluzberg et al. Aug 2015 B2
9131443 Takaki Sep 2015 B2
9146345 Dong et al. Sep 2015 B1
9152963 Blackhurst et al. Oct 2015 B2
9183572 Brubaker Nov 2015 B2
9196188 Kimura Nov 2015 B2
9200154 Teramoto et al. Dec 2015 B2
9238674 Manoj et al. Jan 2016 B2
9275278 Liu et al. Mar 2016 B2
9324091 Randell et al. Apr 2016 B2
9355392 Blackhurst et al. May 2016 B2
9379586 Rahman et al. Jun 2016 B2
9400005 Osborn et al. Jul 2016 B2
9419841 Kozolchyk et al. Aug 2016 B1
9514486 Raman Dec 2016 B2
9519895 Blackhurst et al. Dec 2016 B2
9519929 Hellal et al. Dec 2016 B2
9552603 Chanda et al. Jan 2017 B1
9554274 Castinado et al. Jan 2017 B1
9576279 Pollin et al. Feb 2017 B2
9576294 Gebb et al. Feb 2017 B2
9589256 Thomas et al. Mar 2017 B1
9600839 Calman et al. Mar 2017 B2
9633342 Blackhurst et al. Apr 2017 B2
9639836 Bondesen et al. May 2017 B2
9639837 Laracey May 2017 B2
9639852 Low et al. May 2017 B2
10013153 Freeman et al. Jul 2018 B1
10255300 Jhingran et al. Apr 2019 B1
20020062249 Iannacci May 2002 A1
20020065720 Carswell et al. May 2002 A1
20020095333 Jokinen Jul 2002 A1
20020111907 Ling Aug 2002 A1
20020116214 Horn Aug 2002 A1
20020116249 Ellinger et al. Aug 2002 A1
20020152123 Giordano et al. Oct 2002 A1
20020157029 French et al. Oct 2002 A1
20020174073 Nordman et al. Nov 2002 A1
20020186845 Dutta et al. Dec 2002 A1
20020188561 Schultz Dec 2002 A1
20030004866 Huennekens et al. Jan 2003 A1
20030018550 Rotman et al. Jan 2003 A1
20030045328 Natsuno Mar 2003 A1
20030055727 Walker et al. Mar 2003 A1
20030061170 Uzo Mar 2003 A1
20030064705 Desiderio Apr 2003 A1
20030065805 Barnes Apr 2003 A1
20030074311 Saylors et al. Apr 2003 A1
20030088462 Carrithers et al. May 2003 A1
20030105714 Alarcon-Luther et al. Jun 2003 A1
20030163373 Cornateanu Aug 2003 A1
20030163787 Hay et al. Aug 2003 A1
20030171990 Rao et al. Sep 2003 A1
20030182204 Rhee Sep 2003 A1
20030217005 Drummond et al. Nov 2003 A1
20030220835 Barnes Nov 2003 A1
20040006478 Alpdemir et al. Jan 2004 A1
20040010597 Kirschner et al. Jan 2004 A1
20040021584 Hartz, Jr. et al. Feb 2004 A1
20040024638 Restis Feb 2004 A1
20040024709 Yu et al. Feb 2004 A1
20040030598 Boal Feb 2004 A1
20040064373 Shannon Apr 2004 A1
20040083184 Tsuei et al. Apr 2004 A1
20040117250 Lubow et al. Jun 2004 A1
20040122736 Strock et al. Jun 2004 A1
20040128197 Bam et al. Jul 2004 A1
20040220964 Shiftan et al. Nov 2004 A1
20040238622 Freiberg Dec 2004 A1
20040243468 Cohagan et al. Dec 2004 A1
20040260653 Tsuei et al. Dec 2004 A1
20050021363 Stimson et al. Jan 2005 A1
20050108096 Burger et al. May 2005 A1
20050149436 Elterich Jul 2005 A1
20050160014 Moss et al. Jul 2005 A1
20050165682 Duke Jul 2005 A1
20050197919 Robertson Sep 2005 A1
20050209921 Roberts et al. Sep 2005 A1
20050222961 Staib et al. Oct 2005 A1
20050228717 Gusler et al. Oct 2005 A1
20050240478 Lubow et al. Oct 2005 A1
20060027647 Deane et al. Feb 2006 A1
20060036868 Cicchitto Feb 2006 A1
20060100951 Mylet et al. May 2006 A1
20060142058 Elias et al. Jun 2006 A1
20060169764 Ross et al. Aug 2006 A1
20060287004 Fuqua Dec 2006 A1
20060289621 Foss et al. Dec 2006 A1
20060293956 Walker et al. Dec 2006 A1
20070005427 Walker et al. Jan 2007 A1
20070017976 Peyret et al. Jan 2007 A1
20070055594 Rivest et al. Mar 2007 A1
20070069013 Seifert et al. Mar 2007 A1
20070073589 Vergeyle et al. Mar 2007 A1
20070094080 Wiken Apr 2007 A1
20070094088 Mastie et al. Apr 2007 A1
20070100773 Wallach May 2007 A1
20070140595 Taylor et al. Jun 2007 A1
20070150369 Zivin Jun 2007 A1
20070156842 Vermeulen et al. Jul 2007 A1
20070194884 Didier et al. Aug 2007 A1
20070215696 Macnish Sep 2007 A1
20070219852 Anglum Sep 2007 A1
20070219984 Aravamudan et al. Sep 2007 A1
20070223706 Gantman et al. Sep 2007 A1
20070228157 Eckert Oct 2007 A1
20070244741 Blume et al. Oct 2007 A1
20070250920 Lindsay Oct 2007 A1
20070271141 Storm Nov 2007 A1
20070272740 Palacios Nov 2007 A1
20070288372 Behar et al. Dec 2007 A1
20080010200 Smith et al. Jan 2008 A1
20080011837 Wesley Jan 2008 A1
20080019534 Reichelt et al. Jan 2008 A1
20080040278 DeWitt Feb 2008 A1
20080059303 Fordyce Mar 2008 A1
20080065490 Novick et al. Mar 2008 A1
20080067232 Whytock et al. Mar 2008 A1
20080077486 Davis et al. Mar 2008 A1
20080089499 Hahn et al. Apr 2008 A1
20080091528 Rampell et al. Apr 2008 A1
20080109319 Foss May 2008 A1
20080120155 Pliha May 2008 A1
20080133325 De et al. Jun 2008 A1
20080140509 Amjadi Jun 2008 A1
20080147504 Suk Jun 2008 A1
20080154676 Suk Jun 2008 A1
20080162279 Hershkovitz et al. Jul 2008 A1
20080162338 Samuels et al. Jul 2008 A1
20080162589 Rodeheffer et al. Jul 2008 A1
20080167965 Von Nothaus et al. Jul 2008 A1
20080177624 Dohse Jul 2008 A9
20080189210 Sawhney Aug 2008 A1
20080195499 Meredith et al. Aug 2008 A1
20080214210 Rasanen et al. Sep 2008 A1
20080228637 Scipioni et al. Sep 2008 A1
20080240702 Wassingbo et al. Oct 2008 A1
20080248815 Busch Oct 2008 A1
20080257958 Rothwell et al. Oct 2008 A1
20080262928 Michaelis Oct 2008 A1
20080268876 Gelfand et al. Oct 2008 A1
20080270243 Lewis et al. Oct 2008 A1
20080293397 Gajdos et al. Nov 2008 A1
20080300973 DeWitt et al. Dec 2008 A1
20080301112 Wu Dec 2008 A1
20080306826 Kramer et al. Dec 2008 A1
20080319889 Hammad Dec 2008 A1
20090002630 Lacombe et al. Jan 2009 A1
20090005146 Kelly et al. Jan 2009 A9
20090005152 Kelly et al. Jan 2009 A9
20090005158 Kelly et al. Jan 2009 A9
20090005170 Kelly et al. Jan 2009 A9
20090006191 Arankalle et al. Jan 2009 A1
20090006203 Fordyce et al. Jan 2009 A1
20090006212 Krajicek et al. Jan 2009 A1
20090006230 Lyda et al. Jan 2009 A1
20090019534 Bakshi et al. Jan 2009 A1
20090037275 Pollio Feb 2009 A1
20090057396 Barbour et al. Mar 2009 A1
20090076934 Shahbazi et al. Mar 2009 A1
20090089131 Moukas et al. Apr 2009 A1
20090094125 Killian et al. Apr 2009 A1
20090100529 Livnat et al. Apr 2009 A1
20090102859 Athsani et al. Apr 2009 A1
20090119174 Pfister May 2009 A1
20090119190 Realini May 2009 A1
20090140839 Bishop et al. Jun 2009 A1
20090144164 Wane et al. Jun 2009 A1
20090150211 Bayne Jun 2009 A1
20090150265 Keld Jun 2009 A1
20090150286 Barton Jun 2009 A1
20090164327 Bishop et al. Jun 2009 A1
20090171850 Yuval Jul 2009 A1
20090182630 Otto et al. Jul 2009 A1
20090182748 Walker Jul 2009 A1
20090186699 Kelly Jul 2009 A9
20090192873 Marble Jul 2009 A1
20090204511 Tsang Aug 2009 A1
20090222657 Bender et al. Sep 2009 A1
20090250515 Todd et al. Oct 2009 A1
20090287557 Etheredge et al. Nov 2009 A1
20090287564 Bishop et al. Nov 2009 A1
20090292605 Kniaz et al. Nov 2009 A1
20090313109 Bous et al. Dec 2009 A1
20100010918 Hunt Jan 2010 A1
20100030578 Siddique et al. Feb 2010 A1
20100030654 Dinkin et al. Feb 2010 A1
20100036741 Cleven Feb 2010 A1
20100042477 Cavander et al. Feb 2010 A1
20100051689 Diamond Mar 2010 A1
20100057620 Li et al. Mar 2010 A1
20100064345 Bentley et al. Mar 2010 A1
20100070359 Heasley et al. Mar 2010 A1
20100076819 Wannier et al. Mar 2010 A1
20100076836 Giordano et al. Mar 2010 A1
20100088166 Tollinger Apr 2010 A1
20100096449 Denzer et al. Apr 2010 A1
20100122274 Gillies et al. May 2010 A1
20100122333 Noe May 2010 A1
20100130226 Arrasvuori et al. May 2010 A1
20100145784 Sriver et al. Jun 2010 A1
20100153205 Retter et al. Jun 2010 A1
20100161600 Higgins et al. Jun 2010 A1
20100185529 Chesnut et al. Jul 2010 A1
20100223165 Calman et al. Sep 2010 A1
20100228776 Melkote et al. Sep 2010 A1
20100241571 McDonald Sep 2010 A1
20100250338 Banerjee et al. Sep 2010 A1
20100250581 Chau Sep 2010 A1
20100257066 Jones et al. Oct 2010 A1
20100257099 Bonalle et al. Oct 2010 A1
20100268645 Martino et al. Oct 2010 A1
20100293099 Pauker et al. Nov 2010 A1
20100299195 Nix et al. Nov 2010 A1
20100306080 Trandal et al. Dec 2010 A1
20100312636 Coulter et al. Dec 2010 A1
20110004921 Homer et al. Jan 2011 A1
20110010238 Postrel Jan 2011 A1
20110022483 Hammad Jan 2011 A1
20110022540 Stern et al. Jan 2011 A1
20110029364 Roeding et al. Feb 2011 A1
20110029368 Hsu et al. Feb 2011 A1
20110034176 Lord et al. Feb 2011 A1
20110077046 Durand et al. Mar 2011 A1
20110087531 Winters et al. Apr 2011 A1
20110093318 Guday et al. Apr 2011 A1
20110093326 Bous et al. Apr 2011 A1
20110099104 Nybom Apr 2011 A1
20110106622 Kuhlman et al. May 2011 A1
20110112897 Tietzen et al. May 2011 A1
20110119155 Hammad et al. May 2011 A1
20110131107 Hurst Jun 2011 A1
20110137804 Peterson Jun 2011 A1
20110166992 Dessert et al. Jul 2011 A1
20110191159 Heitman et al. Aug 2011 A1
20110191184 Blackhurst et al. Aug 2011 A1
20110197200 Huang et al. Aug 2011 A1
20110202466 Carter Aug 2011 A1
20110218907 Dessert et al. Sep 2011 A1
20110251892 Laracey Oct 2011 A1
20110276430 Vyas et al. Nov 2011 A1
20110276437 Mullen et al. Nov 2011 A1
20110277016 Hockings et al. Nov 2011 A1
20110288996 Kreutz et al. Nov 2011 A1
20110294066 Hasegawa Dec 2011 A1
20110295744 Wisniewski et al. Dec 2011 A1
20110320255 Gorowitz et al. Dec 2011 A1
20120003002 Hashimoto Jan 2012 A1
20120024947 Naelon Feb 2012 A1
20120030043 Ross et al. Feb 2012 A1
20120030047 Fuentes et al. Feb 2012 A1
20120030109 Dooley Maley et al. Feb 2012 A1
20120054000 Boppert et al. Mar 2012 A1
20120054057 Oconnell et al. Mar 2012 A1
20120059701 van der Veen et al. Mar 2012 A1
20120066064 Yoder et al. Mar 2012 A1
20120100915 Margalit et al. Apr 2012 A1
20120110646 Ajitomi et al. May 2012 A1
20120130785 Postrel May 2012 A1
20120131828 August et al. May 2012 A1
20120136780 El-Awady et al. May 2012 A1
20120143759 Ritorto, Jr. et al. Jun 2012 A1
20120150643 Wolfe et al. Jun 2012 A1
20120150731 Isaacson et al. Jun 2012 A1
20120150740 Isaacson et al. Jun 2012 A1
20120158525 Kae et al. Jun 2012 A1
20120158540 Ganti et al. Jun 2012 A1
20120158586 Ganti et al. Jun 2012 A1
20120160912 Laracey Jun 2012 A1
20120166334 Kimberg et al. Jun 2012 A1
20120171237 Ching et al. Jul 2012 A1
20120179558 Fischer Jul 2012 A1
20120191565 Blank et al. Jul 2012 A1
20120197742 Johnson Aug 2012 A1
20120197743 Grigg et al. Aug 2012 A1
20120197794 Grigg et al. Aug 2012 A1
20120203644 Phillips Aug 2012 A1
20120203700 Ornce et al. Aug 2012 A1
20120221397 Roe et al. Aug 2012 A1
20120221446 Grigg et al. Aug 2012 A1
20120226604 Isaacson et al. Sep 2012 A1
20120239531 McCann Sep 2012 A1
20120252365 Lam Oct 2012 A1
20120254941 Levien et al. Oct 2012 A1
20120260318 Fromentoux et al. Oct 2012 A1
20120271712 Katzin et al. Oct 2012 A1
20120284107 Gemaat et al. Nov 2012 A1
20120290389 Greenough et al. Nov 2012 A1
20120290482 Atef et al. Nov 2012 A1
20120310826 Chatterjee Dec 2012 A1
20120316941 Moshfeghi Dec 2012 A1
20120316949 Chen Dec 2012 A1
20120316992 Oborne Dec 2012 A1
20120317034 Guha et al. Dec 2012 A1
20120323669 Kohlmeier Dec 2012 A1
20120323765 Spaulding et al. Dec 2012 A1
20120323783 Canetto Dec 2012 A1
20120330846 Light et al. Dec 2012 A1
20130009547 Shiu et al. Jan 2013 A1
20130013499 Kalgi Jan 2013 A1
20130018738 Faires et al. Jan 2013 A1
20130024360 Bailout Jan 2013 A1
20130024525 Brady et al. Jan 2013 A1
20130036001 Wegner et al. Feb 2013 A1
20130036048 Campos et al. Feb 2013 A1
20130036117 Fisher et al. Feb 2013 A1
20130046589 Grigg et al. Feb 2013 A1
20130046635 Grigg et al. Feb 2013 A1
20130054336 Graylin Feb 2013 A1
20130054470 Campos et al. Feb 2013 A1
20130060689 Oskolkov et al. Mar 2013 A1
20130060708 Oskolkov et al. Mar 2013 A1
20130073377 Heath Mar 2013 A1
20130073473 Heath Mar 2013 A1
20130080239 Okerlund Mar 2013 A1
20130085927 Scott Apr 2013 A1
20130097002 Dishneau et al. Apr 2013 A1
20130097683 Davis et al. Apr 2013 A1
20130110658 Lyman et al. May 2013 A1
20130124346 Baldwin et al. May 2013 A1
20130159178 Colon et al. Jun 2013 A1
20130159195 Kirillin et al. Jun 2013 A1
20130161381 Roundtree et al. Jun 2013 A1
20130166332 Hammad Jun 2013 A1
20130179341 Boudreau Jul 2013 A1
20130179954 Bidare Jul 2013 A1
20130191195 Carlson et al. Jul 2013 A1
20130191213 Beck et al. Jul 2013 A1
20130191227 Pasa et al. Jul 2013 A1
20130204775 Midkiff et al. Aug 2013 A1
20130204787 Dubois Aug 2013 A1
20130212007 Mattsson et al. Aug 2013 A1
20130212019 Mattsson et al. Aug 2013 A1
20130232067 Bhosle et al. Sep 2013 A1
20130238413 Carlson et al. Sep 2013 A1
20130246258 Dessert Sep 2013 A1
20130246260 Baden et al. Sep 2013 A1
20130254052 Royyuru et al. Sep 2013 A1
20130254102 Royyuru Sep 2013 A1
20130254115 Pasa et al. Sep 2013 A1
20130262315 Hruska Oct 2013 A1
20130268437 Desai et al. Oct 2013 A1
20130304651 Smith Nov 2013 A1
20130311324 Stoll et al. Nov 2013 A1
20130318627 Lundkvist et al. Nov 2013 A1
20130325751 McDonough et al. Dec 2013 A1
20130334304 Yankovich et al. Dec 2013 A1
20130346302 Purves et al. Dec 2013 A1
20140006273 Gopinath et al. Jan 2014 A1
20140012647 Hecht Jan 2014 A1
20140025581 Calman Jan 2014 A1
20140025958 Calman Jan 2014 A1
20140027922 Uzoh Jan 2014 A1
20140058938 McClung Feb 2014 A1
20140092130 Anderson et al. Apr 2014 A1
20140096215 Hessler Apr 2014 A1
20140101044 Blackhurst et al. Apr 2014 A1
20140123244 Resch et al. May 2014 A1
20140129357 Goodwin May 2014 A1
20140130127 Toole et al. May 2014 A1
20140143145 Kortina et al. May 2014 A1
20140143149 Aissi May 2014 A1
20140164030 Katagiri Jun 2014 A1
20140172707 Kuntagod et al. Jun 2014 A1
20140187148 Taite et al. Jul 2014 A1
20140188719 Poornachandran et al. Jul 2014 A1
20140208401 Balakrishnan et al. Jul 2014 A1
20140214640 Mallikarjunan et al. Jul 2014 A1
20140244493 Kenyon et al. Aug 2014 A1
20140244503 Sadlier Aug 2014 A1
20140244506 Gramling Aug 2014 A1
20140245391 Adenuga Aug 2014 A1
20140245411 Meng et al. Aug 2014 A1
20140250009 Carlson Sep 2014 A1
20140278999 Calman et al. Sep 2014 A1
20140279005 Calman et al. Sep 2014 A1
20140279214 Wagoner-Edwards et al. Sep 2014 A1
20140279476 Hua Sep 2014 A1
20140279554 Priebatsch et al. Sep 2014 A1
20140279566 Verma et al. Sep 2014 A1
20140297411 Peil Oct 2014 A1
20140310764 Tippett et al. Oct 2014 A1
20140315159 Mukherjee et al. Oct 2014 A1
20140324690 Allen et al. Oct 2014 A1
20140330721 Wang Nov 2014 A1
20140337175 Katzin et al. Nov 2014 A1
20140359709 Nassar et al. Dec 2014 A1
20140365301 Rappoport et al. Dec 2014 A1
20150019317 Mitchell Jan 2015 A1
20150019439 Phillips Jan 2015 A1
20150032621 Kar et al. Jan 2015 A1
20150032627 Dill et al. Jan 2015 A1
20150039601 Harrang et al. Feb 2015 A1
20150046339 Wong et al. Feb 2015 A1
20150081557 Kinfoil et al. Mar 2015 A1
20150081567 Boyle et al. Mar 2015 A1
20150088753 Van Der Schueren Mar 2015 A1
20150089615 Krawczyk et al. Mar 2015 A1
20150100495 Salama et al. Apr 2015 A1
20150100788 Chastain et al. Apr 2015 A1
20150120569 Belshe et al. Apr 2015 A1
20150120572 Slade Apr 2015 A1
20150145656 Levesque et al. May 2015 A1
20150161610 Sahadevan et al. Jun 2015 A1
20150161638 Chapman, Jr. Jun 2015 A1
20150170149 Sharma et al. Jun 2015 A1
20150172242 Goncalves Jun 2015 A1
20150172411 Maier et al. Jun 2015 A1
20150206131 Phillips et al. Jul 2015 A1
20150206137 Mazarim Fernandes Jul 2015 A1
20150220914 Purves et al. Aug 2015 A1
20150254648 Clements et al. Sep 2015 A1
20150254653 Bondesen et al. Sep 2015 A1
20150254664 Bondesen et al. Sep 2015 A1
20150254698 Bondesen et al. Sep 2015 A1
20150278903 Amjadi Oct 2015 A1
20150294303 Hanson et al. Oct 2015 A1
20150324830 Chandrasekaran et al. Nov 2015 A1
20150348006 Taveau et al. Dec 2015 A1
20160019536 Ortiz et al. Jan 2016 A1
20160029204 Lalwaney Jan 2016 A1
20160055512 Godsey et al. Feb 2016 A1
20160125677 Williams et al. May 2016 A1
20160162853 Blackhurst et al. Jun 2016 A1
20160162868 Blackhurst et al. Jun 2016 A1
20160171570 Dogin et al. Jun 2016 A1
20160189228 Vaccari Jun 2016 A1
20160232518 Butler Aug 2016 A1
20160232607 Spielman Aug 2016 A1
20160261409 French et al. Sep 2016 A1
20160321663 Battle Nov 2016 A1
20170018013 Faust et al. Jan 2017 A1
20170039568 Tunnell et al. Feb 2017 A1
20170068952 Brockmann et al. Mar 2017 A1
20170083966 Raman Mar 2017 A1
20170109540 Heiman et al. Apr 2017 A1
20170109741 Heiman et al. Apr 2017 A1
20170111345 Heiman et al. Apr 2017 A1
20170178113 Mugford et al. Jun 2017 A1
20170193501 Cole et al. Jul 2017 A1
20170195994 Cole et al. Jul 2017 A1
20170228878 Goldman et al. Aug 2017 A1
20170359306 Thomas et al. Dec 2017 A1
20180034862 Friend et al. Feb 2018 A1
20180082284 Gomes et al. Mar 2018 A1
20180191797 Javier et al. Jul 2018 A1
20180285827 Dotan-Cohen et al. Oct 2018 A1
20180352599 Bostick et al. Dec 2018 A1
Foreign Referenced Citations (3)
Number Date Country
1132876 Sep 2001 EP
2012058099 May 2012 WO
2013095486 Jun 2013 WO
Non-Patent Literature Citations (24)
Entry
Werden, Kristina. “How to Combine Visa Gift Cards.” eHow.com. 1 page.http://www.ehow.com/how 6216118combine-visa-gift-cards.html. Retrieved Jan. 8, 2013.
Zumiez com. “The Zumiez Gift Card—CombineYour Gift Cards.” 1 page.http://www.zumiez.com/giftcard/index/combine. Retrieved Jan. 8, 2013.
The Laws, Regulations, Guidelines, and Industry Practices that Consumers Who Use Gift Cards; Phillip Keitel; Jul. 2008.
MasterCard 2005.
PrePaid Gift Cards; May 2012.
Simon, “Credit-Card Reward Programs: A Short History”; Creditcards.com, Nov. 2, 4 pages.
Lane, “History of APIs”; APIEvangelist.com; Dec. 2012, 11 pages.
Digital Wallet to Pay for Travel Hasn't Arrived Yet, Orlando Sentinel[Orlando FL], Jan. 27, 2013; p. J.6.
World's First and Only Global Wallet Sees Strong User Adoption with 150 Million Miles Loaded to Cash in First Month of Launch, Business Wire, Nov. 28, 2012, Zurich.
Bielski, L. (2000). Aggregators aka “screenscrapers”. American Bankers Association.ABA Banking Journal, 92(5), 17-50. Retrieved from http://search.proquest.com/docview/218443115?ac-countid=14753.
Howell, J., & Wei, J. (2010). Value Increasing Model in Commercial E-Banking. The Journal of Computer Information Systems, 51(1), 72-81. Retrieved from http://search.proquest.com/docview/ 808409721?accountid=14753.
Finovate Startup 2009 Video Archives » Expensify (retrieved online from <http://www.finovate.com/startup09vid/expensify. html>and<http://www.finovate.com/startup09vid/videos/ quicktime/Expensify.mov>) pp. 1-3 screenshots of website hosting video presentation. pp. 4-15 screen shots of the Expensify video presentation.
Expensify Blog Oct. 2009, retrieved online from <http://blog. expensify.com/2009/10/» pp. 8.
International Search Report and the Written Opinion for International Application No. PCT/US2010/029811 dated Jun. 1, 2010.
International Preliminary Report on Patentability for International Application No. PCT/US2010/029811 dated Oct. 20, 2011.
Welch, M. J. (2010). Addressing the challenges of underspecification in web search. (Order No. 3446833, University of 3alifomia, Los Angeles). ProQuest Dissertations and Theses, 137. Retrieved from http://search.proquest.com/docview/85810500?accountid=14753. (858101500).*.
K.J. Jeevan, & Padhi, P. (2006). A selective review of research in content personalization. Library Review, 55(9), 556-586. doi:http:// dx.doi.org/10.1108/00242530610706761.*.
Lissner, P. A. (2007). Chi-thinking: Chiasmus and cognition. (Order No. 3297307, University of Maryland, College Park). ProQuest Dis-sertations and Theses, 487. Retrieved from http://search.proquest. com/docview/304851937?accountid=14753. (304851937).*.
Intemational Search Report and Written Opinion for International Application No. PCT/US2012/027892 dated Jun. 14, 2012.
Intemational Search Report and Written Opinion for International Application No. PCT/US2012/027912 dated Jun. 8, 2012.
Intemational Search Report and Written Opinion for International Application No. PCT/US2012/028036 dated May 28, 2012.
Intemational Search Report and Written Opinion for International Application No. PCT/US2012/028008 dated May 22, 2012.
Intemational Search Report and Written Opinion for International Application No. PCT/US2012/048697 dated Sep. 24, 2012.
Intemational Search Report and Written Opinion for International Application No. PCT/US2012/027890 dated Feb. 5, 2013.
Related Publications (1)
Number Date Country
20200137634 A1 Apr 2020 US
Continuations (1)
Number Date Country
Parent 15630270 Jun 2017 US
Child 16725389 US