In this article
- Why passwords and SMS codes fall short on a customer portal
- Why existing eID tools work better for two-factor customer login
- Two-factor options for a customer portal compared
- Customer login is not employee MFA
- When to keep passwords
- How to add two-factor login with Dorvis
- A two-factor authentication example in a customer portal
Why passwords and SMS codes fall short on a customer portal
Customers reuse passwords across sites, forget them and reset them by e-mail. When a password leaks from one site it gets tried on yours, and the e-mail reset becomes the easiest way to take an account over.
An SMS code helps, but not enough. A phishing page can ask for the code and relay it to the real portal in real time, and SMS depends on a phone number that can be redirected. You also pay for every message.
Passwords and SMS codes do not identify the person using your customer portal. They only confirm that someone knows the password and can receive texts on a particular number.
Why existing eID tools work better for two-factor customer login
Smart-ID and eParaksts mobile are two-factor by design: they need the phone with the app (possession) and a PIN only the user knows (knowledge). Bank login relies on the bank’s own strong authentication. There is no new password or app for the customer.
They are also widespread: about 1 million people in Latvia use Smart-ID and more than 540,000 used eParaksts mobile in 2025. Customers without either can use bank authentication with four banks.
You also receive a verified identity. Your system receives the name and personal code from a qualified trust service provider or a bank, so the account belongs to a known customer.
Two-factor options for a customer portal compared
| Method | Security | Identity verified | Cost | Customer effort |
|---|---|---|---|---|
| Password + SMS code | Weak: codes can be phished; SMS depends on the phone number | No | A fee per SMS, plus password-reset support | Remember a password and wait for a text |
| Authenticator app | Medium: codes can still be phished on a fake page | No | No per-login fee; development and support when phones are lost | A password plus a separate app to set up |
| Passkeys | High: resistant to phishing | No – tied to a device, not a person | No per-login fee; development and an account-recovery process | Convenient, but set up per account and device |
| Smart-ID, eParaksts, bank via Dorvis | Strong: two factors from a qualified provider or bank | Yes – name and personal code | Dorvis from €60/month + provider fees (Smart-ID from €0.109, eParaksts per your contract with LVRTC) | A tool the customer already uses; no password |
Customer login is not employee MFA
Most two-factor guides are about staff: e-mail, VPN and internal systems, where the company issues and manages the tool itself.
A customer portal is different: you cannot hand out devices or train customers. The best choice is a tool they already have. If you need to meet requirements on the employee and systems side, see our page on NIS2 in Latvia; Dorvis can also be used for internal systems, for example through Keycloak.
When to keep passwords
eID login can replace passwords entirely or sit alongside them. Keep a password option when:
- some customers have no Latvian e-identity, such as foreign customers or shared company accounts;
- the account holds nothing sensitive and a verified identity is not needed, such as a newsletter or a shop customer profile;
- you are migrating step by step – offer eID as the main login and require it for sensitive actions such as changing details or viewing contracts.
How to add two-factor login with Dorvis
Choose the methods
Most customers can log in with Smart-ID or eParaksts. Bank login serves those who have neither. A Launch Kit shows what your portal lacks.
Register the integration
In the Dorvis portal, enter your redirect URI and receive a client_id and client_secret. The first month is free for new customers.
Sign the provider contracts
Smart-ID with SK ID Solutions, banks under their own price lists. You pay providers directly and the contracts stay with you. A live Smart-ID login needs your own contract with SK, and the Dorvis team walks you through that step; with the Launch Kit we prepare the applications for you.
Add OpenID Connect
Authorization Code flow with
scope=openid profile; examples for Node.js, Python, PHP, Java, .NET and Go are on the developer page.Link existing accounts
On first use the customer logs in with their eID and confirms their existing account; from then on you recognise them by the verified personal code. For data protection, see personal code and GDPR.
A two-factor authentication example in a customer portal
Example: a utility customer opens the portal and picks Smart-ID. The first factor is the phone with the Smart-ID app (something the customer has), the second is the PIN1 code (something the customer knows). The portal stores no password, yet receives a verified name and personal code.
eParaksts mobile, the eID card (card plus PIN) and internet bank login work the same way. This is sometimes called two-step verification. How to switch it on in your portal: OpenID Connect integration.