Dōrvis

Sign in

Direct integration or broker: how to connect Latvian e-identities

Direct integration suits businesses that need one or two methods, have high login volumes and their own development team. A broker such as Dorvis is useful when you need several methods, including banks, and want someone else to handle changes from each provider. Smart-ID alone changed twice in autumn 2026.

Dorvis team 12 October 2026 3 min read

In this article
  1. What does direct integration involve?
  2. How many contracts and APIs in each case?
  3. How much maintenance should you expect?
  4. What changed in the last twelve months alone?
  5. When is direct integration the right choice?
  6. When does a broker fit?
  7. Does a broker create lock-in?

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?

With Dorvis the provider contracts stay in your name: you sign them yourself with SK ID Solutions, LVRTC or the bank and pay them directly under the provider’s own price list. Dorvis is not in that payment flow, so there is no reseller rate and no lock-in.
MethodsDirect integrationWith Dorvis
Smart-ID only1 contract (SK), 1 API1 SK contract + Dorvis, 1 OIDC integration
Smart-ID + eParaksts2 contracts, 2 different APIs2 contracts + Dorvis, 1 OIDC integration
Smart-ID + eParaksts + 4 banks6 contracts, 6 APIs6 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?

Based on the providers' public price lists and notices; checked 12 Oct 2026.
DateChangeWork for a direct integration
11 Nov 2025eParaksts mobile asks for a three-digit code in a new browserNew user flow, support questions
1 Feb 2026Luminor price list: Luminor Link €50/monthCost review
2026Smart-ID+ (QR code, app-to-app) in LatviaBuild the new flow to offer it
6 Oct 2026New Smart-ID API certificateWithout an update Smart-ID stops working
2 Nov 2026Strong TLS ciphers only on the Smart-ID APICheck 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.

Last reviewed:

Try Dorvis integration with Digimaks

An integration with Digimaks is free; you can test the OIDC flow in your own test environment once test credentials are issued. The first month of any paid plan is free.

Loading complete

We use cookies to make this website easier to use. Read our Privacy and Cookie Policy.