Clearing & settlement

NextGenPSD2 XS2A Framework

Verification of Payee

Name-and-IBAN matching before a transfer leaves. Mandatory across the euro area since the Instant Payments Regulation deadline in October 2025.

Why read this

A pre-flight check that changes PISP UX: the PSU may have to confirm a mismatch, which means your initiation screen needs a state it did not need before.

Try editor — open message samples →

Try in live showcase

Messages · acmt.023 → acmt.024

vopconfirmation of payeeacmt.023fraud

Transaction flow

TPPProviderASPSPBankCreditorBank01 Payee name and IBAN captured0102 acmt.023 verification request02 acmt.02303 acmt.024 report03 acmt.02404 Result surfaced to the PSU04
TPP: ProviderASPSP: BankCreditor: Bank
API hop Clearing hopClick a tag on an arrow (pacs.008, …) for info, usage and sample
Messages
01

Payee name and IBAN captured

API layer

The name you send for verification must be the one the PSU typed, not a normalised or cached version.

tppaspsp

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 →