The hardest product challenge isn’t building something powerful. It’s building something powerful that feels effortless to use. Jonas Mendes, Director of Product for the IDnow Trust Platform, on the thinking behind Orchestrate, Observe, Decide, and why the order matters.

There is a question I often come back to when thinking about product: what is the actual problem?

Not the stated problem. Not the problem as it appears in a requirements document or a sales call. The underlying problem that if you solve, makes everything else easier.

In identity verification, the stated problem is usually something like “We need a better document check” or “our biometric matching isn’t accurate enough” or “we need to add eID support.” These are real problems. Solving them matters. But they are symptoms of something deeper.

The actual problem, as I have come to understand it, is this: compliance teams are being asked to move at regulatory speed using infrastructure that moves at development speed. And those two speeds are not compatible.

In a regulatory environment where new AMLA’s customer due diligence standards, eIDAS 2.0 assurance level requirements and evolving fraud typologies can change what “compliant” looks like at relatively short notice, the inability to adapt quickly is an operational inconvenience at best, and compliance risk at worst.

That is the problem the IDnow Trust Platform is built to solve.

Fragmentation is the Real Identity Verification Problem.

It is easy to think of the identity verification challenge as a technology problem — that if you just have the right document analysis, the right biometric check and the right AML screening tool, you are covered. And for a long time, that was roughly how the industry approached it.

In reality, though, for most businesses operating at scale, identity verification is a patchwork. A document verification vendor integrated via one API. A biometric provider via another. An AML screening tool bolted on at a different point in the journey. A fraud detection layer sitting alongside but not quite connected to the onboarding flow. Each tool doing its job in isolation, with no shared data model, no unified audit trail and no single view of what is happening across the customer lifecycle.

When something goes wrong, such as a fraud case slipping through or a compliance gap identified in audit, the work of diagnosing and fixing it is enormous. And when you want to optimise something like improving conversion at a particular stage or reducing false positives on a particular check, it’s often impossible, as you cannot see the journey clearly enough to know where the problem is.

In this sense, fragmentation creates operational complexity, and most importantly, blindness. And, in compliance, blindness is expensive.

Orchestrate, Observe and Decide with the IDnow Trust Platform.

The IDnow Trust Platform has been built around three principles:

1. Orchestrate comes first because control should always come first. A compliance team should be able to design, modify and deploy an identity verification journey without needing to write code or open a development ticket. The IDnow Trust Platform gives compliance and product teams direct control over the customer journey so they can adjust which checks apply to which customer segment, at which risk level and in which market.

The IDnow Orchestrate Workflow builder is a visual, logic-based tool that affords compliance teams the insight and ability to apply rules in hours, not sprint cycles. For example, they can apply certain identity verification methods for specificcustomer types. Then, depending on results, apply a risk score, which, if it exceeds the threshold, triggers an additional check.

That adaptability is not only a feature of convenience. In a regulated environment soon to be reshaped by the Anti-Money Laundering Regulation, eIDAS 2.0 assurance level requirements and evolving national frameworks, the ability to update your verification journey quickly is a crucial compliance capability.

2. Observe comes second because you cannot improve what you cannot see. The Journey Explorer gives a real-time, end-to-end view of what is happening across your customer verification flows. This could be where customers are dropping off, where checks are generating unexpected results or where friction is being created that does not correspond to a genuine risk. For most businesses using point solutions, where each tool reports its own metrics in its own format, assembling a coherent picture of the full journey requires significant manual effort.

The IDnow Journey Explorer changes that and does something much more important: it makes A/B compliance testing possible. If you want to know whether a different verification sequence reduces drop-off without increasing fraud, you can test it — with real traffic, in a controlled way, with results that are statistically meaningful. That’s the kind of optimisation capability that product teams have had for years. Now, with the IDnow Trust Platform, compliance teams have it too.

3. Decide comes third because you can only make good decisions if you have access to good information. The rules engine sits at the heart of the decisioning layer, drawing on the signals collected across the entire customer journey, including document verification results, biometric match scores, device intelligence, location data, email risk and phone risk, before applying the workflow-defined logic to produce an outcome. Approve. Decline. Escalate for human review. Apply enhanced due diligence.

The goal of the IDnow Trust Platform is not to remove human judgment from the process. It is to ensure that when human judgment is required, it is focused on the cases where it genuinely adds value, such as the ambiguous situations or the high-stakes decisions that warrant careful review. Routine decisions, made against well-defined criteria, should not require a human in the loop. This is not a compromise on quality but a better use of expert time.

The IDnow Trust Platform and the Art of the Possible.

There is a version of this story that is purely operational. Yes, the IDnow Trust Platform offers faster deployments, lower integration costs, better conversion metrics. Those things, of course, matter but the more important part of the story is strategic.

When a new regulation comes into force, such as when AMLA’s RTS on customer due diligence defines new requirements or when a new fraud typology requires a new detection layer, a business operating on the IDnow Trust Platform does not need to rebuild. The compliance team simply adjusts the workflow and the customer never notices.

That is what infrastructure is supposed to do. It is not supposed to be the thing that slows you down when the world changes. It is supposed to be the thing that lets you move quickly because the foundations are solid.

The compliance teams I have most respect for no longer view identity verification as a set of tools to be managed, but as a capability to be deployed intelligently. The IDnow Trust Platform is built for that ambition.

Discover more about the IDnow Trust Platform’s first customer, 0TO9 in our blog, ‘“Simple on the surface, powerful underneath,” 0TO9 on Going First with IDnow’s Trust Platform.’

Interested in more ‘Lessons From’ our subject matter experts? Click below!

Senior Architect at IDnow, Sebastian Elfors explains how technical standards are moving from technical guidelines to legal foundations — and what that means for banks, fintechs, wallet providers, and every European citizen.
Former INTERPOL Coordinator, and current Forensic Document Examiner at IDnow, Daniela Djidrovska explains why IDnow offers document fraud training to every customer, regardless of sector.
Research Scientist in the Biometrics Team at IDnow, Elmokhtar Mohamed Moussa explores the dangers of face verification bias and what steps must be taken to eradicate it.
Research Scientist at IDnow, Nathan Ramoly explores the dangers of deepfakes and explains how identity verification can help businesses stay one step ahead of fraudsters and build real trust in a digital world.