What is remote identity verification, and how does it work?

Remote identity verification confirms a person’s identity from their own phone, with no branch visit required. The ID card is read, its contactless chip is verified, and a face check confirms the person holding the card is its owner. The flow starts inside your app and ends there.

The formal Turkish term is uzaktan kimlik tespiti; the industry usually calls it KYC.

How does it work?

There are four steps for the user, and all of them complete in one session.

1. Front of the ID card. The card is framed by the camera. Name, national ID number, date of birth and the other printed fields are read automatically — the user types nothing.

2. Back of the card. The card is turned over. The machine-readable zone (MRZ) along the bottom is parsed and validated against its own check digits. This step is a precondition for the next one.

3. The contactless chip. The card is held to the back of the phone. The chip inside is read over near-field communication, returning the identity data and a high-resolution biometric photo. This is the critical part of the flow: the data on the chip is signed by the authority that issued the card. You have not merely read the information — you have proved it came from a genuine state-issued document.

4. Face and liveness. The user shows their face. Two things are confirmed at once: that the person present is a live human (liveness detection), and that they are the same person as in the photo from the chip (face matching).

When the session ends you receive a single result structure: which fields were read, whether the chip was verified, whether the liveness check passed.

Why in-app instead of a branch?

The identity step is the steepest part of a signup funnel. Every redirect that takes the user out of your app — a branch, an appointment, an email, a browser — takes a share of the applications with it.

	Branch and paperwork	Inside your app
Where the user goes	A branch or an appointment	Nowhere
When it works	Business hours	Any hour
Data entry	By hand, with room for error	Automatic, from card and chip
Result	Days later	Same session

The difference is not only speed. Taking the details from the card and the chip also removes the errors that manual entry introduces.

Who uses it?

Anywhere identity has to be established inside the signup flow:

• Banks and fintech — remote onboarding and account opening.
• Crypto exchanges — verification at signup and at limit upgrades.
• Payment and e-money institutions — wallet opening, on a fully automated flow.
• Public and regulated bodies — identity checks in application and service processes.
• Electronic communications — identity verification on subscription applications.

How long does it take?

For the user, typically under two minutes. Each step takes seconds; the longest is the chip read, at three to six seconds when it goes cleanly.

For integration, typically one day. You add the SDK, call verification where it belongs in your flow, and take the result. There is no separate service to stand up and no infrastructure to provision.

What to check when choosing a provider

Most products look alike in a demo. The differences show up in four places.

What happens when the chip will not read? The right answer is not “it stops”. When the chip does not respond, the flow should fall back to verifying the card’s visual security features and continue. That single question determines your real-world completion rate.

What certification backs the liveness check? Türkiye places a numerical ceiling on the false acceptance rate of the algorithm used in fully automated flows, and requires it to be evidenced. Ask which certification the provider relies on and what rate was measured. The liveness article covers what protects against what.

How much of the interface is yours? Does verification look like part of your product, or like a foreign screen dropped into the middle of it? Brand consistency feeds directly into completion rate.

Who are you talking to? During integration, is the person on the other end from the team that writes the product, or from a support tier? That difference decides whether a bug is resolved in hours or days.

For a fuller checklist, see 12 questions to ask before choosing an SDK.

Next step

The fastest way to explain the flow is to show it. Every screen is published here, and in a fifteen-minute call we can run it end to end on your own device and work out how it fits your signup flow.