The short answer
- It belongs to Verifone. FIPay came to Verifone with AJB Software Design in 2016. Oracle's guides still call one of its connections "AJB FIPay".
- It runs Verifone terminals. Oracle's current guide lists the P400 counter PIN pad, the e280 handheld and other Verifone models for FIPay, with Canada as an operating area.
- It handles more than card sales. Debit, refunds, gift cards, cheques and keyed phone orders all appear in Oracle's FIPay tables.
- The processor list is not public. Verifone's filings describe AJB's product as a payment gateway and switch, but no page we could read lists the processors it connects to.
- A change is often possible, never automatic. Keeping your POS depends on your FIPay version, your terminals and whether the new processor is certified for both.
What Verifone FIPay does
FIPay takes the sale from your POS, runs the card terminal and sends the payment to your payment processor for approval.
- Your POS
- Verifone FIPay
- The terminal
- The processor
- Your bank account
Your cashier rings up the sale, FIPay asks the terminal to take the card, the processor approves it, and the money reaches your bank account once the day's sales settle.
Terminals it runs on
Oracle's current FIPay guide lists only Verifone terminals, from the P400 PIN pad to newer Android models.
| Device | Type | Notes |
|---|---|---|
| Verifone P400 | Counter PIN pad | On Oracle's 25.0 FIPay list. Verifone's page: 3.5-inch touchscreen, keypad, LAN, RS232 and USB, chip and contactless |
| Verifone e280 (e280s) | Handheld reader | Oracle lists the e280. Verifone's e280s page: Bluetooth, Wi-Fi, touchscreen PIN entry, battery |
| Verifone M400, M424, M440, e285, e235 | Other Engage models | On Oracle's 25.0 FIPay list, in Verifone's Engage range |
| Verifone T650, CM5 | Trinity models | On Oracle's 25.0 FIPay list, in Verifone's Trinity range |
| Verifone M425, M450, UX700, V660, P630 | Android models | On Oracle's 25.0 FIPay list, under Verifone Android |
| Verifone MX915, MX925 | Older PIN pads | Listed only for the older AJB FIPay connection |
An earlier edition of Oracle's guide (23.0) also listed Ingenico Tetra, Move/5000 and DX8000 terminals and the PAX A920 for FIPay. The current edition names Verifone models only, so ask Verifone before you plan on another brand.
What it handles
Oracle's FIPay tables cover debit, refunds, gift cards and keyed phone orders, while Interac, pre-authorization and fleet cards are not named on any public FIPay page we could read.
| Feature | What the public pages say |
|---|---|
| Cards and contactless | Credit and debit payments and refunds. The P400 and e280s read chip, swipe and contactless cards |
| Interac debit and cashback | Debit is listed and Canada is an operating area, but Interac is not named. Cashback on the PIN pad is not marked for FIPay in Oracle's current table |
| Gift cards | Settings for Blackhawk, SVS, Givex and InComm. Oracle notes FIPay has six gift card providers, each with its own list of actions |
| Split payment on a gift card | If the card holds less than the total, it pays what it holds and the POS takes the rest another way |
| Offline sales | Oracle refers to FIPay's store-and-forward queue and says cheques cannot go in it. Limits for card sales are not published |
| Tokens | A token lets you refund a sale without the card. Saved cards for repeat charges are not described |
| Pre-authorization and completion | Not on the public pages. Oracle lists manual authorization, where staff key in an approval code |
| Phone orders | Card-not-present sales with security code and address checks, keyed on the PIN pad |
| Cheques | Cheque payment and cheque verification |
| Fleet cards | Not on the public pages we read |
| Encryption | The P400 and e280s are PCI PTS 5.x approved devices. No public page we read describes FIPay's own encryption or a PCI listing for it |
| End of day | On Oracle's direct connection, settlement runs from a batch script supplied by AJB, on a schedule or on demand |
Who uses it
Verifone's filings describe AJB's customers as large merchants in the United States and Canada. Oracle lists FIPay for Canada in its guides for Oracle Retail Xstore, its POS software for stores.
The one POS maker that documents FIPay in public is Oracle. Oracle Retail Xstore connects to it in two ways: a direct connection that Oracle calls AJB FIPay, and the newer Verifone Payments Connector through Oracle Payment Interface. If you run another POS, your POS reseller can tell you whether it uses FIPay. Our pages on integrated POS and semi-integrated POS explain how these connections differ.
Keeping your POS when you change processors
Middleware is what makes this possible. Your POS talks to FIPay, not to the processor, so the processor behind FIPay can change while the POS and its screens stay the same. Verifone's filings call AJB's product a payment gateway and switch, which means it routes each payment on to a processor.
For that to work in your store, five things have to be true:
- Your POS and its version use FIPay. Check the version number, not just the brand name.
- The new processor is certified with FIPay for your setup. That covers your FIPay version, your terminals and the cards you take. Verifone does not publish this list.
- A new merchant account is opened. Your old merchant ID does not move to a new processor. See merchant account.
- Your terminals may need to be re-keyed or replaced. A payment terminal set up for one processor does not always work for another.
- Your POS reseller usually does the install. They change the FIPay settings and test each lane.
None of this is a promise. Some setups need a POS or FIPay upgrade first, and a processor that is not certified with FIPay cannot be used through it.
What to check before a change
Your exact version
Ask your POS reseller for the FIPay version and the POS version. Oracle's tables show features arriving in specific releases, so two stores on FIPay can behave differently.
Your terminals
List each terminal model, and whether it is a counter PIN pad, a handheld or an older model. The MX915 and MX925 appear only on the older connection.
Interac and gift cards
Confirm Interac debit, cashback and debit refunds on your version with the new processor. Then check that activation, reload and balance checks still work with your gift card program.
Offline and phone orders
Ask what happens to card sales during an internet outage, how many can wait in the queue, and whether keyed phone orders stay switched on.
Who supports you after
Your POS reseller is usually the first call, Verifone supports FIPay itself, and the processor handles approvals and deposits. Get a name and a phone number for all three before the switch.
Where CleverPays fits
Verifone builds and supports FIPay. Your POS reseller installs and sets it up. The processor approves each payment and settles it to your bank account. CleverPays makes none of these and does not certify FIPay.
We read your setup and name each part: the POS and its version, the FIPay version, each terminal, and the processor behind it today. Then we tell you in writing whether a change is possible and what it would affect, before anything moves.
Sources
- Validated OPI Partners Guide 25.0: Verifone Payments Connector (FIPay OPI), Oracle, read 29 October 2026
- Validated OPI Partners Guide 23.0: Verifone FIPAY, Oracle, read 29 October 2026
- EFTLink 25.0: AJB FiPay feature reference, Oracle, read 29 October 2026
- EFTLink Core Configuration Guide 24.0: AJB FIPay, Oracle, read 29 October 2026
- EFTLink 24.0: Xstore and EFTLink core compatibility, Oracle, read 29 October 2026
- Form 10-K for fiscal 2016, Verifone Systems, Inc., read 29 October 2026
- Francisco Partners completes acquisition of Verifone (Form 8-K exhibit), Verifone Systems, Inc., read 29 October 2026
- Verifone P400, Verifone, read 29 October 2026
- Verifone e280s, Verifone, 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.
