This supplement is for integration partners who want to develop and run their own applications directly on Axium devices — the all-in-one model — rather than driving an Axium from a separate Android device over the SDK.

It covers setting up an Axium device for on-device development, and how to access and use Ingenico's Hosted Estate Manager (HEM) and e-signing platform to distribute and manage your applications across your device estate.

📘
Already integrating with the Payment Device SDK? The all-in-one app still talks to the device through the same ChipDNA Mobile SDK — over a local connection on the device itself (see Setup for development). For the full transaction API, configuration, and SmartPOS deltas, see the SmartPOS: Ingenico Axium section.

Is this the right path for me?

There are two ways to build on Axium:

Semi-integrated — your application runs on a separate Android device and connects to the Axium over Bluetooth, USB, or TCP/IP. This is the path documented throughout the rest of the SmartPOS: Ingenico Axium section.
All-in-one — your application runs on the Axium itself. This supplement covers the additional steps that path requires: choosing the correct device mode, connecting to the on-device transaction service, managing your estate in HEM, and signing your application for production.

What's involved

Set up for development — choose a development device, and connect to the on-device transaction service. See Setup for development.
Get access to HEM — request access via your Account Manager and learn the core concepts. See Hosted Estate Manager (HEM).
Build and manage your estate — organise devices into estates, deploy software via campaigns, and apply MDM profiles.
Sign your application — sign your APK via Ingenico's e-signing portal before distributing to production devices. See Application signing.