Separate the transactions that need a person from those that do not
Most counter time in a service hall goes to transactions that follow a fixed rule: print a certificate, submit a form, pay a fee, collect a document. None of these require judgement, and all of them can be completed by the applicant directly, provided the terminal can read identity and print an official receipt.
The counter then does what it is actually for: verifying identity where the law requires a human, handling exceptions, and advising on cases that do not fit a rule.
A configuration that covers a typical hall
- Entry terminals. 43-inch or 19-inch units reading identity documents, capturing the service required and issuing a queue number.
- Form terminals. Larger-format units where the applicant completes a form on screen with field-level validation before submission.
- Payment. A terminal with the payment provider’s certified module, positioned so the applicant can reach the card or QR reader comfortably.
- Document collection. A terminal that reads a reference number, confirms identity and dispenses the printed document or a collection slip.
- Calling displays. Sized to the hall — 43-inch for a mid-size area, 55-inch and above for a large concourse.
- Information display. Opening hours, service catalogues, required documents and process explanations.
Identity reading is the critical component
Everything else in the hall depends on the terminal being able to read the identity document reliably. In practice this is where projects succeed or fail, so it is settled first:
- Which document types must be read — national ID card, residence permit, passport, driving licence.
- Whether the reader must also capture a photograph or a signature.
- Whether the legal framework requires the identity check to happen at a staffed counter rather than at a terminal.
- What the fallback is when a document cannot be read.
We integrate the reader module specified by the project, and work with the identity-service provider on driver and protocol questions.
Payment integration
Where the hall collects fees, the payment module must be the one certified for the market — which in most cases means integrating the payment provider’s own device rather than building a payment function into the kiosk. That device is mounted in the enclosure in a position the applicant can reach, and its status is visible from the terminal application.
We work with the payment provider or the acquirer to confirm the mounting and the interface before production, because changing the payment device afterwards means changing the housing.
On-screen forms with field-level validation are the single biggest quality gain over paper. An applicant who enters a number in the wrong format is told immediately rather than after the form has reached a counter. Multilingual prompts, larger type and a defined timeout for abandoned sessions all make the terminal usable across a wider population.
Procurement and documentation
Government projects usually run through a tender. Certification and test documentation is configuration-specific, so we confirm what applies to your build during quotation rather than publishing a generic list — see our Certifications page. For tenders requiring a factory audit or sample evaluation, we can host a visit, run a video walkthrough of the line, or supply an evaluation unit with a 7–14 day lead time.
What we need from you to quote
- The services the terminals must handle, and the identity document types involved.
- The service platform and whether its vendor is already engaged.
- Payment requirement, and which provider or acquirer is specified.
- Screen size preference or viewing distance.
- Number of positions, and the rollout schedule.
- Destination country and any certification requirement in the tender.
