Who IDnow is
IDnow is an identity verification company founded in 2014 and headquartered in Munich, backed by a majority investment from Corsair Capital. It identifies people automatically from a document and a selfie, by video call with an IDnow ident specialist, or with electronic IDs such as the German eID card, and it issues qualified electronic signatures.
Crypto, financial services, insurance, telecom and gaming companies are among its customers. Its Trust Platform, where identity and risk flows are designed in a visual studio and run through one API, is why IDnow is one of the providers our KYC / AML module connects to.
What it does in your platform
KYC / AML
Identifies customers at sign-up with the IDnow flow that suits them: an automated document and selfie check, a video call with an IDnow ident specialist, or an electronic ID. The outcome lands in the module's review queue with the rest of the customer's checks.
How the connection works
The KYC / AML module runs the flows you design in IDnow's Studio through the Trust Platform API. IDnow's credentials stay in your platform's secrets; your app only receives a token for one session.
A session starts
When a customer signs up, the module creates a session for the flow you published, with the customer's details and your own reference.
One token per customer
IDnow returns a player URL with an encrypted token that expires with the session. Your app opens it, or starts IDnow's iOS or Android SDK with the session token.
The customer is identified
The customer completes the flow: a document and a selfie, a video call with an IDnow ident specialist, or an electronic ID, as the flow defines.
A signed notification
When the session ends, IDnow sends a webhook as a signed JSON Web Token, which the module checks against IDnow's published keys. It carries no personal data.
The results are fetched
The module reads the session's results through the API and applies your rules. Clear cases pass, and the rest go to your team's review queue in the backoffice.
Next to other providers
IDnow can sit next to other verification providers in the module, for example for customers who identify by video call or with an electronic ID. Customers are routed by country or risk, with a fallback if a provider is down.
The onboarding screens, the review queue and the audit trail stay the module's own. Adding IDnow, or moving to another provider later, does not change your apps, and past results stay linked to the provider that made them.
When IDnow fits best
A strong fit when
- You want several ways to identify customers, automated, by video call or by electronic ID, from one provider.
- You want the option of an IDnow specialist checking the customer over video, not only automated checks.
- Your customers carry electronic ID cards, such as the German eID, and you want them to use those.
Also worth a look
- A provider focused on automated document and selfie checks, if you never need video identification.
- A provider you already have a contract with: it becomes a connector too.
How we get you live
The contract
We help you get your IDnow account and contract in place, for the identification methods and markets your licence covers.
The flows
We design the flows with you in IDnow's Studio: which steps run, in which order, and for which customers.
The keys
IDnow's API credentials go into your platform's secrets and nowhere else, and the module checks every webhook against IDnow's published keys.
A full test run
The whole flow runs in IDnow's sandbox, from sign-up to the review queue, before your first real customer.
