IDnow: identity verification, screening and digital trust workflows

IDnow supplies identity and fraud controls for customer onboarding and subsequent interactions. Its financial-services offering explicitly covers investment platforms and wealth management alongside banking, lending and embedded finance. For a broker, the relevant work is collecting identity evidence, routing additional checks and authenticating a returning customer within the account journey.[6]

The Trust Platform combines orchestration, operational visibility and configurable decision logic. Teams compose a journey from identity, authentication, fraud and signing capabilities, then inspect its funnel and individual session history. The platform can route a customer to further checks or manual review according to the configured rules.[1]

For AML screening, a match takes precedence over an inconclusive result; only checks that all return no hits produce no_match. Empty match arrays can also accompany an inconclusive response. A downstream account-opening rule therefore needs the returned verdict, not simply a count of matching records.[19]

IDnow maintains separate documentation for Trust Platform, AutoIdent, VideoIdent/eID/eSign, IDCheck and other services. The new platform is an integration layer, while existing product-specific interfaces remain separately documented. That distinction matters when extending an older implementation or moving a workflow into the platform.[7]

Trust Platform integration starts with an organisation, a published flow, matching environment credentials and a webhook. The application obtains a bearer token, creates a session and receives its identifier and Player URL. Results can be obtained after a webhook or by polling; structured data and evidence files are retrieved separately. Each flow has an OpenAPI definition reflecting its configured steps.[8]

Studio supports OpenID Connect single sign-on, with examples including Microsoft Entra ID, Okta and Google Workspace. A registered email domain includes its subdomains and can belong to only one organisation’s SSO configuration. Disabling SSO invalidates current SSO sessions; users who never created a password need the password-reset route to regain access.[12]

The Trust Platform product description separates the platform licence from usage-based and product-specific fees. The platform charge covers access, orchestration, dashboards, analytics, testing capabilities and support under the applicable support terms. Published descriptions explain charge components but provide no general numerical rate card for this configuration.[2]

SIGNIUS describes limits of 25 documents per certificate, 25 signatures per request and 50 MB per signing request, with PDF, DOCX and XML support. Those product limits help define the required signing workload; they are not a price per signature or an included annual allowance.[5]

Trust Platform separates physical Sandbox and Production from the logical Staging and Live deployment slots inside each. Studio Sandbox can expose preview or deprecated steps that Production hides. Its guide explicitly requires flows, step configuration and IDnow/third-party credentials to be recreated in Production. Sandbox credentials do not work there: the API host, authentication endpoint and webhooks also need the production configuration.[13]

Flow edits create draft versions that can be tested before publication. Publishing replaces the active version in the chosen logical environment while preserving deployment history. Session timeout is configurable by version, with a 24-hour default. Analytics can be filtered by environment and deployed version, allowing a team to distinguish a workflow change from an overall shift in customer completion.[14]

Organisation-level Protect rules have three modes: disabled, warning or blocking. The documentation says this feature is not yet available to all customers. Changes affect new sessions, while sessions already in progress retain their existing treatment. Access to that control therefore needs to be established for the actual organisation.[14]

A completed session can produce an accepted or rejected business outcome. Aborted, expired and technical-error sessions do not produce that decision. The integration guide tells customers to retrieve the detailed reason from the data blocks, and separates API request errors from verification reason codes. This prevents a temporary integration failure being recorded as a substantive identity rejection.[15]

The public status service separates products, test systems and identification centres, and publishes planned maintenance as well as incident updates. Subscribers can use email, text messages, webhooks or feeds. This gives an operations team product-specific notices without treating an isolated status snapshot as an availability guarantee.[24]

The vulnerability policy typically promises an initial response within two business days and later confirmation of assessment and expected mitigation timing. That is a disclosure process, not a general incident-restoration SLA. It excludes customer-owned assets from scope and prohibits disruptive or load testing, social engineering and testing without designated accounts.[26]

IDnow GmbH is based in Munich and identifies its commercial-register entry as HRB 283590. The September 2025 identification terms are addressed to end users, identify IDnow SAS as the contact entity and apply French law. They describe an independent identification service: IDnow does not execute payments or transactions between the partner and the user. Those end-user provisions are separate from a business customer’s order and service agreement.[30][27]

Sweden’s Post and Telecom Authority lists IDnow Trust Services AB among its qualified trust-service providers. This is an eIDAS trust-service status attached to the Swedish entity. It should not be read as a brokerage, investment or payment permission for the wider IDnow group.[28]

On 12 October 2026, IDnow announced qualification for electronic archiving and preservation at IDnow Trust Services AB, alongside its existing signing, sealing and attribute-attestation capabilities. The specific new-service claim is the company’s announcement; the inspected PTS provider list confirms the entity’s qualified-provider status.[29][28]

IDnow’s security centre describes EU production hosting, including AWS Frankfurt and Paris for Trust Platform, and Noris locations for AutoIdent and VideoIdent. It specifies AES-256 at rest, TLS 1.2 or later in transit and master keys held in on-premises hardware security modules. Its subprocessors include identification centres outside the EU; customers select the centres used. EU hosting therefore does not establish that every processing or access location is inside the EU.[23]

For UK data checks, the Trust Platform product description identifies a logically separate third-party environment with its own security measures. Its UK 2+2 identity query uses two independent sources and leaves an anti-money-laundering footprint on the person’s bureau profile. The same description discloses product/configuration-dependent transfers outside the EU and assigns controller information and consent obligations to the customer.[2]

IDnow’s history begins with the 2014 launch of VideoIdent. It subsequently added automated verification and acquired identity Trust Management and Ariadnext, bringing technologies including IDCheck.io and YRIS into the group. Its current company history describes Corsair Capital’s 2025 majority investment and the June 2026 launch of the combined Trust Platform.[31]

Philippe Morel became chief executive on 23 July 2026, succeeding Andreas Bodczek. The appointment followed the platform launch and is a relevant distinction from older company announcements that still name Bodczek as CEO.[32]

Operator

IDnow GmbH and relevant group service entities, including IDnow SAS and IDnow Trust Services AB

Service scope

Identity verification, screening, biometric authentication and digital signing through configurable products and Trust Platform workflows.

Customer types

Investment platforms and wealth managers; Banks and lenders; Financial technology businesses; Other regulated enterprises

Delivery

SaaS; API; Managed service; Hybrid; On premises

Pricing publication

Quote only

Headquarters

Munich, Germany

Platforms

IDnow Trust Platform; AutoIdent; VideoIdent; SIGNIUS

Pricing scope

Platform licence, usage and product-specific components; commercial amounts require the applicable proposal.

Implementation

Configure and test a versioned flow, establish environment-specific credentials, and recreate Sandbox configuration for Production.

Support

Customer Center and product status notices; human verification hours and optional SLA commitments vary by product.

Permissions and regulatory scope

Identity and compliance services; qualified trust-service status attaches to IDnow Trust Services AB. Customer configuration and regulatory obligations remain service-specific.

Provider metadata checked 20 Oct 2026Source 31Source 3Source 27Source 13Source 6Source 7Source 30Source 1Source 2Source 28Source 5Source 24Source 4

The 8 October 2026 SDK notice sets iOS 15 as the minimum target for VideoIdent SDK 9.7.16 and AutoIdent SDK 5.23.0 or newer. Applications supporting older iOS versions may retain an existing supported SDK but cannot adopt those new versions without changing their deployment target. The notice says web-based use is unaffected.[25]

The security centre exposes the document inventory but restricts the DPA, security annex, continuity plans and penetration-test reports to customers. It directs existing customers to their Customer Success Manager while document access through Salesforce SSO is still described as forthcoming.[23]