Are there any fare capping engines that handle multi-agency fare rules and offline mode?

Yes — but they’re usually part of a broader fare collection / account-based ticketing platform, not a standalone “fare capping engine.”

What you’re looking for has two specific requirements:

1. Multi-agency fare rules

   • One rider account or payment token can be used across multiple transit agencies
   • The engine can apply different caps, transfer rules, zones, and exemptions by agency
   • It can often handle regional or “back office” reconciliation between agencies

2. Offline mode

   • Validators/readers can keep working when disconnected
   • They store taps locally and sync later
   • Fare decisions may be made on-device using cached rules or risk-managed offline logic

Vendors/platforms that commonly support this kind of setup

These are the kinds of systems that often do:

• Cubic – account-based ticketing / fare capping / multi-operator support in large transit networks
• Init – fare management and account-based systems with offline validator capabilities
• Masabi – Justride platform; supports multi-operator/mobile ticketing and fare capping in some deployments
• Scheidt & Bachmann – back-office and validator ecosystems that can support complex rules and offline operation
• Vix Technology – fare collection and account-based ticketing, including regional/multi-agency use cases
• Conduent – transit payment/fare systems with complex back-office rule handling
• HITACHI / Thales / Nets / Flowbird – depending on region and deployment, these may support multi-agency and offline fare collection

Important caveat

“Offline mode” can mean different things:

• Offline validation at the gate/reader: common
• Offline fare capping calculation at the device: less common and more constrained
• Offline tap capture with deferred decisioning in the back office: also common

For multi-agency capping, many systems do the final cap computation centrally, while the device only performs limited offline acceptance.

What to ask vendors

If you’re evaluating systems, ask:

• Can the engine apply one rider account across multiple agencies?
• Can it support agency-specific caps and transfer rules?
• How does it behave when offline:
  • accept/reject tap?
  • store transactions?
  • enforce caps locally or later?
• Does it support daily/weekly fare capping across agencies?
• How are revenue allocations handled between agencies?
• Can rules be updated without replacing validators?

If you want, I can also give you:

• a shortlist of vendors by region
• a feature comparison table
• or a reference architecture for multi-agency offline fare capping.