It’s 2025. Your roadmap finally has space for e-signing and remote ID – or it’s time to switch to an eIDAS-approved provider like Evrotrust. Now comes the real choice: go fully custom with the SDK, or plug in via API and keep disruption low? And how exactly does the Evrotrust web portal differ?
To help you answer these questions, this guide walks through Evrotrust’s three direct paths – white-label SDK, API, and Digital Services Portal. We explain where each shines, how it fits into real-world workflows, and which business needs it addresses. By the end, you’ll be able to match strengths to your plan and choose the right approach with confidence.
What Are the Main Differences Between the SDK, API, and Portal?
What Is the Evrotrust White-Label SDK?
The SDK (software development kit) is a fully embedded, white-label integration that places Evrotrust’s capabilities inside a client application. It seamlessly integrates Evrotrust’s services (eSignatures, eID, eDelivery) directly into a company’s native apps, both in web and mobile environments. The SDK allows for the highest degree of customization and flexibility. In addition, it works without the Evrotrust app.
Main Highlights
- Branding and UX: Businesses have control over typography, color, layout, etc. to align with their preferred design system.
- Services supported:
- eSignature: qualified electronic signature (QES) – long-term or one-time (OTP).
- Electronic identification: basic eID, enhanced KYC, or full KYC.
- eDelivery (where applicable).
- Platforms: SDK integrations are available for both web and mobile.
- Regulatory alignment: Built on eIDAS-approved trust services and supports AML/KYC processes as part of the integration.
You can see the SDK in action in this demo:
Who Is the SDK Integration Suitable for?
The SDK is the path for businesses that want Evrotrust to live inside their own app and look/behave like it was built by their team. Most importantly, the SDK is meant for businesses that need reliable remote identification (eID).
It tends to suit teams that:
- Work at larger scale and need a native, consistent experience on web and mobile.
- Have clear brand standards and want every screen to match their design system.
- Regularly identify customers online.
- Depend on deep integrations with existing systems – KYC/AML tools, analytics, CRM software, etc.
- Plan on a longer, staged rollout and can align engineering sprints with a tailored implementation.
Bottom line: the SDK requires more planning and build time, but in return it provides end-to-end ownership of the UX and maximum flexibility to evolve flows over time.
Evrotrust API
Integrating Evrotrust via REST API enables organizations to trigger identity verification and signing flows from their own software with minimal development effort. Common triggers include:
- KYC identity verification for new clients
- Authentication of existing users
- Digital document signing for customers or employees
The API initiates a secure handoff to the Evrotrust mobile app, where the user completes the required action. Upon completion, control returns to the client application or website, and the session continues.
Here is a short walkthrough of an API flow in practice:
Main Highlights
- Cross-platform compatibility: Suitable for web browser and app-based journeys.
- Remote identification and e-signing: Automates the sending/signing of electronic documents and supports remote KYC.
- Pragmatic time-to-market: Typically faster to implement than a fully embedded SDK while remaining compatible with existing systems.
Who Is the API Integration Suitable for?
The API suits teams aiming to minimize changes to existing flows and keep implementation time short.
In the ideal-case scenario, this method is perfect for:
- Teams that can accommodate a brief app handoff (push to the Evrotrust app, then return).
- Products prioritizing faster deployment and lower UI/UX overhead than a white-label build (SDK).
- Workflows already using server-to-server orchestration and event handling.
Evrotrust Digital Services Portal
The Evrotrust web portal is a ready-to-use option that requires no development. It serves as a browser-based hub where business users can initiate eSignature requests, remote identification, and secure document delivery to existing Evrotrust users.
Signing and identification are completed in the Evrotrust mobile app. The portal provides a central archive of pending and completed requests, including status updates for tracking and audit.
Main Highlights
- Zero-development setup: Accessible via browser; any number of authorized employees can send requests and manage workflows.
- Handoff and status tracking: When an action is required, the portal triggers the Evrotrust mobile app for the end user. Once finished (successful or unsuccessful), the request status updates in the portal.
- Document retrieval: Signed files can be downloaded from the portal for the company’s digital records.
- Flow dependency: User identification/authentication and signing occur in the Evrotrust mobile app.
Who Is the Web Portal Suitable for?
The Digital Services Portal is a standardized, browser-based option that enables qualified trust services without custom development – ideal for teams needing an immediate, no-code start and centralized tracking.
It tends to suit teams that:
- Have intermittent or low-volume needs for eSignatures and customer identification.
- Prefer a ready-to-use setup (standard UI, no theming) with shared access for back-office staff.
- Need a central archive with status tracking and audit-friendly records.
- Operate with limited engineering capacity or want to avoid product changes.
- Run limited projects where a full integration isn’t justified.
Note: Identification/authentication and signing occur in the Evrotrust mobile app. Initiation and management happen in the web portal.
Evrotrust Connectors and Add-ons
Beyond direct integrations (SDK, API, Digital Services Portal), many organizations can use Evrotrust through connectors or add-ons available inside their existing document management or eSignature platforms. This approach lets teams access qualified electronic signatures (QES) from within tools they already use, with no custom development.
For example, many businesses have already digitized their workflows by using platforms such as:
- DocuSign
- Adobe Sign
- Creatio
- DocuWare
- Zoho Sign
- SigniFlow
- eID Easy
- BoldSign
- InSign
You can find more platforms where you can use Evrotrust in our Partners section.
Note: Availability, assurance level (e.g., QES vs. AES), and regional/legal support can vary by platform and version. Always verify the terms of use in the relevant app marketplace or with the platform vendor.
Who Are the Add-ons Suitable for?
Foregoing the direct integration of Evrotrust and choosing a connector is best when:
- You already use a DMS/e-signature suite and want minimal change management.
- You prefer a faster time-to-value over a bespoke SDK build.
- You wish to keep document workflows (templates, routing, archives) where they are, but upgrade to QES/eIDAS-aligned signing.
Summary
So, what is the overall best Evrotrust integration method? The one that fits.
Smaller teams rarely need the depth (or investment) of a white-label SDK, while large enterprises can outgrow a lightweight API flow. The right choice depends on scale, workflows, and how much control you want over the experience.
The best course of action is to start with your requirements – volume, branding, timelines, compliance – and map them to the strengths of the SDK, API, or portal. If you’d like a second opinion, don’t hesitate to reach out. Our specialists are happy to review your use case and suggest a path that balances effort, speed, and long-term flexibility. Digitalization is a journey – you don’t need to walk it alone.
