Device error messages

PAX Android terminals (A920, A920 Pro, A80, A35): common on-screen messages and what to do

A lookup of messages PAX documents for its Android terminals and PAXSTORE client, what each one means, and the first action to take or when to stop and call Allstar.

Applies to
PAX A920, A920 Pro, A80, A35
Last reviewed
Oct 26, 2026 by Abdul Rashid

Ask Allstar AI about this guide

Exact messages this covers

  • Login failed, terminal (SN:nnnnnnnnnn) not registered
  • NPM
  • Ped Tampered
  • Terminal Be Attacked
  • Check LAN Cable
  • Connect Error
  • Connect Timeout
  • DNS Resolve Error
  • DHCP Error
  • No app available
  • License Not Active or Terminal Not Active
  • Terminal Already Exists
  • Terminal SN Not Exist in Global Marketplace
  • Model Mismatched in PAXSTORE
  • App installation has been delayed as it was busy
  • Comm Err 1505, -400
  • Invalid Batch Seq

Check first

  • Where does the message appear: the PAXSTORE client, the payment application, during boot, or in the PAXSTORE web portal?
  • Did anything change just before (new network, firmware update, drop, battery swap)?

A quick lookup for messages PAX documents on its Android terminals and in PAXSTORE. Each entry gives the meaning and the first thing to do. Tamper, firmware, key and password messages all go straight to Allstar.

Before you start

  • Write the message down exactly, with model and serial number.
  • Note what changed just before it appeared.

Steps

  1. 'Login failed, terminal (SN:...) not registered': serial not added or activated in PAXSTORE. Add and activate it, reopen the client. Expected: client logs in.
  2. 'NPM': no paper or paper not seated. Reload the roll. Expected: clears in Auto mode.
  3. 'Ped Tampered' / 'Terminal Be Attacked': security lock after a drop, tampering or a damaged internal battery. Stop; RMA only. Expected: Allstar arranges RMA.
  4. 'Check LAN Cable', 'DHCP Error', 'Connect Error' at boot: no usable network. Reseat the cable, confirm cable type and link light, check DHCP/static, run Function > Ping. Expected: ping Successful.
  5. 'DNS Resolve Error': the network's DNS is broken; ISP or network admin fixes it. After a download it can also mean a firmware update is due (Allstar). Expected: ping passes once DNS works.
  6. 'Connect Timeout': no host reply within 30 seconds. Check the network, then the host side with Allstar or the processor. Expected: transactions connect.
  7. 'Connect Error' during a PAXSTORE download on a working network: port 9080 is probably blocked. Expected: download completes once opened.
  8. 'No app available': app needs an update, or the client's server settings are wrong. Allstar verifies; then delete and re-push. Expected: app listed.
  9. 'License Not Active or Terminal Not Active': activate the terminal profile in the portal. Expected: clears.
  10. 'Terminal Already Exists' / 'Terminal Serial not available': serial owned by another reseller; they remove it or PAX issues a release form. 'Terminal SN Not Exist in Global Marketplace' / 'Model Mismatched in PAXSTORE': PAX North America corrects its database. Expected: serial can be added.
  11. 'App installation has been delayed as it was busy': clear outstanding transactions, uninstall, re-push. Expected: push succeeds.
  12. 'Comm Err 1505, -400': expected; no RKI download pending. Exit or Cancel. Do not downgrade. Expected: terminal continues.
  13. 'Invalid Batch Seq': batch number out of step with the processor. Function > Settings > Host settings > Batch number, +1; or get the number from the processor. Expected: batch closes.

If that did not work

Anything involving tamper, firmware, keys, passwords or processor parameters stops here and goes to Allstar support with the exact wording, model and serial.

Sources

Stop and contact support if

  • 'Ped Tampered', 'Terminal Be Attacked' or any security or tamper wording: stop, contact Allstar for RMA. Never attempt to clear it.
  • Messages about firmware ('Error Lookup Firmware Entry', 'Warning App Exception', 'SO Open Error UAI', 'Open UAI'): PAX says firmware updates are done by phone with PAX support. Contact Allstar; do not flash firmware.
  • Messages that ask for a password, key, or processor parameter: contact Allstar. Passwords, key injection and processor settings are never handled through this knowledge base.
  • 'Status Error' or 'Authentication Error' on First Data hosts: provisioning or Datawire registration is processor work. Contact Allstar or the processor.

Contact Allstar support (sales@allstarterminals.com, 888-403-7066) with the model, serial number, payment application, processor and the exact message on screen.

Contact support about this

Notes

  • All sources are PAX Technical Knowledge Base support pages (PAX's Confluence site, linked from the pax.us Support menu). Several are written for support agents and mix traditional (non-Android) and Android terminals; only entries PAX applies to Android terminals or PAXSTORE are included.
  • Menu paths (Function > Ping, Function > Settings > Host settings) are for PAX's BroadPOS-style payment applications. Other apps differ.
  • 'Comm Err 1505, -400' and 'Invalid Batch Seq' are documented in the General FAQ without a model list; PAX presents them as general PAX terminal behaviour.
  • Only messages found verbatim in PAX documents are listed. Messages seen in the field but not documented by PAX are not included.

Sources

Was this guide helpful?

Related guides

More A920 guides