Payment terminal lifecycle planning

What happens when a terminal reaches end of support?

When a payment terminal reaches end of support, the manufacturer or another responsible provider may stop supplying some combination of repairs, replacement parts, software updates, security fixes, certifications, or technical assistance for that model. The exact effect depends on the device, its hardware and firmware version, the support notice, and the merchant's service arrangement. A terminal may continue to power on or process transactions, but continued operation should not be mistaken for an assurance that support is still available.

End of support is a planning signal

End-of-support announcements give a business a reason to identify affected devices and build a replacement plan before a failure becomes urgent. The date does not always mean every terminal stops working at once. It does mean the business should confirm what the issuing organization will no longer maintain and which milestones come before or after that date.

Terms such as end of sale, end of service, end of life, and approval expiry can describe different events. End of sale may stop new orders while support continues for installed equipment. End of service may close repair or help-desk options. PCI Security Standards Council listings use an approval-expiry date for evaluated device models and may separately note a vendor-reported end-of-life status. Read the notice that applies to the exact model instead of treating these terms as interchangeable.

What can change after support ends

The consequences vary, so merchants should avoid assuming that every device follows the same timeline. Common operational changes can include:

  • Fewer update options: new software or security fixes may no longer be issued for the affected version.
  • Limited repair service: parts, depot repair, advance replacement, or manufacturer help may become unavailable.
  • Reduced troubleshooting help: support teams may offer only basic guidance or ask the merchant to move to a newer device.
  • Changing deployment guidance: an acquirer, processor, payment brand, or other responsible provider may set its own instructions for devices that have reached a lifecycle milestone.
  • More outage risk: an aging device can become harder to restore quickly when replacement stock, repair paths, or experienced support are limited.

These are possible outcomes, not promises about a particular terminal. Obtain the current notice and provider guidance before deciding whether a device can remain deployed during a transition.

Identify the exact device before making a decision

A model family name is often not enough. Record the manufacturer, full model designation, hardware identifier, firmware or software version, serial number, installed applications, connection type, location or assigned workstation, and the provider that supports the device. Similar-looking terminals can have different hardware revisions, firmware, approval records, or service dates.

Compare those identifiers with the manufacturer's lifecycle notice and the current PCI PTS device listing when relevant. PCI SSC explains that device approvals have expiry dates and encourages merchants implementing devices to review the listing. PCI SSC also says questions about using an expired device should be discussed with the merchant's acquirer or applicable payment brand. This page does not determine whether any particular terminal is acceptable for a specific deployment.

Build a controlled replacement plan

  1. Inventory affected terminals. Match every installed unit to its model, hardware, firmware, location, and support owner.
  2. Confirm the milestone. Obtain the official notice and distinguish end of sale, end of support, vendor end of life, and approval expiry.
  3. Ask the responsible provider. Confirm the expected replacement date, ordering process, setup responsibilities, and return or disposal instructions before acquiring equipment.
  4. Test the operating workflow. Verify transaction entry, receipts, network access, reporting, staff sign-in, peripheral use, and the business's fallback procedure on the planned replacement.
  5. Schedule the change. Choose a lower-risk operating window, prepare staff instructions, and keep the support contact and rollback decision path available.
  6. Retire the old unit safely. Remove it from the active device inventory and follow documented return, data-handling, and electronics-recycling instructions.

A phased plan is usually easier to verify than an emergency fleet-wide swap. Prioritize devices with the earliest documented milestone, unreliable operation, missing update paths, or no practical repair option, while letting the responsible providers determine device-specific requirements.

Prepare for the transition without exposing sensitive data

Keep a record of device identifiers, assigned locations, support contacts, maintenance dates, and replacement status. Do not place cardholder data, PIN data, passwords, encryption material, bank credentials, complete account numbers, or secret API keys in inventory sheets, emails, or general support forms. Share only the minimum identifying information requested through an approved support channel.

Before disconnecting an old terminal, preserve the business records needed for reconciliation through the normal reporting system. Do not attempt to extract sensitive payment data from the device. Ask the provider how to close pending batches, remove the unit from management portals, return leased or provider-owned equipment, and document completion.

Questions to ask before replacement

Which date applies to this exact unit?

Ask for the source notice and confirm the model, hardware revision, firmware, and service identifier. A date for a related model or a different firmware branch may not answer the question.

Who is responsible for configuration and activation?

Confirm which organization supplies the device, loads the required applications, activates service, and handles the old unit. Do not assume that a terminal purchased elsewhere can be placed into service.

How will operations continue during the change?

Document the approved fallback process, staff contacts, test transactions, receipt checks, and reconciliation steps. Avoid improvised collection of card details through email, messaging, spreadsheets, or paper notes.

Related terminal planning resources

Use the credit card machines and hardware FAQ hub for broader equipment guidance. Review when a payment terminal should be replaced to compare lifecycle and operational signals, then follow the checklist for preparing to replace a terminal. When a retired unit is ready to leave service, consult the guide to disposing of old payment terminals.

Choose the next step

Start by photographing or recording the non-sensitive model and version labels for each terminal, then ask the manufacturer and the organization supporting payment service for the current lifecycle notice and replacement instructions. Payments Max can help a merchant organize equipment and workflow questions for that conversation, but the responsible providers must confirm the requirements for the exact deployment.

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.

CONTACT US