---
id: ext-account-information-access
title: "Account Information Access"
description: "Request consented access to a customer's payment account information using an SCA Attestation presented from their EUDI Wallet."
hide_title: false
sidebar_label: Account Information Access
keywords: [Account Information Access, AIS, AISP, PSD2, SCA, EUDI Wallet, TS12, Organisation Wallet, European Business Wallet, open banking]
slug: /extensions/account-information-access
---

> **Build this with an AI coding agent.** Install the iGrant.io Agent Skills, then ask your agent to build the integration:
>
> ```bash
> npx skills add L3-iGrant/skills
> ```


import NoteBox from '@site/src/components/NoteBox';
import ApiEndpoints from '@site/src/components/ApiEndpoint';

The Account Information Access extension enables an Account Information Service Provider (AISP) to request consented access to a customer's payment account information using an SCA Attestation presented from their EUDI Wallet. The flow follows the [TS12 Electronic Payments SCA Implementation with Wallet](https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts12-electronic-payments-SCA-implementation-with-wallet.md) specification.

## How it works

1. The organisation enables the Account Information Access extension from the dashboard.
2. An administrator configures the service description shown to the customer and the account attributes to request (e.g. IBAN, BIC, currency).
3. When a customer needs to grant account access, a verification request with an `urn:eudi:sca:account_access:1` transaction data payload is triggered using the configured presentation definition.
4. The customer reviews the service, AISP identifier and scope of access, and presents an SCA Attestation from their EUDI Wallet.
5. The system verifies the presentation, its Key Binding JWT and the dynamic link to the transaction, and completes the account access consent.

## Configuration

### Account access request

Configure the account attributes the AISP requests from the customer's Payment Account Credential:

| Attribute | Description |
|---|---|
| `iban` | International Bank Account Number |
| `bic` | Bank Identifier Code |
| `currency` | Account currency |

### Transaction data

The verification request includes an `urn:eudi:sca:account_access:1` transaction data object describing the AISP, what is being requested, and the service description shown to the customer:

| Field | Type | Description |
|---|---|---|
| `transaction_id` | String | Unique identifier for the account access transaction |
| `date_time` | DateTime | Timestamp of the access request |
| `aisp` | Object | The Account Information Service Provider requesting access |
| `├─ legal_name` | String | Legal name of the AISP |
| `├─ brand_name` | String | Brand name of the AISP |
| `└─ domain_name` | String | Domain of the AISP |
| `description` | String | Human-readable service description shown to the customer |

### Integration

Once configured, the system automatically generates an SCA Attestation **Presentation Definition** bound to the `urn:eudi:sca:account_access:1` transaction data type. This presentation definition can be viewed from the extension configuration page and is used when initiating account access requests via the API.

**API endpoints:**

<ApiEndpoints endpoints={[
  { method: 'get', path: '/v3/config/extension/account-information-access', description: 'Retrieve current configuration' },
]} />

<NoteBox title="Caution:" variant="caution">
Disabling the Account Information Access extension deletes its configuration. This action is not reversible.
</NoteBox>