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

Yes — there are fare capping engines and back-office transit payment platforms that can handle multi-agency fare rules, and some support offline/at-the-edge validation as well. The exact fit depends on whether you need:

• real-time capping
• account-based ticketing (ABT)
• mobile wallets / open-loop EMV
• offline validation on validators or devices
• regional interoperability across multiple agencies

What to look for

For your use case, the engine should support:

1. Multi-agency rule configuration

   • separate fare products per agency
   • shared regional caps
   • transfer logic across operators
   • zone/peak/off-peak and rider-type rules

2. Offline capability

   • validator-side stored rules/caches
   • delayed synchronization to back office
   • local hotlists / allowlists
   • offline tap decisioning with later reconciliation

3. Capping logic

   • daily / weekly / monthly caps
   • fare aggregation across agencies
   • rider-profile-specific caps
   • distance- or zone-based capping

Common vendor/platform categories

Some vendors in this space include:

• ABT/back-office fare platforms
  • often used by transit agencies for capping and interagency settlement
• EMV open-loop transit payment platforms
  • handle tap-to-pay and often support capping at back office
• Validator/edge fare engines
  • execute limited offline rules locally, then sync later

Examples of companies/products that may be relevant:

• Cubic
• INIT
• Masabi
• FARE / regional ABT vendors
• Scheidt & Bachmann
• Thales
• Conduent
• Cammax / similar validator providers
• open-loop transit payment stacks built around EMV processors and transit account services

Important caveat

Very few systems do full multi-agency capping with robust offline operation completely on-device without any back-office dependency. More commonly:

• offline validators make provisional fare decisions
• the back office computes final caps and inter-agency apportionment
• conflicts are resolved during reconciliation

If you’re evaluating solutions

Ask vendors specifically:

• Can caps span multiple agencies/operators?
• Are fare rules centralized or distributed?
• What happens when a device is offline for hours/days?
• Is capping enforced locally, centrally, or both?
• How are interagency transfers and revenue settlement handled?
• Can it work with closed-loop smart cards, mobile apps, or open-loop EMV?

If you want, I can also give you:

1. a shortlist of vendors by region/use case, or
2. a feature comparison matrix for offline + multi-agency fare capping.