Both run on Stripe Terminal. Here's how they differ.
NectarPay vs. PushPOS
PushPOS and NectarPay both run on Stripe Terminal with your own Stripe account. NectarPay works with every Stripe reader, Tap to Pay included, and is built around Stripe from end to end.
How NectarPay compares to PushPOS
|
PushPOS | |
|---|---|---|
| Payments | ||
| Payments into your own Stripe account | ||
| Payments into your own Stripe account | Yes | Yes |
| Card readers that aren't locked to the software | ||
| Card readers that aren't locked to the software | Yes | Yes Stripe readers, on your Stripe account |
| Tap to Pay on Android | ||
| Tap to Pay on Android | Yes | Not in their documentation Tap to Pay on iPhone, through Zeller |
| Hold a card now, capture it later | ||
| Hold a card now, capture it later | Yes | Yes For bar tabs |
| Phone and mail orders keyed on the reader | ||
| Phone and mail orders keyed on the reader | Yes | Not in their documentation |
| A cut of each vendor's sale, paid out to the venue | ||
| A cut of each vendor's sale, paid out to the venue | Yes | Not in their documentation |
| Selling | ||
| Self-checkout kiosks | ||
| Self-checkout kiosks | Yes | Partly, as an add-on or on some plans Table kiosk from AUD 19 a month |
| Payment links and QR codes | ||
| Payment links and QR codes | Yes | Yes Pay-by-link on invoices |
| Checkout on your own website | ||
| Checkout on your own website | Yes | Not in their documentation Only its own hosted online store |
| Questions and forms at checkout | ||
| Questions and forms at checkout | Yes | Not in their documentation |
| Variants and modifiers | ||
| Variants and modifiers | Yes | Yes |
| Fulfilment | ||
| Pickup, local delivery and shipping | ||
| Pickup, local delivery and shipping | Yes | Partly, as an add-on or on some plans Pickup and delivery; online ordering not on Standard |
| Orders split across locations with the stock | ||
| Orders split across locations with the stock | Yes | Not in their documentation |
| Inventory | ||
| Stock per location, with low-stock alerts | ||
| Stock per location, with low-stock alerts | Yes | Yes |
| Transfers between locations | ||
| Transfers between locations | Yes | Yes |
| Stock changes with reasons, and their history | ||
| Stock changes with reasons, and their history | Yes | Not in their documentation |
| Stock held during checkout | ||
| Stock held during checkout | Yes | Not in their documentation |
| Locations and team | ||
| Prices per location | ||
| Prices per location | Yes | Partly, as an add-on or on some plans Multi-location limited on Standard |
| Several businesses, each with its own payouts | ||
| Several businesses, each with its own payouts | Yes | Yes Franchisees settled under one group |
| Roles limited to the accounts people work in | ||
| Roles limited to the accounts people work in | Yes | Yes |
| Company sign-in and required two-factor | ||
| Company sign-in and required two-factor | Yes | Not in their documentation |
| A log of who changed what | ||
| A log of who changed what | Yes | Partly, as an add-on or on some plans For voids, discounts and comps |
| Your own logo and colours | ||
| Your own logo and colours | Yes | Partly, as an add-on or on some plans A branded POS app costs extra |
| ERP and API | ||
| A REST API for products, stock, orders and reports | ||
| A REST API for products, stock, orders and reports | Yes | Yes Orders, products, customers and reports; no public reference |
| Webhooks for orders and stock | ||
| Webhooks for orders and stock | Yes | Partly, as an add-on or on some plans Orders and payments; no stock events |
| Reports made on a schedule, delivered as files | ||
| Reports made on a schedule, delivered as files | Yes | Yes |
| Products, stock and customers in and out by spreadsheet | ||
| Products, stock and customers in and out by spreadsheet | Yes | Partly, as an add-on or on some plans Import by CSV; no product export documented |
Yes Partly, as an add-on or on some plans No Not in their documentation
Why counters switch from PushPOS
Every Stripe reader
Built only for Stripe
Keep what you have
Bring everything over from PushPOS
Your Stripe account
Keep it. Your payouts, payment history and dashboard stay as they are.
Connect it when you sign up to NectarPay, and pair your Stripe readers to your locations.
Your products
PushPOS's onboarding team handles imports; ask them for your product list as a spreadsheet.
In NectarPay, open Products, Import, and choose the file. Columns are matched by name, and you check the preview before anything is saved.
Your customers
Ask PushPOS for your customer list as a spreadsheet too.
Open Customers, Import, and choose it. First and last names are joined, and anyone already here isn't added twice.
Moving several locations? We'll do it with you.
Send us your PushPOS exports and we'll set up your catalog, locations and readers alongside you.
Switching from PushPOS: questions people ask
Can I keep my Stripe account if I switch from PushPOS?
Yes. Both run on your own Stripe account, so you connect the same account to NectarPay. Your payouts and payment history stay as they are.
Can I use my Stripe readers with NectarPay?
Yes. NectarPay works with the Stripe Reader S700 and S710, the BBPOS WisePOS E, the Stripe Reader M2, the Verifone V660p and P400, and Tap to Pay on Android. Pair each reader to one of your locations.
Can I bring my PushPOS products over?
Yes, as a spreadsheet. Import it under Products; NectarPay matches the columns by name and shows a preview before it saves anything.
Does NectarPay have self-checkout kiosks?
Yes. Kiosks run on Android tablets beside a Stripe reader, sell from the same catalog and stock as the register, and can be locked or taken over from the back office.
Open your first location today
Connect Stripe, add a location and take a payment. Moving several accounts over? We'll help.
What this page says about PushPOS comes from its own documentation and public records, as of October 2026:
PushPOS is a trademark of its owner, used here only to identify it.