Abstract: A system, method, and memory for handling real-time transactional events is disclosed. The exemplary system a processor to detect and add an event to a queue and identify an associated event type. Event types can require downstream processing by at least one provider. The processor decomposes the event into tasks by comparison to event types which associate downstream provider requirements to tasks and routes. One or more routes are assigned to the tasks, each route defined by at least one processor of a plurality of processors. One or more routes are defined by transmitting a request for downstream processing to the at least one provider. The processor, upon detecting incomplete performance of the one or more routes, either updates the tasks associated with the incomplete route, or marks the event associated with the route as incomplete in the queue.

Abstract: The present disclosure involves systems, software, and computer implemented methods for automatically providing linking partner loyalty rewards accounts using authorized user and primary user information associated with an account. One example method includes authenticating a user at a partner system, and receiving from the user information associated with an account. The information associated with user's account is communicated to a financial institution system via an API where the user can then be verified as an authorized user on an account. The financial institution system then provides the partner system with information associated with the primary user of the account, and the partner system can link a loyalty account of the primary user with the loyalty account of the authenticated user.

Abstract: A system, method, and memory for handling real-time transactional events is disclosed. The exemplary system a processor to detect and add an event to a queue and identify an associated event type. Event types can require downstream processing by at least one provider. The processor decomposes the event into tasks by comparison to event types which associate downstream provider requirements to tasks and routes. One or more routes are assigned to the tasks, each route defined by at least one processor of a plurality of processors. One or more routes are defined by transmitting a request for downstream processing to the at least one provider. The processor, upon detecting incomplete performance of the one or more routes, either updates the tasks associated with the incomplete route, or marks the event associated with the route as incomplete in the queue.

Abstract: A system, method, and memory for handling real-time transactional events is disclosed. The exemplary system a processor to detect and add an event to a queue and identify an associated event type. Event types can require downstream processing by at least one provider. The processor decomposes the event into tasks by comparison to event types which associate downstream provider requirements to tasks and routes. One or more routes are assigned to the tasks, each route defined by at least one processor of a plurality of processors. One or more routes are defined by transmitting a request for downstream processing to the at least one provider. The processor, upon detecting incomplete performance of the one or more routes, either updates the tasks associated with the incomplete route, or marks the event associated with the route as incomplete in the queue.

Abstract: A system and method are provided for monitoring transaction events. The method includes connecting the event processor device with at least one payment services channel and listening for events provided by the at least one payment services channel. The method also includes detecting an event associated with a masked transaction being facilitated by a payment service that masks a payment card number. The method also includes determining from the masked transaction a user identifier associated with the transaction, determining from the user identifier the payment card number, and confirming that the payment card number is linked to the loyalty program with the loyalty partner. When the payment card number is linked to the loyalty program, the method includes sending a message to the loyalty partner to have the loyalty partner execute a loyalty program action associated with the transaction that would have otherwise been masked at the point of sale.

Abstract: A system and method are provided for integrating loyalty program partner systems with an enterprise system. The method includes providing a first application programming interface (API) between a loyalty platform and one or more loyalty partner systems, providing an inbound traffic service to the platform, to receive data from the one or more loyalty partner systems via the first API, providing a second API between the platform and at least one payment system configured to detect transactions, and providing an outbound traffic service from the platform, to communicate with the one or more loyalty partner systems via at least one communication channel. The method also includes configuring a plurality of microservices within the platform and orchestrating the plurality of microservices using data received via the inbound traffic service and/or transaction data detected via the second API to update a corresponding loyalty partner system via the outbound traffic service.

Abstract: The present disclosure involves systems, software, and computer implemented methods for automatically providing linking partner loyalty rewards accounts using authorized user and primary user information associated with an account. One example method includes authenticating a user at a partner system, and receiving from the user information associated with an account. The information associated with user's account is communicated to a financial institution system via an API where the user can then be verified as an authorized user on an account. The financial institution system then provides the partner system with information associated with the primary user of the account, and the partner system can link a loyalty account of the primary user with the loyalty account of the authenticated user.

Abstract: The present disclosure involves systems, software, and computer implemented methods for automatically providing linking partner loyalty rewards accounts using authorized user and primary user information associated with an account. One example method includes authenticating a user at a partner system, and receiving from the user information associated with an account. The information associated with user's account is communicated to a financial institution system via an API where the user can then be verified as an authorized user on an account. The financial institution system then provides the partner system with information associated with the primary user of the account, and the partner system can link a loyalty account of the primary user with the loyalty account of the authenticated user.

Abstract: The present disclosure involves systems, software, and computer implemented methods for automatically providing linking partner loyalty rewards accounts using authorized user and primary user information associated with an account. One example method includes authenticating a user at a partner system, and receiving from the user information associated with an account. The information associated with user's account is communicated to a financial institution system via an API where the user can then be verified as an authorized user on an account. The financial institution system then provides the partner system with information associated with the primary user of the account, and the partner system can link a loyalty account of the primary user with the loyalty account of the authenticated user.