Banqware is an API-driven platform for open banking solutions, allowing banks and FinTech companies to access a number of European banking APIs. Banqware helps TPPs and banks quickly access open banking ecosystem and analyse banking data, allowing them to create bold and innovative solutions, as well as cross-sell and up-sell their existing product.
APIHub is a comprehensive solution that connects you to a wide range of financial services from different providers, without the hassle and complexity of integrating separate APIs. It gathers offers of multiple banks, insurance companies and brokerage firms and brings it together as data to implement in your app.
With actionable financial data delivered via API, companies can analyse the customers’ financial behaviour to serve them better.
End customers of our clients can receive personalised product recommendations tailored not only to their preferences but also to financial situation.
Also, companies can enrich the offer with financial services, hints on better finance management and any service they can dream of!
Banqware not only provides financial data, but can also analyse them for the client - providing answers to specific questions, such as “can the customer afford the company
services?”, or “does the customer have a good credit score?” with banking data used as a source similar to BIG or social media.
One safe interface to access multiple banks
Easy addition of new data sources
TPP-level access to payment service providers in all EU under one platform
Minimisation of time required to enter the market
Access to the fintech ecosystem to speed up establishing relationships
This is an overview to show you 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 to 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.
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
With the sandbox, you can
comfortably test connecting to
banking sandboxes, register and test
your call-backs, redirect URLs and
see how the actual financial data is
formatted. 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.
Obtaining authorisation is the first step, however we cannot inform you about the process in the public document. To find out how to authorise our API please visit Security section in the developer portal.
When you receive access to the APIHub, the first action to be taken is to register redirect URLs (mandatory) and call-back 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:
1. Create an object representing user's consent to access data from a specific bank. The initial status of the consent is then requested.
You have to pass one of the registered redirect URLs to us in order for the user to be redirected after the authentication from the bank website.
2. Then pass the authorization URL to the customer.
3. User uses the URL to authorize access to his or her data.
4. User is redirected to our redirect URL.
5. We receive code which we exchange for a token.
6. We change consent status to given. You can check status:
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 initialise an update, you need to be granted customer's consent and use the below endpoint.
You can either provide a call-back 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.
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 firstname.lastname@example.org
We support all EU open banking API standards and
we have more than 300 European banks connected.
We are adding new banks every month, tell us what should be next.
Get in touch to find out more about Banqware and view a demo today.