This is an overview show you an overview of the steps that need to be taken to integrate PSD2 API Hub with your services and applications. They are shown in the diagram and explained in detail below. You can work on the Sandbox API without signing an agreement with us.
The contractual path is only required for working with the production API.
Registration on the Developer Portal is necessary as it gives you access to our documentation and the sandbox environment. After registering you need to subscribe to the selected product and then, after verification, you will receive credentials necessary to use a sandbox.
Link to the Developer Portal : Developer Portal
After you register, you gain access to the sandbox API. Our sandbox is provided to test the integration to our APIHub and to allow you a deeper understanding of how the API works. The Sandbox supports a full, end-to-end experience for multiple banks and has been fully tested with our QA team. The solution is created to be easy to use, so we hope you will not get stuck.
With the sandbox, you can comfortably test connecting to banking sandboxes, register and test your callbacks, redirect urls and see how the actual financial data is formatted. We will not serve you mock data or hardcoded values - what you get is actual data from banking sandboxes. There may be differences between sandboxes and production environments of banking APIs, or other API aggregator solutions but with our API it is not the case. We compile different APIs into one to deliver a seamless and consistent experience between different environments. Integration with our API is an easy process.
In order to use actual banking data and our TPP License, we need you to meet legal requirements. This involves a signed contract between you and banqware in order to establish a formal relationship that will allow us to give you access to production APIs and actual financial data of your customers.
With a signed contract, we can start the process of connecting you to our production environment. We will need a few items to finalize this:
After the process is finished you can access actual financial data of multiple banks through our API and go live with Open Banking.
When using APIHub you don't connect to banking AIS APIs directly. Nor you connect to them indirectly. In order to unify the flows provided by multiple banks and multiple standards, we synchronize them "under the hood" then save the data in our internal persistent store. After the data is updated, you can access general financial data or identity verification data using either our Account Info API or KYC API respectively.
In order to access data you only need to follow a few simple steps described below which depend on Sync API. These steps are necessary to fill our internal storage with your data
Related resources are:
Obtaining authorization is the first step, however we cannot inform you about the process in the public document. To find out how to authorize our API please visit Security section in the developer portal.
When you get access to the APIHub, the first action to be taken is to register redirect urls (mandatory) and callback urls (optional). In order to register or update urls you can use below method.
When creating either consent or update resource later on, you will be able to pass one of the registered urls. You can also register a list of redirects so that you will be able to use our sandbox and production APIs using different environments and different setups.
All the other endpoints have to be applied to the user account, so we need to create a user first. ClientId is an optional user's identifier. You can use it interchangeably with a UserId given by us. If you want to create it, follow the below method
In order to get user's consent to acquire their data you need to:
Now we are ready to make an updated request to ApiHub.
An update object is an abstraction representing the process of updating user data. In order to initialize an update, you need to be granted customer's consent and use the below endpoint.
You can either provide a callback URL on which we'll post information about the update status change or you can check the status of the update by calling the endpoint as below.
Update status completed means that all the data has been fetched, processed and unified and are now available through our API endpoints. First call can take a bit longer - we're fetching as much data as we can, but every following update is just incremental.
After the update status changes to completed, you can access the account information and KYC information using account information resources and KYC resources respectively.
When the user's data is no longer needed you can delete both the user's consent and all the data that has been acquired with this consent with the below call.
This is all you need to configure before making it work. If you have any questions contact us at contact@banqware.com
Banqware is an API-driven platform for open banking solutions, allowing for banks and fintech companies to access a number of European banking APIs.
Banqware helps TPPs and banks quickly access open banking ecosystem and analyze banking data, allowing them to create bold and innovative solutions, as well as cross-sell and up-sell their existing product.
Copyright 2022 © banqware.com
