Getting started

PAX A35: setup, connection options and what it needs from the host POS

How a PAX A35 PIN pad is powered and connected (Type-C communication cable with DC power, optional Powered USB, Ethernet or Wi-Fi), what the host POS must provide, and the on-device reset.

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

Ask Allstar AI about this guide

Check first

  • Which POS software drives the A35, and has that vendor certified the A35 and told you which connection (USB or Ethernet) to use?
  • Is the unit powered from the AC adapter on the communication cable, or from a Powered USB port?
  • Does the A35 need to be on the same network as the POS (Ethernet or Wi-Fi), or is it on a direct cable?

The A35 is a customer-facing PIN pad driven by a POS or ECR. This guide covers power, cabling and what the host side must do.

Before you start

  • Confirm with the POS vendor that the A35 is supported and which connection they want (USB over the communication cable, Ethernet, or Wi-Fi).
  • Power comes from the AC adapter on the communication cable's DC port by default; a Powered USB cable from the POS is the alternative.
  • Allstar can ship the unit injected for the processor; the POS integration itself is the ISV's or ISO's job.

Steps

  1. Open the rear cover, seat the communication cable in the Type-C interface, and fit any SAM or microSD card. Expected: cable firm, cover closed.
  2. Power via the AC adapter on the cable's DC port, or via Powered USB from the POS. Expected: screen lights, unit boots.
  3. Connect to the POS as instructed: USB side of the cable, Ethernet, or Wi-Fi (2.4 or 5 GHz) in Android settings. Expected: POS sees the PIN pad or the A35 shows a network connection.
  4. Give the POS vendor or ISO the connection details; they configure the PIN pad in their software and in the payment application. On BroadPOS-style apps the terminal must be in External POS mode (Func > Settings > System Settings > ECR-Terminal Integration Mode > External POS). Expected: a test transaction from the POS reaches the A35.
  5. If the unit hangs, hold X and O for 5 to 8 seconds. Expected: the OS restarts.

If that did not work

If the POS cannot see the A35 after power and cabling are confirmed, the problem is on the integration side (POS software, IP addressing, or payment app mode). Collect the POS software name and connection type and contact Allstar support or the ISO.

Sources

Stop and contact support if

  • The A35 is not listed as supported by the POS vendor: stop. Integration of PAX Android devices goes through the ISV, the ISO or PAX sales, not the merchant.
  • The application asks for a password you do not have, or the mode setting is locked: contact Allstar or your ISO. Passwords are never shared here.
  • Any tamper or security message on screen: stop, contact Allstar support for RMA.

Contact Allstar support (support@allstarterminals.com, 888-403-7066) with the serial number, the POS software name, the connection type and the exact message on the A35 or POS.

Contact support about this

Notes

  • The A35 quick setup guide shows ports only in an image and gives no host-side setup steps. It says the A35 'typically connects to a retail POS system or ECR, or a standalone payment terminal via a communication cable'. RS232 is not mentioned on the pax.us page or guide; PAX's connection table lists the A35 as LAN and Wi-Fi.
  • The External POS mode path is for PAX's BroadPOS-style applications (General Information for Android Terminals). Other payment apps (for example Datacap or gateway apps) configure integration differently.
  • PAX's semi-integration page says Android device integration questions go to PAX sales; the integration itself needs a PAX Developer Portal account and PAXSTORE access, which is ISV or ISO work.
  • The guide gives no version or date; the product page lists PCI PTS 6.x SRED.

Sources

Was this guide helpful?

More A35 guides