In the scope of the European Payment Services Directive 2015/2366 (also known as PSD2), Beobank provides API access to qualified Third Party Payment Service Providers for the following purposes:

• Account and Transaction Information for Account Information Service Providers (AISPs)
• Checking of Funds Coverage for Card-Based Payment Instrument Issuers (CBPIIs)
• Payment Initiation for Payment Initiation Service Providers (PISPs)

These APIs are available at https://oauth2-apiii.e-i.com/beobank/, with a sandbox environment at https://oauth2-apiii.e-i.com/sandbox/beobank/.

Recent and upcoming changes

  Stay up-to-date with our updates feed.

Subjects

• Registration for API Access - Who can access the APIs, under what criteria?
• OAuth 2 and Strong Customer Authentication Workflows - How, when, and under which conditions will Strong Customer Authentication be processed?
• OAuth 2 Endpoints - How is OAuth 2 implemented?
• Open Banking API Endpoints - How to call the endpoints, what do they return?

API Specifications

If you want to dive directly into the APIs, they are documented as OpenAPI Specification (Swagger) files:

• View OAuth 2 Endpoints Specification
• Open Banking API Endpoints Specification:

  • View v2.2 Published

    Changelog

    • On the /accounts endpoint, field psuStatus has been added, indicating whether the PSU is a holder, a co-holder, or an attorney for the given account;
    • On the /accounts endpoint, field product has been added, and gives the name of the product of which the given account is an instance of. These product names correspond to names that are shown on the Beobank online banking interfaces;
    • On the /accounts endpoint, the field name has been simplified, and only contains a simple label for the account - whereas whereas v2.1 of this API returned a composite name. Please refer to the name field documentation for information for how to reconstruct the old composite name from the data returned in this version;

  • View v2.1 End-of-life on June 1, 2025

    Changelog

    • On the /accounts endpoint, credit cards are now identified by their masked PAN, using the MPAN scheme;
    • On the /accounts/{id}/transactions endpoint, all amounts are returned in absolute values with a CRDT/DBIT indicator;
    • [ERRATUM March 9, 2022] Previous changelog said that amounts on the /accounts endpoint were returned in absolute values, which is not the case;
    • On the /accounts/{id}/transactions endpoint, pending credit card transactions are now marked with status OTHR instead of PDNG;
    • On the /accounts/{id}/transactions endpoint, in case where counterparty information is available, they will be in the appropriate fields;
    • In payment initiation workflows, once the PSU has validated the SCA, debtor.name will be filled in response to a GET request;
    • In payment initiation workflows, in cases of pending validation by Beobank, status PDNG will be returned instead of ACSP;

API specifications updates and deprecation announcements are also in our updates feed.

Publication of statistics

• View statistics

Contact us

• Need some help? Get in touch with Beobank