Lifted Pay turns a PAX A920 into your whole counter — tap, dip, and swipe with full catalog checkout on the terminal, and a back office that tracks true item cost and margin on every sale.
Demo on a simulated processor · no live card charged.
Built and operated by the team behind LiftedPOS and the Lifted merchant portal — the same people who answer when you call.
Lifted Pay is a Lifted-built application offered inside a qualified merchant processing deployment — most counter-service merchants land on Lifted Pay on a PAX A920, and where a full POS or gateway integration fits better, we say so before you sign.
Payment ISO with your own processing relationships? Lifted Pay deploys on your VAR sheet — see ISO partners.
SwipeSimple stops at items and low-stock alerts — no cost field, no purchase orders, no margin report. Lifted Pay ships all three today, with invoices and payment links next on the roadmap.
Comparison lines are drawn from SwipeSimple’s and Square’s own published documentation.
Actual Lifted Pay interface · demonstration against a simulated processor · no live card charged.
Actual merchant portal · sample catalog data.
Today it sells on the counter — from a keypad or straight from your product catalog — prints the itemized receipt, reports, handles eligible refunds, and keeps the back office honest with tracked stock and true item cost.
The terminal stays dead simple on purpose — one big keypad, one Charge button, glove-friendly and one-handed. When it’s time for the card, the secure PAX payment layer takes the screen for tap, dip, or swipe, and hands back a clean approved-or-declined result. All the complexity lives in the portal, not in your cashier’s way.
Actual Lifted Pay interface · sale demonstrations run against a simulated processor · no live card charged.
Ring up products, not just amounts. Category tabs, favorites, variants, and quantities build the cart in a couple of taps; item-level taxes — including prompt-at-sale — apply per line; and a barcode scan on the terminal’s built-in scanner drops the item straight into the cart. The catalog syncs automatically from the portal, so there is nothing to key in on the terminal.
Actual Lifted Pay interface · demonstration against a simulated processor · no live card charged.
The portal manages the whole catalog — items, variants, categories, item-level taxes, images, CSV import and export — and tracks the stock behind it. Every quantity change lands in an auditable movement ledger with who, when, and why; low-stock alerts arrive by email; and item cost is a weighted average recomputed as purchase orders are received, not a number someone typed once.
Actual merchant portal · sample catalog data.
Draft a purchase order against a linked supplier, send it, and receive stock line by line — partial deliveries included. Every delivery is booked as an immutable receipt against the order with a full status history, weighted-average cost re-weights on each receive, and the item-margin report shows what every product actually earns: revenue, COGS, margin, and margin % per item.
Actual merchant portal · sample catalog data.
The saved-card processing path is proven internally, but its self-service merchant route and hosted-fields verification are not released. Refunds of qualifying completed transactions are live today for eligible roles and payment rails.
Actual Lifted interface · simulated data · saved-card charge is a product preview · qualifying refunds are live · no charge performed.
Gross, refunds, and net volume, tips, average ticket, a net-volume trend, and totals by terminal, rail, and card brand — with the batch reconciled on the dashboard. Margin reporting now ships with the catalog: the item-margin report above puts revenue, COGS, and margin % on every item you sell.
On-device totals ship on the terminal, too.
Actual merchant portal · sample catalog data.
An approved catalog sale gets two pieces of paper, each from the layer that owns it: the secure payment layer prints the card slip — with per-device copy settings you control from the portal — and Lifted Pay prints its own itemized merchant receipt, because the secure layer can’t print your basket. Missed the tear-off? Reprint the last receipt from the admin menu. Connection dropped? A durable offline queue holds receipts and customer saves and replays them until the server acknowledges every one.
Actual merchant portal · receipt copies and tip presets are set per device and sync to the terminal.
These features are specced and in build — not shipping yet. Card-present and catalog sales, dual pricing, inventory, purchasing, and reporting run today; the browser virtual terminal and browser card-on-file routes remain previewed until hosted-fields validation and release gating are complete.
Build invoices from the catalog, take a deposit or partial payment, with reminders on by default.
Fixed, open, or per-item links with a QR, paid on a hosted page where card data never touches your device.
Manage the fleet and invite your team with Admin, Manager, and Member roles from one screen.
Branded, itemized receipts with masked PAN and auth code, delivered by email or text. Branded templates and copy/signature rules land at launch.
From the tap forward, Lifted Pay never touches a card number. What it holds instead — a secure network token — is what makes saved cards, late refunds, and a small compliance footprint possible.
The customer picks card or cash; the moment they tap, the card is already ciphertext. It’s end-to-end encrypted inside the secure reader, and on a qualified account what comes back to Lifted Pay is a network token scoped to that card — stable across taps, so the same card is the same customer next week. Either way, the card number itself never reaches the app or the portal: they hold the token, and receipts carry masked details only — which is what supports a SAQ-A compliance posture. And because the token stays valid after the batch closes, so do your refunds.
Compliance scope depends on your complete environment — SAQ-A is the posture this design supports, not an automatic outcome. More: tokenization & SAQ-A.
Actual Lifted Pay interface · demonstration data · no live card charged.
Nobody fills in a signup form at a counter. So Lifted Pay builds the list from the sales themselves: every approved credit sale can mint an encrypted saved card and a deduplicated customer record automatically — and even when no token comes back, the card’s own identity still matches the sale to the same customer. Charging a saved card happens right on the terminal, behind the admin PIN, and the portal keeps an expiring-cards view so a renewal never surprises you.
Terminal charges to a saved card are live. The browser saved-card charge route remains a product preview in release gating.
Actual merchant portal · sample data · auto-saved cards appear beside manually added customers.
This is how the shipped release is built—not a generic terminal diagram. The Android app composes the sale, journals it before the card is touched, hands payment interaction to PAX, and keeps reporting the same result until the back office acknowledges it.
The journal-before-send rule means only one transaction can ever be in flight, and approved and declined results commit atomically with their outbound report. An interrupted response becomes a question we resolve — not a card charged twice.
Lifted Pay uses PAX POSLink2 to hand the transaction to the configured secure payment layer for card prompts and reader handling, then receives a normalized result without PAN, track, or PIN data.
For qualified accounts, an approved sale can mint a secure token for card-on-file charges and refunds. The raw token is kept in Android Keystore-backed encrypted storage, stripped from the plaintext journal, and never printed on a receipt.
The outbound queue is acknowledgement-gated. If connectivity drops after the host responds, Lifted Pay replays the stored result by transaction reference until the server acknowledges it — so the terminal and the portal always reconcile to one sale, and a network blip never becomes a second charge.
Apply for a Lifted Payments account or bring your existing processor’s VAR sheet. We board you and ship your terminal — it’s waiting in your portal before the box arrives.
Your PAX A920 arrives ready. It activates on first boot from its serial — no config, no cables, no IT.
Charge cards on the counter and watch every sale land in the merchant portal — gross, tips, fees, and net, per terminal.
Actual merchant portal · sample catalog data.
The whole shipped feature set, scannable — so nothing on this page is the thing you find out about later.
On the roadmap, not in the box yet: invoices with deposits, payment links and hosted pay pages, emailed & SMS receipts, and the browser virtual terminal. They’re marked Coming until they ship.
Pay for the devices you run and the people who use them. That’s it.
The app on one PAX terminal. Card-present and catalog sales, itemized receipts, batch, and reporting — with full catalog, inventory, and purchase-order management in the web portal. First user included.
Add a teammate with their own login and role. First user is included with your first device.
Show a card price and a lower cash price on every sale. The terminal presents both before payment, receipts itemize the difference, and the portal records your signed disclosure attestation. Enabled per device. The cash path stays surcharge-free.
Add Verizon Mobile Internet to any terminal. Sell anywhere there’s signal — no Wi-Fi required.
Software fees are billed monthly. Processing rates are quoted with your account — most merchants either beat their current effective rate or eliminate it with dual pricing. Bring a recent statement and we’ll show you the math before you sign anything.
Everything on this page priced here ships today; roadmap items aren’t billed until they ship.
One handheld smart terminal that runs your whole counter — touchscreen, card reader, scanner camera, printer, and battery in one device.
| Model | Display | Printer & battery | Best for |
|---|---|---|---|
| PAX A920 | Compact touchscreen | Built-in printer, all-day battery | Portable checkout and straightforward card acceptance |
| PAX A920 Pro | Larger, brighter display | Built-in printer, all-day battery | Busier counters that want more screen and headroom |
| PAX A920 Max | Largest display in the family | Built-in printer, top-end battery | Catalog-heavy and higher-volume counters |
Wi-Fi included · Verizon cellular +$19.99/mo per device. Compare current models and first-boot steps in the PAX A920 setup guide.
Start the merchant application. We will review the account, qualify the deployment, and determine where Lifted Pay fits.
Built and operated by the team behind LiftedPOS and the Lifted merchant portal — the same people who answer when you call.
PAXSTORE-approved · PAX PayDroid