Integration Guides

The A-Trust platform supports different integration models depending on how identity verification is performed and how much of the certificate lifecycle is managed by your application.

These guides describe the supported integration options, the required APIs, and the workflows for certificate activation and remote signing.

Choose the integration model that best matches your application architecture.

Available Integration Models

Identity Provider Integration

Choose this integration model if you already operate your own identity verification process.

After successfully identifying the customer, your application creates an identity record and submits it to the A-Trust identity interface. A-Trust validates the submitted information and continues with the certificate activation process.

This integration is intended for partners who have an existing identification solution and want to integrate certificate issuance and remote signing into their own workflow.

→ See: Identity Provider Integration

Full Service Integration

Choose this integration model if your application does not perform identity verification itself.

A-Trust manages the complete identification and activation workflow. Your application requests an activation token, redirects the end customer to the identification and activation process, and can subsequently initiate signing operations.

This is the recommended integration for partners who want to integrate qualified electronic signatures with minimal implementation effort.

→ See: Full Service Integration

Which Integration Should I Choose?

If you...	Use
Already have your own identification process	Identity Provider Integration
Want A-Trust to perform the customer's identity verification	Full Service Integration

Both integration models support the activation of certificates and the creation of qualified electronic signatures. The individual guides describe the required APIs, request parameters, and implementation steps for each workflow.