Skip to Content
RegistrationClient ManagementManage consent display name

Manage consent display name

The consent display name is the name users see when they authorize your TPP. It initially comes from the Organization (O) attribute in the leaf eIDAS QWAC used during registration, not the name in the registration payload.

Before changing the display name, obtain a management access token.

You can set the display name only to a value that exactly matches the Organization attribute in the leaf QWAC of one of your current certificate chains. Copy the value without changing capitalization or whitespace. Changing it does not change your generated OAuth client name.

Get the current display name

curl \ -H "Authorization: Bearer your-access-token" \ --cert client.pem \ --key client.key \ https://tpp.openbanking.prod.lunar.tech/tpp/your-client-id/display-name

A successful request returns:

{ "displayName": "Example TPP A/S" }

Update the display name

curl \ -X PUT \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ --data '{"displayName":"Example TPP A/S"}' \ --cert client.pem \ --key client.key \ https://tpp.openbanking.prod.lunar.tech/tpp/your-client-id/display-name

A 403 Forbidden response with the code NAME_NOT_CERTIFICATE_BACKED means the requested name does not exactly match the Organization attribute in the leaf QWAC of one of your current certificate chains. The response body lists the names you can use in possibleDisplayNames:

{ "code": "NAME_NOT_CERTIFICATE_BACKED", "message": "display name is not backed by an associated certificate", "possibleDisplayNames": ["Example TPP A/S"] }

Copy one of those values verbatim. To use a name that is not listed, add a certificate whose leaf QWAC carries it. See Error responses for the error envelope and the complete list of codes.

Last updated on