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.
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.
Outdoor and unattended deployments such as vending, EV, parking, transit and kiosks, with native applications and, where equipment supports it, MDB or pulse connectivity.
Android applications for retail, hospitality and field service with tipping, split tender, loyalty and back-office integration.
Embedded payment products and OEM readers, where the work centers on SDK integration and the host product.
The reader handles card interaction. The host application, backend connections, and transaction handling are what turn it into a production payment system.
Integration of the reader into your host application through the applicable SDK and interface, confirmed per device.
Data capture, loyalty, age verification, PIN entry where supported, and guided unattended journeys.
Backend connectivity, receipts, transaction records and result handling, plus supported peripherals.
Assessment of firmware and SDK updates, compatibility validation, deployment, documentation, and maintenance options.
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.
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.
NETePay and dsiEMVUS middleware.
Gateway and unattended processing.
Gateway and tokenization platform.
Gateway and developer platform.
CardPointe and CoPilot platforms.
Direct integration with an acquirer or processor, assessed for the specific scope.
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.
Outdoor acceptance and session-start workflows.
Payment tied to ticket, session, and exit systems.
Contactless fare and access integrations.
MDB or pulse connectivity on supported machines.
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.
Reader, host, interface, SDK and firmware, processor, region, and workflow requirements.
Review of SDK access, approvals already held, and dependencies on third parties.
Reader, application, backend, and machine work.
Application QA and device and provider validation. Certification assessment where your scope calls for it.
A pilot, then rollout across the fleet.
Source ownership, documentation, maintenance, and firmware or SDK change assessment are set in the engagement agreement.
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.
Tell us about your project — we route you to the right specialist.