WebID

About WebID

WebID is a German eIDV service for online end-user identification and contract signing. It has the highest standard of security and is compliant with AML regulations like German AML Law (GwG) and BaFin.

The WebID service provides call-center functionality, where trained support agents can verify the provided identity papers, the validity of the ID paper and ask security questions to the end-user during a live video call. The verification process is recorded and evidence is made available for the merchant.

From the end-user perspective, the online identification consists of three main steps:

  1. The end-user enters personal details in an online form (desktop or mobile).
  2. The end-user shows an ID paper to the a support agent in a live video call.
  3. The end-user receives and fills in a one-time password (OTP) to confirm the identification process.

Key features

The WebID service provides:

  • Live video assurance of non-business individuals in compliance with AML regulations (Anti-Money Laundering).
  • IdP containing validated identities collected during earlier verification (optional).
  • AI-driven services based on known fraudulent ID papers.

Identity verification

WebID is used to verify the end-user’s identity and obtain relevant personal details about them.
Typically, the merchant can obtain the following information:

  • User: Title, sex, family name, first name, date of birth
  • Address: Street, street number, postal code, city, country
  • Contact: Email, telephone, mobile
  • ID document: Type, authority, issue date, expiry date, nationality, ID number

This filled-in information is double-checked when the end-user shows ID papers during a video call to customer support.

Use case

WebID is useful in many scenarios, for example, as an identification method before signing a document, or when digitally onboarding new customers. In addition, you can obtain a (short term) qualified electronic signature (QES) if the identification completed successfully.

In this example, a merchant wants to onboard a new customer. The merchant uses WebID to both identify the customer and for signing the provided contract.

  1. The personal data is sent via Signicat to WebID. The data is processed and checked, for example towards any prefilled information.
  2. WebID sends back a 9-digit transaction number. The customer enters this number to proceed to a video call with a support agent, for example via Skype.
  3. The support agent guides the customer through the video call and asks the customer to show a picture ID in front of the web camera.
  4. WebID checks the authenticity of the ID and matches the picture with the face in the video.
  5. The customer completes the identification by entering a 6-digit one-time password (OTP).
  6. Once the identity is verified, the verified identity-data can be used to establish a QES process. The customer signs the provided document with the QES, which means it is equally valid from a legal perspective as a handwritten signature.

Integrating with WebID through Signicat

Web integration with WebID is done via the same API as Signicat’s other ID methods. See Get started with authentication for more information. Through the single point of integration, you will get access to Signicat’s wide portfolio of integrated ID methods, not only WebID, but also other services like identity paper verification and lookups.

Signicat supports WebID’s end-user video identification. This service enables merchants to send identification requests about their customers and receive a response status and evidence files after the identification is verified.

Data flow

The integration flow between the different components can be illustrated as follows:

1. Create user interaction: The service posts end-user data to the Signicat user action endpoint to create an identification user action.
2. Response with redirect link: The service redirects the user to the WebID call-center, using the redirect URL in the previous step.
3. Redirect to video identification: The end-user is now checked in a video-call identification at the WebID’s call-center.
4. Complete user interaction: After completion at the call-center, the end-user is redirected to the endpoints configured in the user action creation (see step 1).
5. Notify status change: The merchant will later receive a callback as a notification about the completed status.
6. Status retrieval: The merchant retrieves the user action status which contains the outcome of the identification. The status also contains a link to the evidence file if the outcome is successful.
7. Evidence retrieval: If the outcome is successful, the merchant downloads the evidence file and stores it safely.

How to get started with WebID

If you want to start using WebID through Signicat, please contact Signicat and our sales team will guide you through the process.

Test information

Signicat’s test environment preprod.signicat.com is available 24×7, and may be used during your development and test phase.

After you are registered as a service provider in the WebID platform, you will receive a client_id and a client_secret to authenticate your application.

Other sources

WebID official web site

OpenAPI Specification documentation