---
title: "GenericIdentification"
canonical: "https://openfinanceguide.com/en/stet/1.6.3/resources/generic-identification"
edition: "STET PSD2 API 1.6.3.1"
source: "https://openfinanceguide.com/docs/stet/1.6.3/pdf/api-dsp2-stet-v1.6.3.2-openapi.yaml"
pdf: "https://openfinanceguide.com/docs/stet/1.6.3/pdf/api-dsp2-stet-v1.6.3.1-part-2-functional-model.pdf"
section: "4.1.6"
pdf_pages: "14"
language: "en"
normative: "The normative text is the English PDF and OpenAPI file published by STET. This Markdown reproduces it for reading; where they differ, the PDF prevails."
license: "CC BY 3.0 FR (https://creativecommons.org/licenses/by/3.0/fr/), STET. Converted to Markdown by Open Finance Guide."
---

# GenericIdentification

Type: `object` · Kind: ISO20022 · Source: [§ 4.1.6, PDF p. 14](https://openfinanceguide.com/docs/stet/1.6.3/pdf/api-dsp2-stet-v1.6.3.1-part-2-functional-model.pdf#page=14)

ISO20022: Unique identification of an account, a person or an organisation, as assigned by an issuer.
API: The ASPSP will document which account reference type it will support.

Fields:

- `identification`, `string`, required — API: Identifier
  Constraints: maxLength 70.
- `schemeName`, `string`, required — Name of the identification scheme.
  Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
  | Code | Name | Description |
  | ---- | ---- | ----------- |
  | BANK | BankPartyIdentification | Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. |
  | BBAN | BBANIdentifier | Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. |
  | COID | CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) |
  | SREN | SIREN | The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. |
  | SRET | SIRET | The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. |
  | NIDN | NationalIdentityNumber | Number assigned by an authority to identify the national identity number of a person. |
  Other values are also permitted, for instance:
  | Code | Name | Description |
  | ---- | ---- | ----------- |
  | OAUT | OAUTH2 | OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU |
  | CPAN | CardPan | Card PAN |
  | MPAN | MaskedPan | Card PAN where some digits were replaced for security reason |
  | TPAN | TokenizedPan | Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field |
  | TBAN | TokenizedIBAN | Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field |
  Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used
  Constraints: maxLength 70.
- `issuer`, `string` — ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
  Constraints: maxLength 35.

## Example

```json
{
  "identification": "12FR5",
  "schemeName": "COID",
  "issuer": "ACPR"
}
```

## Used by

- `GET /accounts` (accountsGet)
- `GET /accounts/{accountResourceId}/owners` (accountsOwnersGet)
- `GET /accounts/{accountResourceId}/transactions` (accountsTransactionsGet)
- `PUT /consents` (consentsPut)
- `POST /funds-confirmations` (fundsConfirmationsPost)
- `POST /payment-requests/{paymentRequestResourceId}/confirmation` (paymentRequestConfirmationPost)
- `PUT /payment-requests/{paymentRequestResourceId}` (paymentRequestPut)
- `GET /payment-requests/{paymentRequestResourceId}` (paymentRequestsGet)
- `POST /payment-requests` (paymentRequestsPost)
- `GET /payment-requests/{paymentRequestResourceId}/transactions` (paymentRequestTransactionsGet)
- `GET /trusted-beneficiaries` (trustedBeneficiariesGet)