Dejavoo is best known for its terminals: the countertop and wireless units that a large share of independent processors place. Less known is that Dejavoo also runs a gateway, iPOSpays, so a merchant with a Dejavoo terminal can take online, keyed, recurring and link payments on the same account with one report. We are a Dejavoo dealer. This page describes the gateway, how it fits with the hardware, and when we use it versus an independent gateway.
What iPOSpays does
From Dejavoo’s site as of September 2026:
- Hosted payment page (checkout). A payment page for websites that keeps card entry off your server.
- Cloud POS virtual terminal. Browser-based keyed and stored-card transactions.
- Recurring payments. Scheduled billing from tokenized cards.
- Payment links. Send a request by email or text; the customer pays on a hosted page.
- Tokenization. Stored cards for repeat customers.
- Level 2 and 3 data enrichment. Auto-fill so commercial card transactions qualify for lower interchange.
- S.A.F.E. fraud protection. Proactive transaction monitoring.
- SPIn. Dejavoo’s turnkey API for POS software integration, described as a one-and-done integration.
Sold to ISOs, ISVs and resellers as part of Dejavoo’s partner ecosystem. Merchants get it through a dealer.
How it fits with the terminals
A Dejavoo terminal (the Z-series countertop units, the wireless and mobile units) is boarded to a merchant account and processor. iPOSpays sits on the same account for everything that is not a tap or dip at the counter. The benefit is one login and one reconciliation for in-store, online, keyed and recurring. The limitation is that iPOSpays is Dejavoo’s gateway; if your website, practice management or invoicing software has a native integration to accept.blue, NMI or Authorize.net and not to iPOSpays, those are the better fit for the online side while Dejavoo stays on the counter.
Dual pricing on Dejavoo
Dejavoo terminals support dual pricing configured at the processor level: the cash price and card price display on the terminal before the customer chooses, the receipt shows the price paid and tender type, and the merchant’s processing cost on in-store sales is zero. It is the default configuration on terminals we place. For online and link payments, transactions are card-only and run at the card price; the disclosure rules are the same. Details and the comparison to surcharging are on the dual pricing vs surcharging vs cash discount page.
Pricing
Dealer-set, as with every partner-sold gateway. Through us the quote shows: terminal placement (free-equipment program where the merchant qualifies, or purchase), the dual pricing program, the gateway monthly and per-item fee if iPOSpays or an independent gateway is added, and interchange-plus processing for any card-not-present channel. Month to month.
When we use iPOSpays vs an independent gateway
| Situation | Gateway |
|---|---|
| Dejavoo at the counter, occasional keyed or link payments, no cart | iPOSpays: one account, one report |
| Dejavoo at the counter plus a WooCommerce, Magento or BigCommerce store | accept.blue or NMI for the store, on the same merchant account |
| Invoicing synced to QuickBooks | Hyfin or accept.blue invoicing; Dejavoo for walk-ins |
| B2B with commercial cards | Either; both do Level 2 and 3 |
| Software with a SPIn integration | Dejavoo terminals driven by the software; gateway per the software’s online integration |
The virtual terminal page covers keyed-payment pricing and PCI for staff, which applies to iPOSpays’ cloud terminal as much as any other.