Build and distribute an on-device Axium app
Understand development hardware, local SDK connection and signing before deploying an all-in-one checkout.
Choose development hardware
Development Axium units use test keys, connect to Android Studio and bypass application signature validation. Returning such a unit to production mode requires return to Ingenico. Production units use production keys, require signed apps and cannot be used for Android Studio development. The on-device guide specifies SDK v5.3.1+ and Android target29.
Connect locally
For TransactionInitiatorUI on the same device, use TCP/IP, 0.0.0.0 and port8088. Continue using SmartPOS SDK configuration. Parameters local = new Parameters(); local.add(ParameterKeys.PinPadConnectionType, ParameterValues.TcpIpConnectionType); local.add(ParameterKeys.PinPadName, "Axium-" + Build.MODEL); local.add(ParameterKeys.PinPadIpAddress, "0.0.0.0"); local.add(ParameterKeys.PinPadPort, "8088"); ChipDnaMobile.getInstance().setProperties(local);
Handle foreground ownership
Ingenico ARC UX comes forward for payment and the integrating app continues to receive SDK events in the background. Returning your Activity is the app’s responsibility. The source prefers FLAG_ACTIVITY_REORDER_TO_FRONT with a short delay and notes Android background-launch restrictions. Its SYSTEM_ALERT_WINDOW permission requires an explicit device grant; declaring it alone is insufficient.
Separate signing from distribution
Production apps require the Ingenico signing process. HEM distributes software through a library and campaigns; campaigns can target individual terminals or estates. Use development testing before submitting the production binary for review and signing.
Organize the estate
HEM sponsors own software libraries and estates; estates can contain sub-estates and terminals. Devices initially wait in a holding estate, then join the sponsor after backend connection. Use scoped roles: PGP-ADMIN creates users; device and campaign managers have distinct operational responsibilities. HEM is an Ingenico product and its Help center remains the detailed operational reference.
Plan a controlled rollout
Verify the assigned sponsor/partner code, signed application version, target estate and MDM policy before scheduling a campaign. Test the policy on a pilot device first. This portal guide explains the integration boundary; it does not reproduce every current HEM console screen or claim that any campaign was launched.