The CDM middleware layer your dev team shouldn't be writing
Banks deploying multi-vendor cash deposit machines use Azimut SDK to integrate every device through a single API — and connect to 1LINK or RAAST without building a separate payment integration layer.
What the SDK handles for banking deployments
Pre-built integrations and managed runtime features so your team writes application logic, not infrastructure.
Pre-built CDM drivers
Cash acceptors, cheque scanners, and receipt printers — all pre-integrated. Swap hardware models by updating a driver, not the application.
Payment network connectivity
Deployed integrations include 1LINK and RAAST. The SDK connects kiosks to national clearing infrastructure through the same unified API as the physical devices.
Real-time CDM health monitoring
Device fault detection, cash jam alerts, transaction error rates, and operational dashboards. Operations teams see faults before customers do.
Security-audited platform
The SDK has undergone a formal security overhaul addressing vulnerability reports. Banking environments get an audited, patched runtime.
Customers
Deployed with
Production deployments in banking environments across multiple regions.
Bank Alfalah
Cash and cheque deposits, and bill payments via CDMs at Digital Branch kiosks.
Meezan Bank
Cash deposits via CDMs integrated through the SDK.
Bank Al Habib
Live production cash and cheque deposits via CDMs, with active operational support.
DIB Bank
Completed CDM deployment for cash deposit self-service flows.
Faysal Bank
Cash deposits via CDMs integrated through the SDK.
Banque Atlantique
Cash and cheque deposits via self-service kiosks.
Go deeper — use cases
From the blog
Ready to build on banking infrastructure that's already proven?
Talk to our team about your hardware requirements, deployment size, and integration timeline.
