Lifted Connect is an application we built for merchants using LiftedPOS with supported PAX hardware. Apply for processing and we will qualify the account, terminal, payment stack, and complete register-to-terminal deployment.
The application connects the stack. We configure the stack.
Lifted Connect is not a standalone download funnel. It is one component of a qualified merchant solution that can include processing, LiftedPOS, supported PAX hardware, deployment validation, and ongoing support.
01 / APPLY
Submit the merchant application.
Underwriting reviews the business and processing profile while our team learns the register, terminal, locations, and workflow.
02 / QUALIFY
Confirm the complete payment path.
We validate processor compatibility, PAX configuration, LiftedPOS requirements, networking, and the supported Lifted Connect build.
03 / LAUNCH
Configure and test before go-live.
The register, terminal, merchant account, and reporting path are exercised together before the merchant begins accepting payments.
Lifted Connect has one job: move a payment request and its result between LiftedPOS and the configured PAX payment stack.
01 / REGISTER
Send the total.
The cashier starts credit or debit in LiftedPOS. The register sends the amount and a transaction reference to the paired terminal.
02 / TERMINAL
Take the card.
Lifted Connect presents the payment choice and hands card interaction to the configured payment application on the PAX device.
03 / RESULT
Close the sale.
The approved or declined result returns to LiftedPOS so the order, receipt, and reporting stay connected.
Code-backed architecture
Inside the approved build.
The product page is grounded in the shipped Android implementation. Lifted Connect is a small, guarded payment bridge: discover and pair the device, authenticate it, hand the card flow to PAX, and return one durable result to LiftedPOS.
01 / DISCOVER
Pair without broadcasting the terminal serial.
The app advertises an opaque per-install identity over NSD/mDNS so an authenticated LiftedPOS register can claim it in one tap. Discovery never opens an inbound money-control socket; commands still arrive over the outbound cloud channel.
02 / AUTHENTICATE
Prove the terminal, not a reusable password.
After pairing, the terminal signs its hello with HMAC over its identity, serial, timestamp, and nonce. The per-terminal secret stays in Android Keystore-backed encrypted storage and does not cross the wire again.
03 / HAND OFF
POSLink2 calls BroadPOS on the device.
Lifted Connect binds to BroadPOS through PAX POSLink2 over AIDL. BroadPOS owns tap, insert, swipe, PIN, and host authorization; Lifted Connect maps only the safe result fields needed by the register—never PAN, track, or PIN data.
04 / RECONCILE
Retry the message, never the charge.
Single-flight state blocks double taps. A repeated transaction reference re-reports the stored terminal result instead of running the payment again, while unacknowledged results are replayed after reconnect until LiftedPOS commits them.
CaptureCredit or debit sale with a host-approved transaction number and authorization code.
VoidResolve the original terminal result and reverse an open-batch authorization by its host transaction.
ReturnCard-present refund, plus a qualification-gated token return when the original sale minted card-on-file data.
Inquire + closeResolve ambiguous outcomes and close the terminal batch through the same POSLink2 engine.
Real application screens
The real screens, seated in the PAX A920.
These product mockups use the approved build's actual UI captures inside the terminal screen—ready, rail selection, and the final host result.
READY / waiting for LiftedPOS
RAIL / credit or debit
RESULT / approved
What approval means
Approved for distribution. Qualified for each rollout.
PAXSTORE approved Lifted POS Connect version 0.2.8 for the PAX PayDroid platform on July 27, 2026. That verifies the approved application build and its PAXSTORE distribution state.
It is not a blanket processor, PCI, EMV-kernel, or merchant-production certification. Lifted validates the complete deployment before a merchant goes live.
A production deployment still needs:
Supported PAX PayDroid hardware and operating environment
A compatible processor, BroadPOS package, and terminal configuration
Merchant boarding and the correct account credentials
LiftedPOS pairing, network reachability, and end-to-end validation
Yes. PAXSTORE approved version 0.2.8 on July 27, 2026 under the application name Lifted POS Connect. Lifted Connect is the customer-facing product name.
Can any PAX terminal use it immediately?
No. A merchant rollout depends on supported hardware, the processor and BroadPOS configuration, boarding, network access, LiftedPOS pairing, and successful end-to-end validation.
Does Lifted Connect replace the payment application?
No. It coordinates the request between LiftedPOS and the PAX terminal. The configured payment application and processor stack handle card interaction and authorization.
Where do I learn about the full register?
Visit LiftedPOS.com for the retail, inventory, staff, reporting, and register product.
Lifted Connect
Apply for the payment setup behind LiftedPOS.
Submit the merchant application so we can review the account and qualify the processor, hardware, LiftedPOS, and Lifted Connect requirements.
