Lane/Series

NMI’s Customer-Present Cloud API makes EMV integration simple by moving everything into the browser. Instead of managing drivers, SDKs, or OS-specific dependencies, developers can connect certified payment devices directly to their web-based POS applications. The result is a fast, portable, and processor-certified solution that runs on any operating system with no local installs. With support for chip and contactless payments across a growing list of devices and acquirers, it’s the quickest way to deliver secure, cloud-managed EMV acceptance to your merchants.

1. 📦 Unbox & Verify

Included in the box

• Lane terminal
• Multipoint Interface Cable
• Power adapter

Tamper checks (on arrival & regularly)

• Keypad firmly attached
• No unusual wires/devices attached

Precautions

• Indoor use only
• Keep away from heat, dust, strong magnets, and PCs
• Use only the supplied power adapter

💡

Current NMI Partners can purchase test and live devices from within the NMI Partner Portal.

If you are not yet an NMI Partner but would like to purchase a test device, you can purchase devices directly from NewBold Technologies here.

2. ⚡ Hardware Setup

1. Place terminal on a stable surface/stand.
2. Connect Multipoint Interface Cable to the underside Multipoint Port.
3. Connect Ethernet (open internet access).
4. Attach power adapter to the cable, then plug into outlet.
5. Device boots and shows:

   Unregistered
   [Rotating Code]

   If no code → check network/firewall.

3. 🔐 Enable Encrypted Devices

• Partner Portal → Marketplace → Enable Encrypted Devices
• Merchants will then see it under Merchant Portal → Marketplace Apps

4. 📝 Register the Lane Device

Manual (Merchant Portal)

• Go to Registered Devices
• Enter Nickname + Rotating Code
• Save → device is ready for EMV in Virtual Terminal

API (Recommended)

Endpoint

POST https://secure.networkmerchants.com/api/v2/devices/register

Headers

Authorization: Bearer {MERCHANT_API_KEY}
Content-Type: application/json

Request

{
  "registrationCode": "8AVJWV",
  "deviceNickname": "My POI Device"
}

Response (truncated)

{
  "poiDevice": {
    "poiDeviceId": "414b0420-b31c-4c76-9fc3-8a4f1a6dcffc",
    "deviceNickname": "My POI Device",
    "registrationStatus": "registered"
  }
}

5. 💰 Process Payments

Endpoint

POST https://secure.networkmerchants.com/api/transact.php

Required fields

• security_key (from Merchant Portal)
• poi_device_id (from registration)
• type → sale | auth | credit | validate
• amount (omit or 0.00 for validate)
• response_method → synchronous | asynchronous

Synchronous Example

security_key=...&type=sale&amount=1.00&poi_device_id=XXXXXXXX-XXXX&response_method=synchronous

Asynchronous Example

security_key=...&type=sale&amount=1.00&poi_device_id=XXXXXXXX-XXXX&response_method=asynchronous

6. 🔄 Poll Async Transactions

Endpoint

GET https://secure.networkmerchants.com/api/asyncstatus/{asyncStatusGuid}

Success Example

{
  "transaction": {
    "id": 4869813602,
    "type": "sale",
    "success": true,
    "condition": "pendingsettlement",
    "authCode": "A99BUO"
  },
  "asyncStatus": "interactionComplete"
}

7. 🛠 Device Management

Deregister

DELETE https://secure.networkmerchants.com/api/v2/devices/deregister/:poiDeviceId

Update Nickname

POST https://secure/networkmerchants.com/api/v2/devices/update/:poiDeviceId

List Devices

GET https://secure.networkmerchants.com/api/v2/devices/list
GET https://secure.networkmerchants.com/api/v2/devices/list/:poiDeviceId

8. ➕ Optional Device Features

• Signature Capture → /devices/sign/:poiDeviceId
• Yes/No Prompt → /devices/yesno/:poiDeviceId
• Multiple Choice → /devices/menuselection/:poiDeviceId
• Display QR → /devices/qrcode/:poiDeviceId
• Hide QR → /devices/display/:poiDeviceId

9. 🧪 Test with Virtual Pin Pad (VPP)

• Registration codes: T00001 (success), T00002 (fail)
• Device/Async GUIDs end with 12 zeroes in test mode
• Amount ≥ 1.00 → approved
• Amount < 1.00 → declined

Demo API Key

2F822Rw39fx762MaV7Yy86jXGTC7sCDy

10. 🚨 Error Handling

Common HTTP Status Codes

• 400 → Missing Platform ID / API Key
• 401 → Invalid API Key
• 404 → Device not found
• 300 → Long processing / retry, check connectivity

Error Example

{
  "errors": [
    {
      "code": 300,
      "refid": "12345",
      "message": "Transaction took too long"
    }
  ]
}

Notes

• Generate Security Keys in Merchant Portal → Settings → Security Keys (type: API).
• Ensure network connectivity; if no rotating code shows after boot, check firewall/proxy.
• POI prompt variables (poi_prompt_tip, poi_prompt_amount_confirmation, etc.) customize cardholder flow.

✅ You’re now ready to integrate the Customer Present Cloud API and Lane device into your app.

Navigate through the pages in the developer portal for more details, including visual aids, flow diagrams, and code samples.