Telecom / Banking / Insurance / Marketplaces / Age-restricted services
Identity Verification, Answered by the Chip
Ask who is on the other side of the phone and get an answer the state signed —
without ever holding a copy of anyone’s document.
Why a Photo of an ID Proves Nothing Anymore
If the ID number, the document image and even the signature are already circulating,
asking for them only proves the other side knows how to search.
What already circulates
What the chip proves instead
- The document is genuine, signed by the issuing state, and unaltered
- A live person is holding the phone right now
- That person is the holder: their face matches the portrait inside the chip
- Nothing anyone can find in a leak can stand in for that signature
Flagship use case · Telecom
A Mobile Line in Seconds: Identity → Payment → eSIM
A traveller lands, or a subscriber is at home, and wants a line now. Where the law requires identity to register a line, ID Protekt answers it from the chip — then your checkout and your eSIM platform take it from there.
Identity
ID Protekt reads the chip in the passport or ID card, confirms a live person and matches their face to the chip portrait: holder-bound, level L4.
Payment
Your own checkout charges the plan. The verified identity is already attached to the order.
eSIM
Your platform issues the activation. The line is live before the customer leaves the arrivals hall.
- No store visit
- No plastic SIM, no shipping
- No document photocopies to store
SIM swap and number portability
The swap is the classic account-takeover move: whoever holds the number receives the bank’s one-time codes. Re-verify the holder against the chip before a number moves, and that door closes.
ID Protekt owns the identity step; payment and eSIM provisioning stay in your systems.
How It Works
One question from your backend, one minute on the person’s phone, one answer back.
1. You ask
Your backend asks only what the case needs — “over 18?”, “is this the policyholder?”, or the verified name — with a purpose the person reads before agreeing.
2. They verify on their phone
In the ID Protekt app: one tap on the document’s chip, a live check and a face match against the chip portrait.
3. You receive the answer
Only what you asked, the level reached and a consent receipt id. Never the document, never the selfie.
Developers: how to integrate · Assurance levels: L1 document authentic to L4 holder-bound
Core Use Cases
Each one is a question ID Protekt answers today. Each one replaces a document copy you no longer have to keep.
Age Gating
Betting and gaming, alcohol and tobacco delivery, adult content
The problem: A birth date typed into a form proves nothing; a scanned ID is a liability you must store.
You ask: “Is this person over 18?” (or 21, or 25)
You receive: Yes or no
Never handed over: The birth date, the ID number, the document image
Remote Onboarding & KYC
Banks, cooperatives, fintech
The problem: An agent squinting at a scan cannot tell a forged document from a real one.
You ask: The verified name and document number, holder-bound (L4)
You receive: Data read from the chip the state signed, with the level reached
Never handed over: A document scan or a selfie for your database
Insurance: Policies, Claims, Proof of Life
Insurers, pension funds
The problem: Claims and annual proof of life are where impersonation pays.
You ask: “Is the person in front of the phone the policyholder?” — at sale, at claim, every year
You receive: Yes or no, matched against the state’s own portrait
Never handed over: A copy of the ID; a selfie enrolled years ago
Marketplaces: Verified Sellers
Classifieds, vehicles, real estate, rentals
The problem: Fake sellers drive buyers away from the whole marketplace.
You ask: The verified name of the seller, holder-bound
You receive: The name for a “verified seller” badge — every seller on MiAuto.ec is verified this way before an ad reaches review
Never handed over: The document photo
Account Recovery & Call Centers
Banks, telecom, utilities, any account with value
The problem: Security questions are answered from the same leaks that fuel the fraud.
You ask: “Is the caller the account holder?” before a sensitive change
You receive: Yes or no
Never handed over: Personal data read aloud over the phone
Consent & Regulated Acts
Data authorization, telemedicine, contracts, a company’s legal representative
The problem: Anyone who knows an ID number can tick an “I agree” box.
You ask: “Is the person consenting the holder of the declared ID?”, with the purpose they read
You receive: Yes or no, and a consent receipt id tied to that purpose
Never handed over: A consent nobody can attribute
Built In, Not Bolted On
No document copies to store or leak
You hold answers, not scans. A breach of your systems exposes no ID images.
Biometrics never leave the phone
The face match happens on the device; the API refuses to release the portrait at any tier.
Consent the law can read
The person sees the purpose before agreeing, and the receipt records it — collect only what you need under the LOPDP.
One integration, every channel
Web, your own app or a link sent from a call center: the person verifies on their phone and returns to you.
The person verifying uses the free ID Protekt app. What happens on their side, and what stays on their phone: id.ism.ec.
Put the Chip to Work Before Your Competitors Do
Tell us your use case — telecom, banking, insurance or your own — and we’ll design the verification for it.
🍪 We value your privacy
We use cookies and analytics to understand how you use our site and improve your experience. This includes Google Analytics for tracking site usage.
By clicking "Accept", you consent to analytics tracking. Learn more in our Cookie Policy and Privacy Policy.