Skip to main content
Azimut SDK

Azimut SDK Platform

Build self-service kiosk softwarewithout writing device drivers

Azimut SDK connects your kiosk web app or native application to supported hardware through one JSON API. Use it to accept cash, capture identity documents, print receipts or issue SIMs.

Request a DemoSee Customer Stories

How it fits together

Azimut SDK, Weave, middleware and Satellite: product roles

Azimut is the brand used on this website. Your app stays on top and your existing systems stay underneath; each part of the platform handles one layer in between.

Your app

Android, iOS or web

Weave

Mirror or embed your app

Azimut SDK

Every device, one JSON API

  • Cash
  • ID
  • Print
  • Card
  • Scan

Azimut middleware

REST · SOAP/XML · MQ · SFTP

Your systems

Billing · CRM · KYC · archives

Satellite · fleet health & releases
Your app runs on the kiosk through Weave. Azimut SDK connects it to cash, identity, printing, card and scanning devices. Azimut middleware connects the kiosk to your existing systems. Satellite monitors and updates the whole fleet alongside.

  • Weave

    Brings your app to the kiosk

    Weave is a feature of Azimut SDK. It runs an existing Android, iOS or web app natively on self-service kiosks, by mirroring app changes into the kiosk app or embedding the app on a device inside the kiosk. Hardware stays in a Windows enclave under Azimut SDK.

    How Weave works

  • Azimut SDK

    Connects kiosk apps to hardware

    The hardware middleware. It connects the kiosk application to supported cash, document, identity, printing and issuance devices through a JSON API, while the application and its business services own the customer journey and transaction decisions. Start with the kiosk software developer guide and configuration evidence, or read what kiosk software does for how middleware differs from app lockdown and fleet tools.

  • Azimut middleware

    Connects the back end

    Sits between the kiosk and the operator’s systems and translates each request — REST for modern services, SOAP/XML and message queues for legacy billing and CRM, and SFTP for document archives — so legacy back ends work with a modern frontend. Each integration is confirmed during scoping.

    See it for telecom

  • Satellite

    Supports fleet operations

    The device-management product for fleet visibility, supported diagnostics and application releases. Its Windows, Linux and Android scope describes fleet management; it does not establish SDK peripheral compatibility on those operating systems.

    Satellite’s kiosk management software and access controls
Use the supplied runtime release and its reference to establish the supported interface, rather than assuming an older article describes the current package or a compatible version. The site’s contact footer identifies Wavetec FZCO. Confirm the contracting entity, product inclusions, licensing and support responsibilities in your proposal. Review deployment, security evidence and buying requirements

Trusted by banks, telecoms, and governments across 4 continents

du
Virgin Mobile
Rakuten Mobile
Bank Alfalah
Meezan Bank
Airtel
MTN
Axian Telecom
Digicel
Cable & Wireless
Vodafone
Diamond Trust Bank
Bank Al Habib
Banque Atlantique
PCFC
Sharaf DG
Asiacell
Blue Jays

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.

Pre-Built Drivers for the Full Hardware Stack

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.

Payment Network Integration, Not Just Hardware

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.

New Kiosks Go Live Without Per-Machine Setup

Device enumeration, startup health checks, and session lifecycle are managed by the SDK. Deploying machine 50 is operationally identical to deploying machine 1.

Your Ops Team Sees Every Fault Before Customers Do

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.

The Full Telecom Self-Service Journey, End to End

Physical SIM purchase, eSIM provisioning, SIM swap, plan changes, top-ups, and biometric KYC — all handled through a single SDK runtime. With Weave, the kiosk runs your own Android, iOS or web app, and Azimut middleware connects it to legacy billing and CRM.

Swap the Hardware Model, Keep the Application

When a new device model enters the fleet, the SDK gets a driver update. The application code above it stays unchanged — swap hardware models without touching application logic.

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.

The SDK API is JSON over HTTP, so the same integration works from .NET, JVM, Python, or JavaScript — no per-language library, no vendor DLL. Explore the SDK.

For day-to-day fleet operations, explore Satellite remote device management. Monitor Windows, Linux and Android devices, investigate application issues and manage supported updates across your sites, with dedicated controls for self-service kiosk fleets.

Architecture
Your Application / Business Logic
↕   Azimut SDK API
SDK Middleware — drivers, session mgmt, monitoring
↕   hardware protocols
Physical Devices — cash, scanner, printer, terminal, SIM

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.

Banking

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

Telecom

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

Government & Ports

Invoice generation, payment collection, and document workflows at government service points — built on the SDK by system integrators.

Deployed at PCFC Dubai

Retail & Education

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
TelecomNigeria

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
TelecomUAE

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
BankingPakistan

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

Ready to stop writing device drivers?

Talk to our team about your deployment — hardware requirements, fleet size, integration timeline.

Get in Touch