
In this article
What does direct integration involve?
In a direct integration your system talks to each provider through that provider’s own API: Smart-ID through the SK ID Solutions RP API, eParaksts through LVRTC’s OAuth2 interface, and each bank through its own identification service. Each comes with its own contract, test environment, keys and documentation.
A broker maintains those integrations and gives your system one standard interface. With Dorvis that interface is OpenID Connect: you receive given_name, family_name and person_code whichever method the person used.
How many contracts and APIs in each case?
| Methods | Direct integration | With Dorvis |
|---|---|---|
| Smart-ID only | 1 contract (SK), 1 API | 1 SK contract + Dorvis, 1 OIDC integration |
| Smart-ID + eParaksts | 2 contracts, 2 different APIs | 2 contracts + Dorvis, 1 OIDC integration |
| Smart-ID + eParaksts + 4 banks | 6 contracts, 6 APIs | 6 contracts + Dorvis, 1 OIDC integration |
How much maintenance should you expect?
An integration is not a one-off job. Providers change certificates, security requirements and user flows, and in a direct integration each change costs developer time, testing and sometimes an urgent release.
What changed in the last twelve months alone?
| Date | Change | Work for a direct integration |
|---|---|---|
| 11 Nov 2025 | eParaksts mobile asks for a three-digit code in a new browser | New user flow, support questions |
| 1 Feb 2026 | Luminor price list: Luminor Link €50/month | Cost review |
| 2026 | Smart-ID+ (QR code, app-to-app) in Latvia | Build the new flow to offer it |
| 6 Oct 2026 | New Smart-ID API certificate | Without an update Smart-ID stops working |
| 2 Nov 2026 | Strong TLS ciphers only on the Smart-ID API | Check and possibly upgrade the runtime |
The Smart-ID changes are covered in detail in Smart-ID changes in autumn 2026. None of them required a code change from Dorvis customers.
When is direct integration the right choice?
- You need one method only – say, Smart-ID – and do not plan to add more.
- Volume is very high – hundreds of thousands of logins a month, where a broker fee is noticeable and development costs are spread across many logins.
- You have your own team that knows the SK and LVRTC APIs and can react to changes within days.
- You need a feature, method or country that the broker does not support. Dorvis supports Latvian login methods and offers document signing as a separate product.
- Internal policy forbids third parties in the authentication chain.
When does a broker fit?
- You need several methods – Smart-ID, eParaksts mobile, the eID card and banks. The law requires accepting national eID means (eID law), so single-method portals are the exception.
- Your team is small, or an agency builds the portal and has no time to follow every provider notice.
- You already use OpenID Connect – Keycloak, Auth0, Entra or a framework with an OIDC library. Dorvis is then just another identity provider; see the Keycloak guide.
- You are preparing for the EUDI wallet – businesses already required by law or contract to use strong user authentication must accept it at the user’s request by the end of 2027 (Regulation (EU) 2024/1183, Article 5f(2)). Dorvis will add the state EUDI wallet as another method in the same connection when it becomes available; Digimaks works today.
Does a broker create lock-in?
To a degree – which is why the interface matters. Dorvis uses standard OpenID Connect, so moving to another OIDC provider means a new client_id and discovery URL, not a new integration. The SK, LVRTC and bank contracts are in your name and stay valid if you later decide to go direct.
The other question is data: the broker processes the personal code on your behalf. Dorvis infrastructure and data stay in Latvia, and every login is recorded in an audit log.