# OB-PIS-006 — Execution information and status until the end

> As soon as it receives the order, the ASPSP gives the PISP at least the initiation and execution information the payer would see, then every update, status included, until the payment is executed or rejected.

- Article: PSR 37(3) (See also PSR 36(4)(f), PSR 40(b))
- Who is bound: ASPSP
- Who it is for: API, Product
- 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. 36(1)(b); PSD2, Art. 66(4)(b)

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: Partial

The PISP polls `GET /payment-requests/{id}`, with `nextStatusRequestHint` as a pacing hint. Nothing is pushed to the PISP apart from the redirect callback.

- <https://openfinanceguide.com/en/stet/1.6.3/endpoints/pisp/payment-requests-get>
- <https://openfinanceguide.com/en/stet/1.6.3/endpoints/pisp/payment-request-transactions-get>

## Sources

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

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