ID TECH Development

ID TECH Payment Reader Integration and Development

ID TECH builds the payment hardware. Paying.co builds the software around it: reader and application integration, backend connectivity, receipts and transaction handling, and unattended workflows. Where a deployment requires it, we support certification as a separate scope. An approved reader alone does not establish approval for every application or processor.

illustrative · sample dataEXAMPLE
// Illustrative flow, not a specific project
[Reader] card presented
[Host app] workflow step · amount=12.50 (sample)

// Authorization through your gateway or processor
[Gateway] request → response
[Host app] result handled · receipt
EXAMPLESample transaction
SAMPLE
$12.50
sample data
✓ ILLUSTRATIVE RESULT
Reader + hostintegration and application work
Per deviceSDK and kernel confirmed individually
UnattendedMDB and pulse where applicable
Certificationassessed for your scope
01 · Reader families and host environments

Unattended readers, mobile readers, and OEM modules.

These are different products with different integration requirements, and we do not treat them as one implementation. 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.

FAMILY 01

Unattended readers

AP6800 · VP6825 · Kiosk V

Outdoor and unattended deployments such as vending, EV, parking, transit and kiosks, with native applications and, where equipment supports it, MDB or pulse connectivity.

UNATTENDEDMDB / PULSE
FAMILY 02

Mobile and handheld readers

AP3880P Android · mobile readers

Android applications for retail, hospitality and field service with tipping, split tender, loyalty and back-office integration.

ANDROIDMOBILE
FAMILY 03

OEM and embedded modules

SDK · ATM readers

Embedded payment products and OEM readers, where the work centers on SDK integration and the host product.

SDKOEM
02 · What we build

The software around the reader.

The reader handles card interaction. The host application, backend connections, and transaction handling are what turn it into a production payment system.

01

Reader integration

Integration of the reader into your host application through the applicable SDK and interface, confirmed per device.

02

Application workflows

Data capture, loyalty, age verification, PIN entry where supported, and guided unattended journeys.

03

Backend and transaction handling

Backend connectivity, receipts, transaction records and result handling, plus supported peripherals.

04

Lifecycle support

Assessment of firmware and SDK updates, compatibility validation, deployment, documentation, and maintenance options.

03 · SDK, interface, and kernel support

Confirmed device by device.

Applicable SDKs, interfaces, and kernel versions differ across ID TECH devices, so we do not present the range as sharing one implementation. For each project we confirm the interface, SDK, firmware, and kernel version, and what they mean for your approvals.

READERModel, firmware, interface
HOSTDevice or OS, SDK version
PAYMENTSGateway, middleware, or direct processor
MACHINEMDB or pulse, where applicable
04 · Gateway and processor paths

Delivered combinations versus custom work.

Version, region, and approval dependencies decide whether a path is a known combination or custom work requiring assessment. Paths we have worked with are below. Availability depends on device, region, and your agreement.

GATEWAY / MIDDLEWAREhub

Datacap

NETePay and dsiEMVUS middleware.

GATEWAYcloud

Worldnet

Gateway and unattended processing.

GATEWAYmemory

BridgePay

Gateway and tokenization platform.

GATEWAYpayments

Cardknox

Gateway and developer platform.

GATEWAYcredit_card

CardConnect

CardPointe and CoPilot platforms.

CUSTOM WORKalt_route

Direct processor

Direct integration with an acquirer or processor, assessed for the specific scope.

05 · Unattended deployments

Machine requirements come first.

Before recommending an MDB or pulse integration we check the equipment, controller, and available interface. Payment approval, machine activation, and fulfillment feedback are separate events, and not every machine reports back. Licensing software does not necessarily supply every hardware or processing component. See MDB Pay Connect and Pulse Pay Connect for supported equipment, and Unattended Payment Systems for broader engineering.

EVEV charging

Outdoor acceptance and session-start workflows.

PARKINGParking

Payment tied to ticket, session, and exit systems.

TRANSITTransit

Contactless fare and access integrations.

VENDINGVending

MDB or pulse connectivity on supported machines.

06 · Testing and certification

Existing approvals and project-specific assessment.

A reader that holds approvals helps, but it does not make every application, processor, configuration, or deployment approved. We assess your actual integration scope, and explain when additional testing or a certification project applies. Our engineering and coordination work is separate from approval activities performed by external parties, and we make no universal approval or timing promises. See EMV Certification, the Payment Application Testing Checklist, and Payment Gateway Integration: Scope, Timeline, and Hidden Dependencies. Paying.co's 133 EMV Level 3 certifications are company-wide and are not a count of ID TECH projects. Choosing hardware? Read How to Choose a Payment Terminal.

07 · Deployment, ownership, and lifecycle

From discovery to support.

forumSTEP 01

Discovery

Reader, host, interface, SDK and firmware, processor, region, and workflow requirements.

lock_openSTEP 02

Access and dependencies

Review of SDK access, approvals already held, and dependencies on third parties.

buildSTEP 03

Integration

Reader, application, backend, and machine work.

verified_userSTEP 04

Testing and approvals

Application QA and device and provider validation. Certification assessment where your scope calls for it.

rocket_launchSTEP 05

Pilot and rollout

A pilot, then rollout across the fleet.

handshakeSTEP 06

Handoff and support

Source ownership, documentation, maintenance, and firmware or SDK change assessment are set in the engagement agreement.

Common questions

Does an approved ID TECH reader mean my application is approved?
No. A reader's own approvals do not establish approval for every application, processor, configuration, or deployment. We assess the actual integration scope with you, including any additional testing or certification that applies.
Do all ID TECH models use the same SDK and kernel?
No. Applicable SDKs, interfaces, and kernel versions differ by device and family. We confirm them individually for the models in your project.
Can ID TECH readers connect to vending or laundry equipment?
For supported equipment, through MDB or pulse interfaces. That needs compatible interface hardware and a compatible machine or controller. Licensing MDB Pay Connect or Pulse Pay Connect software does not by itself supply every component of a deployment.
Who owns the application and documentation?
Ownership, documentation, handoff, and maintenance terms are set in the engagement agreement.
Scoping inquiry

Tell us which reader and host environment you're building for.

Share the reader model, host device or OS, connection interface, SDK and firmware, gateway or processor, region, transaction requirements, existing approvals, application status, 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.