lumex عربي Get started
Buying guide

Choosing an identity verification provider: 7 questions to ask before you sign

· 6 min read

Every identity verification provider promises the same things: fast checks, high accuracy, global coverage. The differences only show up after launch, when real users with real phones and real cards start going through the flow. These seven questions bring those differences out before you sign. They apply to any provider, including us.

The short answer

Ask how the document and face are captured, which documents in your market are actually supported, how liveness works and how it was tested, exactly what data comes back, what you pay per check and for what, where images go and how long they stay, and how much work integration really takes. Then test the flow yourself, on your own phone, with your own ID.

1. Is capture live, or can users upload files?

This is the first question because it decides how much the rest is worth. If the flow accepts a picture from the photo library, it accepts borrowed, edited and AI-generated images, and every later check runs on material you cannot trust. Ask whether the verification page opens the camera itself, whether there is any upload fallback, and what happens when a user starts on a computer. A QR hand-off to the phone is a better answer than a file upload.

2. Which documents in your market are really supported?

"Over 10,000 document types" sounds reassuring, but what matters is the documents your users carry. In the Gulf that means the national ID cards of each country and passports from everywhere, because a large share of residents are expatriates. Ask how each document is read: from the machine-readable code lines with check digits, or only by recognising printed text. Ask what extra fields come back for your local cards. For a Kuwait Civil ID, that means the civil number and the Arabic name, not just the card serial.

3. How does liveness work, and how was it tested?

Ask whether the liveness check is active, passive or both, and what the user is asked to do. Long sequences of movements cost conversions. Ask whether it has been tested against the international standard for presentation attack detection, ISO/IEC 30107-3, and what the rates were for attacks accepted and real users rejected. A provider that cannot explain where it sets that balance has probably not thought hard about it.

4. What exactly comes back to your system?

Get a sample response and read it. You want a clear decision, the specific reasons for any decline, the document fields in a consistent format, and a face match score so you can see how close a decision was. Check that results arrive by a signed webhook you can verify, not only by polling, and that you can fetch any result again later. A vague answer such as "review required" pushes the hardest decisions back onto your team.

5. What do you pay, and for what?

Per-check prices vary widely, and so do the rules around them. Ask:

  • Is there a monthly minimum or an annual commitment?
  • Are abandoned checks charged? What about checks that expire unfinished?
  • Are extras such as document copies or a white-label flow priced separately?
  • Is billing prepaid or invoiced, and what happens when credit runs out?
  • Is there a free test mode that runs the real flow?

Work out the cost at your expected volume, including failed and abandoned attempts, not just the headline price.

6. Where do images go, and how long do they stay?

Identity checks handle some of the most sensitive data there is. Ask what is stored, where, and for how long. The best answer is "as little as possible, for as short as possible": selfies deleted as soon as the decision is made, document images deleted too unless you explicitly ask for a copy, and a clear statement of how that is done. Ask whether the provider is the controller or the processor of the data, and read its privacy policy and biometric notice before you link to them from your own site.

7. How much work is the integration, really?

Ask for the API reference and read it before the sales call. A good integration is one call from your server to create a check, one link to send the user to, and one webhook to receive the result. Look for test keys, clear error codes, retries on webhooks, idempotency for safe retries, and documentation in plain language. If your users speak Arabic, check that the flow itself is fully in Arabic, not just translated buttons.

Test it yourself

No answer to these questions replaces ten minutes with a test key. Run the flow on your own phone, in English and Arabic, with your own ID. Try it in poor light, try it starting on a laptop, and try it with an expired card if you have one. Look at what arrives on your server. You will learn more from that than from any comparison table.

How lumex.id answers

  • Capture: live camera only, no uploads, with a QR hand-off from computer to phone.
  • Documents: passports and national ID cards with machine-readable code lines, every check digit verified. For Kuwait Civil IDs we also return the validated civil number and the Arabic name when it reads cleanly.
  • Liveness: one head turn to the right, plus a passive check on the frames.
  • Results: approved or declined with reasons, document fields and the face match score, by signed webhook and API.
  • Pricing: Standard $19 a month with 50 checks included, then $0.20 per check, prepaid. Unfinished checks that expire are not billed. Test mode is free.
  • Data: selfie frames never returned and deleted once the result is decided. Document copies only if you switch them on, held for 24 hours.
  • Integration: one API call, one link, one webhook, in English and Arabic.

See pricing, the developer reference and the security page for the details.

Frequently asked questions

What is the difference between KYC and identity verification?

Identity verification confirms that a person is who they claim to be, using their document and face. KYC, know your customer, is the wider process a regulated business follows, which can add checks such as sanctions screening and proof of address.

Do I need a provider with manual review?

Manual review can help in edge cases, but it adds delay and cost. With live capture and check-digit verification, most checks can be decided automatically, and a declined user can simply try again.

How long does integration usually take?

With a hosted flow and a webhook, a developer can usually have test checks running in a day. Most of the time goes into deciding what your own site does with approved and declined results.

Can I switch providers later?

Yes, if you keep the integration simple. Store the decision and the fields you need in your own database, not the provider's identifiers alone, and changing providers becomes a small job.

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