Document and receipt printing for self-service kiosks
Thermal receipt printing and document output — managed through a single SDK layer across banking, telecom, government, and retail kiosk deployments.
This workflow covers document and thermal receipt output. Card personalisation and SIM issuance use separate devices, stock controls and issuer or carrier approval steps; a successful print job does not activate a card or SIM.
How it works
How the document & receipt printing flow works
The SDK handles supported device operations. Your application coordinates the workflow with the services responsible for identity, payment and account decisions.
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. A retry policy must account for an uncertain print outcome to avoid duplicate documents. 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 — link each print outcome to its transaction record
- Fleet monitoring — report supported printer health signals
- Fault handling — respond to the paper and device states exposed by the printer
- Core banking and BSS backends — application-provided transaction context for document generation
- Document template engine — structured payloads, not raw printer commands
- Receipts, invoices, queue tickets, KYC slips, and account summaries across all sectors
Customers
Deployed with
Production deployments running document & receipt 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.
Related solutions
From the blog
Ready to deploy document & receipt printing on your kiosks?
Talk to our team about your hardware, integration requirements, and deployment timeline.
