Axium devices receive over-the-air (OTA) application updates via the NMI Device Agent application installed on the device. The update experience is designed to mirror the existing Miura OTA flow, so the SDK-side API is unchanged — any integration that already handles Miura firmware updates handles Axium OTA updates the same way.

How Updates Are Surfaced

When an update is available, two things happen in parallel:

• The integrating application receives a FirmwareUpdate callback from the SDK.
• A notification appears on the Axium device itself.

From there, you have two ways to trigger the update.

Update via the Axium device

The merchant can tap the notification — which opens the NMI Device Agent application — or open the Device Agent application manually and start the update from there.

Update via the SDK

Triggering the update through the SDK hands off to the NMI Device Agent application, which takes over the foreground and begins the update immediately. When the update completes, your integrating application is automatically brought back to the foreground.

The SDK-side calls are identical to the existing Miura firmware update flow — connectAndConfigure and the FirmwareUpdate callback. See the shared Configuration and Utility Methods page for the standard firmware-update lifecycle.

---

Update Types

The FirmwareUpdate callback indicates which type the available update is — your integration can choose to surface a "Update now" prompt for Deferrable updates or block transaction flow for Required updates.

---

Behaviour During the Update

If an update fails, the Axium device displays a retry screen allowing the operator to attempt the update again. The integrating application is not involved in the retry — the NMI Device Agent handles it.