Frequently Asked Questions

Connectivity

Q: How does my POS app connect to the Axium?
A: It depends on the integration type.

Semi-integrated (your app runs on another device and uses the Payment Device SDK for Android): Bluetooth only. USB is not supported between the SDK and Axium, including over the RX5000's IDMI port.
All-in-One (your app runs on the Axium): your app connects to the on-device TransactionInitiatorUI app over TCP/IP at 0.0.0.0, port 8088. See Setup for development.

Q: How does the Axium connect to the internet?
A: All models connect over Wi-Fi, which is set up on first boot. The countertop RX5000, RX7000 and RX9000 also support Ethernet.

Development devices

Q: Can I open Developer options on a Development-mode device?
A: No. Ingenico's hardened build removes the Developer options menu, and neither Estate Manager nor an MDM profile can turn it back on. You don't need it: USB debugging is already enabled on Development-mode devices, so adb and Android Studio work.

Q: My computer doesn't see the Development device over USB.
A: Connect it directly to your computer's USB-C port; you shouldn't need a hub. Use the cable supplied with the device, because some cables are charge-only.

Q: Can a Development device be switched back to Production?
A: No. Once a device is in Development mode, it must be returned to Ingenico to revert.

Transactions

Q: How do I handle tips, including adding a tip after authorisation?
A: Axium doesn't prompt for tips on the device. Your app collects the tip and passes it in ParameterKeys.TipAmount when it calls startTransaction().

To add more tip later (for example, auto-gratuity plus a tip on top), start the sale with the known tip. Then confirm the transaction with the total tip once it's known. The sale settles at the higher amount.

Two conditions apply:

The merchant account must have Allow Merchant to Capture for an Amount higher than Authed turned on, or the confirmation is rejected. Ask your NMI contact or Support to enable it.
The confirmation must be made on the same Axium that took the payment. Confirming from another terminal on the same account isn't supported, so each terminal closes its own checks at the end of a shift.

NMI sets no cap on how much higher the capture can be; any limit comes from the card schemes and the processor.

Differences from other PIN pads

Q: Does the SDK behave the same on Axium as on Miura and other PIN pads?
A: Almost. Differences are kept to a minimum. The ones that exist are listed in the Axium Smart POS Supplement included in the Android SDK release bundle, and on these pages:

If you find a difference that isn't listed, it's unintentional. Contact Support and include the SDK log.