Event-Driven Messaging Architecture for Payment Network Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing network services face challenges in efficiently managing and updating messaging pathways and destinations, particularly in payment networks, due to the complexity of technical routing and regulatory compliance.

Innovation Solution

The implementation of an event-driven architecture where requests are published to messaging platforms under specific topics, allowing services to subscribe and respond accordingly, promoting loose coupling and efficient service invocation without requiring changes to underlying codes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If message driven architecture is used where recipients await messaging arrival and react, then services can be provided in payment networks, but the complexity of managing and updating messaging pathways and destinations increases

Engineering Contradiction:

ImproveAbility to update messaging pathways and destinationsVSAvoidComplexity of managing messaging pathways

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the monolithic message-driven architecture into a distributed event-driven system where the network is divided into multiple event networks. Each event network handles specific event types independently, allowing services to subscribe to relevant events without managing complex routing paths. This segmentation enables independent updates and additions of services without affecting the entire system's messaging complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces event networks as intermediary layers between message originators and service recipients. These event networks act as mediators that publish events to multiple subscribers simultaneously, eliminating the need for originators to manually direct messaging to specific recipients. The intermediary event network handles the complexity of pathway management, allowing services to be added or updated without changing underlying routing codes.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If originators are responsible for properly directing messaging and conforming with regulations, then messaging can be coordinated between institutions, but the difficulty of disseminating and updating routing knowledge increases

Engineering Contradiction:

ImproveProper coordination and regulatory complianceVSAvoidEase of disseminating and updating routing knowledge

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent inverts the traditional message-driven responsibility model. Instead of originators being responsible for directing messages to correct recipients, the system allows any service to publish events to event networks without knowing who will consume them. The consumers (services) subscribe to events they need, reversing the direction of knowledge flow. This inversion maintains reliability through event validation while dramatically improving ease of operation, as routing knowledge is disseminated through event subscriptions rather than complex manual configuration.

Inventive Principle:

Principle #13The other way round (Inversion)

3Productivity

If services are tightly coupled with messaging pathways, then message routing can be controlled, but the speed of service implementation and updates decreases

Engineering Contradiction:

ImproveSpeed of service implementationVSAvoidCoupling between services and messaging pathways

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the coupling between services and messaging pathways by introducing event networks as an independent layer. Services are taken out from direct dependency on routing infrastructure and instead interact through standardized event publications and subscriptions. This extraction allows services to be implemented, added, or updated independently without affecting messaging pathway complexity, thereby increasing productivity while reducing coupling.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS20250200574A1Systems and methods for distributing event driven network services

Publication Date: 2025.06.19 MASTERCARD INT INC

AI summary

Systems and methods herein provide event-drive network services. One example method includes subscribing to a first event topic on a first event-driven messaging platform and, in response to publication of a first event, consuming, from the event-driven messaging platform, the first event based on the first event being published to the first event topic. The method also includes compiling and delivering a first message to a computing device located in a second region, based on consumption of the first event, whereby at least a second event including information from the first message is published, by the second consumption computing device, to a second event topic on a second event-driven messaging platform in the second region. The method further includes receiving a second message from the computing device, responsive to the first message, and publishing a third event on the first event-driven messaging platform under the first event topic.