Merchant Kiosk and Backoffice Platform

Problem and Context

• Browser-based merchant flows needed direct control of local devices without unsafe plugin patterns.
• Field operation constraints required offline tolerance and robust recovery behaviors.

Built

• CefSharp bridge from portal JavaScript to local camera, scanner, printer, and media workflows.
• ffmpeg transcoding, resumable FTP uploads, integrity checks, and REST metadata pairing.
• ASP.NET MVC 5 backoffice with Castle Windsor, Kendo UI, FluentValidation, and EF6 repository/UoW patterns.

Architecture

• Two-screen kiosk model separating portal and media/camera display.
• Configuration-driven behavior for language, device, and media settings.
• Shared infrastructure for auth, validation, localization, and error handling.

Integrations

• CefSharp JS bridge to camera/scanner/printer workflows.
• FTP/media pipelines with ffmpeg and REST metadata services.

Reliability, Security, and Operations

• Offline caching and sync recovery for kiosk operation continuity.
• Self-update/restart guards, single-instance controls, and local+server alerting.

Operations

• Offline advert caching and sync.
• Self-update/restart, disk-space guard, single-instance guard, TLS enforcement.
• Local logs and server-side alerts for upload and sync failures.

Technology Stack