Process Steps

Key

This attribute is optional and can be used for identification when returning the status. The value can be defined by the customer and ideally is unique for each process.

Types

Type	Description
Selfie	Liveness detection in three steps to verify the user's identity.
DocumentRegistration	Scanning of configured identification documents for identity verification.
AgentReview	Applicable only upon prior agreement. Routes processes with a low score to manual agent review.
UserReview	Users are presented with extracted names for correction. Must be combined with "DocumentRegistration."
QesSignature	For qualified electronic signatures (QES). Only available for configured tenants.
Signature	For advanced electronic signatures (AES).
Welcome	Displays an introduction screen with general identification tips. Please note that this ProcessStep is provided for special cases. Please do not use it.
PdfScan	Allows users to take a photo, which is then provided as a PDF.
PersonalData	Only available upon prior agreement and configuration. Enables custom user forms.
HandwrittenSignature	To be used in combination with QES. Allows the user to draw a signature, which is provided as an image.
Info	Reserved for change requests and applicable only upon agreement with fidentity.

Subtypes

Subtype	Description
main*	Default subtype. Can be used with all process steps.
nfc*	Prompts the user to read the NFC chip from their identification document. Only passports are accepted. This subtype must only be used with "DocumentRegistration."
zoom	Only available upon prior agreement and as a change request.
readonly	Only available upon prior agreement and as a change request.
api	Only available upon prior agreement and as a change request.
identOnly	Must only be used with the type "QesSignature." Triggers a QES identification.
signOnly	Must only be used with the type "QesSignature." Triggers the signature process for the associated identification process.
singleRun	Must only be used with the type "QesSignature." Triggers a temporary QES identification without WebAuthn.

*correct use of the attributes main and nfc:

For identification via NFC, the subtype “nfc” must be set for DocumentRegistration. Otherwise “main” should always be used.

Example Selfie with NFC

  "processSteps": [ 
    {
      "type": "Selfie",
      "subtype": "main"
    },
     {
      "type": "DocumentRegistration",
      "subtype": "nfc"
    }],

Example for a QES process:

When creating a Qualified Electronic Signature (QES), set “QesSignature” as type and “main” as the subtype. This ensures that all necessary steps, including Selfie, DocumentRegistration, NFC scans Signature are included in the process.

Example QES

"processSteps": [
    {
      "type": "QesSignature",
      "subtype": "main"
    }],