Open banking APIs

An aggregator gives you many banks through one API and handles each bank’s differences, at a per-call or per-connection cost. Direct connections give more control and can suit a small number of important banks. Many products start with an aggregator and add direct connections later. We compare the options against the banks and countries you need.

Account information and payment initiation are regulated activities in many countries. Either your company holds the authorisation, or you work through a licensed provider that holds it. Which applies depends on your country and use case, and your legal and compliance advisers should confirm it. We build the integration for whichever route you take.

The customer sees what data is shared, for what purpose and for how long, and authenticates with their own bank. The connector stores the consent and its tokens encrypted, and every call is tied to a valid consent. Customers can withdraw consent, and the connector stops calling that bank for them when they do.

Coverage depends on the region’s rules and the banks’ APIs. The European Union and the United Kingdom have broad coverage under PSD2 and the UK Open Banking Standard. Elsewhere coverage varies, and aggregators fill some of the gaps. We check coverage for the banks your customers use before you commit to a design.

Not for most corporate treasury work. Host-to-host channels handle bulk payment files and full statements for your own accounts. Open banking suits customer-facing products, real-time balances and single payments. Many businesses use both: host-to-host for their own payment runs and open banking for their customers.

Tokens and consent records are encrypted at rest, only the connector can use them, and every call is logged with the consent behind it. We collect only the data the purpose needs and set how long it is kept. Data protection rules such as GDPR apply to this data, and we design with your data protection officer.