Before You Contact PayTree: What to Send for Faster ATM Support

Collect the right ATM details, photos, logs, reports, and safe-check results before contacting PayTree so your support case can move faster.

---

Before you send an ATM issue to PayTree

A useful support case begins before the first message is sent. When PayTree receives the terminal identity, exact symptom, timing, evidence, and the results of safe checks in one place, we can separate likely printer, dispenser, communications, configuration, and processor issues much faster.

Use the steps below to prepare the case. Do not delay an urgent security or safety report to complete every item; the stop conditions later in this guide take priority.

1. Identify the exact terminal

Send the ATM manufacturer, exact model, terminal ID, and location. Include the software or firmware version when it is visible through an ordinary operator screen or report. Error numbers are reused across manufacturers and device families, so a code without terminal context can point to the wrong definition.

2. Record exactly what happened and when

Copy the complete error code and wording, then describe what the ATM did and what it failed to do. Include the incident date and local time, the last-known-good time, whether the ATM is in service, and the business impact. Note whether the problem affects every transaction, one cassette, one card, receipt printing, settlement, communications, or remote monitoring.

If possible, attach a clear photo of the complete screen. Redact customer information before sending it. A factual description such as ‘receipt paper advances during a test but no receipt prints after a withdrawal’ is more useful than ‘printer is broken.’

3. Protect customer and security information

Never send PayTree a PIN, full card number, password, encryption key, encryption material, safe combination, restricted host setting, or another customer’s identifying information. Use only the approved support channel and redact sensitive values from photos, reports, and journal excerpts.

4. Preserve logs and reports before resetting

When the terminal makes them available to an operator, save the electronic-journal or event-log entries immediately before and after the incident, the error summary, and any relevant setup, status, cassette-total, or transaction-statistics report. A final error may be the consequence of an earlier sensor, communication, or authorization event.

Do not clear counters, erase logs, repeatedly reboot the ATM, or change configuration before the evidence is saved unless the terminal is unsafe or an approved PayTree or manufacturer procedure tells you to act immediately.

5. Record every operator-safe check and its result

List each check in the order performed and state what happened. Examples include confirming receipt-paper orientation, verifying that an operator-accessible door is fully closed, checking whether a visible cable is seated without opening a restricted assembly, printing an approved status report, or confirming whether another authorized network device at the location is online.

Do not disassemble a component, bypass a sensor or security control, enter restricted service settings, or attempt work outside your assigned role. If the guide or terminal does not match the condition in front of you, stop instead of forcing the next step.

6. Tell PayTree what changed recently

Include any recent cash load, paper replacement, network or router change, processor change, software update, power interruption, configuration change, maintenance visit, relocation, or environmental event. Also state whether the ATM worked normally after the change and before the current incident.

Stop and contact PayTree immediately when

Contact PayTree without continuing routine troubleshooting when you see suspected tampering, a suspicious overlay, exposed power, unusual heat or odor, physical damage, a cash-security concern, repeated unexplained dispensing, a retained card involving customer risk, or any requested action that needs credentials or authority you do not have. Secure the ATM according to your operating procedures while you wait for direction.

Before you send the case to PayTree

Terminal: Manufacturer, exact model, terminal ID, location, and visible software version.

Incident: Exact code or symptom, complete wording, local time, last-known-good time, and business impact.

Evidence: Redacted screen photo, relevant journal range, error summary, and available setup, status, cassette, or transaction reports.

Safe checks: Each operator-safe check performed and the result, in order.

Recent changes: Cash load, paper, network, processor, software, power, configuration, maintenance, relocation, or environmental changes.

Sensitive data removed: No PINs, full card numbers, passwords, encryption material, keys, safe combinations, or restricted settings.

Urgency: Any safety, tampering, physical-damage, cash-security, or unexplained-dispensing condition clearly identified at the top.

Send the case to PayTree

Put the checklist information into one concise message, attach the relevant redacted evidence, and keep the case number with the terminal history. Complete evidence helps PayTree choose the next safe diagnostic step without asking you to repeat work or erase the original context.

Ready to send the details? Contact PayTree support

Need to identify an exact error code or symptom first? Search the PayTree Help Center

Genmega evidence examples in the PayTree Help Center

The following guides show where Genmega operators can collect several of the evidence types described above. Other ATM manufacturers and models may use different menus, reports, terminology, and access boundaries; use the guidance that matches the exact terminal.

Record the terminal's software context: How to check Genmega software and firmware versions

Preserve the sequence surrounding the failure: How to use the Genmega event log

Capture the accumulated error history: How to use the Genmega error summary

Create a configuration snapshot: How to print a Genmega ATM setup report

Add transaction evidence without exposing customer data: How to read the Genmega transaction statistics report

Use only operator-safe diagnostic tools: How to use Genmega diagnostic tools safely

Document what the terminal's sensors report: How to use the Genmega sensor viewer