Ingenico builds the terminals. Paying.co builds the software: application engineering, integration with existing payment applications, processor connectivity, and certification support where required. Ingenico's lineup is not one interchangeable environment, so we scope the work to your specific platform and device.
Approval does not prove activation, and activation does not prove delivery. What can be confirmed depends on the machine interface.
We separate AXIUM development from other Ingenico application environments, because SDKs, access requirements, and deployment constraints differ. Support for a specific combination depends on the device or reader model, firmware, SDK, host environment, processor, and region. A delivery on one combination does not establish support for every model or approval for every deployment.
Android application development on AXIUM devices, including unattended and mobile models. Model-specific capabilities and access are confirmed per project.
Other Ingenico application environments. SDK, access, and deployment approach are confirmed per device.
Where a device-specific SoftPOS implementation fits, see Commercial Android COTS. It does not apply to every Ingenico deployment.
Capabilities are confirmed for each platform. Not every feature is available on every device.
Checkout workflows, tipping, and split tender, where the platform supports them.
Loyalty enrollment, data capture, and customer-facing workflows.
Printers, scanners and other peripherals where the device and SDK allow.
Connections to your POS, backend, and reporting systems.
We identify which combinations have been delivered and which are proposed custom work. Gateway and middleware paths we have worked with include Datacap, Worldnet, BridgePay, Cardknox, and CardConnect. Availability depends on device, region, and your agreement. See Platform Integrations for POS, gateway, and backend work.
Payment logic and application built on the device, with the approval implications that follow.
Your application integrates with an existing payment application on the device.
Connectivity to a gateway, middleware, or processor from the application.
Kiosk, vending, parking, petroleum and other deployments each have their own hardware and controller requirements. Not every Ingenico device directly supports MDB or pulse, and interface components may be needed. Card interaction, authorization, machine activation, and fulfillment feedback are separate events. See MDB Pay Connect, Pulse Pay Connect, and Unattended Payment Systems.
Cashless payment on supported equipment.
Checkout and self-order workflows.
Payment tied to access and exit systems.
Controller and transaction-flow dependencies assessed per deployment.
An existing approved integration path used unchanged is different from changes that need additional testing or certification assessment. We assess the scope with you. Our engineering and coordination work is separate from external approval activities, with no universal approval or timing promises. See EMV Certification, Managed EMV Certification vs. Full Payment Application Development, and the Payment Application Testing Checklist. Paying.co's 133 EMV Level 3 certifications are company-wide and are not a count of Ingenico projects.
Platform, device, SDK access, processor, and workflow requirements.
Application, payment integration, and protocol work.
Application QA, validation, and certification assessment where required.
Signing, distribution, configuration, updates, and fleet support for the applicable platform.
Ownership, documentation, maintenance, and support per the engagement agreement.
Share the device model, application platform, firmware and SDK, available access, processor, region, existing application status, transaction requirements, peripherals, machine interface, deployment size, and target timing.
Tell us about your project — we route you to the right specialist.