Consents

Manage user consents for accessing account information.

AIS consent management endpoints for accessing banking account information.

Overview

Account Information Services (AIS) allows authorized access to banking data including
accounts, balances, and transactions. Users must authorize access through their bank’s
Strong Customer Authentication (SCA) flow.

Consent Scope

When creating a consent, you can specify which types of data you want to access:

Note: Other scope combinations are not supported. If no scope is provided, full scope is assumed.

Consent Lifecycle

1. Create consent with desired scope (accounts, balances, or full)
2. User authorizes via bank’s SCA flow
3. Consent becomes active for data access
4. Use data endpoints to retrieve banking information
5. Refresh data as needed using background jobs

Consent Statuses

Understanding Expiration vs Revocation

There are two different time-based concepts for consents:

• Expired: The authorization link has timed out - only affects the ability to complete the SCA flow
• Revoked: The data access consent has been explicitly terminated via the /ais/consents/revoke API endpoint (manual/client-driven)
• Deactivated: The consent validity period has ended (authorized_until reached) - automatic/system-driven, no more access to banking data

Webhooks

Configure webhook_url when creating consents to receive notifications on status changes.

Webhook Payload:

{
  "type": "consent_status_update",
  "consent_id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "active"
}