Skip to navigation

developerportal

Your customers’ banks, public administrations and utilities, read with their consent — in an experience we host for you, or server to server from yours.

Choose your path

Two ways in. One platform underneath.

A flow puts an experience we host in front of your customer; a direct execution leaves the screen — and the code — to you. Both run the same engines and return the same data models.

What teams build

One session, more than one answer.

The same records serve more than one decision. A few of the ones our clients make with them:

Bank reconciliationA company’s business accounts, read again every day and matched against the invoices it expects.
Account verificationWho holds an account and its IBAN, before paying out to it.
Income verificationSalaries and pensions, read from the movements that came in.
AffordabilityRecurring expenses beside the balances, before lending.
Money managementEvery account, card and debt across banks, kept up to date.
Recurring paymentsWho charges your customer by direct debit, how much and how often.
Every Financial Rider use case, with what it reads
The toolbox

What you build with, whichever path you take.

Built with