← Back to Help Center
Cantaloupe Support

Cantaloupe Seed reader pairing guide

Pairing flow, MDB wiring tips, and initial data sync steps.

Updated Feb 9, 2026

Overview

Create the device in the Cantaloupe portal and assign it to the correct location. Verify the MDB harness is seated and the reader powers on.

Complete the pairing workflow and confirm the reader status changes to “online.” Run a test vend to validate payment processing and telemetry flow.

If pairing fails, reboot the reader and re-check the device profile, machine type, and wiring. A mismatched profile can block data sync.

Portal checks

  • Confirm the device is assigned to the correct location.
  • Verify the machine type and pricing profile.
  • Check for pending firmware updates or configuration warnings.

Device actions

  • Power cycle the reader after pairing changes.
  • Reseat MDB and power cables.
  • Run a second test vend to confirm data sync.

Escalation info

  • Provide serial number, device ID, and last online timestamp.
  • Include photos of wiring if troubleshooting hardware.
  • Note any recent location or profile changes.

Expanded guidance

  • Confirm all steps are documented so the next technician can reproduce the results.
  • Capture before/after metrics (errors cleared, sales restored, or uptime improved).
  • Review machine, reader, or route settings to ensure they match location standards.

Common pitfalls

  • Skipping a controlled test leads to false positives.
  • Updating hardware without documenting configuration changes.
  • Forgetting to verify payout, refund, or reconciliation data after changes.

Next-step checklist

  • Run a final test with known-good inputs.
  • Log the outcome with date, time, and device identifiers.
  • Schedule a follow-up check if the location has high traffic or seasonal demand.

<!-- expanded:v2 -->

Additional details

Operational notes

  • Document changes with time, machine ID, and location name.
  • Verify settings, pricing, and service modes after each fix.
  • Capture before/after results to confirm resolution.

Field checklist

  • Test with known-good inputs and controlled conditions.
  • Validate telemetry, alerts, and payment logs where applicable.
  • Confirm location expectations and update the site contact.

Common root causes

  • Configuration drift after firmware or component swaps.
  • Inconsistent power or network conditions at the location.
  • Gaps in preventive maintenance routines.

Next steps

  • Monitor for 7 days and note any repeat errors.
  • Schedule follow-up if the site is high-traffic.
  • Escalate with full logs and photos if issues repeat.

Cantaloupe specifics

Device pairing

  • Verify the reader is paired to the correct machine ID.
  • Confirm MoMa configuration and device firmware are current.

Alerts

  • Ensure alert thresholds align to route service windows.
pairingseedmdb