OB-IF-017PSR 36(2)(a)Dedicated interface

TPP identification towards the ASPSP

What the text fixes

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)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.
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.The mandate names this article.
Origin: RTS 2018/389, Art. 30(1)(a), 34; PSD2, Art. 66(3)(d), 67(2)(c)

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.

Handbook pages

3. Prerequisites and technical details

Sources

Checked on October 4, 2026

The entry as JSON

{
  "id": "OB-IF-017",
  "article": "PSR 36(2)(a)",
  "alsoIn": [
    "PSR 46(1)(f)",
    "PSR 47(1)(c)"
  ],
  "articleFinal": null,
  "actors": [
    "aspsp",
    "aisp",
    "pisp"
  ],
  "roles": [
    "api",
    "infra",
    "pentest"
  ],
  "appliesAt": "T+21",
  "title": {
    "fr": "Identification du TPP auprès de l'ASPSP",
    "en": "TPP identification towards the ASPSP",
    "es": "Identificación del TPP ante el ASPSP",
    "pt-br": "Identificação do TPP perante o ASPSP"
  },
  "level1": {
    "fr": "L'interface permet aux AISP et aux PISP de s'identifier auprès de l'ASPSP, et ils le font à chaque initiation de paiement pour le PISP et à chaque session pour l'AISP.",
    "en": "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.",
    "es": "La interfaz permite a los AISP y a los PISP identificarse ante el ASPSP, y lo hacen en cada iniciación de pago en el caso del PISP y en cada sesión en el del AISP.",
    "pt-br": "A interface permite que AISPs e PISPs se identifiquem perante o ASPSP, e eles o fazem a cada iniciação de pagamento, no caso do PISP, e a cada sessão, no caso do AISP."
  },
  "level2": {
    "mandate": "PSR 89(1)(e)",
    "instrument": "rts",
    "deadline": "T+12",
    "link": "named"
  },
  "origin": [
    {
      "act": "rts-2018-389",
      "articles": "30(1)(a), 34"
    },
    {
      "act": "psd2",
      "articles": "66(3)(d), 67(2)(c)"
    }
  ],
  "stet": {
    "1.6.3": {
      "status": "present",
      "note": {
        "fr": "STET identifie le TPP par un certificat eIDAS QWAC en mTLS et contrôle que le `client_id` correspond au numéro d'agrément du certificat. Le PSR ne dit pas par quel moyen le TPP s'identifie.",
        "en": "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.",
        "es": "STET identifica al TPP con un certificado eIDAS QWAC en mTLS y comprueba que el `client_id` corresponde al número de autorización del certificado. El PSR no dice por qué medio se identifica el TPP.",
        "pt-br": "O STET identifica o TPP com um certificado eIDAS QWAC em mTLS e verifica se o `client_id` corresponde ao número de autorização do certificado. O PSR não diz por qual meio o TPP se identifica."
      },
      "pages": [
        "framework/3-prerequisites-and-technical-details"
      ]
    }
  },
  "verification": null,
  "sources": [
    {
      "document": "8221/26",
      "page": 243
    },
    {
      "document": "8221/26",
      "page": 268
    },
    {
      "document": "8221/26",
      "page": 269
    }
  ],
  "verifiedAt": "2026-10-04"
}

All obligations Markdown version