Concepts
The Notification Service is an application that produces Payment Status Notifications, based on Domain Events it receives. It does this by implementing an observer pattern where it reports a configurable subset of domain events to an external system or systems.
The Notification Service application supports the following features:
-
Converting domain events to PAIN.002 messages in JSON format
-
Filtering domain events - create notifications for specific domain events in specific flows, and optionally where some other related attribute matches a configured rule (e.g. related CSM)
-
Customisation of the PAIN.002 message output - based on the triggering domain event and the original payment instruction, status, reason and additional info can be customised
-
Sending notifications to multiple bank endpoints
Further reading
-
Data Flows - The Notification Service essentially has two key data flows which are worth understanding, to show how various components are linked together to provide a solution which can produce notifications.
-
Resequencer - The Resequencer Pattern is used for reordering of messages before processing to ensure PAIN.002s are published in the correct order.