How do you decide between NFC, optical review, and video verification in a compliant onboarding programme?

How to choose the right verification path in a compliant onboarding flow

The decision is usually less about “which method is best” and more about which method can meet the assurance requirement for the specific document, device, and customer context. A compliant programme should route applicants to the strongest method their situation supports, then keep the evidence trail clear enough for audit, review, and exception handling.

NFC is typically the preferred path when the device and document support it, because it can strengthen assurance without adding as much manual judgement. Optical review is the wider coverage option for cases where NFC is unavailable or unsupported, while video verification is best reserved for situations that need human judgement, exception handling, or a stronger step-up before acceptance.

What each method contributes to onboarding assurance

NFC, optical review, and video verification are not interchangeable controls. They each answer a different assurance question: whether the document appears genuine, whether the presented identity matches the document, and whether the reviewer can resolve ambiguity or exception conditions without breaking the policy.

For the strongest path, NFC can help validate document chip data where the issuer and device ecosystem support it. Optical review expands eligibility because it works across more devices and document types, but it depends more heavily on image quality, forgery detection, and reviewer consistency. Video verification adds live interaction, which can be useful where the applicant or document needs additional scrutiny, but it also introduces more operational variability and requires tighter review discipline.

That means the programme design should avoid treating video as a default fallback for weak prior steps. It should be a controlled exception path, not a substitute for a well-built primary flow. The better policy pattern is to use the method that best fits the case, then escalate only when the earlier method cannot confidently complete the decision.

How policy-driven routing keeps the programme compliant

Compliance depends on consistent routing rules, not on ad hoc reviewer choice. The flow should define when NFC is required or preferred, when optical review is acceptable, and which edge cases must move to video or manual escalation. If the rules are unclear, two similar applicants can receive different treatment, which creates both compliance and fairness problems.

A good policy also records why a case took a given path. That matters when a regulator, auditor, or internal control owner asks why one applicant was processed through optical review and another through video. The justification should be visible in the workflow, not reconstructed later from reviewer memory.

Useful routing criteria usually include device capability, document compatibility, image quality, liveness or interaction confidence, and whether the applicant falls into an exception bucket. The programme should also define what happens when a preferred method fails partway through the journey, so the customer can stay in a compliant path instead of restarting in an inconsistent state.

Risk and Threat Considerations

Verification choice creates different exposure profiles. NFC can reduce some document fraud risk, but only when the device, chip read, and document ecosystem are working correctly. Optical review is more scalable, but it is more exposed to image tampering, poor capture quality, and inconsistent human judgement. Video verification can help resolve uncertainty, but it also raises the stakes for reviewer training, fraud cues, and operational controls around exceptions.

Failure mechanism: Weak routing lets low-assurance methods absorb cases that should have been escalated, or pushes applicants into paths that the evidence quality cannot support. That can produce false accepts, false rejects, or inconsistent treatment across the onboarding population.

Impact: The result is weaker onboarding assurance, more manual rework, higher fraud exposure, and a less defensible audit trail if the programme cannot explain why a particular method was used.

Practitioner Guidance

What to prioritise: Set the policy around assurance requirements first, then map each method to the cases it can support. Do not let operational convenience, queue length, or reviewer preference decide the path.

What to verify: Confirm that the workflow records the decision inputs, fallback logic, and exception reason for every routed case. If you cannot show why NFC was used, or why a case moved from optical to video, the control is harder to defend.

Common mistake: Treating video verification as the universal backup. In practice, video is often the most expensive route to operate well, so it should be reserved for cases where the added judgement genuinely improves confidence.

Practitioner takeaway: The most defensible onboarding programme is the one that routes each case to the lowest-friction method that still meets the required assurance level, while preserving a clear escalation path for exceptions.

Related resources from NHI Mgmt Group

• What is the difference between automated identity verification and human review in onboarding?
• How should organisations choose between biometric face verification and video call verification for remote onboarding?
• What is the difference between video KYC and traditional in-person identity verification for regulated onboarding?
• How do you know if an access review programme is actually working?