Dynamic client registration (DCR) lets a provider's software register itself with a bank's authorisation server automatically, instead of each registration being arranged by hand. It uses a Software Statement Assertion from the Open Banking Directory to prove who the provider is. It is essential plumbing for scaling across banks, and it is something your provider handles, not you.
What DCR does
To call a bank's APIs, a provider must be registered as a client with that bank's authorisation server. Doing this by hand for every bank would not scale, so the Standard defines dynamic client registration: the provider's software presents its credentials to the bank programmatically and is registered automatically. The bank gets a verifiable record of who it is dealing with, and the provider gets a client it can use, without a manual exchange for each bank. For where this sits, see the Directory and certificates.
The Software Statement Assertion
DCR works because of trust established centrally. The Open Banking Directory issues a Software Statement Assertion (SSA): a signed statement that describes a provider's software and vouches that the provider is a genuine, enrolled participant. During registration the provider presents the SSA, and the bank verifies the signature against the Directory before registering the client. In effect, the Directory acts as the referee, so each bank does not have to vet each provider independently.
Where it sits in onboarding
DCR is one step in a provider's onboarding to a bank, alongside holding the right certificates and meeting the security profile. The sequence is roughly: enrol in the Directory, obtain certificates and an SSA, register the client with each bank via DCR, then begin making authenticated API calls under the FAPI profile. See the security profile. A mature provider has this running across the banks its customers use, which is part of what you are buying when you choose one.
Why most data consumers never touch it
If you are a lender, broker or accountant using open banking through a platform, DCR is invisible to you. Your provider holds the Directory enrolment, the certificates and the registrations, and exposes a ready-made capability. Understanding DCR helps you ask a provider the right question, how broadly and reliably they are registered across banks, but you will not implement it. The practical takeaway is on choosing a provider: bank coverage is partly a function of how well a provider manages registration and certificates at scale.
From the data consumer's side
Treat DCR as a sign of maturity rather than a task for you. A provider that registers cleanly and broadly across banks gives you better coverage and fewer connection failures; one that struggles with it will show gaps in exactly the smaller banks your customers sometimes use. You never see the mechanism, but you feel the quality of it in your connection success rate.
How Credit Canary does it
Credit Canary works through a regulated provider that manages Directory enrolment, certificates and client registration across banks, so you get broad, reliable coverage without touching DCR. You consume connections that work, not the onboarding behind them.
Common questions
What is dynamic client registration?
Dynamic client registration (DCR) lets a provider's software register itself automatically with a bank's authorisation server, rather than each registration being set up by hand. It uses a Software Statement Assertion from the Open Banking Directory to prove who the provider is.
What is a Software Statement Assertion?
A Software Statement Assertion (SSA) is a signed statement issued by the Open Banking Directory that describes and vouches for a provider's software. The bank uses it during DCR to verify the provider before registering it.
Do data consumers need to handle DCR themselves?
No. DCR is handled by the provider whose platform you use. It matters for understanding how onboarding to banks scales, but it is not something a lender or broker implements.
Related pages
Primary sources
- Open Banking Standard, Dynamic Client Registration specification (checked 14 Oct 2026).
- Read/Write API v4.0.1 security profile (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.