Merchants rarely notice a POS network that works. They absolutely notice one that doesn’t — a terminal that times out during a queue, a routing failure that declines a card that should have gone through, a reconciliation report that doesn’t match what actually settled. Over years of advising acquirers and PayFacs on POS infrastructure, the pattern is consistent: uptime and routing resilience are what merchants judge you on, even when they can’t articulate it that way.
Uptime Is a Design Decision, Not a Monitoring Metric
Too many acquirers treat terminal uptime as something you measure after the fact rather than something you design for upfront. By the time a monitoring dashboard tells you connectivity dropped at a merchant location, the transaction — and often the customer’s confidence in that merchant — is already lost.
- Dual-path connectivity (cellular failover alongside primary broadband or ethernet) should be standard for any merchant location above a modest transaction volume threshold, not an upsell.
- Store-and-forward transaction handling for brief connectivity drops prevents a network blip from becoming a declined sale.
- Proactive terminal health monitoring that flags degrading connections before they fail entirely gives field teams a window to intervene.
Routing Resilience Matters as Much as Uptime
A terminal that’s online but routing transactions through a single acquirer connection with no failover is still a single point of failure — just a less visible one. We’ve seen acquirers lose meaningful merchant trust not because a terminal went offline, but because a single scheme or processor outage took down authorisations across their entire merchant base simultaneously, with no alternate routing path to absorb the failure.
Building genuine routing resilience means multiple acquiring relationships or processor connections that can absorb an outage without merchants noticing — and it means testing that failover regularly, not just architecting it once and assuming it will work when needed.
“The acquirers merchants stay loyal to for the long term aren’t the ones with the cheapest rates — they’re the ones whose terminals just keep working, transaction after transaction, outage or no outage.”
Integration Debt Compounds Faster in POS Environments
POS networks accumulate integration debt quickly — a legacy terminal model here, a back-office ERP connector built for a version that’s since been upgraded there. Left unmanaged, that debt eventually shows up as exactly the kind of reliability and reconciliation problems merchants notice. Regular technical audits of the full POS estate, not just the newest deployments, are what keep that debt from compounding into a customer-facing failure.
What We Recommend to Acquirers Building Out Their Networks
- Design connectivity failover and store-and-forward into every new deployment as a baseline, not a premium tier.
- Maintain genuine multi-processor routing resilience and test failover on a defined schedule.
- Audit the full terminal estate — including legacy deployments — on a recurring basis, not only when a merchant complains.
- Build reconciliation reporting that flags discrepancies automatically rather than relying on merchants to spot them first.