Payment Event Notification Conversion to ISO 20022

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in efficiently converting and delivering event notifications across different computer systems and formats, particularly in the context of electronic payments, where various parties require real-time or non-real-time notifications in diverse formats, leading to compatibility issues and potential data loss.

Innovation Solution

A method and system that involves converting upstream messages from one format to a downstream format suitable for event consumers, utilizing a dead letter channel repository to handle errors, and implementing a retry mechanism for undeliverable messages, leveraging technologies like Apache Kafka, Apache Camel, and Springboot for event routing and delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If message format conversion is implemented across different computer systems, then compatibility and versatility are improved, but system complexity increases due to multiple format requirements

Engineering Contradiction:
Improvemessage format compatibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

An intermediary message conversion system is introduced between event producers and event consumers. This converter receives events in various source formats (XML, JSON, CSV, fixed-width) and transforms them into standardized downstream formats, eliminating the need for each system to implement multiple format handlers and reducing overall system complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message conversion system implements multi-functionality by supporting multiple input formats (XML, JSON, CSV, fixed-width) and multiple output formats through a single unified conversion engine. This universal approach allows one system to serve multiple format requirements without increasing complexity

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Speed

If real-time event notification is implemented, then response speed is improved, but data loss risk increases due to potential conversion or delivery errors

Engineering Contradiction:
Improveevent notification speedVSAvoiddata delivery reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary validation and error checking during the message conversion process before delivery. By detecting and handling conversion errors, formatting issues, and delivery failures in advance through retry mechanisms and error logging, the system prevents data loss while maintaining real-time notification capabilities

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Feedback mechanisms are implemented through retry logic for failed deliveries and error reporting systems. When conversion or delivery fails, the system receives feedback about the error, attempts recovery through retries, and logs failures for monitoring, ensuring reliable data delivery while maintaining real-time performance

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If multiple message formats are supported for different consumers, then adaptability is improved, but processing time increases due to format conversion overhead

Engineering Contradiction:
Improveconsumer format supportVSAvoidmessage processing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary conversion to a standardized intermediate format during event ingestion. This pre-conversion approach eliminates the need for repeated format transformations for different consumers, reducing processing time while maintaining support for multiple consumer formats through the standardized intermediate representation

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12456119B2Method and system for event notification
Publication Date: 2025.10.28 ROYAL BANK OF CANADA
  • US12456119B2 patent drawing
  • US12456119B2 patent drawing
  • US12456119B2 patent drawing

AI summary

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.