Signer name parsing rules for the QES level

๐Ÿ“˜

Please note that we use both "given name" and of "first name" in this note. The given name refers to the element present in legal documents, while the first name refers to the API payload attribute for Signers.

The identity verification of QES Signers relies on a matching between the declared Signer identity (first and last names provided in the Signature Request API payload) and the extracted identity from the Signer identity document (given and last names displayed on the identity document).

Performing this match is not always straightforward because of national specificities and the wide range of possible formats for names. This process can be facilitated during your API integration process by pre-parsing Signer names according to the guidelines outlined below. Implementing these guidelines will improve the overall success rate for the identification of your Signers.

If your Signers meet identification issues even after following these guidelines, please refer to the Signer identification errors page.

Parsing of characters

  • First and last names can be provided either in lowercase or uppercase formats.
  • Latin special characters (ร , รฉ, รงโ€ฆ) can also be written in their normalized form (a, e, cโ€ฆ). Whenever such characters are extracted from an identity document, transliteration is performed based on ICAO specifications (Document 9303 Part 3).
  • Hyphens (-) can be converted to spaces. Thus, a given name or a last name can be declared with a space instead of a hyphen.
  • Apostrophes (Nโ€™O) can be converted to spaces (N O). Thus, a given name or a last name can be declared with a space instead of an apostrophe.
  • When handling Signers with identity documents displaying given and last names written in Latin and other alphabets (Cyrillic, Arabic, Chinese,โ€ฆ), the Latin version must be used. In the example below, "OBRAZETS" and "TESTER" should be used as first and last names.
  • Note that as a result of this parsing, the Signer name drawn on their document Signature Field will not visually match exactly the Signer name from their identity document. This is not an issue because the electronic signature attached to the document will contain the "real" legal name extracted from the Signer identity documents, and it's this electronic signature that has legal value (while the signature image is just a visual hint).

Matching of first name

  • The Signer first name must match exactly one of the extracted given names from the identity document. In the example below, either the first ("Maรซlys-Gaelle") or second ("Marie") given names can be declared in the Signer data. In both cases, the matching will be successful (exactly one match). However, providing "Maรซlis-Gaรซlle, Marie" will result in a failed identification (two matches).
  • Compounded first names are sometimes written without hyphens
    • e.g. "Jean-Franรงois" is sometimes written as "Jean Franรงois". In that case, the identity document parsing will handle these 2 words as 2 different given names. For such Signers, only the first word of their first name should be provided (e.g. "Jean" in this case).
  • A few identity documents do not comply with the above rule. A space is not interpreted as a separator, so everything before the first separator expected must be written.
    • e.g. for a French Passport, a Signer has two first names "Jean Franรงois" and "Baptiste" which are written on the identity document โ€˜Jean Franรงois, Baptisteโ€™. It is expected that โ€˜Jean Franรงoisโ€™ is written in full because it is the character string before the comma, which is the expected separator.
    • The list of separators is defined below:
CountryDocumentVersionFirst names separator
ARGPassportP7, P8,
CHLPassportP4,
COLPassportP10,
DNKPassportP9, P12, P13,
DNKResidence PermitRP2, RP4,
ESPIDI4, I5, I6,
ESPPassportP3, P5,
ESPResidence PermitRP19,
FRAIDI5,
FRAPassportP3,
ITAIDI7, I6,
ITAResidence PermitRP1, RP4,
RP5, RP6
,
MEXPassportP6,
PERPassportP6,
VENPassportP6,

Matching of last name

  • The Signer last name must must match exactly either birth name or usage name. If the Signer has both birth and usage names displayed in the "last name" field of their identity document, only one of them should be provided. In the example below, either "GABLER" or "MUSTERMANN" can be used for the Signer last name. However, the providing the compounded birth name-usage name "GABLER-MUSTERMANN" will result in a failed identification. Note that these last names can have multiple particles (e.g. "VAN DEN DRIES" will be successfully parsed as one single last name).
  • The name used in the certificate of signature will be the declared name, whether birth name or usage name, as long as the identity matching between the declared identity and the identity document yields a positive result.

Honorary/Nobiliary/doctorate titles

  • Some European country citizens have honorary titles (e.g. "Baron", "Dr."). These honorary titles are displayed in their identity document last name field before the last name. Such titles must not be provided in the Signer data. Only the first and last names must be declared to match with the identity document.