# AISP Account Information Service Provider.

Consent is given using the OAuth2 as a pre-step authentication flow described in PSD2 specifications. This means you don't have to manage consents using the dedicated endpoints (which are not implemented), but only to redirect the PSU to our authorisation page (using AISP as OAuth2 scope). After performing a strong customer authentication, the PSU will be redirected to your redirect URI with an authorisation code that you can then exchange for an access token.

This access token will let you authenticate at the XS2A interface to request the PSU accounts balances and transactions history. ## Operations - [Retrieval of the PSU accounts](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-list.md) - [Retrieval of an account balances report](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-list_balances.md) - [Retrieval of an account overdraft](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-get_overdraft.md) - [Retrieval of an account owners](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-list_owners.md) - [Retrieval of an account transaction set](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-list_transactions.md) - [Retrieval of transaction details](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-list_transaction_details.md) - [Forwarding the PSU consent](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-update_consents.md) - [Retrieval of the identity of the end-user](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-get_identity.md) - [Retrieval of the trusted beneficiaries list](https://docs.iban.nash.io/operation/operation-openbankingweb-aispcontroller-list_beneficiaries.md) [Powered by Bump.sh](https://bump.sh)