The Event Notification API Profile describes the flows and common functionality to allow an AISP/PISP to receive event notifications.
The Event Notification Subscription API Profile provide mechanisms for AISPs/PISPs to register for event notifications.
The Event Notification Subscription API allows AISPs/ PISPs to register to receive all or specific event types via the Real Time Event Notification API and/or the Aggregated Polling API.
TPP must complete each of the steps below in order:
Step 1: Setup Event Notification Subscription
This flow begins with an AISP/PISP creating an event-subscription resource with an ASPSP. This may optionally contain a callback url, and a series of event types
Step 2: Deliver Event Notification
An event corresponding to one of an ASPSP's event types occurs on a resource
Step 2a: ASPSP Sends Real Time Event Notification
AISP/PISP must have provided a callback URL with the event-subscription resource in order to receive the real time event notification
The ASPSP sends a signed event notification to the callback URL, detailing the nature of the event and identifying the affected resource
The AISP/PISP may optionally initiate a client credential grant to retrieve the resource using the details contained in the event notification
Step 2b: AISP/PISP Requests Event Notifications
AISP/PISP may request event notifications using aggregated polling
Step 3: Retrieve/Update/Delete Event Notification Subscription
AISP/PISP may Retrieve/Update/Delete the event notification subscription
The Event Subscription resource is used by an AISP/PISP to subscribe to events with an ASPSP.
The Real Time Event Notification API Profile describes the flows common functionality for the Real Time Event Notification API, which allows ASPSPs to notify an AISP/ PISP that an event has occurred.
Aggregated polling allows an AISP/ PISP to request an aggregated set of events from multiple users/customers during a specific period.