← Back to Help Center
Nayax Support
Nayax telemetry data missing
Steps to restore inventory and sales reporting.
Updated Feb 9, 2026
Overview
Confirm the reader is online in the portal and the MDB cable is seated. Run a test vend to verify the machine is communicating with the reader.
Check the machine profile in Nayax and ensure the correct controller type is selected. Telemetry will fail if the machine type or device settings are incorrect.
If data remains missing, update firmware and verify DEX/MDB settings on the machine controller.
Portal checks
- Verify telemetry is enabled for the device profile.
- Confirm the correct machine type and controller model.
- Review the last telemetry timestamp.
Device actions
- Reboot the reader after any profile changes.
- Reseat MDB cables and check controller firmware version.
- Perform a test vend and confirm inventory updates.
Escalation info
- Provide device ID, machine type, and controller model.
- Include last telemetry timestamp and any error codes.
- Note any recent changes to firmware or configuration.
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.
Nayax specifics
Reader health
- Check SIM signal strength and APN configuration.
- Validate telemetry is active and alert rules are configured.
Settlement workflow
- Review the settlement calendar and payout thresholds.
telemetryinventorysync