Skip to main content

Full Service Provider - Short-Term Certificates

The activation process consists of the following steps:

  1. Obtain an activation token

    The partner requests an activation token from the Token API for a specific Identification Provider. The returned token can either be communicated to the end customer or used directly as part of a redirect URL to initiate the activation flow.

  2. Complete the identification process

    The end customer starts the identification process using the provided token. During this process, the customer is redirected to the configured Identification Provider, where their identity is verified.

  3. Complete the activation

    After the identification has been completed successfully, the end customer completes the EU-Identity activation process. Once the activation is finished, the identity is ready for use.

  4. Optional: Start the signature process

    After the activation has been completed, the partner may initiate one or more signature processes using the activated EU-Identity, depending on the requirements of the application.

Requried documentation and interfaces​

Token API​

To initiate the activation process, the partner must first obtain an activation token using the Token API. When requesting the token, the partner selects the Identification Provider that will be used to perform the customer's identity verification.

The returned activation token can either be communicated to the end customer or embedded in a redirect URL.

Once the identification flow is started, the customer is automatically redirected to the selected Identification Provider and subsequently to the EU-Identity activation process.

Signature Interfaces​

After the activation process has been completed successfully, the partner may initiate one or more signing operations using the activated EU-Identity. The following interfaces are available for creating digital signatures:

Optional: Timestamp​

The Timestamp API can be used to create a timestamp as part of the signing process. This step is optional and may be used if required by your application's workflow.

Refer to the Timestamp documentation for implementation details.

Optional: Qualified Seal​

The a.sign seal qualified API can be used to apply a qualified electronic seal to the resulting document as part of the signing process.

Refer to the a.sign seal qualified documentation for implementation details.