NMI Payment Device SDK for Windows & Linux

Connect supported card-present terminals to Windows and Linux applications through a consistent, secure integration layer.

NMI’s Payment Device SDK, powered by ChipDNA, abstracts much of the terminal-specific complexity involved in EMV payments. Developers can build attended point-of-sale, kiosk, vending, parking, EV charging and ticketing applications while the SDK manages terminal communication, gateway routing and device configuration.


What the NMI Payment Device SDK Does

The SDK provides a hardware-abstracted API between the business application, supported payment terminal and NMI gateway. This lets developers focus on their checkout workflow instead of separately implementing low-level EMV behavior for every device.

Core Architecture

  • ChipDNA Server: local service managing the PIN pad, EMV processing, terminal management and gateway communication.
  • ChipDNA Client: the merchant application communicates with the server through a client library or command-line interface.
  • NMI Gateway: processes the transaction and communicates the result through the SDK.
  • Terminal Management System: delivers eligible configuration, firmware and certificate updates.

Supported Development Environments

  • Windows: NMI currently documents Windows 10 and 11 with the required .NET Framework.
  • Linux: supported through documented Mono and Java runtime requirements.
  • macOS: not supported by this Windows/Linux SDK.
  • Windows emulator: available for development and prototyping without physical hardware.

Where the SDK Fits

  • Retail and hospitality point-of-sale systems
  • Unattended kiosks and vending
  • Parking, transit and ticketing equipment
  • EV charging and automated service systems
  • Software platforms supporting multiple certified terminals

Critical Transaction Flow

NMI’s current guidance emphasizes that a successfully authorized sale must be followed by the SDK’s transaction-confirmation step. Without confirmation, the transaction will not settle and the merchant will not receive the funds. Production integrations should also define voids, refunds, linked refunds, declines, timeouts, restarts and reconciliation behavior.

Plan Before Development

  • Confirm the processor, merchant account and supported terminal
  • Obtain appropriate sandbox and production gateway credentials
  • Review firewall, network and service-startup requirements
  • Define device registration, replacement and remote-management procedures
  • Complete EMV, security and production-certification testing required for the project

SDK packages, operating-system requirements, supported devices and certification procedures change over time. Developers should use NMI’s current integration documentation for implementation.