The short answer
- Middleware is the go-between. It talks to your POS on one side and to the processor on the other, and it runs the terminal in the middle.
- It is why staff do not key the amount twice. The total goes from the register to the terminal, and the result comes back to the POS on its own.
- It can let you keep your POS. When a middleware is certified with more than one processor, the processor can change while the POS, the menus and the staff routine stay.
- Your exact setup decides it. Certification is checked for the middleware, its version, your POS and your terminals together. A product name alone does not answer it.
- Your POS reseller usually knows which one you run. The company that installed your POS set the middleware up, and it is the first call before any change.
How middleware fits
A card sale passes through five parts, and the middleware is the one that joins the POS to everything after it.
- Your POS
- The middleware
- The card terminal
- The processor
- Your bank account
The POS sends the amount to the middleware, the middleware runs the terminal and sends the card sale to the processor, the processor approves and settles it, and the money reaches your bank account. The approval comes back the same way, so the POS records the sale without anyone typing it in. For the terminal side of this, see semi-integrated POS.
The middleware we cover
These eight products cover retail and restaurant counters, large multi-lane stores, gas stations and self-service machines.
| Middleware | What it is | Terminals it runs on | Common in |
|---|---|---|---|
| Datacap NETePay | Windows payment middleware from Datacap Systems, between the POS, the terminal and the processor | Verifone P400, PAX IM30 and PAX Android models | Retail and restaurant counters, kiosks, vending |
| Verifone FIPay | Verifone's store payment middleware, first built by Toronto's AJB Software | Verifone P400, e280 and other Verifone models | Large retail chains on enterprise POS |
| AurusPay | Payment platform from Aurus Inc., built to work with many processors and terminals | Ingenico Lane and Link, Verifone, Equinox, Castles | Big box, grocery, specialty and restaurant chains |
| Tender Retail | Canadian payment middleware since 1985, now part of ACCEO | Ingenico, Verifone and Castles terminals, unattended kiosks | Grocery, convenience, hotels, parking, pharmacy |
| LOC Software | Quebec POS and back office with payments and a fuel module built in (LOC SMS, now ThriVersA) | Ingenico PIN pads, pump payment readers | Independent c-stores, unbranded fuel sites, grocers |
| Wayne iX Pay | Dover Fueling Solutions' card reader and software at the pump, reporting to the site's POS | iX Pay 2 readers, iX Pay T7 retrofit | Gas stations with Wayne dispensers |
| Apriva BV1000 | Apriva's gateway with an outdoor chip, PIN and tap kit for machines with no cashier | BV1000R reader, BV1000K PIN pad, BV1000CL contactless reader | Parking pay stations, fuel pumps, vending, kiosks |
| FreedomPay | Payment platform between the POS, hotel system or website and the processor | Ingenico Lane/3600 and Lane/7000, Castles S1F4 PRO, Verifone, PAX | Hotels, food service, venues, large retail |
Each page explains what the product does, what it handles, and what to check before you change the processor behind it.
How to tell which one you have
Most owners do not know the name of their middleware, and they do not need to. These are the quickest ways to find out.
- Ask your POS reseller. The company that installed or supports your POS chose the middleware and can name it and its version.
- Look at your POS payment settings. The tender or payment setup screen often names the payment software it talks to.
- Look at the terminal. The start-up screen or the payment app on the terminal sometimes shows the middleware's name.
- Look at your invoices. A middleware licence or support line may appear on your POS reseller's bill.
- At a gas station, check the pump and the counter separately. The pump reader and the store counter often run different software.
Keeping your POS when you change processors
Changing processors without changing your POS is often possible, but only when every part of your setup lines up.
- The new processor has to be certified with your middleware. Each middleware keeps its own list of the processors it is certified with, and it can differ by version and by terminal.
- Your POS version has to be on the list too. Some middleware certifications are for specific POS products and versions.
- You open a new merchant account. A merchant number belongs to the processor that issued it and does not move to another one. See merchant account.
- Your terminals may change. The new processor may need your terminals re-keyed, re-loaded or replaced.
- Your POS reseller usually does the work. The switch is a configuration change on your POS and middleware, and the reseller is often the one who makes it.
When any of these does not line up, the change becomes a POS project rather than a settings change. That is worth knowing before you sign anything.
What to check before a change
Your POS and its version
Write down the POS product, its version and the middleware version. Certification is checked against these exact versions, not the brand name.
Your terminals
List each terminal model and how many you have, at the counter, on the floor and outdoors. Some middleware runs only on certain models.
Gift cards, loyalty and fleet cards
Gift card and fleet card programs connect through the middleware too. Check that each program you accept still works after the change.
Offline and phone orders
If you take cards during an internet outage or key in phone orders, confirm the new setup does the same before the change, not after.
Who supports you after
Know who answers when a terminal stops: your POS reseller, the middleware company or the processor. The answer often changes when the processor does.
Where CleverPays fits
The middleware company builds the software. Your POS reseller installs and supports it. The company that processes your card payments approves and settles each sale. CleverPays makes none of the software on these pages.
We can read your setup and name each part: the POS, its version, the middleware, the terminals and the processor behind them. Then we tell you in writing what a change would affect, before anything moves.
Sources
- Each middleware row is sourced on its own page, linked in the table above: Datacap NETePay, Verifone FIPay, AurusPay, Tender Retail, LOC Software, Wayne iX Pay, Apriva BV1000 and FreedomPay, read 29 October 2026
- Semi-integrated POS and POS integrations, read 29 October 2026
Product and company names on this page are trademarks of their respective owners. CleverPays is not affiliated with or endorsed by them.

