OpenFinance
Development Portal

openFinance API Framework Implementation Guidelines Administrative Services (1.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

After conclusion of necessary contracts an API Client has to execute a technical onboarding at the openFinance API of an ASPSP. As part of the technical onboarding the ASPSP can check if all necessary contractual steps have been finished before. If everything is ok the ASPSP will assign a unique apiContractId to the API Client and will return this to the API Client as response of the technical onboarding. The API Client has to use this apiContractId for all further accesses to the extended services at the openFinance API of the ASPSP.

Start onboarding

POST /v2/onboardings

Creates the onboarding resource at the ASPSP.

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.

Body-Sig-Profile string , optional

Indicates the signature profile used for signing (parts of) the body. Shall be used if the body is signed.

Allowed values: JAdES_JS, XAdES, EMV_AC, EUDIW

Example: XAdES

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

Field Type Description
schemeId string , required

Identification of the corresponding scheme, in case of no scheme involved use constant BILATERAL Example: giroAPI-payment The schemeIds supported by the ASPSP should be provided in the Discovery API [oFA Discov].

serviceIds array[string] , required

Identification of the extended services for which the onboarding will be done. Possible values to identify a service have to be defined by the service owner (scheme or ASPSP). The service types supported by the ASPSP should be provided in the Discovery API [oFA Discov].

Allowed values: PIS, RPIS, BPIS, XFPIS, XDPIS, XDFPIS, XMDPIS, XMDFPIS, XRPIS, XRFPIS, XMRPIS, COF, CONS-AIS, XCONS-DOC, XCONS-PSUP, XCONS-COF, AIS, XAIS-LA, XAIS-SA, XAIS-CA, XAIS-SC, XAIS-ST, SGNB, MAN, DOC, XPAIS-AE, XPAIS-AB, XPAIS-AS, XPAIS-RTP, RTP, VOP, XPIS, XBPIS

apiClientContacts array[object] , optional

Contacts (of different categories) of the API Client. Only to be given if not already available by e.g. a directory service.

serviceContractId string , required

Identification of the service contract concluded between the service owner (scheme or ASPSP) and the API Client to use these services.

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

Field Type Description
validTo string , optional

Date until when the successful onboarding is valid. The attribute validTo shall only be provided if the onboarding resource has been created and the resource status is set to valid. Otherwise this attribute shall be missing.

Format: date

validFrom string , optional

Indicates the date after which the API Client can access the services at the openFinance API of the ASPSP using the apiContractId returned with this response.

Format: date

onboardingId string , required

Unique identification of the onboarding resource created by this initiation.

apiContractId string , optional

Unique identification of the successful onboarding of the API Client for the list of services. Shall be used by the API Client if accessing the services after the onboarding. The attribute apiContractId shall only be provided if the onboarding resource has been created and the resource status is set to valid. Otherwise this attribute shall be missing.

Format: uuid

onboardingStatus string , required

Status of the onboarding process.

Allowed values: received, rejected, expired, terminatedByApiClient, terminatedByAspsp, valid, validTimeRestricted

_links object , optional

A list of hyperlinks to the next steps to read a price list and to confirm a price list. The attribute _links shall only be provided if the technical onboarding requires the execution of the two step process according to section 2.2. Otherwise this attribute shall be missing. If this attribute is provided it shall contain the following link: • readConditions • confirmConditions Remark about future versions: Future versions of the data dictionary [oFA DaD] will contain the definition of these href types.