Our API allows dynamic client registration in order to create a valid client that is able to use our Authorisation Server. We only trust Software Statement Assertions (SSAs) issued by the Open Banking Directory provided by OBIE. eIDAS certificates are supported via onboarding to the Open Banking Directory (as discussed in more detail below).
The url of the registration endpoint is advertised on our OIDC Discovery Endpoints (see below) using the registration_endpoint claim.
aud claim used in the outer JWT of a Dynamic Client Registration request is the OBIE issued
org_id (as documented in the OBIE DCR v3.1 standard)
As defined further in the Monese Open Banking API Specification
For private_key_jwt - the
audclaim is the url of the token endpoint as specified in OIDC client authentication The request object used in OIDC flows the aud claim is the issuer url from the Monese ASPSP .wellknown endpoint (linked below).
Note: Our Sandbox API also offers less strict profiles to assist with integration testing. See below for more details.
We recommend that TPPs use OB Transport and OB Signing certificates where possible. TPPs can use their QWACs and QSeals to onboard to the OBIE directory and generate these certificates.
We support the use of OBWAC and OBSeal on our production and sandbox environments. TPPs can use their QWACs and QSeals to onboard to the OBIE directory and generate these certificates.
We support the use of QWACs, but this is not our recommended approach. TPPs facing issues onboarding with QWACs should contact our support desk. Please attach a pem file of the certificate to your support ticket.
We support the use of QSeals that have been attached to your software statement in the OB Directory.