A technician corrects a reversed paper roll in a receipt printer at a Toowoomba bakery checkout.

If your receipt printer isn’t printing, check its power, paper and connection first. Then restart it and print a test receipt. These checks can help identify whether the fault is with the printer, its settings or its connection to the POS system. A methodical approach to troubleshooting receipt printer issues can also help fix blank, cut-off or crooked receipts without changing several settings at once.

A printer failure during a transaction is frustrating, but you can check the common causes step by step. This guide covers refreshing printer settings and running a test, loading paper correctly, adjusting print margins, and checking Ethernet or Wi-Fi connections. You’ll also learn what to look for in the printer’s lights and cables, and when a persistent fault may need technical support. Start with simple checks, then follow the steps that match the problem.

Key Takeaways

  • Start with the printer’s power, paper and cable connections to narrow down why it isn’t printing.
  • Refresh printer settings and use a test receipt to help identify whether the issue is with the printer or POS setup.
  • Load the roll in the correct direction and adjust print settings to address blank, crooked or cut-off receipts.
  • Check Ethernet or Wi-Fi settings when the printer disconnects, and recognise when a persistent fault needs repair support.

Why is my receipt printer not printing?

Check the printer’s power, paper and connection before changing any settings. A methodical approach to troubleshooting receipt printer issues can help isolate the fault, whether it involves the printer, computer or POS system.

Check Power, Status Lights, and Paper Loading

  1. Check that the power switch is on and the adapter is firmly connected. Turn the printer off for 30 seconds, then restart it. A solid green status light indicates it’s powered on. An error light can signal an empty roll, an open cover, overheating or a connection issue. Open the cover and check that paper feeds from the top of the roll. If red keeps flashing, fit a fresh roll and close the lid before testing a transaction.

Inspect Cable and Network Connections

  1. Check that USB and Ethernet cables are fully plugged into the printer and connected device. Look for damage or loose connections, then try another cable or port if available. For network printing, confirm the Ethernet cable connects to the router or network switch. Hold Feed while powering on to print a configuration page. Check the bottom receipt for an IP address; 0.0.0.0 indicates the printer hasn’t connected to the network.

Check Printer Drivers and Test Page

  1. Print a test page from the computer before sending another POS receipt. If it prints, the printer can receive a local job, so check which printer the POS system is set to use. If the test fails, inspect the driver. In Windows Device Manager, right-click the receipt printer and select Uninstall Device. Install the correct driver, then restart the computer to apply the configuration. This helps distinguish a driver problem from other troubleshooting receipt printer issues.

Clean the Thermal Print Head Safely

  1. Turn off the printer and open its cover before inspecting the print head. Gently wipe away visible dust or residue with a soft cloth. Don’t pull paper forcefully, as this can damage the cutter. Reload the roll neatly, close the cover and print a test. If output is still blank or faint, note the status light and test results before moving to the next diagnostic step.

Refreshing printer settings and printing a test receipt

Change one setting at a time and test before returning to a live transaction. This helps distinguish Windows, POS hardware and receipt-design problems.

  1. Refresh Printer Settings

    After checking the selected connection, restart the printer and POS system. This may make the receipt printer appear again among the available devices. In the POS hardware or device settings, select the correct printer and save the changes. Avoid changing several options at once. Testing after each adjustment shows which setting restores printing.

  2. Set the Windows Default Printer

    Open Windows printer settings and set the receipt printer as the default. Turn off “Allow Windows to manage my default printer”, then apply the change. This stops Windows from switching the default to another device. Return to the POS program and check its printer selection too, since the Windows default and POS default are separate settings.

  3. Configure POS Hardware and Device Settings

    Open the POS device settings and select the receipt printer for receipts. Set “Auto print receipts” to “Yes” if receipts should print after each sale. Choose 1, 2, or 3 copies to match the required transaction output. Save the configuration, then reconnect the printer or restart POS if the device doesn’t appear.

  4. Adjust Receipt Logo Settings and Print a Test Receipt

    Reduce or remove a detailed logo if receipts print slowly; complex artwork can delay output. Print a Windows test page, then make a test sale in the POS system. Check that a receipt appears, the text is legible, and copies match the selected setting. If the Windows test page still fails, printer repair support can investigate the hardware fault.

How to troubleshoot receipt printer issues and fix print errors

Correcting paper orientation and print margins

For cut-off receipts, select the receipt printer in Chrome and set the margins to Minimum. If paper feeds incorrectly or the print is faded, reseat the roll, check that its thermal side faces the print head, and replace any damaged or unsuitable paper.

  1. Open the printer cover and check that the paper roll matches the printer. Receipt printers commonly use 72mm or 80mm rolls. Feed paper from the top, not underneath, and make sure the printable thermal side faces the print head. If a receipt comes out blank, switch the roll’s orientation and test again. Position the roll evenly, then close the lid firmly.
  2. Turn off the printer before clearing a paper jam. Open the cover and carefully remove the jammed paper. Don’t yank it, as forceful pulling can damage the cutter. Reload the paper neatly, aligned with the guides. Avoid tugging the paper while printing, as a skewed roll can cause crooked receipts or another jam.
  3. In Chrome’s print window, set Destination to the receipt printer and choose the paper size that matches the roll. Set margins to Minimum, then turn off Headers and footers. These settings can reduce cut-off edges and excess blank paper. Check the preview before printing: the wrong destination or page size can make the output look incorrectly scaled.
  4. Print a test receipt after changing the roll or Chrome settings. If paper feeds crookedly, check that the roll sits evenly, the guides are adjusted and the top lid closes properly. For faded output, confirm the roll is thermal paper and loaded correctly, then try a fresh roll. If the text still looks faint, gently wipe residue from the print head with a soft cloth.

How to check receipt printer power, cables, and network connection

  1. If the printer won’t turn on, check the power switch, wall outlet and adapter. Make sure the adapter is firmly connected at both ends. If the outlet works with another device but the printer remains off, inspect the adapter and cable for visible damage. A power fault can prevent status lights and network checks from working.
  2. For a connection refresh, turn off the printer and unplug its cables. Wait 30 seconds before reconnecting them, then restart the printer and POS system. Check USB, Ethernet or Serial connections at both ends. If the printer reconnects after changing a cable or port, the original connection may have been loose or unstable.
  3. Watch the printer’s status light after restarting. A slowly flashing red light indicates a network connection problem. Print a configuration page to inspect its network details. If the page shows 0.0.0.0, the printer hasn’t connected to the network; check its Ethernet cable and router connection.
  4. Compare the printer’s IP address with the register’s network details. Example addresses for devices on the same network are 192.168.1.10 and 192.168.1.11. These are examples, not required addresses. If the printer has no assigned address, check its connections, restart the router, then print another configuration page.
  5. For Ethernet or Wi-Fi, confirm the printer and POS device are connected to the correct network. Restart the router, then reconnect the printer. Network interruptions, a worn cable or overheating can cause disconnections, including during busy periods. Keep the printer ventilated and check that the network cable is intact.
  6. If power is present but the printer repeatedly loses its network connection, record its light pattern and configuration-page details. These clues help narrow down the fault before repair. Arrange receipt printer repair support if cable, router and connection checks don’t restore stable printing.

Aspire Computing: Printer Supply and Repair

Aspire Computing provides Printer Supply and Repair when a receipt printer still fails after you’ve checked its power, paper, settings and network connection. Recurring disconnections, failed test prints or persistent errors may point to a fault that needs hands-on diagnosis. Repair can help identify whether the issue is with the printer, its cables or its setup, so you can decide on a practical next step. If the computer connected to the printer is also affected, PC and Laptop Repair can address that related issue. Share what you’ve tested and describe any error lights or messages. Contact Aspire Computing to discuss your receipt printer issue.

Keep your checkout ready for the next transaction

Recurring printer faults are a useful prompt to review how your checkout setup is maintained. Keep a brief record of error messages and when printing fails. This can help distinguish an isolated interruption from a recurring problem and give a technician useful context if the fault continues.

Troubleshooting receipt printer issues can also reveal a wider computer problem. Aspire Computing offers PC and Laptop Repair, Hardware Upgrades and Data Recovery Services for related technology needs. The right support depends on what is failing, so describe the symptoms and steps you’ve already tried when you get in touch. This helps focus the conversation on a practical next step instead of making further changes blindly.

Contact Aspire Computing about printer help to discuss the issue and find a clear way forward.

Frequently Asked Questions

How do I troubleshoot a receipt printer that will not print?

Check whether printing fails in every program or only in the POS application. Send a small print job from another application or computer. If it prints, check the POS device assignment or receipt setup. If no application can print, look for paused or stuck jobs in the computer’s printer queue, then confirm that the selected printer matches the connected device.

How do I fix a receipt printer paper jam or blank receipts?

Turn off the printer before clearing a jam. Remove trapped paper without using sharp tools or forcing the cutter. Check inside the paper path for small torn scraps, which can obstruct feeding even after the main piece is removed. For blank output, test with a fresh thermal roll and check that it is loaded the right way around.

How do I install or update receipt printer drivers on Windows and Mac?

Use the driver intended for the exact printer model and operating system. On Windows, remove the old device entry before installing the replacement driver, then restart the computer. On Mac, open Printers & Scanners in System Settings, remove the printer if its entry is outdated, and add it again after installing the driver. Choose the matching USB or network connection.

How do I troubleshoot receipt printer connectivity with a POS system?

If the computer can print but the POS cannot, check the printer assignment in the POS application. A POS system may have separate device settings for different registers, so confirm the affected terminal is set to the correct printer. If only one terminal has a problem, compare its device selection with a working terminal before changing network settings.

How do I test and reset an Epson, Star Micronics, or Bixolon receipt printer?

Many receipt printers can print a configuration page for a basic test when you hold Feed while powering on. This output can show the printer’s current settings and network details. Epson, Star Micronics and Bixolon models may use different reset procedures, so follow the sequence for the exact model. Avoid a factory reset until you know which settings it will change.

Securing a Retail POS System from Hackers: A Practical Guide

What if the weakest point in your checkout isn’t the payment terminal, but an account, connected device or staff routine around it? Securing a retail POS system from hackers means protecting the whole checkout workflow, not just the hardware that takes payments.

It’s understandable to worry about payment data being exposed or sales stopping after a compromise, especially when security responsibilities are shared between your team, the POS provider and payment processor. Practical steps can reduce avoidable risks and give your staff a clearer response if something goes wrong.

This guide explains how to strengthen POS devices and accounts, limit network exposure and set clear security procedures for staff. It also covers how to document responsibilities and respond to suspected compromise. These controls can help protect customer information and support business continuity, so your team is better prepared before, during and after a security incident.

Key Takeaways

  • For securing a retail POS system from hackers, look beyond the terminal to connected devices, accounts, software and staff workflows.
  • Prioritise practical controls: map POS assets, limit access, apply updates, separate networks and review activity.
  • Document who manages each safeguard, including your business, POS provider and IT support team.
  • Give staff clear procedures for account use, suspicious messages and unexpected system behaviour.
  • Prepare a response plan so your team knows how to record concerns, limit risk and escalate a suspected compromise.

What does securing a retail POS system from hackers actually involve?

Securing a retail POS system from hackers means protecting the devices, accounts, software, payment components and staff workflows that work together to complete a sale. A checkout terminal is only one part of the environment. It may connect to a back-office computer, a network, inventory software or a cloud service, each with its own access and support arrangements. For businesses using comprehensive systems like PROTEUS420 that unite retail POS with inventory and distribution, keeping every connected touchpoint secure is essential.

Protecting the terminal alone can leave those connections exposed. An attacker might gain access through a stolen account, introduce malicious software onto a connected device or exploit weak remote access. Even without confirmed payment-data exposure, unexpected system changes or unavailable checkout equipment can disrupt transactions and affect business continuity.

To see why network security matters to a checkout setup, watch this relevant video:

Which parts of a retail POS setup need protection?

Start by listing the equipment and services involved in checkout, not just items at the counter. These may include checkout computers, payment terminals, receipt printers, routers, staff accounts, POS software and connected services such as inventory or loyalty systems. Note which devices are used for payment processing and which handle general business tasks. Their connections and security needs may differ.

For each item, record who owns it, who maintains it and who can access it. Note which systems are managed by a POS provider and where your own business or IT support team is responsible. This simple record helps prevent gaps, such as assuming a device is being updated or monitored when no one has taken ownership of that task.

Who is responsible for POS security?

Responsibility is often shared. Retailers typically manage staff accounts, everyday device use and workplace procedures. A POS provider may manage parts of its platform or supplied equipment, while a payment processor may have separate responsibilities for payment services. The division depends on the systems and service arrangements involved, so write down the responsibilities rather than relying on assumptions.

Record who manages user access, software updates, backups, security alerts and incident escalation. Include the appropriate support contact and the process for reaching them. Clear ownership gives staff and support teams a practical starting point if a concern arises, instead of leaving them to work out responsibilities during a disruption.

A simple inventory makes the POS environment easier to understand. Group devices and services by purpose, identify their owner and support contact, and note whether they handle payments or connect to payment systems. This creates a useful foundation for prioritising controls across the whole checkout workflow, rather than treating each terminal as an isolated device.

How to harden a retail POS system against common attacks

A reliable hardening plan is practical and staged. Start with the devices and services in your POS inventory, then reduce unnecessary access, keep software supported, limit network connections and review activity. Make security changes deliberately. Rushed updates or untested settings can disrupt checkout just when the business needs it most.

A strong POS security baseline maps every checkout device, limits access to named users, applies approved updates, separates networks where possible and checks for unexpected activity.

  1. Map the setup. Record checkout devices, software, connected services, their purpose and who supports each one. Include any remote access used for maintenance.
  2. Restrict access. Give each staff member an individual account where supported, with permissions suited to their role. Shared logins make it harder to trace activity and remove access cleanly.
  3. Update carefully. Apply vendor-approved operating system and POS software updates. Follow the relevant update instructions and consider the operational impact before scheduling changes, especially during trading hours.
  4. Limit network exposure. Keep checkout equipment separate from guest Wi-Fi and general-use devices where the setup supports it. Limit connections and remote access to what the system needs.
  5. Review activity. Check available account, access and system records for unfamiliar users or unexpected changes. Assign someone to review them and make sure they know how to escalate concerns.

Control access to POS devices and accounts

Use unique accounts rather than a shared staff password wherever the system allows. Choose long, hard-to-guess passphrases that aren’t reused for other services. Restrict administrator accounts to people who need them, and enable multifactor authentication (MFA) for those accounts when available. Set a clear process for access changes: when someone changes roles or leaves, review their permissions and remove access they no longer need.

Keep administrator credentials separate from everyday staff sign-ins. Staff should never share passwords in messages or leave them beside the terminal. If the POS system doesn’t support individual accounts, document the limitation and use the access controls that are available. Clear account procedures reduce confusion and help the business act promptly when access needs to change.

Reduce network and software exposure

Keep POS devices focused on checkout tasks. Avoid installing unapproved applications or using them for general browsing and email, which can expose the system to unnecessary risks. Follow the update process for the system and consider a suitable maintenance window so changes don’t interrupt sales. Don’t disable security settings to resolve a short-term inconvenience without understanding the impact.

Keep checkout devices separate from guest and general-use networks where the POS setup supports it, and have network changes reviewed by someone familiar with the environment. Small-business cyber security support can help retailers consider malware protection alongside device and account controls. Review the setup after adding a terminal, service or staff account so new connections don’t quietly widen access.

How to compare POS security controls without disrupting sales

Compare controls by the risk they address, the work needed to manage them and the visibility they provide. There’s no single setup that suits every retailer. Separate what the POS system can do from what your business must configure and what staff need to follow. Plan changes for a suitable maintenance window and test their effect on checkout before relying on them during trade.

Use this table to organise responsibilities for your POS setup and service arrangements.

ControlProvider role to clarifyRetailer setup and staff practiceRisk it helps reduce
Access controlsDocument the available user roles, MFA and account management options.Assign individual accounts where supported, limit permissions and remove access when it’s no longer needed.Unauthorised access through exposed or unnecessary accounts.
Software updatesRecord how updates are delivered, tested and supported.Schedule approved updates, understand operational impact and avoid delaying them without a reason.Exposure to weaknesses addressed by available updates.
Network separationDocument options for separating checkout devices from guest or general-use networks.Use the agreed network settings and avoid connecting unapproved devices.Unwanted access spreading between connected devices.
LoggingRecord which events are logged, how long records are available and who can access them.Assign someone to review relevant records and escalate unfamiliar activity.Delayed detection of unexpected access or changes.
BackupsDocument which POS data or settings are included and how restoration works.Understand what the business is responsible for protecting and follow the agreed recovery process.Loss of access to important information after an incident or failure.
Support ownershipDocument support boundaries, incident contacts and escalation steps.Keep contact details and responsibilities accessible to relevant staff.Delays and confusion when a control or service needs attention.

Questions to ask your POS provider and payment processor

Use your service arrangements and documented support processes to establish who applies software updates, how your team is notified and what steps to take before or after an update. Record which security events are logged, who can review those records and how they can be accessed if you notice a concern. Keep incident contacts and responsibilities documented, including how the POS provider and payment processor coordinate with your business. Don’t assume one party manages every control.

Compare controls by the risk they reduce

Account controls help limit unauthorised access, while approved updates help address known software weaknesses. Network separation can restrict unwanted connections, and logging may help you spot unusual activity. Backups support recovery, but it’s important to understand their scope and how restoration works. Each control has practical considerations: tighter access requires clear account administration, while logging is only useful if someone reviews it. For businesses concerned about cardholder data exposure, automated scanning from EmberHound helps identify where sensitive card records reside across systems so they can be properly secured.

For securing a retail POS system from hackers, review current PCI DSS guidance and your payment arrangements to understand which payment security obligations apply to your environment. A small-business IT support plan can help you consider POS security alongside wider business systems.

Securing a Retail POS System from Hackers: A Practical Guide

Staff actions to prevent POS compromise and spot signs

Staff don’t need to diagnose a cyber incident. They need clear instructions for what to do when something doesn’t look right. A short, written procedure can reduce hesitation during a busy shift and help protect checkout operations while the right people investigate. It makes securing a retail POS system from hackers a shared responsibility, rather than a task left only to technical support.

Stop, don’t experiment with the system, and report suspicious activity promptly. A message asking for a password, an unexpected sign-in prompt or an unfamiliar change to the checkout screen may have a harmless explanation. Staff should still follow the reporting process instead of clicking through, changing settings or attempting fixes on their own.

Build simple POS security procedures for a small team

Write down who is authorised to use checkout devices, which tasks each role can perform and who staff should notify about concerns. Keep instructions easy to find, such as in a staff procedure folder. Cover everyday account use, suspicious messages, unexpected prompts and how to escalate an issue without sharing credentials or bypassing approved security steps.

Keep the procedure brief enough to use during a busy period. Review it when the POS setup, staff roles or support arrangements change. A small-business IT policy can make ownership clear by naming who handles account changes, who contacts the POS provider and who coordinates with IT support. That reduces uncertainty when an unusual event needs attention.

Recognise suspicious activity and report it safely

Possible warning signs include an unfamiliar account, an unexpected change to settings or unexplained behaviour, such as a prompt nobody recognises. One sign alone doesn’t prove a system has been compromised, so staff should report what they see without making assumptions or attempting a repair.

Ask the staff member to note the time, device, message or change they observed, and who they notified. They should avoid deleting messages, clearing records or altering the device, since those actions could make it harder for support teams to understand what happened. Follow the business’s escalation procedure and notify the designated POS and IT support contacts. Staff should also follow any instructions about whether to continue using the affected device.

Use simple scenarios in team briefings. For example, what should an employee do if a checkout screen requests an unfamiliar sign-in, or a message asks them to install software? Rehearsing the reporting steps helps staff respond consistently without technical expertise. Small-business cyber security advice can help owners consider how staff procedures fit into their overall security approach.

If your team needs help turning security concerns into practical procedures, small-business IT support can help you plan clear responsibilities and reporting steps to support business continuity.

Responding to a POS hack: contain, recover, improve

A suspected POS compromise can feel urgent, especially if checkout or payment services are affected. A calm, agreed response helps limit further exposure and gives support teams useful information to investigate. Don’t assume every unexpected prompt means a breach, but treat unusual activity seriously and follow your established escalation process.

Use this sequence as a starting point, alongside the incident procedures in your POS and payment service arrangements:

  1. Follow the documented incident process. Use the official support or escalation channel and explain what staff observed.
  2. Limit further use where advised. Don’t keep using an affected device or disconnect it unless the POS provider or IT support recommends that action.
  3. Record observations. Note the time, device, messages or unexpected changes, and steps already taken. Preserve relevant records and avoid deleting information.
  4. Escalate appropriately. Contact the payment processor if payment systems may be involved. Seek guidance from relevant Australian authorities, such as the Australian Cyber Security Centre or the Office of the Australian Information Commissioner, when appropriate to the incident.

Respond without making the incident harder to investigate

Avoid guessing at the cause, experimenting with settings or installing tools to investigate. Unapproved changes can affect checkout and make it harder for support teams to understand what happened. Keep a clear record of who was notified and when, and follow professional guidance about preserving evidence and limiting system use.

Responsibility for payment security and incident handling can vary across the retailer, POS provider and payment processor. Use the escalation channels in your service arrangements and document any instructions you receive. For Australian privacy or data breach questions, consult current guidance from the relevant authority rather than relying on an outdated internal procedure.

Turn the incident into a stronger continuity plan

Once systems are stable and the appropriate teams have reviewed the incident, identify what needs to be restored first. A practical recovery plan names trusted contacts, critical checkout and business systems, the data needed to resume operations and where clean backups are available. Confirm who can approve restoration and how the team will know a backup is suitable to use.

Then review what happened with the people responsible for POS support and staff procedures. Check whether access, updates, escalation steps or unclear responsibilities contributed to delays. Update the plan and make sure staff know where to find it. These lessons help strengthen security for a retail POS system while supporting continuity across the wider business.

Aspire Computing supports small businesses with computer and network protection, focusing on protecting and maintaining machines and data for business continuity. Toowoomba-area businesses can learn about computer and network protection from Aspire Computing as part of a wider security plan.

Make POS security part of everyday business continuity

Strong POS security isn’t a one-off project. Set a regular time to review who has access, whether responsibilities are clear and whether staff know how to raise concerns. A brief review after a system change can help catch gaps before they affect checkout or customer confidence.

For small businesses, security also needs to fit daily operations. Aspire Computing has supported local businesses since 1999. Owner and lead technician Chaim Lee brings over 20 years of hands-on experience, with on-site and remote support for small businesses. That practical perspective can help you consider how computer and network protection supports your broader business continuity plans.

Talk with Aspire Computing about protecting your small-business computers and network. Reviewing access or documenting who to contact when something seems wrong can make securing a retail POS system from hackers more manageable.

Start with one clear action, such as reviewing staff access or documenting who to call if something seems wrong. Small, consistent improvements can help your business stay prepared and keep serving customers with confidence.

Frequently Asked Questions

Can a small retailer secure a POS system without a dedicated IT team?

Yes. A small retailer can reduce common risks by assigning someone to coordinate security, following the POS system’s documented support process and bringing in IT support for tasks beyond the team’s skills. Start with a simple record of devices, support contacts and account owners. Review staff access and unresolved updates regularly. This gives the business a manageable foundation for securing a retail POS system from hackers without building an in-house IT department.

Does using cloud-based POS software mean the system is secure?

No. Cloud hosting describes where some software or data is managed, not whether every account, connected device or business setting is secure. Retailers still need to protect their own logins, staff devices and network access. For example, a secure cloud service can still be exposed if a staff member’s email account is compromised and reused credentials provide access. Understand which security tasks are handled by the service and which remain your responsibility.

Do retail businesses need to worry about cyber crime targeting POS systems?

Yes. A retailer’s systems may be affected by attacks aimed at payment data, business accounts or connected software, even if the business is small. Criminals can also use less direct routes, such as phishing a staff member or accessing a reused password, rather than attacking a payment terminal itself. Treat unusual requests for credentials or unexpected account activity seriously, and make sure staff know how to report concerns promptly.

What should a small-business IT security policy say about POS systems?

It should explain who may use checkout equipment, how individual accounts are managed and who approves administrator access. Include rules for handling passwords, unexpected prompts, software changes and remote support requests. The policy should also name the person responsible for contacting the POS provider or payment processor if something goes wrong. Keep it practical so staff can find the right instruction quickly during a busy shift.

Should a POS system be connected to the same network as guest Wi-Fi?

Ideally, checkout devices should be kept separate from guest Wi-Fi and general-use devices, using a network arrangement supported by the POS setup. Sharing network equipment doesn’t always mean devices can access one another, but that depends on how the network is configured. Don’t rely on a separate Wi-Fi name alone as proof of isolation. Make sure the network setup clearly separates guest access from checkout systems.

What should I do first if I suspect someone has hacked my POS system?

First, use the POS provider’s official incident or support channel and follow its instructions. Don’t try to investigate by changing settings, deleting records or installing software. Note what staff noticed, when it happened and any actions already taken. If payment services may be affected, follow the payment processor’s escalation process too. For possible privacy or data breaches, consult current Australian guidance from the relevant authorities.