Every kiosk transaction ends with a printed record
Receipts, invoices, queue tickets, KYC slips, and account summaries — document printing is a core requirement across every kiosk sector. The SDK manages printer readiness, document generation, job delivery, fault handling, and transaction-level logging through a single stable API.
How the document printing flow works
Every step is managed by the SDK. Your application calls SDK methods and receives results — the device interactions happen inside the platform layer.
Check printer readiness
Before starting a print-required flow, the SDK confirms the printer is online, paper is loaded, and no faults are active. Paper-low and cover-open states are surfaced before the customer reaches the print step.
Build the document payload
The application assembles the document from transaction data — amount, reference, timestamp, account details, or service confirmation. The SDK accepts a structured template payload and handles the rest.
Send the print job
The application calls a single SDK method. The platform handles the attached thermal printer's protocol, command set, and device-specific communication — the application does not need to know the printer model.
Confirm or retry
The SDK returns a job result — success, failure, or timeout. Where the printer spec allows, the SDK retries automatically. Controlled failures are handed back to the application with a clear error state rather than a silent hang.
Log the outcome
Print result — success or failure — is logged against the transaction record and reported to the management portal. Operations teams can see print fault rates per device across the fleet without visiting the kiosk.
What the SDK handles
Hardware
- Thermal receipt printers (multiple vendor families)
- Thermal paper management — low paper and paper-out detection
- Printer health status — online, fault, cutter, cover state
- Print job queuing and session-level retry handling
Integrations
- Transaction logging — every print job linked to a transaction record
- Real-time fleet monitoring via the management portal
- Fault alerting — paper-low and device-fault states surfaced before customer impact
- Core banking and BSS backends — transaction context pulled for document generation
- Document template engine — structured payloads, not raw printer commands
Deployed with
Production deployments running document printing flows in real environments.
du
SIM registration confirmations and service receipts printed across 200+ kiosks. Receipt printing is part of every completed kiosk session on the du network.
Bank Alfalah
Receipts generated at the close of cash deposit, cheque deposit, and bill payment sessions at Digital Branch kiosks.
Bank Al Habib
Live production CDM deployments include receipt printing at session close for every cash and cheque deposit transaction.
Meezan Bank
Cash deposit receipts issued via CDMs. Printer state is monitored as part of the SDK's kiosk health model.
PCFC
Invoice generation and payment confirmation printing at government kiosks, built by Wavetec on the Azimut SDK runtime.
