OpenFinance
Development Portal

Authorisation API for V2.x (2.1)

The Berlin Group - A European Standards Initiative | info@: info@berlin-group.org | URL: https://www.berlin-group.org/

License: Creative Commons Attribution 4.0 International Public License

The Authorisation API provides services for managing Strong Customer Authentication (SCA) authorisation processes for various resource types including consents, payments, and other financial services. The API supports starting authorisation processes, updating PSU data, and checking authorisation status in compliance with PSD2 and EBA-RTS requirements.

Get authorisation status

GET /v2/{resource-path}/{resourceId}/{authorisation-category}/{authorisationId}

Checks the SCA status of an authorisation or cancellation authorisation sub-resource.

Parameter Type Description
resource-path string , required

This resource path can be a one-level parameter {service} or a two-level parameter {service}/{product-type}, where * {service} stands for the service type of the related business transaction, e.g. /payments or /consents source. * {product-type} stands for the product-type of the related business transaction where applicable, e.g. sepa-credit-transfers in the case of payments or account-access in case of consents.

Example: consents/account-access

resourceId string , required

Resource identification of the related payment initiation, signing basket, consent, subscription or other related business transaction resource.

Example: 1234-resource-567

Allowed length: max: 70

authorisation-category string , required

The following two categories are supported: * authorisations: used in case of an authorisation of the related business transaction. * cancellation-authorisations: used in case of the cancellation authorisation of the related business transaction. Used only if applicable to the addressed {service}

Allowed values: authorisations, cancellation-authorisations

Example: authorisations

authorisationId string , required

Resource identification of the related SCA.

Example: 123auth456

Allowed length: max: 70

Header Type Description
Digest string , optional

Integrity hash of the request body in the form SHA-256=<base64>. For an empty body, use the hash of an empty string. See Signing requests for how the Digest and signature are built.

Example: SHA-256=hl1/Eps8BEQW58FJhDApwJXjGY4nr1ArGDHIT25vq6A=

x-jws-signature string , optional

Detached JSON Web Signature over the signed request headers and body. See Signing requests for how it is constructed.

X-Request-ID string , required

Unique ID of the request, set by the initiating party and echoed back in the response.

Example: 99391c7e-ad88-49ec-a2ad-99ddcb1f7721

Format: uuid

Select a status code to see the structure and an example of the response.

Field Type Description
psuName string , optional

Name of the PSU (Usage is following the mandate resulting from EBA Q&A 2020_5165). In case of a corporate account, this might be the person acting on behalf of the corporate.

scaStatus string , required

This data element is containing information about the status of the SCA method applied.

Allowed values: received, psuIdentified, psuAuthenticated, scaMethodSelected, started, unconfirmed, finalised, failed, exempted

apiClientMessages array[object] , optional

Errors and warnings describing why the request failed. See Errors for the message format.

_links object , optional

Should refer to next steps if the problem can be resolved via the interface e.g. for re-submission of credentials.