Abstract: Software executing on a mobile device collects custom metadata for an image taken by a camera of a mobile device. The image with the custom metadata is sent from the software to an external network service. The external network service processes the custom metadata to at least determine a physical location of the image. In an embodiment, the physical location is used to uniquely identify the image and perform an automated transaction on behalf of a user that operates the mobile device.

Abstract: Software executing on a mobile device collects custom metadata for an image taken by a camera of a mobile device. The image with the custom metadata is sent from the software to an external network service. The external network service processes the custom metadata to at least determine a physical location of the image. In an embodiment, the physical location is used to uniquely identify the image and perform an automated transaction on behalf of a user that operates the mobile device.

Abstract: Software executing on a mobile device collects custom metadata for an image taken by a camera of a mobile device. The image with the custom metadata is sent from the software to an external network service. The external network service processes the custom metadata to at least determine a physical location of the image. In an embodiment, the physical location is used to uniquely identify the image and perform an automated transaction on behalf of a user that operates the mobile device.

Abstract: Software executing on a mobile device collects custom metadata for an image taken by a camera of a mobile device. The image with the custom metadata is sent from the software to an external network service. The external network service processes the custom metadata to at least determine a physical location of the image. In an embodiment, the physical location is used to uniquely identify the image and perform an automated transaction on behalf of a user that operates the mobile device.

Abstract: Various embodiments herein relate to data processing, in particular with regard to a rule-based data processing engine. Such a rule-based data processing engine is employed in various embodiments to apply rules to customer data to generate offers of systems and programs, such as credit card and customer loyalty offerings, that achieve desired goals of an offering entity. One embodiment includes identifying at least one program for which an individual qualifies based upon data of the individual in view of respective program qualification criteria. This method further includes determining, for each identified program, at least one variable parameter of the respective program based on a respective parameter rule. This method then transmits, via a network, representations of each of the identified programs with respective determined parameters for presentation within a user interface.

Abstract: Various embodiments herein each include at least one of systems, methods, software, and modules for collateralization of reward or loyalty program liability. Some such embodiments provide mechanisms for identifying program liability that has a low likelihood of being redeemed, such as liability associated with participant accounts that have had no activity, and are therefore considered stale accounts, for a certain period, such as two or more years. Liability associated with such accounts may then be bundled into a pool and the entity operating the program may pay another entity to incur the liability for those accounts, typically for pennies on the dollar of financial value of the rewards involved.

Abstract: The various embodiments herein each include at least one of systems, methods, and software for single and multi-tenant rule driven crediting systems and methods, such as may be utilized for implementing reward programs that reward customer loyalty. One such embodiment in the form of a method includes receiving input defining a rule to be applied against transaction data, the rule identifying at least one applicable transaction type and a value to be credited to an account associated with an account involved in the transaction. The method further includes storing the rule in a rulebase of a plurality of rules. The method also may include executing a rules engine to apply rules of the rulebase against transactions in a transaction system where a type of a respective transaction matches the at least one applicable transaction type of a respective rule.