# AISP

> Account Information Service Provider

An authorised provider that reads your bank accounts — balances and transactions — with your consent. It views, it never initiates a payment.

_Category: acteur_

---

## Definition

An **AISP** (_Account Information Service Provider_) is an authorised provider that reads your bank accounts — balances and transactions — with your consent, in order to present them somewhere else.

It looks, it does not act: no payment or change is possible on your accounts.

## AISP vs PISP: don't confuse them

Two distinct PSD2 roles, often combined in a single app but with different authorisations:

- **AISP** — read-only: it consults your accounts to display, aggregate and analyse.
- **PISP** — payment initiation: it triggers a credit transfer from your account, without going through the card.

An AISP that also wants to trigger transfers must obtain the PISP authorisation separately.

## What an AISP can do

- Aggregate several accounts from several banks into a single view.
- Present history, balances and transaction categorisation.
- Refresh the data within the limits of consent (regular renewal required by the PSD2 RTS).

## What an AISP cannot do

- Initiate a payment from your account: that is the PISP's role.
- Access the data without the PSU's explicit consent, nor beyond the consented scope.
- Operate without an authorisation (in France, ACPR / PSP register) or without the technical safeguards — eIDAS certificates, mTLS — required by the banks.

## In the PSD2 ecosystem

The AISP is a TPP (third-party provider) just like the PISP or the CBPII, but with a scope strictly limited to reading. The PSU gives their consent, the ASPSP exposes the data through secure APIs, and the AISP connects to them within the regulated framework.

```mermaid
flowchart TB
    PSU["PSU — account holder"]
    ASPSP["ASPSP — bank holding the accounts"]

    subgraph TPP["TPP — authorised third-party provider"]
        direction TB
        AISP["AISP\n• Reads balances / transactions\n• Account information service (AIS)\n• Does not initiate payments"]
        PISP["PISP\n• Payment initiation — PIS\n• Does not replace the ASPSP on the flow of funds"]
        CBPII["CBPII\n• Limited info for card collection\n• No free access to history"]
    end

    PSU -->|"Consent"| AISP
    PSU -->|"Consent"| PISP
    PSU -->|"Consent"| CBPII

    AISP -->|"Account Information API (AIS)"| ASPSP
    PISP -->|"Payment Initiation API (PIS)"| ASPSP
    CBPII -->|"Dedicated regulated access"| ASPSP

    ASPSP -->|"Holds the accounts of the"| PSU
```

## Concrete examples

- **Individual — aggregation and budgeting**: Bankin', Linxo or Lydia connect to all your banks to show a unified budget, categorise spending and warn you of an overdraft. They read, they don't move the money.
- **Business — invoicing and accounting**: Pennylane, Qonto or Indy automatically retrieve the bank entries to reconcile them with invoices, feed the accounting and prepare VAT. No more manual CSV exports.
- **Lender — credit scoring**: Algoan or Bridge analyse the account history to assess creditworthiness in a few seconds, complementing (or replacing) payslips.

## Sources

- [Directive (EU) 2015/2366 on payment services in the internal market (PSD2)](https://eur-lex.europa.eu/legal-content/FR/TXT/?uri=CELEX:32015L2366) — EUR-Lex, 2015-11-25
- [Register of payment institutions and account information service providers — REGAFI](https://www.regafi.fr/) — ACPR / Banque de France

---

Source: https://openfinanceguide.com/en/glossary/aisp