Account information

NextGenPSD2 XS2A Framework

Account access with redirect SCA

The canonical AIS journey: create a consent, hand the PSU to the bank for authentication, then read data until the consent expires.

Why read this

Every account aggregator starts here. Most integration failures are in steps 2 and 5 — the redirect contract and the moment the consent flips to valid.

Try editor — open message samples →

Try in live showcase

Messages · camt.052

aisconsentredirectberlin group

Transaction flow

PSUUserTPPProviderASPSPBankSCAAuth01 Pick a bank, agree to share0102 Create the consent resource02 POST03 consentId + scaRedirect link0304 Authenticate at the bank0405 Poll until the consent is valid05 GET06 List accounts06 GET07 Read transactions07 camt.052
PSU: UserTPP: ProviderASPSP: BankSCA: Auth
API hop Clearing hopClick a tag on an arrow (pacs.008, …) for info, usage and sample
Messages
01

Pick a bank, agree to share

API layer

The TPP shows which data it wants and for how long. This screen is the legal basis for the access field you are about to send — keep them in sync or you will fail an audit.

psutpp

No payload

This step is a redirect, a wait or an out-of-band event — there is no message on the wire to inspect. Steps with a payload are marked with a method or a message id in the diagram.

See this step in live →