Ingenico Development

Ingenico Application Development and Payment Integration

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.

INGENICO · ILLUSTRATIVE EXAMPLE
UNATTENDED WORKFLOWExample sequence
SAMPLE
1 CardCard interactionEVENT
2 AuthorizationGateway or processorEVENT
3 ActivationMachine command or signalEVENT
4 FulfillmentFeedback, if supportedEVENT
ILLUSTRATIVEFour separate events

Approval does not prove activation, and activation does not prove delivery. What can be confirmed depends on the machine interface.

Illustrative example, not a specific project
Platform-specificAXIUM and other environments scoped separately
Three pathson-device, existing app, gateway
MDB + Pulsewhere the device and equipment allow
Certificationassessed for your scope
01 · Platforms and devices

Android-based AXIUM and other Ingenico environments.

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.

PLATFORM 01

Android-based AXIUM

AXIUM series

Android application development on AXIUM devices, including unattended and mobile models. Model-specific capabilities and access are confirmed per project.

ANDROIDAXIUM
PLATFORM 02

Other Ingenico environments

Lane · Self · Tetra Desk · Move

Other Ingenico application environments. SDK, access, and deployment approach are confirmed per device.

ATTENDEDUNATTENDED
PLATFORM 03

SoftPOS

SoftPOS

Where a device-specific SoftPOS implementation fits, see Commercial Android COTS. It does not apply to every Ingenico deployment.

SOFTPOS
02 · What we build

Applications, peripherals, and backend engineering.

Capabilities are confirmed for each platform. Not every feature is available on every device.

01

Checkout and tipping

Checkout workflows, tipping, and split tender, where the platform supports them.

02

Loyalty and data capture

Loyalty enrollment, data capture, and customer-facing workflows.

03

Supported peripherals

Printers, scanners and other peripherals where the device and SDK allow.

04

Backend connections

Connections to your POS, backend, and reporting systems.

03 · Payment integration paths

Three paths with different responsibilities.

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.

PATH 01Custom on-device development

Payment logic and application built on the device, with the approval implications that follow.

PATH 02Existing payment application

Your application integrates with an existing payment application on the device.

PATH 03Gateway or processor connectivity

Connectivity to a gateway, middleware, or processor from the application.

04 · Unattended applications

MDB, pulse, and the hardware they need.

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.

VENDINGVending and micro markets

Cashless payment on supported equipment.

KIOSKSelf-service kiosks

Checkout and self-order workflows.

PARKINGParking

Payment tied to access and exit systems.

FUELPetroleum

Controller and transaction-flow dependencies assessed per deployment.

05 · Testing and certification

Existing approved paths versus changes.

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.

06 · Deployment, ownership, and support

From concept to deployment.

01

Discovery

Platform, device, SDK access, processor, and workflow requirements.

02

Development

Application, payment integration, and protocol work.

03

Testing

Application QA, validation, and certification assessment where required.

04

Deployment

Signing, distribution, configuration, updates, and fleet support for the applicable platform.

05

Handoff and support

Ownership, documentation, maintenance, and support per the engagement agreement.

Common questions

Is an Ingenico application portable across every Ingenico device?
No. Ingenico's lineup includes Android-based AXIUM devices and other application environments with different SDKs, access requirements, and deployment constraints. We confirm the exact platform, model, SDK, and access for your project.
Can I integrate with an existing payment application instead of building payment logic on the device?
Often that is one of the available paths. The options are custom on-device development, integration with an existing payment application, and gateway or processor connectivity. Each has different approval and ownership implications, so we assess which fits your scope.
Does every Ingenico device connect to MDB and pulse equipment?
No. Support depends on the device, the interface hardware, and the equipment. We confirm the integration path and the required interface components before recommending one.
Will my change require a new certification?
It depends on whether it uses an existing approved integration path unchanged or changes elements that need additional testing or assessment. We assess the scope with you. Approval activities performed by external parties are not ours to promise or time.
Scoping inquiry

Tell us which Ingenico device and platform you're building for.

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.

Start your project

Sales online

Tell us about your project — we route you to the right specialist.

person
error_outlinePlease enter your name.
business
mail
error_outlinePlease enter a valid email address.
call
link
tune
error_outlinePlease tell us a bit about your project.

lock Your details go straight to our sales engineers — never shared or sold.