Roommatik Identity verification
Document reading, ready to embed
OCR reading of identity documents and biometric verification, ready to embed in your application, your kiosk or your check-in flow. The identity component that integrators and chains add to their own solution.
We show you the component and how it integrates into your stack. No commitment.
From capture screen to verified data, integrated in days
Any application that registers people needs to confirm who they are: read their document, structure their data and, where appropriate, check that the person registering is the genuine holder. Building that piece from scratch —reliable reading of documents from several countries, biometric capture, handling of sensitive data— takes months of development and is not the core of your product.
Manual data entry, unstructured document photos and half-finished checks don’t hold the process together: they cause errors, drag out registration and leave your solution exposed when identity really matters.
Roommatik‘s identity verification is that piece already solved: it reads the document, structures the data and checks it against the person presenting it, ready to embed in your application, your kiosk or your flow. You integrate; we provide the identity.
What it is
What is identity verification?
Identity verification —also known as KYC, from the English «know your customer»— is the process by which the identity of the person registering is confirmed. The user photographs their document —identity card, residence card, passport or others, from various countries— and, where appropriate, an image of their face confirms that they are the document’s holder.
From that reading, the component structures the document’s data and returns it to your application already ordered and ready to use. Your product receives the complete, verified information; the user only presents their document once.
The same component works inside a self-service kiosk, in an online check-in flow or in any application you embed it into. Whatever the environment, the verified data is delivered in the same format.
You have probably seen it under other names: document verification, user identification, identity control or KYC. They all describe the same thing: checking identity reliably and delivering the structured data without manual work.
How it works
From document to verified data in three steps
Document capture
The user photographs their document —identity card, residence card, passport or others— from the kiosk, their mobile or the application where the component is embedded. Front and back in a single operation.
OCR reading of the data
OCR reading of the document structures the fields: full name, document number, date of birth, nationality and expiry date, without manual transcription. The data is returned to your application ready to use.
Biometric check
When your data protection policy allows it, an image of the face confirms that the person registering is the document’s holder. The verification result returns to your flow so that you decide how to proceed.
No photocopies, no paperwork and no typing data by hand.
A complete identity component, ready to integrate
OCR document reading
Reads every visible field of the document: identity card, residence card, passport and residence permit, from various countries. The data reaches your application structured and free of transcription errors.
Biometric verification
An image of the face confirms that the person registering is the document’s holder. Enabled according to each client’s data protection policy; if you prefer not to process biometric data, it works just the same as document verification.
Structured data output
The component returns the document’s data already ordered, in a stable format, so that your application consumes it with no parsing logic or double captures.
Compliance and data handling
Designed to handle sensitive data carefully: it collects only what is needed and keeps the information only for as long as necessary, without accumulating paper or photocopies that must later be safeguarded.
Compliance use cases
Among the supported flows, it can generate the Spanish traveller registry report from the data read. It is one more capability of the component, not its only purpose.
Flexible integration
The same component is embedded in a self-service kiosk, in an online check-in flow or inside the application your team is already building.
Privacy by design
Identity data, only for as long as needed
Verifying identity means handling sensitive data. Roommatik‘s identity verification is designed to collect only what is needed, keep it only for as long as necessary and return it to your application in a clear format.
Only what is needed, for only as long as needed
Only the data your flow requires is captured, and it is kept only for the necessary period. No accumulated photocopies or signed sheets to safeguard afterwards.
Biometrics under your control
The face check is optional and is enabled according to each client’s data protection policy. If your legal team prefers not to process biometric data, the component works just the same as document verification.
Reliable verification doesn’t require keeping more than needed: it identifies the person, returns the data and doesn’t accumulate information it doesn’t need.
What you gain by integrating identity already solved
Embedding Roommatik‘s identity verification is not just about meeting a requirement: it means adding a proven piece to your product without diverting your team from the core of what they build.
For the integrator or chain
- Identity ready to integrate, without building document reading or biometrics from scratch.
- Structured data in a stable format: less parsing logic on your side.
- The handling of sensitive data already thought through, without you having to design it.
- The same component on kiosk, mobile or your own application, without rewriting it per channel.
For the end user
- Identifies themselves once, with their mobile camera or at the kiosk.
- No waiting while someone types in their document.
- Their data, handled only for as long as needed and with biometrics under control.
- A faster registration, within the application they are already using.
Why Roommatik
Not all identity components go equally far
On paper, almost all of them read a document. The differences appear when you look at what they deliver afterwards and how much work they leave on your side when it comes to integrating them.
What’s usual in the sector
- They read the document, but return unstructured data that you have to normalise by hand.
- Biometrics from a different provider: two services that you have to stitch together yourself.
- An SDK designed for a single channel: it doesn’t fit equally on kiosk, mobile and application.
- The handling of sensitive data and the retention periods are left on your shoulders.
With Roommatik
- OCR reading and biometrics in one component, with structured data output.
- The verified data is returned ready to consume, with no double capture.
- The same component on the kiosk, in online check-in and inside your application.
- Data collected to the minimum and kept only for as long as needed, by design.
Proven in production, in Roommatik‘s kiosks and check-in
The endorsement of this component is that Roommatik uses it inside its own products. The same document reading and the same biometric verification that we offer for integration work every day in the self-service kiosks and in the online check-in of the platform itself. It is not a laboratory project: it is the piece that already identifies real people in real operations.
That means it arrives already road-tested: capture in difficult lighting conditions, the reading of documents from various countries and the handling of sensitive data come proven before landing in your product. You start from a validated base instead of discovering the edge cases on your own.
And it is embedded where your solution already receives the user —kiosk, mobile application or check-in flow— without forcing you to change how you work: the component fits into your stack, not the other way round.
Three ways to integrate it
In a self-service kiosk
Embed document and biometric verification into your kiosk’s self-service flow. It’s the same piece Roommatik uses in its own kiosks, with no staff in attendance.
In your online check-in
Add verification to your application’s pre-arrival process. The user identifies themselves beforehand, and your flow receives the data already checked when it needs it.
In your application
Bring verification into the product you already build. The document is read, checked and the data returns to your application in a stable format, within your own flow.
Proven in Roommatik‘s products
More than reading a document: a component that already works in production
Roommatik‘s identity verification is not a laboratory piece: it is the very same one that operates inside the platform’s own online check-in and self-service kiosks, identifying real people every day.
That’s why it arrives ready to embed in your solution. And where your product needs to send that data to other systems, it relies on the integrations already available so it reaches where it needs to go.
What we’re usually asked before integrating
What is Roommatik‘s identity verification?
It is a B2B component that reads identity documents via OCR and, where appropriate, uses biometrics to check that the person registering is the holder. Integrators and chains embed it into their own application, kiosk or check-in flow: the user photographs their document —identity card, residence card, passport or others— and the component returns the structured, verified data. It is also known as KYC.
Which documents can it read?
Identity card, residence card, passport and residence permit, from various countries. OCR reading recognises the document’s visible fields, so the data reaches your application complete and free of transcription errors.
How does it integrate into my application?
The component is embedded into your product’s flow —kiosk, mobile or application— and returns the document’s data already structured along with the verification result. It is the same piece Roommatik uses in its own kiosks and check-in, so it arrives proven in production. In a demo we show you how it fits into your stack.
Is the biometric check mandatory?
No. The face check is optional and is enabled according to each client’s data protection policy. If your legal team prefers not to process biometric data, the component works just the same as document verification.
Does it work for the Spanish traveller registry?
Yes, it is one of the supported compliance use cases: with the data read from the document you can generate the Spanish traveller registry report. It is one of the component’s capabilities, which is also used in other identity flows unrelated to that regulation.
How is the user’s data handled?
The component collects only the data needed for your flow and keeps it only for as long as necessary, designed for the handling of sensitive data. Without accumulating photocopies or signed sheets that must later be safeguarded.
How does the data reach other systems?
The component returns the verified data to your application in a stable format, ready for you to send it wherever you need. Where it is necessary to connect with other platforms in the sector, it relies on the integrations already available. See the full list of integrations.
It fits into your stack
Roommatik‘s identity verification doesn’t force you to switch systems: it is embedded into the application, kiosk or flow you already have. And where your product needs to send the verified data to other platforms, it relies on the available integrations, with no manual intervention.
Compatible with more than 50 platforms and providers in the sector.
Add identity verification to your product
OCR reading of the document, biometric verification and structured data output, ready to integrate into your application, your kiosk or your flow. We show you the component and how it fits into your stack in a demo. No commitment.