Dynamic Client Registration (DCR)

Register OAuth 2.0 / OIDC clients programmatically with Kang Open Banking using RFC 7591 Dynamic Client Registration. Signed Software Statement Assertion (SSA), FAPI 1.0 Advanced extensions, mTLS binding, rotation and revocation.

Programmatic OAuth 2.0 / OIDC Client Registration

Kang Open Banking implements RFC 7591 Dynamic Client Registration with the FAPI 1.0 Advanced extensions required by UK Open Banking, Berlin Group NextGenPSD2, and FDX. One signed Software Statement Assertion (SSA) authorises a Third-Party Provider (TPP) against every connected bank in the directory.

Endpoint

POST https://api.kangopenbanking.com/v1/dcr/register
Content-Type: application/json

{
  "software_statement": "eyJhbGciOiJQUzI1NiJ9...",
  "redirect_uris": ["https://yourapp.com/callback"],
  "grant_types": ["authorization_code", "refresh_token", "client_credentials"],
  "response_types": ["code"],
  "token_endpoint_auth_method": "tls_client_auth",
  "scope": "openid accounts balances transactions payments offline_access"
}

Required SSA claims

software_id — stable identifier for the TPP application
software_client_name — human-readable name shown on consent screens
software_roles — AISP, PISP, CBPII or any combination
software_jwks_uri — public JWKS for request signing
org_id — verified organisation identifier from the KOB Directory

Lifecycle (RFC 7592)

GET /v1/dcr/clients/{client_id} — read the live registration
PUT /v1/dcr/clients/{client_id} — rotate metadata or secret
DELETE /v1/dcr/clients/{client_id} — revoke the client and all issued tokens

Standards: RFC 7591, RFC 7592, RFC 8705 mTLS, FAPI 1.0 Advanced § 5.2.2.

Developer Portal Home | OpenAPI Spec (JSON) | Contact