# OB-OBS-012 — Two SCAs in a payment-initiation-only journey

> When the PISP sends all the information needed, the ASPSP may not require one SCA for the funds confirmation and a second one for the initiation.

- Article: PSR 44(1)(l)
- Who is bound: ASPSP
- Who it is for: Product, API, Audit and pentest
- Application: 21 months after entry into force, the general application date (Article 112).
- Level 2: No EBA mandate covers this obligation.
- Origin: RTS 2018/389, Art. 32(3); EBA Opinion of 4 June 2020 on obstacles

Provisional numbering of the April 2026 compromise (Council doc. 8221/26). The final numbering will be added when the Official Journal publishes the text, without changing the id.

## STET 1.6.3: Covered

A payment request is confirmed with a single authentication, and the PISP has no separate funds confirmation call.

- <https://openfinanceguide.com/en/stet/1.6.3/endpoints/pisp/payment-request-confirmation-post>
- <https://openfinanceguide.com/en/stet/1.6.3/flows/8-2-payment-request-with-multiple-instructions-having-different-beneficiaries>

## Sources

- [Council doc. 8221/26, page 264](https://data.consilium.europa.eu/doc/document/ST-8221-2026-INIT/en/pdf#page=264)

Checked on 2026-10-04. https://openfinanceguide.com/en/dsp3/obligations/ob-obs-012