# OB-IF-017 — TPP identification towards the ASPSP

> The interface lets AISPs and PISPs identify themselves towards the ASPSP, and they do so at every payment initiation for the PISP and at every session for the AISP.

- Article: PSR 36(2)(a) (See also PSR 46(1)(f), PSR 47(1)(c))
- Who is bound: ASPSP, AISP, PISP
- Who it is for: API, Operations, Audit and pentest
- Application: 21 months after entry into force, the general application date (Article 112).
- Level 2: RTS under Article PSR 89(1)(e), draft due at T + 12 months.
- Origin: RTS 2018/389, Art. 30(1)(a), 34; PSD2, Art. 66(3)(d), 67(2)(c)

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

STET identifies the TPP with an eIDAS QWAC over mTLS and checks that the `client_id` matches the authorisation number in the certificate. The PSR does not say how the TPP identifies itself.

- <https://openfinanceguide.com/en/stet/1.6.3/framework/3-prerequisites-and-technical-details>

## Sources

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

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