"All of the sprints were completed on schedule and on budget. We highly recommend RaftLabs!"
Charles E.
Entrepreneur at Aggie Technologies
Kiosk Software Development Services
Kiosk software for one unattended transaction that recovers.
We build a bounded self-service workflow around session reset, accessibility, identity, catalogue or booking lookup, scanning, peripherals, payment handoff, printing or dispensing, offline state, remote configuration, health monitoring, support, and reconciliation. The operator, hardware and payment vendors, security teams, and advisers own identity, age, payment, safety, accessibility, privacy, regulatory, and service decisions.
Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.
Trusted by
The brief
Start with what is not working.
Good software decisions begin with the constraint, not a list of features or a preferred technology.
01
Does a disconnected scanner, printer, terminal, API, or network leave the public screen stuck with no safe recovery path?
02
Can operations see which unit, application version, peripheral, session, transaction, receipt, and backend record belong to an incident?
Plain answer
Kiosk software runs a bounded self-service transaction on managed hardware, resets each public session, coordinates peripherals and backend systems, handles offline and failure states, and reports fleet health remotely. Compatibility must be proven on target devices. RaftLabs scopes one device profile and workflow first.
What to remember
- Session reset, privacy, and accessibility are designed in from the start; a shared device is not a phone.
- Transaction and offline state are core: the payment completing while the kiosk prints an error is the failure mode.
- Peripheral and backend adapters isolate the hardware mess from the application logic.
- Fleet monitoring and support ship with the product; one kiosk is a project, many kiosks are an operation.
- Offline payment acceptance is only possible when the provider, terminal, market, merchant account, certification, risk settings, and transaction type explicitly support it.
The payment completed. The kiosk printed an error.
The terminal approved the charge, the printer disconnected, and the kiosk retried the whole transaction when the user tapped again. Operations saw two backend records and no usable receipt. An unattended flow needs explicit device and transaction states, idempotency, recovery, session cleanup, and remote evidence.
Adjacent device and transaction evidence
- offline-capable sync utility
- Under 10 MB
- Gas-station operations case
The mobile POS case proves payment software delivery, while the gas-station operations case demonstrates a lightweight offline-capable edge utility. Neither was a public kiosk. These examples do not guarantee hardware, peripheral, payment, certification, uptime, unattended operation, accessibility, security, or fleet outcomes.
The first decision is not what to build.
It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.
- 01
Buy
Choose a maintained product when it handles the core workflow and the remaining gaps can be solved with configuration, a connector, or a small process change. Paying for software you do not have to maintain is often the better trade.
- 02
Repair
Keep the existing product when users still get value from it and the code can be understood safely. Start with evidence: where the code lives, how the data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.
- 03
Build
Own the system when the workflow shapes margin, customer experience, speed, or a product customers pay for. Start with one complete path and the system connections that path cannot work without.
- 04
Wait
Do not turn a changing policy into permanent software. Stabilise the rules, name the workflow owner, and measure the cost of the current process before paying for a product.
Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.
Build a kiosk when one self-service transaction, target device, environment, and support model are already defined.
A tablet web page is not automatically an unattended system; the device, application, peripherals, backend, fleet, and operations form one product.
A fit
A repeated self-service flow benefits from fixed hardware and must run with limited staff intervention across one or more locations.
Operations, IT, security, privacy, accessibility, payments, facilities, support, and product owners can approve release.
Target hardware plus representative users, disconnects, peripheral faults, reboots, abandoned sessions, transactions, and support cases are available.
Not a fit
A responsive web page on a staffed tablet covers the need, or hardware, environment, workflow, and operational ownership are still unknown.
The request assumes an operating system, terminal, reader, printer, scanner, enclosure, or vendor works without device-level proof.
The operator expects software alone to guarantee uptime, accessibility, identity, payment, safety, security, compliance, or labour savings.
Choose the interface by the operating environment
| Need | Best fit | Primary boundary |
|---|---|---|
| Personal device with a signed-in user | Mobile or web app | User-owned device, browser or app lifecycle, account, and network |
| Staff-operated fixed terminal | POS or staff workstation | Trained operator, supervised peripherals, shift controls, and support |
| Public unattended self-service | Kiosk system | Session isolation, managed device, peripherals, failure recovery, fleet health, and staff fallback |
| Telemetry and control across embedded assets | IoT platform | Provisioning, device identity, data, commands, fleet state, updates, and operations |
Scope
What belongs in one unattended transaction
Session, privacy, and accessibility
Start from a clean state, state the task and limits, support required language and accessibility modes, minimise data, time out safely, confirm cancellation, clear local and visible personal information, and prevent the next user from seeing prior state.
Managed device and application lifecycle
Configure supported single-purpose mode, auto-launch, health check, application and operating-system version, signed update, maintenance window, rollback, reboot, storage limits, remote configuration, logs, and authorised service access on target hardware.
Peripheral and backend adapters
Isolate scanner, printer, terminal, reader, camera, dispenser, or sensor drivers from the core workflow. Track connection, readiness, job, acknowledgement, error and recovery, then reconcile each device event with the backend record.
Transaction and offline state
Use stable session and transaction keys, explicit state transitions, local encryption where approved, bounded offline operations, retry without duplication, confirm backend status, issue receipts only from known state, and route ambiguity to staff.
Fleet monitoring and support
Show unit, site, app and OS version, connectivity, peripheral health, queue age, storage, restart, update, transaction and reconciliation failures. Alert named owners and provide safe staff intervention, evidence, recovery, and escalation.
How it works
From target hardware to one recoverable self-service workflow
- Phase 101
Define transaction, device, and ownership
Choose one use case, environment, users, session, hardware profile, peripherals, backend systems, offline limits, accessibility, support model, owners, risks, and acceptance measures.
- Phase 202
Prove hardware and failure states
Test exact devices, operating-system builds, drivers, SDKs, payment certification, scanners, printers, network loss, power loss, idle reset, accessibility, tamper cases, remote management, and vendor support.
- Phase 303
Develop the bounded kiosk system
Implement session state, managed mode, application flow, peripheral adapters, backend integration, approved payment handoff, offline behaviour, reset, role access, logs, monitoring, update, recovery, and reconciliation.
- Phase 404
Soak test, release, and hand over
Run repeated and adverse sessions on target hardware, test accessibility, payments, peripherals, disconnects, reboots, updates, support, fleet alerts, reconciliation, rollback, training, and staged rollout.
Risk
What the kiosk contract must settle
- Exact hardware
- Operating-system name is not enough. Confirm model, build, drivers, ports, power, enclosure, cooling, orientation, peripherals, SDKs, certifications, device management, supply, warranty, and vendor support.
- Public session
- Protect the previous user's data, constrain navigation and input, prevent unsafe system access, minimise retained information, handle abandonment, reset visibly, and provide accessible staff help.
- Payments and identity
- Providers and qualified advisers own merchant, payment, identity, age, privacy, security, regulatory, liability, and evidence decisions. Implement only approved certified paths and operational controls.
- Unattended recovery
- Network, backend, terminal, scanner, printer, dispenser, storage, application, operating system, and power will fail. Define safe behaviour, reconciliation, remote evidence, alert, restart, rollback, and staff fallback.
What it costs
Every project starts at $10000.
The first phase covers one bounded self-service workflow, with session reset, accessibility, and the backend adapters it needs.
Starting investment
Starts at $10000
Start with the queue or lookup where staff time costs you the most. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.
Related services
- 01
IoT Development
Build provisioning, telemetry, commands, fleet state, updates, monitoring, and device operations.
- 02
Custom Software Development
Create the backend and operating workflow when maintained products cannot fit.
- 03
Payment Integration
Implement provider-approved payment, webhook, settlement, refund, and reconciliation paths.
- 04
Restaurant Automation
Connect order, kitchen, inventory, supplier, labour, payment, and reporting workflows.
Proof
What clients say about working with RaftLabs
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.
I genuinely feel they care about where we're trying to take it.
Aaron McGoona
Founder, TicketStop
Work with us
Bring the target hardware, self-service flow, environment, and failure cases.
Share device models, operating systems, enclosure, peripherals, payment provider, backend, connectivity, accessibility, privacy, session limits, deployment, fleet, support, and owners.
- Scope and cost agreed before work starts. No surprises. No obligation.
- Working prototype within 3 weeks of kickoff.
- Pay by milestone. You see progress before each invoice.
- 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
- All conversations are NDA-protected.
Common questions
A focused kiosk release may include session reset, managed device mode, touch-first flow, accessibility, identity or booking lookup, scanning, payment handoff, receipt or label printing, offline state, remote configuration, health monitoring, update and rollback, support tools, audit, and reconciliation. Scope depends on the exact hardware and environment.
We confirm the exact model, operating-system build, enclosure, display, ports, drivers, SDKs, scanner, printer, terminal, camera, reader, network, remote-management agent, certifications, and vendor support. A listed operating system or past peripheral category does not guarantee another device. Target hardware is tested before production scope is locked.
Only if the selected payment provider, terminal, market, merchant account, certification, risk settings, and transaction type explicitly support it. The provider and operator define limits, authorisation, storage, settlement, reversal, and liability. We implement and test the approved path; we do not promise offline acceptance or PCI compliance by software alone.
Define safe local state, user message, retry, timeout, cancellation, receipt, backend idempotency, reconciliation, session cleanup, application restart, device reboot, remote alert, and staff fallback for each step. Never claim success without confirmed state, and never expose the prior user's information after reset or recovery.
The grease-on-PCs frame: commercial hardware fails in hostile environments. Grease and commercial PCs do not get along, so budget industrial hardware where the environment demands it. The peripherals-are-the-cost-driver frame: payment devices, scanners, RFID, cash handling, offline operation, EMV and PCI compliance drive both cost and complexity. The cost-driving questions vendors ask first: cash, card, NFC, bill-recycler? Dispensing change? Peripheral devices? Offline-mode operation? Reporting and admin requirements?
Kiosks are a fleet: remote monitoring, diagnostics, content pushes, MDM provisioning matter more than per-unit software polish. Plain web tech can be enough for the application layer; the systems knowledge of the market matters more than the stack. TCO math: hardware plus software licensing plus maintenance plus power. Define uptime and transaction-time targets in the contract, and prefer modular designs that extend kiosk lifespans.
A first release covers one device profile, self-service flow, peripheral set, backend integration, managed mode, offline and recovery states, remote configuration, monitoring, reconciliation, and handover. Payments, identity devices, several hardware models, dispensing, certification, or large fleets increase scope. Request a 30-min call and we will scope your release and give you the number.