← Back to Help Center
Machine Technical Issues

Bill validator keeps rejecting bills

Step-by-step checks for jammed transport, dirty sensors, and denomination settings.

Updated Feb 9, 2026

Quick checks

  • Power cycle the machine and remove the validator to inspect the bill path.
  • Remove crumpled bills, labels, or residue from the transport path.
  • Confirm the stacker is fully seated and the stacker switch is engaged.

Deep cleaning and calibration

  • Clean optical sensors and the magnetic head with manufacturer-approved cleaner.
  • Let all components dry before reassembly.
  • Verify the validator configuration for your currency and denominations (dip switches or config card).

Electrical and control checks

  • Reseat the MDB harness and inspect for bent pins.
  • Test with known-good bills only (no tape, no excessive wear).
  • Read any error code and match it to the validator manual.

Replace if needed

  • Replace worn or glazed belts that slip under load.
  • Replace a faulty stacker sensor if rejections are intermittent.
  • Swap in a known-good validator to isolate controller issues.

Diagnostic checklist

  • Verify door and service switches are engaged and the controller is not in service mode.
  • Confirm the validator shows ready/idle status before accepting bills.
  • Run a test bill and listen for transport motor strain or slipping.

Preventive maintenance

  • Clean the bill path and sensors monthly in high-traffic locations.
  • Keep spare belts and stacker sensors on the route truck for quick swaps.
  • Train route staff to remove taped or heavily worn bills during service.

When to escalate

  • Rejections persist after swapping a known-good validator.
  • Error codes indicate controller board or power supply faults.
  • Burning smell, overheating, or repeated motor stalls.

<!-- 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.

Technical deep dive

Diagnostics

  • Inspect harness integrity, connectors, and power supply stability.
  • Review error codes against the OEM manual before swapping parts.
  • Compare with a known-good component to isolate the fault.

Preventive actions

  • Clean sensors monthly and replace wear parts on schedule.
  • Log firmware versions and configuration baselines.
cashvalidatorerror codes