Error codes

Errors encountered specifically during the OAuth authorization flows will be returned in accordance with section 4.1.2.1 of OAuth 2.0 Authorization Protocol. In particular, the 'error' parameter indicates the overall type of error.

Further details about the error can be found in the error_description parameter.

If the error_description string begins with "base64UrlEnc-" , e.g.

error_description=base64UrlEnc-eyAiRGVzY3JpcHRpb24iOiJUbyBsb2cgaW4sIHlvdSBtdXN0IGJlIGEgY2xpZW50IG9mIFN5ZGJhbmsgYW5kIGhhdmUgYSB2YWxpZCBOZXRiYW5rIGFncmVlbWVudC4gUGxlYXNlIGNvbnRhY3QgSG90IExpbmUgYXQgKCs0NSkgeHggeHggeHggeHggb3IgeW91ciByZWxhdGlvbnNoaXAgbWFuYWdlci4iLCAiRGlzcGxheWVkIjoidHJ1ZSIsICJDb2RlIjoiQ1VSX0FHUjAyMSIgfQ%3D%3D 

then the remainder of the string can be URL- and base64 decoded (notice for example that '%3D' in the string above is a URL-encoding and has to be converted back into a '=' sign before the full string can be base64-decoded). The decoded error description will reveal a JSON struct on the form:

{ "Description":"To log in, you must be a client of Sydbank and have a valid Netbank agreement. Please contact Hot Line at (+45) xx xx xx xx or your relationship manager.", "Displayed":"true", "Code":"CUR_AGR021" }

Where the

• 'Description' text (intended for the PSU), in this case indicating that the PSU is not a client in the specific bank
• 'Displayed' field indicates, if the value is true, that this error message has already been displayed to the PSU in a dialog; otherwise, the TPP client application should show an appropriate error message
• 'Code' is an error id that specifies the type of error (see below)

The error ids that may be returned in 'Code' can be found in the table below together with their description (subject to dynamically inserted texts for bank names, hot line numbers and error correlation ids.) The error correlation ids (on the form "error code xxxxxxxx"), when present, will be useful for the support to locate and analyze the specific error scenario in server logs.