Connect certified payment devices to a browser-based POS without local drivers or operating-system-specific installs.
NMI Customer-Present Cloud lets developers register compatible devices and send EMV payment requests from a web application through the gateway. Card data is collected by the device rather than the browser application.
How It Works
- Register a supported device to the merchant account.
- Submit a transaction through the compatible NMI API.
- Use asynchronous status polling for the recommended customer-interaction workflow.
- Manage registered devices and test with NMI’s Virtual PIN Pad.
Implementation Requirements
- Use a supported processor, certified device and secure API key.
- Plan for device registration, timeouts, error handling and transaction confirmation.
- Test refunds, device replacement and network outages before launch.
Important Limitations
- This is a developer integration, not a ready-made POS.
- Hardware, processor and transaction support vary.
- Approved transactions must be handled and confirmed according to the integration requirements.
Why Software Platforms Use Customer-Present Cloud
- Connect eligible browser applications to certified EMV devices without installing a traditional local driver on every workstation
- Keep sensitive card interaction on the approved payment device rather than in the browser interface
- Support centralized device registration and cloud-connected transaction workflows
- Build a consistent customer-present experience across compatible operating systems and locations
Good Fits for Customer-Present Cloud
- Cloud POS and software-as-a-service platforms
- Browser-based retail, service and hospitality applications
- Developers replacing legacy local payment-device integrations
- Multi-location systems needing centrally managed certified devices
Customer-Present Cloud Frequently Asked Questions
What is NMI Customer-Present Cloud?
Customer-Present Cloud is an NMI developer integration that connects a compatible browser-based application with registered, certified payment devices for eligible in-person EMV transactions.
Is Customer-Present Cloud a complete point-of-sale system?
No. It provides payment-device and gateway capabilities for a software application. The developer must supply the POS interface, business logic, reporting and operational workflow.
Does Customer-Present Cloud require local device drivers?
Its cloud-connected design is intended to avoid traditional operating-system-specific local driver installs. The certified device still requires supported connectivity, registration and configuration.
Which payment devices work with Customer-Present Cloud?
Only supported, certified device and processor combinations should be used. Availability varies by model, region, transaction type, firmware, encryption and connected processor.
Why is asynchronous status polling recommended?
Customer interaction at a payment device can take time and may involve prompts, cancellation or errors. An asynchronous workflow lets the application monitor status without holding a single browser request open indefinitely.
What is the NMI Virtual PIN Pad?
It is a testing tool for compatible Customer-Present Cloud development. It helps simulate supported device interactions before or alongside testing with production hardware.
Does Customer-Present Cloud eliminate PCI DSS responsibility?
No. Keeping card interaction on a certified device can reduce exposure, but the merchant and software provider must still address applicable PCI DSS, credential, network and integration-security requirements.
Related NMI Tools
- Supported Processors and Devices for compatibility planning
- ID TECH VP3350 for a compatible mobile-reader option
- iProcess for a ready-made NMI mobile payment application
- Webhooks for compatible event-driven application workflows
Plan the Device and Processor Path Before Development
Tell VCCP which software platform, processor, device type and in-person workflow you need to support. We can help confirm the account path before the integration is built around unsupported hardware.
Availability depends on the processor, device, API workflow and merchant configuration.