Which PSU identifier does the bank recognise?

National identifier
A public identifier of the person.
Customer identifier
The identifier the bank assigns to its customer.

In STET 1.6.3: Part 1, §3.3 Customer Authentication Approaches, p. 18
Part 1, §3.3.2 Decoupled approach, p. 18
Bank side: Document the type of identifier expected, and the field that carries it. Part 2 does not name this field for decoupled PISP.
TPP side: With decoupled, the TPP must capture an identifier the bank can process and pass it on. With redirect, it may pass it if the protocol allows, through login_hint (OPT-OAU-004).

The entry as stored

{
  "id": "OPT-SCA-002",
  "edition": "1.6.3",
  "chooser": "aspsp",
  "title": {
    "fr": "Identifiant du PSU attendu",
    "en": "Expected PSU identifier",
    "es": "Identificador del PSU esperado",
    "pt-br": "Identificador do PSU esperado"
  },
  "question": {
    "fr": "Quel identifiant du PSU la banque reconnaît-elle ?",
    "en": "Which PSU identifier does the bank recognise?",
    "es": "¿Qué identificador del PSU reconoce el banco?",
    "pt-br": "Qual identificador do PSU o banco reconhece?"
  },
  "options": [
    {
      "label": {
        "fr": "Identifiant national",
        "en": "National identifier",
        "es": "Identificador nacional",
        "pt-br": "Identificador nacional"
      },
      "text": {
        "fr": "Un identifiant public de la personne.",
        "en": "A public identifier of the person.",
        "es": "Un identificador público de la persona.",
        "pt-br": "Um identificador público da pessoa."
      }
    },
    {
      "label": {
        "fr": "Identifiant client",
        "en": "Customer identifier",
        "es": "Identificador de cliente",
        "pt-br": "Identificador de cliente"
      },
      "text": {
        "fr": "L'identifiant que la banque attribue à son client.",
        "en": "The identifier the bank assigns to its customer.",
        "es": "El identificador que el banco asigna a su cliente.",
        "pt-br": "O identificador que o banco atribui ao cliente."
      }
    }
  ],
  "stet": {
    "sections": [
      {
        "part": "framework",
        "section": "3.3",
        "page": 18
      },
      {
        "part": "framework",
        "section": "3.3.2",
        "page": 18
      }
    ],
    "openapi": [],
    "flows": [],
    "changes": [],
    "remark": null
  },
  "aspsp": {
    "fr": "Documenter le type d'identifiant attendu, et le champ qui le porte. La partie 2 ne nomme pas ce champ pour le decoupled PISP.",
    "en": "Document the type of identifier expected, and the field that carries it. Part 2 does not name this field for decoupled PISP.",
    "es": "Documentar el tipo de identificador esperado y el campo que lo contiene. La parte 2 no nombra ese campo para el decoupled PISP.",
    "pt-br": "Documentar o tipo de identificador esperado e o campo que o transporta. A parte 2 não dá nome a esse campo no decoupled PISP."
  },
  "tpp": {
    "fr": "En decoupled, le TPP doit capturer un identifiant que la banque sait traiter et le lui transmettre. En redirect, il peut le transmettre si le protocole le permet, par `login_hint` (OPT-OAU-004).",
    "en": "With decoupled, the TPP must capture an identifier the bank can process and pass it on. With redirect, it may pass it if the protocol allows, through `login_hint` (OPT-OAU-004).",
    "es": "En decoupled, el TPP debe recoger un identificador que el banco sepa tratar y transmitírselo. En redirect, puede transmitirlo si el protocolo lo permite, con `login_hint` (OPT-OAU-004).",
    "pt-br": "Em decoupled, o TPP deve capturar um identificador que o banco saiba tratar e repassá-lo ao banco. Em redirect, pode transmiti-lo se o protocolo permitir, por `login_hint` (OPT-OAU-004)."
  },
  "regulation": null,
  "note": null,
  "production": null,
  "verifiedAt": "2026-10-19"
}

All options

The options