PAX A920 in 2026: What End-of-Life Means for Merchants

The PAX A920 is still installed in a lot of merchant environments, but the buying decision changed in 2026.

PAX's current North American product page labels the original model A920 (EOL). That is an important procurement signal. It is not, by itself, proof that every installed A920 must be unplugged today.

Short answer: do not order the original A920 for a new deployment without written confirmation from the organization supporting the complete payment configuration. An existing A920 can remain usable only while its hardware, security support, payment application, processor configuration, and merchant deployment are all still supported.

This is the distinction merchants and developers need to make.

End-of-life is a lifecycle signal, not a transaction response

A payment terminal does not become unusable merely because a product page changes. The fielded system has several independent support boundaries:

Boundary	The question to ask
Hardware	Can the device, battery, printer, charger, and radios still be supported?
Firmware and security	Is the installed firmware still accepted under the provider's security and compliance program?
Payment application	Is the exact app build approved and assigned to this model?
Processing configuration	Does the processor or acquirer still support this terminal, application, host, and merchant setup?
Merchant operations	Do sales, receipts, reversals, refunds, settlement, and support escalation still work as designed?

PAX itself still publishes the original A920 product page and an A920 quick setup guide. The product page's title currently carries the EOL label. Treat that label as a reason to verify the whole stack, not as permission to guess in either direction.

A920, A920 Pro, or A920 Max?

PAX's own A920 family comparison describes three different positions:

• A920: the compact original model for basic mobile or countertop acceptance. PAX currently marks this model EOL.
• A920 Pro: the performance step up, with a larger display and newer hardware. PAX lists Wi-Fi, LTE, Bluetooth, an integrated printer, camera capability, and PAXSTORE access on its A920 Pro PCI 5 page.
• A920 Max: the premium member of the line for environments that need more display, battery, and processing headroom.

PAX also announced a newer A920Pro PCI 7 in April 2026. PAX describes Android 14, PCI PTS 7, a 6.56-inch main display, a secondary customer-facing display, 4G LTE, Wi-Fi, Bluetooth, eSIM support, an integrated scanner, and a 6000mAh battery.

Those specifications matter, but they do not choose a payment terminal for you. The correct model is the one supported by the payment application, processing configuration, merchant category, connectivity plan, and operating workflow being deployed.

When an installed A920 can reasonably stay in service

Keep an existing device only when the responsible provider can confirm all of the following:

1. The serial number remains assigned to the correct merchant and location.
2. The device firmware and security posture remain supported.
3. The required payment and business applications still receive managed updates.
4. The processor configuration is still supported for that merchant account.
5. Chip, contactless, swipe fallback, receipt, reversal, refund, and settlement workflows have been safely validated.
6. Wi-Fi or cellular connectivity is stable in the real operating environment.
7. There is a documented support and replacement path.

A device that turns on is not necessarily a supported payment deployment. Conversely, an EOL procurement label does not automatically erase a working, supported installed base.

PAXSTORE approval is necessary evidence, not the entire deployment

PAX describes PAXSTORE as its device and application management ecosystem. That distribution layer is one of the reasons Android payment terminals can carry business applications alongside the configured payment stack.

But three statements are different:

• the application build is approved for distribution;
• the application is assigned to a particular device;
• the merchant's complete production workflow is ready.

Do not collapse them into one claim.

For example, Lifted Payments currently offers two PAX PayDroid applications:

• Lifted Pay is the standalone merchant-operated application for qualified card-present deployments.
• Lifted POS Connect is the payment companion that receives a sale from LiftedPOS, presents the supported tender flow on the terminal, and returns the result to the register.

PAXSTORE approved Lifted Pay version 0.0.5 and Lifted POS Connect version 0.2.9 on July 27, 2026. That is evidence about the named application builds and their distribution status. Merchant rollout still requires supported hardware, processing configuration, boarding, and validation.

A practical first-boot and handoff checklist

The official PAX quick guide covers the physical basics: inventory the terminal, power supply, and paper roll; prepare the battery; and hold the power key for roughly three to five seconds.

For a production handoff, extend that checklist:

1. Record the model, serial number, location, owner, and intended payment application.
2. Charge the device fully and inspect the battery, printer, charging contacts, and paper path.
3. Join the approved Wi-Fi network or validate the managed cellular plan.
4. Confirm the correct PAXSTORE assignment and let all managed updates finish.
5. Verify the merchant identity and processing configuration before taking a payment.
6. Run a controlled card-present test through the real workflow.
7. Confirm the result appears in the expected reporting and receipt surfaces.
8. Safely test the supported reversal or refund path.
9. Document who owns terminal, app, processing, and connectivity support.

That last item matters. A merchant should never have to discover during an outage that four vendors each believe someone else owns the problem.

Replace the device when support becomes ambiguous

Replacement is the safer choice when any of these are true:

• the provider will not confirm continuing model or firmware support;
• managed updates no longer arrive;
• battery, printer, or connectivity failures are recurring;
• the payment application is not approved or supported on the installed build;
• the merchant cannot safely test reversals, refunds, or reporting;
• security or compliance policy requires a newer device generation;
• downtime and support cost now exceed the value of keeping the device.

For new purchases, get the complete supported configuration in writing before ordering hardware. The terminal model alone is not the solution.

The merchant decision is bigger than the terminal

A PAX device is one layer of a payment system. The merchant account, processing configuration, terminal application, POS or gateway workflow, reporting, refunds, connectivity, and support ownership all have to agree.

The full PAX A920 setup and application guide maintains the current model comparison, setup steps, PAXSTORE explanation, troubleshooting path, and merchant-deployment checklist in one place.

If the goal is a new processing relationship rather than hardware-only research, start with the merchant application so the business, risk profile, hardware, and software path can be evaluated together.

---

Source note: product names and specifications above are based on the linked PAX Technology North America pages reviewed August 3, 2026. Availability, certification, firmware, and provider support can change. Confirm the exact configuration before purchasing or fielding a device.