Skip to main content

Productivity Tips

Edge Computing in Self-Service Banking: Local and Connected Tasks

Published: 05/11/2026

Edge Computing in Self-Service Banking: Local and Connected Tasks

Edge computing places some processing close to the kiosk hardware. A local runtime can handle device communication, application state and selected processing without sending every operation to a distant service. That can simplify the connection between the customer interface and its peripherals.

The design still needs a clear boundary between local work and actions requiring a bank or payment service. A responsive screen or an available cash device does not establish permission to approve a payment, open an account or credit a deposit during an outage.

Decide what can continue without a connection

Start with the customer workflow. Static instructions and selected application content may remain available locally. Identity decisions, account lookups and transaction approval may depend on connected services. Offline payment authorisation, where offered, must follow the payment provider’s approved configuration and operating policy.

Document the behaviour of every interrupted step. If the application cannot establish a safe outcome, show an unavailable or pending state rather than a success message. Physical cash and card outcomes need particular care: cash retained by a device or a card dispensed before a lost backend reply still requires reconciliation.

Preserve the original transaction

Keep an operation reference and record what the device and backend each confirmed. On reconnection, reconcile the original request before retrying a financial action. A queue of local requests is useful only when its replay, expiry, ordering and duplicate-handling rules are agreed with the receiving system.

Test connection loss before submission, after submission and after an acknowledgement. Include restarts and session abandonment. Check that another customer cannot inherit the previous session’s data and that support can identify unresolved outcomes without exposing personal information in diagnostic logs.

Azimut SDK handles supported peripheral integrations, while Satellite provides fleet operations and application-release workflows. Evaluate each with the platforms and permissions required by your fleet. The SDK entry point and deployment evaluation guide help structure that discussion.

Try it yourself

Book a demo

See how Azimut SDK works in your self-service environment. We'll walk through your use case, hardware setup, and integration options.

Book a demo