PAXSTORE

PAXSTORE for resellers: push an application to a terminal

Push a payment application (with or without a parameter file) from PAXSTORE to one PAX terminal: Push Immediately, Scheduled Push and Force Update, plus how to monitor, disable or reset the push.

Applies to
PAX A920, A920 Pro, A80, A35, A77, A60
Payment application
PAXSTORE
Last reviewed
Oct 26, 2026 by Abdul Rashid

Ask Allstar AI about this guide

Exact messages this covers

  • App installation has been delayed as it was busy
  • No app available

Check first

  • Is the terminal powered on and online? A push only completes when it is.
  • Does the app use a parameter file? If so, is there a saved template, or must the parameters be completed by hand?
  • Is a payment application already on the terminal with an open batch? Force Update overwrites it; close the batch first.
  • Should the push run only over Wi-Fi or Ethernet (to avoid cellular data)?

For resellers managing their own PAXSTORE estate. This pushes an application to a single terminal; group pushes are a separate PAXSTORE feature.

Before you start

  • Terminal profile exists under an active merchant. Pushes stage on inactive profiles but only deliver once the profile is active and the device is online.
  • Know whether the app takes a parameter file and have the values ready. Processor and host values come from the ISO or processor.
  • If replacing a live payment app, close the batch first.

Steps

  1. Terminal Management > merchant > Terminal List > terminal > App & Firmware > + PUSH APP. Expected: Add Push App pop-up.
  2. APP > tick the application(s), or Push Templates for a saved parameter file > OK. Expected: 'Push App added successfully'; Edit Parameter opens for parameter apps.
  3. Parameter apps: fill every required field on every tab (last successful push values are pre-filled), then NEXT, or SAVE / SAVE AS TEMPLATE then NEXT. Expected: 'App parameter saved successfully'.
  4. Choose Push Immediately, Scheduled Push (time zone, effective and expired date) or Force Update (confirm the overwrite). Expected: option selected.
  5. Optional: Push Configuration > Wi-Fi Only > Enable. Expected: the download avoids cellular data.
  6. ACTIVATE > OK. Expected: 'Activated Successful'; a moving arrow while the push runs.
  7. Check Push Detail and the terminal. Expected: 'Your push task is success' and the app in Installed Apps.
  8. DISABLE to stop a running push; RESET to return it to Pending. Expected: task disabled or reset.

If that did not work

  • The device must be powered on and online; a scheduled push keeps retrying until its expiry date.
  • 'App installation has been delayed as it was busy': clear outstanding transactions, uninstall, re-push. Ask Allstar first if unsure.
  • 'No app available' on the terminal: the app needs an update, or the terminal's PAXSTORE server settings are wrong. Allstar can check them; do not edit server settings yourself.
  • Firmware and RKI pushes are different task types. Contact Allstar.

Sources

Stop and contact support if

  • Force Update on a payment application with an open batch can lose transactions. Confirm the batch is closed before confirming Force Update.
  • 'App installation has been delayed as it was busy' in Push Details: make sure no transactions remain in the terminal database, uninstall the app on the terminal, then re-push. If unsure, contact Allstar before uninstalling.
  • Parameter values for Host, Communication or security tabs: use only values supplied by the ISO or processor. Never guess host URLs, ports or key settings.
  • Pushes of firmware or remote key injection (RKI) are separate task types and are not covered here. Contact Allstar.

Contact Allstar support (sales@allstarterminals.com, 888-403-7066) with the serial number, application name and version, push status shown in PAXSTORE and any message on the terminal.

Contact support about this

Notes

  • The Push App QRG is from 2020 (PAXSTORE 7.0 era) and the Reseller User Guide from 2022 (8.4). PAXSTORE is at 10.0 (12-30-2025), which added Push Task Approval (9.8) and Parameter Partial Push (10.0); if your marketplace has approval switched on, a push may wait for an approver. Screens may differ from the QRG.
  • Parameter tabs listed are those of PAX's traditional BroadPOS-style applications; Android apps from other developers have their own parameter layouts or none.
  • Several QRG steps rely on screenshots (icons, the Push Templates selection). The text alone does not show where the green arrow or trash-can icons are.
  • The PAXSTORE QRGs were read from local copies downloaded from pax.us.

Sources

Was this guide helpful?

Related guides

More A920 guides