We build identity, authentication and signing systems for banks, governments and regulated businesses — the applications people use to prove who they are, approve a payment, and sign a document that holds up in law.
This work runs at national scale. The Smart-ID mobile applications we build are used by millions of people across the Baltic states and Belgium, and carry over a billion transactions a year.
Smart-ID is an electronic identity solution used for strong authentication, digital signing and payment authorisation across the Baltic states and Belgium. We build its mobile applications for Android and iOS, distributed through Google Play, Apple's App Store and Huawei AppGallery — including biometric enrolment, qualified signing, and PSD2-compliant strong customer authentication for payment confirmation.
A qualified electronic signature carries the same legal weight as a handwritten one across the EU. That is a high bar, and most of the engineering sits behind it rather than in front of it: the signing flow the user sees is short, and everything that makes it defensible is not.
Under PSD2, approving a payment is not the same as signing in. We build the authentication and payment-confirmation flows that keep the two distinct for the person using them, and provable afterwards.
Onboarding someone remotely means establishing who they are without meeting them. We build biometric enrolment and remote identification flows — and the review paths for the cases that should not be decided automatically.
The application technology behind Smart-ID also powers locally branded identity solutions in other markets. If what you need is an identity app that belongs to you rather than a platform you rent, that is work we already do.
We built the original application portal for Estonia's e-Residency programme — the service through which the first e-residents applied. Government-facing, and public from the first day.
eIDAS, PSD2, SCA. The standards are easy to list and harder to live with, because they turn ordinary engineering decisions into things somebody has to justify later.
We have shipped into environments where the code is reviewed by professionals whose job is to audit the code and test the reliability, and we build expecting that: decisions recorded, flows traceable, and an answer available when someone asks why the system did what it did.
Identity is often only one part of the regulated workflow. We also build onboarding, AML/KYC and transaction-monitoring systems for banks.