Event notifications let a bank tell a provider when something relevant changes, such as a consent being revoked or a resource updating, so the provider can react immediately rather than only finding out on its next call. They are how open banking data and state stay fresh, and they favour a push model over constant polling.
What the event notification API does
Most of open banking is request and response: you ask, the bank answers. Event notifications add the other direction, the bank telling you that something happened, so you are not left guessing between calls. The classic case is a customer revoking consent: without notifications you would only discover it the next time you tried to read, which might be too late; with notifications you know at once and stop using the access. See open banking consent.
What you get notified about
- Consent changes, most importantly revocation, so you can stop using access that no longer applies.
- Resource updates, where a resource relevant to you has changed, so your view can be refreshed.
The exact events depend on the bank's implementation, which is one more thing a good provider tracks across banks on your behalf.
Polling vs push
There are two ways to stay current, and they trade off simplicity against efficiency:
| Approach | How it works |
|---|---|
| Polling | You repeatedly ask the bank whether anything changed. Simple, but heavier on calls and slower to detect change. |
| Push | The bank notifies you when something changes. More timely and efficient, at the cost of needing to receive and verify notifications. |
Push via event notifications is the better model where it is available, because it reacts in near real time and avoids wasteful polling. A robust integration often uses push as the primary signal with light polling as a safety net.
Keeping data fresh
Freshness is the whole point. For a lender relying on ongoing access, knowing immediately that a consent was revoked or an account changed means your records stay accurate and you never act on access you no longer have. It also reduces load: you refresh what changed, when it changed, instead of re-reading everything on a schedule. This pairs with robust status and error handling to keep an integration both current and efficient.
From the data consumer's side
You will not build notification receivers yourself, but you should expect your provider to use event notifications where banks support them, so that revoked consents are honoured immediately and your data is current. The question to ask is simple: how quickly do you learn when a customer withdraws access, and how do you keep ongoing data fresh? A good answer involves push notifications, not just polling.
How Credit Canary does it
Credit Canary uses event notifications where banks support them, so revoked consents are honoured at once and ongoing data stays current, with light polling as a fallback. You get accurate, fresh data without managing notification infrastructure.
Common questions
What is the event notification API?
It is the open banking profile that lets a bank notify a provider when something relevant changes, such as a consent being revoked or a resource updating, so the provider can react rather than only finding out on the next call.
What is the difference between polling and push?
Polling means repeatedly asking the bank whether anything changed; push means the bank notifies you when it does. Push is more efficient and timely; polling is simpler but heavier and slower to detect change.
Why do event notifications matter for keeping data fresh?
They let you learn immediately when a consent is revoked or an account changes, so you stop using stale access and keep your records accurate without constantly re-reading everything.
Related pages
Primary sources
- Read/Write API v4.0.1 event notification profile (checked 14 Oct 2026).
- Open Banking Standard hub (checked 14 Oct 2026).
Credit Canary provides open banking through fumopay limited, an FCA-authorised account information and payment initiation service provider (FRN 925689), of which Credit Canary is an agent. Underlying bank connectivity is also provided by fumopay limited. This page is an evergreen reference and is reviewed and dated; it is not regulatory, legal or financial advice.