Contracts and methods
| Method | What the portal Configuration needs |
|---|---|
| Smart-ID | A service UUID from SK ID Solutions and the name users see in the app |
| eParaksts | Username and password issued by LVRTC |
| Swedbank | A key, which the portal can generate, and the sender ID from the bank |
| SEB | The sender ID from the bank |
| Citadele | A key and certificate plus the sender ID from the bank |
| Luminor | A key, the sender ID and the public key received from the bank |
| Digimaks | An agreement with Dativa; credentials are issued after it is signed |
Technical checklist
- HTTPS redirect and logout URIs registered on the production integration
- The secret is in a secret store and test credentials are not used in production
- Every enabled method tested with a real identity
access_deniedandauth_method_disablederrors handled- Users are linked by
person_code, not by name - Logout ends the Dorvis session too
- The privacy policy describes how the personal code is processed
Did not find the answer?
Write to us and a developer will reply.






