This page documents the event and error-code deltas for SmartPOS / Axium integrations. For the underlying event model that applies to all integrations, see the shared Configuration and Utility Events page.

New Transaction Update Event

A new value is emitted on the TransactionUpdate callback when running against an Axium device:

Update	Meaning
`AttemptingToReconnect`	The SDK has lost connection to the Axium and is attempting to reconnect so it can retrieve the transaction result. The transaction may still be running on the Axium — do not assume failure until either reconnection succeeds or you explicitly call `terminateTransaction()`.

See Device disconnection during a transaction for the full reconnection lifecycle and the parameters returned if you terminate during a disconnection.

New Error Codes

A full list of SDK error codes is generated in the API documentation supplied with each release bundle — open doc/index.html from the SDK ZIP and navigate to Modules → ChipDnaMobileErrorCodes. The following codes are new for SmartPOS.

Start Transaction

Returned from startTransaction() when an invalid value is passed in a SmartPOS-specific parameter.

Error code	Meaning
`TransactionAuthPreferenceInvalid`	The value passed with `ParameterKeys.TransactionAuthPreference` is not one of the accepted values. See TransactionAuthPreference for the accepted values.
`OfflineTransactionUploadModeInvalid`	The value passed with `ParameterKeys.OfflineTransactionUploadMode` is not one of the accepted values.

Transaction Finished

Returned in the transactionFinishedListener callback.

Error code	Meaning
`TransactionInformationUnavailable`	The transaction's information could not be retrieved because the connection to the Axium device failed. The transaction itself may or may not have completed on the device — call `getTransactionInformation()` once the device is reachable again to see the final outcome.

Confirmation Behaviour on Axium

❗️
The AUTO_CONFIRM parameter is not supported for Standalone Refunds on Axium devices.
Use the TRANSACTION_RESULT and TRANSACTION_STATUS values returned in the Transaction Finished and Transaction Information events to determine whether a confirmTransaction() call is expected to succeed.

Specifically:

A transaction with TRANSACTION_STATUS = Committed is already confirmed — calling confirmTransaction() on it will fail.
A transaction with TRANSACTION_RESULT = Declined cannot be confirmed — calling confirmTransaction() on a declined transaction will fail.

In both cases, inspect the transaction state before attempting confirmation rather than relying on AUTO_CONFIRM.