Before you use our APIs, you should do a few basic tasks in the following order:
Browse the available APIs
Take a look at our APIs to see what choices are available. Is there an API you can exploit in one of your applications? Use the supplied APIs to quickly construct a fully-featured application.
Sign Up on Sandbox Developer Portal
Found a useful API? Sign up for the Sandbox Developer Portal to create an account and get started. It is free to join. Contact us at PSD2.email@example.com to register.
Register your application
Before you can use an API you have to register your application. When you register an application, the application is assigned a unique client ID and client secret. You must use the client ID when you call an API that requires you to identify your application by using a client ID, or a client ID and client secret. Check the API description for the details.
The use of the Akcenta APIs (hereinafter the “API”) and the test Developer Portal (hereinafter the „Sandbox“) requires Qualified Website Authentication Certificates (QWACs) as a method to authenticate the ‘Internet Entity Identity’ and encrypt communications in order to provide confidentiality.
Under eIDAS, a QWAC is a legal term for the existing certificates that are issued under the Certification Authority & Browser Forum’s standards for Extended Validation Secure Socket Layer (EV SSL) Certificates.
The primary objectives of an EV SSL Certificate are to:
1. Identify the legal entity that controls a web site by providing reasonable assurance to the user of an Internet browser that the web site the user is accessing is controlled by a specific legal entity identified in the EV Certificate by name, address of Place of Business, Jurisdiction of Incorporation or Registration and Registration Number or other disambiguating information;
2. Enable encrypted communications with a web site by facilitating the exchange of encryption keys in order to enable the encrypted communication of information over the Internet between the user of an Internet browser and a web site.
If you are experiencing issues with your eIDAS certificate, accessing our Developer Portal, during the enrollment process/ consumption of our APIs please make sure on the following:
- CA signing your certificate is part of the official list of Qualified Trust Service Providers (QTSPs) available in the European Union,
- the certificate is not expired,
- the certificate is valid for the role you are authorized (i.e. AISP, PISP),
- the certificate is not revoked by the National Authority
If you are in possession of a valid test certificate but aren’t able to consume our APIs please contact us.
Invite your developers
Invite other developers from your organization to develop and maintain your application.
Select a plan and test your application
Finally, now that your application is registered, you need to subscribe to a plan. The plan determines the number of API calls that your application can make. Some plans are free and no approval is required, some require approval, and some require approval and a monthly subscription. Think about what you need and choose the most suitable plan. Once your application is subscribed, you can use received credentials to test all APIs included in the subscribed products.
The Accounts API allows third party applications to interact with the accounts of a bank user on his behalf, allowing the following operations:
Since Account API provides only information about the account(s) and transaction(s), it is read-only, and therefore this API supports only GET requests.
The Payments API allows third-party applications to initiate single payments for both private individuals and legal entities, on client’s behalf.
Payments placed via open banking are charged to clients of Akcenta same as the payments initiated via the current OLB according to client’s pricing plan. Exchange rates are the same as those used on current OLB.
<<section will be completed>>
<<section will be completed>>
Should you have any questions, please do not hesitate to contact us at PSD2.firstname.lastname@example.org.
When you add an application you are provided with a client ID and client secret for the application. You must supply the client ID when you call an API that requires you to identify your application by using a client ID, or a client ID and client secret.
To register an application please contact us at PSD2.email@example.com. Once you have provided an application name, description, etc. you will be shown your application client ID and client secret. You must supply the client secret when you call an API that requires you to identify your application by using a Client ID and Client secret.