Lifted Pay and Lifted Connect give us two proven ways to configure a supported PAX deployment. Start with the merchant application; we will determine whether either app, another compatible integration, or a custom solution fits the business.
A Lifted-built option for merchants who need card-present payments on a supported smart terminal, connected to Lifted's merchant tools.
Explore Lifted Pay
A Lifted-built option for merchants running LiftedPOS who need a supported PAX terminal to handle the card-present payment flow.
Explore Lifted Connect
| Decision | Lifted Pay | Lifted Connect |
|---|---|---|
| Primary job | Standalone payment application and merchant portal | Card-present companion for LiftedPOS |
| Cashier starts in | Lifted Pay on the PAX terminal | LiftedPOS on the register |
| Best fit | A counter that needs payments without a full inventory register | A retailer using LiftedPOS for orders, inventory, staff, and reporting |
| PAXSTORE application | Lifted Pay, version 0.0.4 | Lifted POS Connect, version 0.2.8 |
| Public product | Lifted Pay details | Lifted Connect details · LiftedPOS |
PAXSTORE approved Lifted Pay version 0.0.4 and Lifted POS Connect version 0.2.8 on July 27, 2026. The approved builds are the distribution foundation for the Lifted payment application family.
Precise by design: PAXSTORE approval is not a PAX endorsement, processor approval, PCI certification, EMV-kernel certification, or guarantee that any unqualified merchant configuration is production-ready.
The merchant application gives us the account and operating context needed to qualify Lifted Pay, Lifted Connect with LiftedPOS, another integration, or custom development.