Get your new customer in within seconds, not minutes.
Verification starts and ends inside your app. No branch visit, no waiting, nowhere else to send the user.
- Four steps
- ID card, chip and face verified in one session
- One SDK
- From install to production in a single integration
- Four platforms
- iOS, Android, Flutter and React Native
- Türkiye
- Built locally, data processed locally
Industries
Who uses it?
Anywhere identity has to be established inside the signup flow.
-
01 · Banking
Banks and fintech
Identity checks inside remote onboarding.
-
02 · Crypto
Crypto exchanges
Verification at account opening and limit upgrades.
-
03 · Public
Public and regulated bodies
Identity checks in application and service processes.
How it works
Four steps for the user, that is all.
Every step says what to do, so nobody drops out halfway.
-
Frame the card
Identity details are read automatically.
-
Flip the card
The remaining details are completed.
-
Hold it to the phone
Identity data and the photo come from the chip.
-
Show your face
A liveness check confirms the cardholder.
Why change
You already know where applications are lost.
The moment the identity step sends a user out of your app, the application leaves too.
The branch and paperwork route
- The user is sent to a branch or an appointment
- Applications wait for business hours
- Details are typed by hand, with room for error
- The longer it takes, the more applications are abandoned
Inside your app
- The user never leaves the signup flow
- Verification works at any hour
- Identity details come from the card and the chip
- The application resolves in the same session
Compliance and security
Have the answer ready before the auditor asks.
The duty to verify identity sits with the regulated institution itself, under BDDK, MASAK or SPK. Our job is to give you the infrastructure and the record you lean on while meeting it.
-
Audit trail
Every session is logged: which step, which result, which timestamp. You pull the record an audit asks for from one place.
-
Identity from the chip
Details come from the ID card’s chip, not from what the user types. No manual entry, no checking by eye.
-
Processed in Turkey
Development and data processing both happen in Turkey. The cross-border transfer question under KVKK never reaches your agenda.
Fifteen minutes is enough.
We show the flow live and work out together how it fits your signup.
Integration
Ready on the platform you build with.
One SDK, four platforms. Put verification wherever it belongs in your signup flow.
- 01
Quick start
Add it, call it, take the result. No extra services to stand up.
- 02
Your own design
Verification looks like part of your product.
- 03
A clear result
When the session ends you see who was verified and with what.
Getting started
No commitment to try it.
See it first, decide after. We are with you through the setup.
-
Free demo
Try the flow on your own device at no cost.
-
Test environment
Work freely through development with a sandbox.
-
Integration support
You do not have to do the setup alone.
-
Direct technical contact
Talk to the team that builds it, not a call centre.
FAQ
Common questions
- How long does integration take?
- Typically one day. Add the SDK and call the flow.
- Which documents are read?
- The Turkish ID card: both sides and the chip.
- Which platforms does it run on?
- iOS, Android, Flutter and React Native, with the same experience on all four.
- Can we try it first?
- Yes. The demo and test environment are free, and there is nothing binding if you stop there.
Demo request
See the flow on your own device.
Leave your details and we will show you.
- A live demo
- A setup that fits your signup flow
- A pricing proposal for your volume
Request received.
We will get back to you shortly.