Skip to content
Fizen

Account access

PDF statements and screenshots are out of date the moment they are made, easy to fake and have to be retyped by hand.

How it works

  1. Step 01

    The customer picks a bank

    In the Fizen Connect widget or your own interface they choose their bank.

  2. Step 02

    They consent in the bank

    They log in to the bank, choose the accounts and confirm consent with strong authentication.

  3. Step 03

    You fetch data via the API

    Balances and transactions in one format, for 180 days after consent.

What you get

  • Balances, transaction history and account holder data, limited to the scope you need
  • One data format from 40+ banks in 6 countries
  • Access for 180 days, refreshed up to 4 times a day without the customer present
  • The customer decides which accounts to share
  • Webhooks about new transactions and expiring consent
  • Read-only: no payment can be made through AIS

Use cases

Banks and financial institutions

Better risk assessment and customer service based on current data.

Credit scoring

Scoring models fed with account data instead of declarations.

Fintech apps

Services and recommendations based on real financial behaviour.

Compliance and AML

A fuller picture of a customer's financial activity in AML procedures.

Regulation

We access data as an account information service provider (AIS) under the Polish Payment Services Act and PSD2, supervised by the KNF. Consent lasts 180 days, the customer can revoke it at any time, and we process data only for the purpose they agreed to, in line with the GDPR.

Security

Pricing

from PLN 79

per month, net, Business plan; developers from PLN 249

Full pricing

Try Fizen on your own data

We set up business accounts and API keys after a short conversation: tell us what you do and we reply within one business day. For yourself, you can start right away.