Abstract: Methods, systems, and techniques for using an actor model payment processing engine to process payments. A payment instruction is received. An event corresponding to the payment instruction is stored in an event journal. The payment processing engine, which is event-sourced and actor-based, performs the payment instruction. Performing the payment instruction involves transitioning the engine through one or more states in response to the payment instruction, and may involve performing actions with non-event sourced and event sourced actors in both stateless and stateful environments.

Abstract: Methods, systems, and techniques for event notification. An event, such as a payment event that represents a payment transaction having been initiated, completed, or that the transaction is in progress, results in an event engine sending an upstream message to one or more servers. The one or more servers receive the upstream message, which is in a first format. The one or more servers convert the upstream message into a downstream message that is in a second format, such as an ISO 20022 format, and the downstream message is subsequently consumed by an event consumer. The event consumer may consume the downstream message in real-time relative to when the event occurs. Undelivered upstream or downstream messages may be stored in a dead letter channel repository for attempted redelivery.