Trusted by banks, telecoms, and governments across 4 continents
What the SDK handles so you don't have to
Hardware integration, payment network connectivity, device health monitoring, and session management — the SDK absorbs this entire layer so your team writes application logic, not integration code.
Cash acceptors, dispensers, coin handling, biometric scanners, SIM printers, and PCI card terminals — all pre-integrated. Your team calls SDK methods; the platform handles each device's protocol.
The SDK connects kiosks to backend payment infrastructure — interbank clearing, instant payment rails, and card scheme processing — through the same unified API as the physical devices.
Device enumeration, startup health checks, and session lifecycle are managed by the SDK. Deploying machine 50 is operationally identical to deploying machine 1.
Device health, transaction status, error rates, and alert thresholds are surfaced through the management portal in real time. Hardware faults surface to your operations team first.
Physical SIM purchase, eSIM provisioning, SIM swap, plan changes, top-ups, and biometric KYC — all handled through a single SDK runtime. Deployed across 200+ du kiosks across UAE retail locations.
When a new device model enters the fleet, the SDK gets a driver update. The application code above it stays unchanged — whether the device is a GRG unit today or a different module tomorrow.
Think of it less like a library, more like Android on a phone
The SDK is the base platform that makes everything above it possible — it does not ship as a feature you bolt onto an existing codebase. It replaces the entire hardware integration layer that your team would otherwise have to write, maintain, and rewrite every time a device model changes.
When a bank adds a new cash-deposit machine model, they update an SDK driver. The application code above stays unchanged.
Deployed across industries, adapted to each
The SDK's hardware abstraction layer is the same regardless of sector. What changes is the business logic above it.
Cash and cheque deposits via CDMs, wallet management, bill payments, and account opening — integrated with national payment networks.
10+ bank deployments across Pakistan, UAE, and Africa
New SIM purchase, eSIM provisioning, SIM swap, plan management, top-ups, and biometric KYC — all self-served without a store rep.
200+ du kiosks; deployments across Japan, Africa, and the Caribbean
Invoice generation, payment collection, and document workflows at government service points — built on the SDK by system integrators.
Deployed at PCFC Dubai
Payments, purchasing integration, and fee collection via self-service — the same SDK runtime as banking and telecom deployments.
Deployed in UAE retail and LATAM education
Featured deployments
Three examples across the two largest sectors — telecom and banking — showing what the SDK enables in production.
MTN Nigeria
MTN customers register SIMs, access self-service mobile features, and manage plans via kiosks powered by the SDK — replacing assisted-service workflows at scale.
Read story →du
200+ du kiosks across all UAE retail locations handle new SIM purchase (physical and eSIM), plan management, top-ups, KYC identity checks, and bill payments — without a store representative.
Read story →Bank Alfalah
Bank Alfalah's Digital Branch kiosks accept cash deposits, cheque deposits, and wallet top-ups via the SDK — integrating directly with the bank's core banking backend through a single SDK API layer.
Read story →