Azimut Logo
BankingGovernment

Cash deposit via CDM, integrated in one SDK call

Banks integrating mixed-vendor CDM fleets call a single SDK method. The platform handles device protocol, note validation, and error states — then posts to the bank's core banking backend.

How the cash deposit 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.

1

Customer identification

Account lookup via card swipe or biometric verification. SDK manages the session from this point forward.

2

Cash insertion

SDK accepts bills and cheques, counts denominations, handles multi-note errors, and prompts for reinsertions without the application managing device state.

3

Amount confirmation

Real-time count displayed before the customer confirms. SDK holds the session in a safe state until confirmed or cancelled.

4

Transaction posting

SDK sends the confirmed amount to the core banking API. Handles success, failure, and partial-credit states — and retries where the network spec allows.

5

Receipt and session close

SDK triggers the receipt printer, logs the transaction, and cleanly ends the device session.

What the SDK handles

Hardware

  • Cash acceptor
  • Cheque scanner
  • Receipt printer
  • Biometric scanner (optional)

Integrations

  • 1LINK interbank clearing
  • RAAST instant payments
  • Core banking APIs

Deployed with

Production deployments running cash deposit flows in real environments.

Bank Alfalah
BankingPakistan

Bank Alfalah

Cash and cheque deposits at Digital Branch kiosks.

Meezan Bank
BankingPakistan

Meezan Bank

Cash deposits via CDMs.

Diamond Trust Bank
BankingKenya

Diamond Trust Bank

Cash deposit flows via self-service kiosks.

Bank Al Habib
BankingPakistan

Bank Al Habib

Cash and cheque deposits via CDMs.

Related solutions

From the blog

Ready to deploy cash deposit on your kiosks?

Talk to our team about your hardware, integration requirements, and deployment timeline.