Funds confirmation

NextGenPSD2 XS2A Framework

Funds confirmation (PIIS)

One call, one boolean. No amount, no balance, no history.

Why read this

Card issuers checking coverage before authorising. The narrowest scope in PSD2 and the easiest to get approved.

Samples in this flow

Try in live showcase

piiscbpiifundsberlin group

Transaction flow

TPPProviderASPSPBank01 Ask whether funds are available01 POST02 fundsAvailable: true | false02
TPP: ProviderASPSP: Bank
API hop Clearing hopClick a tag on an arrow (pacs.008, …) for info, usage and sample
01

Ask whether funds are available

API layer

POST/v1/funds-confirmations→ 200

Requires a PIIS consent established outside the API — usually at card issuance. The cardNumber is optional but most banks want it for matching.

Codes you can see here

tppaspsp

API payload· XML

Funds confirmation request

The response is {"fundsAvailable": true} and nothing else. Data minimisation is enforced by the RTS, not by preference.

<payload>
<cardNumber>525412******3241</cardNumber>
<account>
<iban>FR7630006000011234567890189</iban>
</account>
<payee>Librairie Gallimard</payee>
<instructedAmount>
<currency>EUR</currency>
<amount>84.90</amount>
</instructedAmount>
</payload>
8 elementsdepth 2309 charsxml

Try it

Mock ASPSP

Substitute your own ids in the path — the mock resolves any UUID-shaped consentId and advances the SCA state machine on each call, so polling behaves the way a real ASPSP does.