Check Axium SDK method support
Branch on SmartPOS mode before calling SDK functions shared with traditional readers.
Use the release-matched contract
The public appendix lists capability availability; doc/index.html in the SDK archive supplies exact signatures for that release. SmartPOS requires IsSmartPosIntegration TRUE. In shared code, select the integration mode before invoking unsupported operations.
Configuration and state methods
Method Axium support / condition initialize Yes; SmartPOS flag required. setProperties Yes. connectAndConfigure Yes. getAvailableCurrencies Yes; documented GBP/USD. getAvailablePinPads Yes; only Axium in SmartPOS mode. getStatus Yes; full data requires active connection. getTransactionInformation Yes; active connection required. getMerchantData No. requestTmsUpdate Yes. disconnect / dispose Yes.
Transaction and continuation methods
Method Axium support / condition startTransaction Yes; SmartPOS-specific parameters apply. continueDeferredAuthorization No; select TransactionAuthPreference instead. continueForcedAcceptance / continueVoiceReferral No. continuePartialApproval Yes when startTransaction requests PartialApproval TRUE. continueSignatureVerification Yes from SDK5.3.1 using external verification. continueSignatureCapture No; terminal captures signatures. continueApplicationSelection No. confirmTransaction / voidTransaction / linkedRefundTransaction Yes; active device connection required. getCardDetails / terminateTransaction Yes; termination during lost connection can return Unknown.
Receipts and offline methods
Method Axium support / condition processReceipt / setIdleMessage No. deleteFailedOfflineRequest / retryFailedOfflineRequest No. processOfflineRequest Yes for queued SmartPOS requests.
Do not reuse ordinary-reader recovery blindly
Axium transaction execution and offline storage are on the terminal. A host disconnect does not stop the payment. Use the SmartPOS recovery guide and processOfflineRequest rather than unsupported ordinary-reader failed-queue methods.