lumex عربي Get started
Security

Why a photo of an ID is no longer enough: the case for live capture

· 6 min read

For years the standard way to "verify" someone online was a file upload: take a picture of your ID, attach it to the form, wait for someone to look at it. It is simple to build and familiar to users. It is also the weakest point in many sign-up flows, and it is getting weaker every year. This post explains why, and what live capture does differently.

The short answer

A file upload proves only that someone had an image of an ID. It does not prove the card was in their hand, that it was theirs, or that the image is real. Live capture, where the verification page opens the camera itself and records the card and the face on the spot, removes the easiest routes for borrowed, edited and generated images. It does not make fraud impossible, but it moves the effort from minutes to something most fraudsters will not bother with.

Three ways an uploaded ID goes wrong

The borrowed photo

People photograph their IDs all the time: for a hotel, a landlord, a job application, a group chat. Those pictures end up in inboxes, shared drives and leaked databases. Anyone who has one can upload it as their own. Nothing in a file proves who took the picture or when.

The edited photo

Changing a date of birth or an expiry date on a picture of a card takes a few minutes in any photo editor. A reviewer glancing at the image will rarely notice. Even a careful automated check that reads the printed text can be fooled if it does not verify the check digits in the machine-readable lines.

The generated photo

This is the newest problem. In 2024, reporters showed a website selling realistic AI-generated photos of ID cards for about 15 dollars each, complete with a convincing background of a carpet or a kitchen table. Images like that are made to be uploaded. A form that accepts any file from the photo library has no way to tell that the card never existed.

What live capture changes

With live capture, the verification page asks for camera access, shows a frame for the card, and takes the pictures itself. The image never passes through the photo library, so there is nothing to choose and nothing to upload. Several things follow from that:

  • The card has to be physically present. A borrowed picture cannot be placed in front of the lens without becoming a photo of a screen, which looks different from a real card.
  • The capture is tied to the moment. The document and the face are recorded in the same short session, so the face match compares a live person with the card they are holding now.
  • Image quality goes up. The page waits until the card is sharp, well lit and fills the frame before it captures. Fewer honest users fail because of a blurred or cropped picture.
  • The check digits get a clean read. A straight, sharp image of the code lines can be read reliably, and every check digit verified. Edits that slip past the eye do not slip past the arithmetic.

What live capture does not stop on its own

Being honest about the limits matters. Live capture raises the bar, but three kinds of attack still need their own defences:

  • A photo or screen held up to the camera. This is a presentation attack. It is answered by liveness detection: asking for a movement and checking the frames for the texture and reflections of paper or a screen.
  • A fake camera feed. Software can pretend to be a camera and play a prepared video into the browser. This is called an injection attack. It is harder to pull off, and good systems look for its signs in the video itself.
  • A real person with a real card, acting for someone else. No camera can tell why someone is verifying. That is a matter for your own rules: limits, monitoring and follow-up on unusual behaviour.

A sensible stack combines all of these: live document capture, check-digit verification, liveness, face match, and your own business rules on top.

Does live capture hurt conversion?

It is a fair worry. Every extra step loses some users. In practice, live capture often converts better than uploads, for two reasons. First, the user does not have to leave the page, find a photo, or take one in a separate camera app. Second, the page gives instant feedback, so a bad picture is retaken on the spot instead of failing a review hours later.

What hurts conversion is a confusing flow. Keep it short: a clear frame for the card, one instruction at a time, and a visible sign that the scan is working. If the user starts on a computer, show a QR code so they can continue on their phone, where the camera is better.

How lumex.id handles it

lumex.id accepts live capture only. There is no upload button. The verification page opens the camera in the phone browser, frames the ID card or passport, and shows a moving scan line once the card is clear, so the user knows the scan is happening. The code lines are read and every check digit verified. The user then turns their head once for the liveness check, and the face is matched against the document photo. If they start on a computer, a QR code hands them over to their phone.

Your server receives approved or declined with reasons, the document fields and the face match score. See the developer reference for the request and webhook format, or the guide to how online ID checks work for the full picture.

Frequently asked questions

Can I let users upload a photo if their camera does not work?

You can, but it reopens the gap live capture closes. A better fallback is the QR hand-off: the user continues on their phone, where the camera almost always works.

Does live capture need an app?

No. Modern phone browsers can open the camera directly from a web page, so the whole check runs in the browser without installing anything.

Are images stored after the check?

With lumex.id, selfie frames are never returned and are deleted once the result is decided. Document images are deleted too, unless you have switched on document copies, which are held for 24 hours for you to download.

Can AI-generated ID images pass a live check?

A generated image is a file, and live capture does not accept files. To use it, someone would have to display it on a screen in front of the camera, which is exactly what liveness detection and check-digit verification are there to catch.

Add ID verification to your site this week.

Live ID scan, liveness and face match in the phone browser. From $19 a month with 50 checks included.

More from the blog