What Is an ASPSP? PSD2 Open Banking Roles 2026 — ASPSP, AISP, PISP Explained

ASPSP, AISP and PISP explained: who holds your account, who reads it, who pays from it under PSD2. Licences (no capital for AISPs, 50,000 EUR for PISPs), the 180-day SCA rule, the API fallback test, and where PSD3/PSR and FIDA stand in October 2026.

Fact-checked against primary sources on · figures re-verified on regulator, issuer or SEC filings — not copied from other sites

Which PSD2 role is this, and what must it hold?

Pick what you want to do with someone else’s payment account. The answer names the role, the regime, the figure and the article each one comes from — every sentence quoted from the directive, not summarised.

The role

What you are doing makes you AISP — account information service provider. The directive defines it in Article 4(19).

The regime

A registration, not an authorisation. Article 33(1) exempts a person providing only this service from the procedure and conditions of Sections 1 and 2, keeping only a named list.

Initial capital

None. Article 7 is in Section 1 and is not among the exceptions Article 33(1) lists, so the initial-capital requirement does not reach you. The directive says this by omission — it never writes it as a sentence, and this line is our reading of the exception list, not a quotation.

Professional indemnity insurance

Required, as a condition of the registration itself, under Article 5(3). The directive sets no minimum amount anywhere: Article 5(4) hands the figure to EBA guidelines, so this tool does not state one.

Does the right exist for this account?

Yes — the account is reachable online, which is what Article 67(1) requires. Nobody searches for this condition, and it is in three separate provisions.

Article 33(1) applies to a person providing only the payment service of point (8) of Annex I, so it is a registration rather than an authorisation.

What the usual question gets wrong

Reading account data and initiating a payment are asked about as one question and answered in two regimes. Reading data: registration, initial capital EUR 0, Article 33(1). Initiating a payment: authorisation, initial capital EUR 50 000, Article 11(1). The only requirement they share is the professional indemnity insurance — and even that is a different paragraph for each, Article 5(3) against Article 5(2).

What the bank may and may not require

It may not require a contract with you. Article 66(5): “The provision of payment initiation services shall not be dependent on the existence of a contractual relationship between the payment initiation service providers and the account servicing payment service providers for that purpose.”

When the bank may refuse

Not in Article 66 or 67, where readers look for it, but in Article 68(5): “An account servicing payment service provider may deny an account information service provider or a payment initiation service provider access to a payment account for objectively justified and duly evidenced reasons relating to unauthorised or fraudulent access to the payment account by that account information service provider or that payment initiation service provider, including the unauthorised or fraudulent initiation of a payment transaction.”

One phrase that is not in the rulebook

Neither instrument says an account servicing provider must give you API access free of charge. “at no charge” occurs exactly once in the whole technical standard, Article 30(3), and it is about the interface documentation: “Account servicing payment service providers shall at a minimum, and no less than 6 months before the application date referred to in Article 38(2), or before the target date for the market launch of the access interface when the launch takes place after the date referred to in Article 38(2), make the documentation available, at no charge, upon request by authorised payment initiation service providers, account information service providers and payment service providers issuing card-based payment instruments or payment service providers that have applied to their competent authorities for the relevant authorisation, and shall make a summary of the documentation publicly available on their website.” The no-fee rule the market applies is read out of the absence of a charging provision together with Article 66(5). That is a reading, not a sentence.

Where a licence claim is checkable

Article 14(2) and the EBA central register of Article 15(1). A claim that a firm holds one of these permissions is either in a register or it is nothing.

Article 4(17)

‘account servicing payment service provider’ means a payment service provider providing and maintaining a payment account for a payer; ‘payment initiation service provider’ means a payment service provider pursuing business activities as referred to in point (7) of Annex I; ‘account information service provider’ means a payment service provider pursuing business activities as referred to in point (8) of Annex I;

What this tool will not tell you: the minimum amount of the professional indemnity insurance — Article 5(4) hands the figure to EBA guidelines addressed to competent authorities. The directive itself states no amount, so neither does this tool. your national competent authority’s own forms, fees and timelines — Article 11 is addressed to Member States, and each one transposed it into its own procedure. The figures here are the directive’s floor, not any one regulator’s application pack. PSD3 and the Payment Services Regulation — They are proposals under negotiation, not law in force. 26 of the 350 queries on this page already ask about them; nothing in this tool is read from a text that has not been published in the Official Journal. when strong customer authentication may be skipped — The exemptions are Articles 10 to 18 of Delegated Regulation 2018/389 — low value, contactless, trusted beneficiaries, transaction risk analysis — and each carries its own thresholds. That is a second resolver, and 10 queries on this page ask for it. It is not answered here. whether a named firm actually holds a licence — That is what the registers are for: the national register of Article 14 and the EBA central register of Article 15. A claim about one firm has to be read there, not here. legal advice — Every figure and sentence here is quoted from the published text with its article number so it can be checked. Applying it to a real business is a lawyer’s job, not a web page’s.

Read from the publisher: 32015L2366 · 32018R0389 — Both texts were read from the EU Publications Office, which publishes the Official Journal, over content negotiation on the CELEX identifier.

Provisions read 2026-10-30. A quoted article does not go stale on its own — it is either still the text or it was amended, and an amendment changes the CELEX.

See your own accounts in one place

PSD2 & Open Banking in the EU (2026): ASPSP, AISP and PISP Explained for Personal Finance Apps

Quick Answer

ASPSP (Account Servicing Payment Service Provider) is the bank or payment institution that holds your payment account. AISP (Account Information Service Provider) reads that account with your consent. PISP (Payment Initiation Service Provider) starts a payment from it on your behalf. Under PSD2 the ASPSP must give licensed AISPs and PISPs access through a secure interface, and you authenticate in your own bank, so the third party never sees your password.

PSD2 is the EU directive (2015/2366) that since 14 September 2019 has obliged every bank in the EEA to expose secure APIs so that licensed third-party providers can — with your explicit consent — read your account data and initiate payments on your behalf. It is supervised by the European Banking Authority (EBA) together with national competent authorities such as BaFin (Germany), ACPR (France), Bank of Italy, Banco de España, DNB (Netherlands) and KNF (Poland). For you as a user it means: multi-bank aggregation in personal finance apps, two-factor login (Strong Customer Authentication / SCA) and SCA on remote card payments above 30 EUR. The successor rules (PSR and PSD3) were agreed politically on 27 November 2025 but, as of October 2026, are not yet formally adopted.

Educational content, not legal or regulatory advice. PSD2 and PSD3 are evolving; verify current state with your national competent authority.

What changed: pre-PSD2 vs PSD2 vs PSD3

Before PSD2 (pre-2018): banks held a monopoly on your transaction data. The only way to feed a budgeting app was screen-scraping — handing the app your online-banking password and letting it log in as you. This violated most bank terms of service, exposed credentials, and broke whenever the bank changed its login page. Card payments online required only a static CVV and, optionally, a clumsy first-generation 3-D Secure SMS.

Under PSD2 (2018–2026): every "Account Servicing Payment Service Provider" (ASPSP — almost every retail bank in the EEA) must publish a free, documented production API for account information and payment initiation, in parallel with its customer interface. Two new licensed roles are created: AISP (Account Information Service Provider) reading data and PISP (Payment Initiation Service Provider) pushing payments. Screen-scraping is permitted only with a fallback mechanism if the bank's API is unavailable, and only by licensed firms.

Toward PSD3 (proposed June 2023, not yet adopted): the European Commission's package splits PSD2 into a directly applicable Payment Services Regulation (PSR) plus a directive (PSD3) on licensing and supervision. Parliament and Council reached a provisional agreement on 27 November 2025; Parliament's ECON committee approved the agreed text on 5 May 2026, and the plenary vote is scheduled for December 2026. The separate Financial Data Access (FIDA) regulation, which would extend data sharing beyond payment accounts, is still in negotiation.

Stakeholders: who is who in the open-banking chain

  • ASPSP (Account Servicing Payment Service Provider) — defined in Art. 4(17) as “a payment service provider providing and maintaining a payment account for a payer”. Your bank: ING, BNP Paribas, mBank, Santander, Revolut, N26, Monzo, etc. Obliged to expose the API.
  • AISP (Account Information Service Provider) — Art. 4(19): a provider pursuing the activity of point (8) of Annex I. A regulated firm that reads your accounts after you consent, under the right in Art. 67. Examples: Tink (Visa), TrueLayer, Yapily, Salt Edge, Finicity (Mastercard), Nordigen / GoCardless Bank Account Data, Klarna Kosma. Many personal finance apps operate as AISPs themselves or connect through such an aggregator.
  • PISP (Payment Initiation Service Provider) — Art. 4(18): a provider pursuing the activity of point (7) of Annex I. A regulated firm that pushes "pay by bank" credit transfers on your behalf, under the right in Art. 66. Examples: Trustly, Volt, Token, GoCardless.
  • PIISP / CBPII (Card-Based Payment Instrument Issuer) — a third party that issues a card and needs to query an account balance before authorising a transaction, under Art. 65. Rarer in personal finance. The directive never uses the acronym: Art. 65 calls it “a payment service provider issuing card-based payment instruments”, and CBPII is the market's shorthand.
  • You, the Payment Service User (PSU) — you give the consent; for account information your bank must ask for SCA again at least every 180 days.

The directive itself is Directive (EU) 2015/2366 of 25 November 2015, supplemented by the Regulatory Technical Standards (RTS) on SCA and common, secure open standards of communication — Commission Delegated Regulation (EU) 2018/389, applicable from 14 September 2019. Each EEA Member State transposed PSD2 into national law:

  • Germany: Zahlungsdiensteaufsichtsgesetz (ZAG), supervised by BaFin
  • France: Ordonnance n° 2017-1252, supervised by ACPR (Banque de France)
  • Italy: D.lgs. 218/2017, supervised by Bank of Italy
  • Spain: Real Decreto-ley 19/2018, supervised by Banco de España
  • Netherlands: Wet op het financieel toezicht (Wft) amendment, supervised by DNB
  • Poland: Ustawa o usługach płatniczych (PSD2 amendment 2018), supervised by KNF
  • Ireland: European Union (Payment Services) Regulations 2018, supervised by the Central Bank of Ireland

The UK transposed PSD2 via the Payment Services Regulations 2017 but, since Brexit, has diverged — its parallel open-banking framework is supervised by the FCA.

The condition nobody searches for: the account has to be online

Of 350 distinct search queries that reached this page in a nine-week window, not one named the condition that decides whether the right exists at all. Three separate provisions carry it, one per service:

What the third party wants Provision The condition
Initiate a payment Art. 66(1) “The right to make use of a payment initiation service provider shall not apply where the payment account is not accessible online.”
Read account information Art. 67(1) “That right shall not apply where the payment account is not accessible online.”
Confirm funds for a card payment Art. 65(1)(a) “the payment account of the payer is accessible online at the time of the request”

No licence creates the right where the account is not reachable online: the condition is about the account, not about the provider. It is why a passbook savings account or a product with no online channel simply falls outside open banking, and why the answer to “can this app see my account” sometimes has nothing to do with the app.

Where the bank may refuse is a different article again. Readers look for it in Art. 66 and Art. 67. It is Art. 68(5), inside the article about limits on the use of a payment instrument: an ASPSP “may deny an account information service provider or a payment initiation service provider access to a payment account for objectively justified and duly evidenced reasons relating to unauthorised or fraudulent access to the payment account”. The bank must then tell the payer and report the incident to its competent authority.

Does PSD2 say the API is free?

Not in those words. Neither the directive nor the RTS contains the words “free of charge” in connection with giving a third party access to an account. The phrase “at no charge” occurs exactly once in the whole of Delegated Regulation (EU) 2018/389, in RTS Art. 30(3), and it is about the interface documentation, not the access:

make the documentation available, at no charge, upon request by authorised payment initiation service providers, account information service providers and payment service providers issuing card-based payment instruments

The no-fee rule the market applies is read out of two things together: there is no charging provision anywhere in PSD2 for this access, and Art. 66(5) forbids making payment initiation depend on a contract with the ASPSP — and without a contract there is nothing to price. That is a sound reading. It is still a reading, not a sentence you can quote, and a reader who goes looking for the sentence will not find it.

API technical standards: not one but four (or five)

PSD2 deliberately did not mandate a single API specification, only common security and functional requirements. Four industry standards emerged:

  1. Berlin Group NextGenPSD2 — by far the most widely adopted, in DACH, Benelux, CEE and Nordics. Also offers an openFinance API extension.
  2. STET PSD2 API — French market, used by BNP Paribas, Société Générale, Crédit Agricole, BPCE.
  3. PolishAPI — Polish standard developed by the banking sector, used by most Polish banks; covers AIS, PIS and CAF endpoints.
  4. Open Banking UK (OBIE) Read/Write API — UK-only, technically the most mature; not part of PSD2 strictly but rooted in the CMA9 order.
  5. Bank-specific dialects — many large banks add proprietary endpoints on top of Berlin Group for richer data (categorisation, beneficiary enrichment).

This fragmentation is why third-party aggregators exist: a single Tink / TrueLayer / Yapily / Salt Edge integration abstracts hundreds of bank-specific quirks behind one developer-friendly API.

Made your pick? See how it fits the rest of your money — accounts, cards and investments in one view.

See your Freedom Runway — free

AISP / PISP licensing — what it takes

The tool above answers this for one case at a time. It takes three inputs: what you want to do with someone else's payment account, what you are today — nothing yet, a bank, an authorised payment institution, a registered account information provider — and whether the account you want to reach is accessible online. It returns the role, the regime, the initial-capital figure and the article each one comes from. The middle input is the one that changes the answer most and the one nobody types: a bank needs none of this, because Art. 1(1)(a) already makes it a payment service provider by status.

To become a licensed AISP or PISP in the EU you go through your national competent authority (KNF in Poland, BaFin in Germany, Bank of Italy in Italy). Headline requirements:

  • Initial capital: Art. 7(b) sets 50,000 EUR for a payment institution providing the service of point (7) of Annex I — payment initiation; Art. 7(c) sets 125,000 EUR for the services of points (1) to (5), such as executing transfers or issuing cards; a separate regime sets 350,000 EUR for an e-money institution. An AIS-only firm needs no initial capital. The directive never writes that sentence: Art. 33(1) exempts a person providing only point (8) from Sections 1 and 2 “with the exception of” a closed list, and Art. 7 is not on that list. It must still hold professional indemnity insurance or a comparable guarantee.
  • Professional indemnity insurance — and it is a different paragraph for each role: Art. 5(2) attaches it to an application for authorisation to do payment initiation and covers liability under Arts. 73, 89, 90 and 92; Art. 5(3) attaches it to an application for registration for account information and covers liability for unauthorised access to account data. The amount is nowhere in the directive — Art. 5(4) hands the figure to EBA guidelines, which is why it arrives as EBA/GL/2017/08, calculated on risk profile and volume rather than as a number in the law.
  • Fit and proper check — for all directors and qualifying shareholders.
  • Operational & security framework — incident reporting, business continuity, ICT risk management under DORA (Digital Operational Resilience Act, applicable since 17 January 2025).
  • Governance — three-line-of-defence model, outsourcing register.
  • EEA passport: once authorised in one Member State, the licence can be "passported" to every other EEA country via notification (typically 1–3 months).

Everyone else obtains authorisation as a payment institution under Art. 11(1), which requires it before the service is provided and grants it only to a legal person established in a Member State. An AIS-only provider is registered rather than authorised (Art. 33(1)) and can still passport its service. Small payment institutions can be exempted nationally under Art. 32, but those cannot passport.

Doing both is not the cheaper of the two. Art. 33(1) reaches a person providing only point (8). Add payment initiation and the exemption stops applying, so the answer becomes the Art. 11 authorisation with the Art. 7(b) figure — which is why “what licences do payment initiation and account information service providers need” has no single answer, and the two halves of that question sit in different regimes.

Where a licence claim is checkable.

Art. 14(2) requires every Member State to keep a public register that names the services each firm is authorised or registered for, lists authorised institutions separately from Art. 32/33 exemptions, and is “publicly available for consultation, accessible online, and updated without delay”. On top of that, Art. 15(1) puts EBA in charge of a central electronic register fed by the national authorities — the EBA register of payment and electronic money institutions. A claim that a firm is a licensed AISP or PISP is either in one of those registers or it is nothing; no amount of website copy substitutes for the entry.

SCA: Strong Customer Authentication, the user-facing part of PSD2

Whenever you log in to online banking, initiate a payment, or consent to an AISP reading your accounts, the bank must authenticate you with at least two of the following three independent factors:

  • Knowledge — something you know: password, PIN, response to a secret question
  • Possession — something you have: registered phone with a banking app, hardware token, registered SIM for SMS
  • Inherence — something you are: fingerprint, Face ID, voice

Hence the proliferation of bank push-notifications: a tap in the mobile app is the "possession" factor, your biometric is "inherence", and the two together satisfy SCA.

PSD2 RTS recognise several exemptions so SCA is not required on every single action:

  • Low-value payments — single transactions up to 30 EUR (with cumulative caps: 100 EUR or 5 consecutive transactions before SCA is forced)
  • Recurring transactions — subscriptions of the same amount to the same beneficiary, SCA only on the first
  • Trusted beneficiaries — once you "whitelist" a payee with SCA, future payments to that payee can skip it
  • Transaction Risk Analysis (TRA) — payment service providers with low fraud rates (e.g. <0.13 % at the 100 EUR band, <0.06 % at 250 EUR, <0.01 % at 500 EUR) may exempt transactions case-by-case
  • Corporate payments through secure dedicated protocols
  • Account information — the bank must not demand SCA for balance and last-90-days data accessed through an AISP, except on first access and when more than 180 days have passed since the last SCA (Article 10a, added by Delegated Regulation (EU) 2022/2360; the old rule was 90 days)

Liability shift: the user-protective backbone

Under PSD2, if an unauthorised payment leaves your account, the bank must refund it immediately and at the latest by the end of the next business day (Art. 73), unless it has reasonable grounds to suspect fraud and reports them to the authority. Your own loss from a lost or stolen payment instrument is capped at 50 EUR, unless you acted fraudulently or with gross negligence (Art. 74). If a PISP initiated the payment, you still claim the refund from your bank, which can then recover it from the PISP. AISPs move no money, so they carry no payment liability, but they are data controllers under GDPR.

PSD3, PSR and FIDA — where the reform stands (October 2026)

File What it does Status
Payment Services Regulation (PSR) Directly applicable rules replacing most of PSD2: SCA, open-banking access, fraud and refunds Provisional agreement 27.11.2025; ECON approved the text 5.05.2026; plenary vote scheduled for December 2026
PSD3 Licensing and supervision of payment institutions; e-money institutions folded into the same regime Agreed together with the PSR, same timetable
FIDA (Financial Data Access) Data sharing beyond payment accounts: savings, investments, pensions, insurance, loans Still in negotiation; no agreement

Until the PSR applies, PSD2 and the RTS above stay in force. After publication in the Official Journal, the new rules apply only after a transition period, so PSD2 governs open banking well into 2027 at least. Commentary from law firms on the agreed text points to stricter fraud rules (name-and-IBAN verification for all credit transfers, refunds for some bank-impersonation scams) and a dashboard where users see and withdraw the access they gave to AISPs; check the text published in the Official Journal before relying on any detail.

Worked example: three accounts in one app

Anna lives in Warsaw and has three payment accounts: a PLN current account at a Polish bank, a EUR account at a neobank and a German current account. She connects all three to an AISP-based app. What it can read:

  • Balances and transactions of each payment account, with a fresh SCA in each bank's app at least every 180 days.
  • Up to 4 automatic refreshes a day per account when she isn't using the app (more when she opens it).

What is NOT covered by PSD2: investment and pension accounts, mortgages and insurance (outside the payment-account scope; FIDA would cover them if adopted), and anything she did not consent to share. Older transactions than the last 90 days may need an extra SCA, depending on the bank.

Polish reader angle: PolishAPI and KNF

Poland developed its own API standard, PolishAPI, created by the banking sector with the Polish Bank Association (ZBP). It covers account information (AIS), payment initiation (PIS) and confirmation of funds (CAF), and is used by most Polish banks, though PSD2 itself does not require any particular standard.

A Polish firm that wants to be an AISP registers with the KNF. The core requirements are the ones above: professional indemnity insurance, fit-and-proper management, a security and ICT risk framework (DORA) and complaint handling. A registered AISP can then passport to other EEA countries.

FAQ

What is an ASPSP?

An Account Servicing Payment Service Provider: the bank, e-money institution or payment institution that provides and maintains your payment account. Under PSD2 it must let licensed AISPs and PISPs access that account when you consent, through a dedicated interface (API) or its customer interface.

What is a PISP?

A Payment Initiation Service Provider: a licensed firm that starts a credit transfer from your bank account at your request, for example "pay by bank" at checkout. You confirm the payment with SCA in your bank; the PISP never holds your money. It needs at least 50,000 EUR of initial capital.

What licences do AISPs and PISPs need under PSD2?

An AIS-only provider is registered with its national authority (Art. 33 PSD2) and needs professional indemnity insurance but no initial capital. A PISP needs authorisation as a payment institution, 50,000 EUR initial capital and indemnity insurance. Both can passport across the EEA.

How does PSD2 affect open banking?

It made open banking a legal obligation in the EEA: banks must open payment accounts to licensed third parties with your consent, authentication happens at the bank (SCA), and screen-scraping with shared passwords is replaced by tokens issued through the bank's interface.

Is open banking safe?

Yes. Banks never share your password with the AISP; authentication happens in the bank's own SCA flow, and the AISP only receives a time-bounded access token. The AISP itself is licensed, regulated and supervised by a national authority and must hold professional indemnity insurance.

Yes, at any time, in two places: inside the AISP/PISP app (which should expose a "disconnect bank" button) and inside your bank's online or mobile banking under "Connected services" / "Third-party access". Either action terminates data access immediately.

Why does my bank ask SCA so often?

Because the RTS require SCA at login, end the session after 5 minutes of inactivity, and require SCA for remote payments above 30 EUR unless an exemption applies. For AISP connections the bank asks again after 180 days.

Why don't UK banks work in EU apps?

Because the UK left the EEA, UK banks are no longer under PSD2 obligations toward EU AISPs. Some aggregators bridge the two regimes via separate FCA permissions, but coverage is not automatic.

Do I pay for open banking?

Not for the regulated access. PSD2 does not let the bank make AISP or PISP access depend on a contract with the third party, and the bank must treat their requests without discrimination against its own channels. The app itself may charge for its service.

Can the bank require a contract with the AISP or PISP first?

No. Art. 66(5) is one sentence long: “The provision of payment initiation services shall not be dependent on the existence of a contractual relationship between the payment initiation service providers and the account servicing payment service providers for that purpose.” What the bank may do is refuse a specific provider under Art. 68(5), for “objectively justified and duly evidenced reasons relating to unauthorised or fraudulent access” — and it must then tell you and report the incident to its competent authority.

Can my bank charge an AISP for API access?

PSD2 and the RTS nowhere say this access is free of charge. The only “at no charge” in the RTS is Art. 30(3), about the interface documentation. The reason no bank in the EEA prices third-party access is indirect: there is no provision letting it charge, and Art. 66(5) means there is no contract to price. A sound reading, but not a sentence to quote.

How do I check that a provider really holds the licence?

In a register, not on the provider's website. Art. 14(2) requires each Member State to keep a public, online register naming the services each firm is authorised or registered for; Art. 15(1) puts EBA in charge of a central register fed by the national authorities, which is searchable at euclid.eba.europa.eu. An AIS-only firm appears as registered, separately from authorised institutions — that is Art. 14(2) again, and it is how you tell a registration from an authorisation without asking anybody.

What if my bank's API is down?

The interface counts as unavailable when five consecutive requests get no reply within 30 seconds. The bank must then, unless its national authority exempted it, let licensed AISPs and PISPs use the customer-facing interface as a fallback. Your connection may still fail for a while; the app should show it.

Track your money without sharing bank logins

Freenance works from bank statement CSV exports (mBank, ING, PKO BP and more) plus XTB, Binance and Bybit, and shows your Financial Freedom Runway, the number of months your savings would last.

Sources

  • Directive (EU) 2015/2366 (PSD2) — read 2026-10-30 from the EU Publications Office
  • Commission Delegated Regulation (EU) 2018/389 (RTS on SCA), as amended by Delegated Regulation (EU) 2022/2360 (Article 10a, 180 days) — read 2026-10-30
  • EBA register of payment and electronic money institutions (Art. 15(1))
  • European Commission proposals COM(2023)366 and COM(2023)367 (PSD3 / PSR)
  • European Parliament Legislative Observatory, procedures 2023/0210(COD) (PSR) and 2023/0205(COD) (FIDA), checked 26.10.2026
  • Council of the EU documents on the payment services package (provisional agreement 27.11.2025, Coreper 22.04.2026)
  • Directive 2009/110/EC (EMD2), Art. 4: 350,000 EUR initial capital for e-money institutions
  • EBA Guidelines EBA/GL/2017/08 (professional indemnity)
  • DORA — Regulation (EU) 2022/2554
  • Berlin Group NextGenPSD2 framework
  • STET PSD2 API specification
  • PolishAPI standard (Polish Banking Association)
  • OBIE Read/Write API specification (UK)
  • National competent authorities: BaFin, ACPR, Bank of Italy, Banco de España, DNB, KNF, Central Bank of Ireland
Free 14-day trial

Compared the options?See how they fit your money.

Freenance pulls your accounts, cards, investments and crypto into one view — so the moment you choose a bank or broker, you see the whole picture and your Financial Freedom Runway. Demo data is seeded on signup, so you can explore before importing anything.

Start free — no card
14 days free
No credit card
Exchange keys AES-GCM-encrypted