Abstract: Systems and methods for executing tasks using modular code containers, intelligent code containers and data containers are provided. The system may comprise a master coordinator configured to implement algorithmic intelligence, artificial intelligence, and/or machine learning to intelligently generate, store, maintain, and retrieve the modular code containers and data containers. The system may receive task requests having at least one feature comprising functional components and data components. The system may retrieve the code containers based on the functional components, and the data containers based on the data components. The system may generate a result set by executing code from the code container to process data from the data container.

Abstract: A messaging balancing and control (B&C) system is disclosed. The system is configured to handle message transfers having different message exchange patterns, including: in-only exchange patterns, out-only exchange patterns, in-optional-out exchange patterns, out-optional-in exchange patterns, robust in-only exchange patterns, and robust out-only exchange patterns. The system may write a message transfer confirmation in response to a message transfer between a consumer system and a provider system, with the confirmation including at least a first hash of the message. The system may also write a message acknowledgement to the blockchain with the acknowledgement including at least a second hash of the message. The blockchain may execute a smart contract to compare the first hash of the message to the second hash of the message to identify an out-of-balance message transfer event. A monitoring device of the system may read the out-of-balance message transfer event from the blockchain.

Abstract: A system receives a source and a metadata layer that describes the source. The source may comprise source records with fields containing source data, and the metadata layer may include metadata comprising at least one of a field data type, a field data length, a field description, or a record length. The processor may further validate the metadata layer against the source and write results to a log. The processor may further be configured for transforming the source records into transformed records for a load ready file. The processor may further balance a number of records in the source against a number of transformed records in the load ready file to generate a transformation failure rate.

Abstract: In various embodiments, a system, method, and computer readable medium (collectively, the “System”) for authenticating a mobile device configured to initiate payments is provided. The System may be configured to perform operations and/or steps comprising receiving, by the processor and in a secure environment, a secret element. The secret element may be transmitted to the processor (e.g., the issuer system) via a payment terminal. The System may further comprise comparing, by the processor and in the secured environment, the secret element to an issuer element. The issuer element may be linked with a flag that is associated with the transaction account. Moreover, the issuer element may be a data module that corresponds to be is not equal to the secret element. The System may also comprise authorizing, by the processor, a transaction initiated by the mobile device in response to the comparing being a satisfactory comparison.

Abstract: A balancing and control (B&C) system for API transactions is disclosed. The system may write a request confirmation and a request acknowledgement to a blockchain in response to an API request being transmitted from a consumer system to a provider system, with the request confirmation and the request acknowledgement each comprising a request hash of the API request. The system may also write a response confirmation and a response acknowledgement to the blockchain in response to an API response being transmitted from the provider system to the consumer system, with the response confirmation and the response acknowledgement each comprising a response hash of the API response. The blockchain may execute a smart contract to compare the request hashes from the request confirmation and the request acknowledgement and the response hashes from the response confirmation and the response acknowledgement to identify one or more out-of-balance events.

Abstract: A blockchain-based multi-merchant loyalty point partnership system may include a blockchain API host that receives a request to create a partnership smart contract for a multi-merchant loyalty point partnership. The request may specify various partnership parameters to include in the partnership smart contract. The blockchain API host may create the partnership smart contract and write the partnership smart contract to a blockchain. One or more qualified merchants may join the partnership smart contract to make the partnership active. In response to a customer completing a plurality of purchases that complete the partnership parameters of the partnership smart contract, the system may issue the customer a purchase reward which may include a loyalty point payout.

Abstract: A blockchain-based loyalty point system may include a blockchain API host that receives a request to transfer an amount of loyalty points from a first customer account to a second customer account. The system may validate the request by performing a cryptographic operation on the request using a public key associated with the first customer account. The system may also propagate a proposal to consensus participants for writing to a blockchain, wherein the proposal comprises the first customer account, the second customer account, and the amount of loyalty points. The system may also receive an exchange request from a loyalty wallet associated with the second customer account, validate the exchange request by performing the cryptographic operation on the exchange request using a public key, and propagate an exchange proposal to the consensus participants for writing to the blockchain.

Abstract: Systems and methods of improving the operation of a transaction network and transaction network devices is disclosed. A lightning KNN host may comprise various modules and engines as discussed herein wherein lookalike records may be identified whereby the speed of the lightning KNN network may be enhanced and the accuracy and precision of results improved whereby the transaction network more properly functions according to approved parameters.

Abstract: A transaction card includes a card body that may comprise a card body comprising a ceramic material, the card body including a primary surface and a first mating surface. A card backer comprises a metallic material and includes a secondary surface and a second mating surface. A portion of the first mating surface and a portion of the second mating surface are coupled together.

Abstract: A rewards management system is configured to facilitate the redemption of loyalty benefits at a financial institution and apply credits, payments, debits, and/or the like associated with the loyalty benefit to transactions that are characterized by a set of predetermined rules (e.g. an item purchased during a particular transaction, the merchant from whom the transaction originated, the vendor who manufactured the item). The system provides real-time management of the loyalty account so that the loyalty benefit can be used to offset the liability associated with a particular eligible transaction. The system may also be configured to allow a user to satisfy various obligations to the financial institution (e.g. a minimum payment associated with a statement from a transactions account). As such, the system allows the loyalty account provider or the financial institution to provide a customizable rewards program that allows loyalty benefits to be used for any type of transaction.

Abstract: A method and system of using widgets embedded in web pages as virtual storefronts is disclosed. A user of a social networking site may create a merchant account with a transaction service provider. The user embeds a storefront widget provided by the transaction service provider in the user's profile page on the social networking site and the user can use the storefront widget to input information about products that the user is selling. Other users of the social networking site view the user's profile page and the storefront widget will display the products that the user is selling. The other users may interact with the storefront widget to purchase the products that the user is selling.

Abstract: A system for applying access permissions to read requests may write a file to a storage media. The file may contain data, an embedded flag, and an embedded verification datum of the embedded flag. The embedded flag may indicate an access permissions requisite for file access. The system may also receive a request to access the file from a user and retrieve an access permission for the user. The system may also compare the embedded flag to the access permission for the user to determine the user has permission to access the file. A verification datum may be calculated, and the calculated verification datum may be compared to the embedded verification datum to determine the embedded flag has not changed.

Abstract: A system may receive a request for access to a first variable. The request may include a requested action and a variable identifier for the first variable. The request may also have a syntax that is incompatible with first data storage format. The system may parse the request to capture the variable identifier from the request. The system may also look up a location of the first variable in a catalog using the variable identifier. The location of the first variable may include the first data storage format. The system may generate a query to access the first variable. The syntax of the query may be compatible with the first data storage format. The system may then submit the query to access the first data storage format. The query may be configured to complete the requested action.

Abstract: The method includes receiving a communication from a customer; identifying a customer profile associated with the customer; accessing account activity data associated with the customer profile; analyzing the account activity data; and/or determining an intent prediction associated with the communication based on the analyzing the account activity data, wherein the intent prediction comprises a predicted reason for the communication.

Abstract: A consumer may view a transaction account statement in a GUI. The transaction account issuer may utilize batch processed data and real time data to determine an eligibility for fixed fee payment plans. The consumer may be presented with the option to place a single transaction into a fixed fee payment plan by selecting the transaction. The fixed fee payment plan may comprise a fixed monthly cost. The monthly cost may be calculated to be equal to or less than the amount the consumer would pay if the transaction were subject to the transaction account APR. The transaction account may have a minimum amount due for the fixed fee payment plan and a minimum amount due for the revolving APR balance each month.

Abstract: The systems, methods, and computer program products (collectively “systems”) described herein are generally configured to monitor actions in digital channels. More specifically, the systems are capable of creating reservations for items and initiating payments for the items based on actions or information received from the digital channel. The systems are capable of syncing transaction accounts with various digital channels. Moreover, the systems are capable of initiating or completing transaction based on user information. The systems may also be capable of providing rewards based on activities or accomplishments in the digital channels. Moreover, the systems may be capable of verifying activities based on transaction information.

Abstract: The system manages database structure updates. The system may receive, via a development gateway, a development script. The system may also copy, via a backup engine to an update module, an existing object code. The system may deploy, via an update engine, the development script directly to the database structure. The system may also generate new object code within the database structure associated with the existing object code. The system may determine, via a database health monitoring module, at least one of a successful deployment of the new object code or an unsuccessful deployment of the new object code.

Abstract: Systems and methods of improving the operation of a transaction network and transaction network devices is disclosed. A SBO identification network host may comprise various modules and engines as discussed herein wherein the probability that a cardholder is a small business owner may be evaluated for establishing proper usage of differentiated transaction instruments according to their proper purposes, marketing and cross-marketing of differentiated transaction instruments, and provision of value-added services. For instance, a probable SBO may be identified, whereby the SBO identification network network may tailor the handling of the transactions, such as by denying them, whereby the transaction network may actively deter misuse of transaction products, or tailor the handling of electronically delivered advertisements, such as by targeting them, whereby the SBO identification network more properly functions according to approved parameters.

Abstract: A consumer may enroll in an event gamification system. An event listener may detect an event. The event gamification system may determine that the event qualifies for a game in which the consumer is enrolled. The event gamification system may transmit an achievement notification to the consumer as soon as the event occurs. The game may be displayed in a GUI on a consumer device. The consumer may be rewarded for completing the achievements in the game.

Abstract: Systems, methods, and articles of manufacture for expense management are disclosed. A user may submit receipts for one or more transactions into an expense management system. The expense management system may extract information from the receipts and match the extracted information to one or more of a plurality of Records of Charge (ROCs). The expense management system may match the extracted information to a ROC based on vendor name, location, time stamp, and the like. The expense management system may further assign a ROC to an expense category. The expense management system may assign a ROC to an expense category based on a standard industrial classification (SIC) code of a merchant, a category assigned to a different ROC, and a location associated with the ROC. An expense report for all submitted receipts may be generated.