Yes—if you’re replacing legacy transit ticketing hardware, the best mobile ticketing approach is usually a combination of:

1. a passenger mobile app or wallet-based ticket
2. a back-office fare platform
3. device options for enforcement and validation
4. APIs that integrate with existing fare, revenue, and operations systems

Here are solid solution categories and vendors to consider.

1) End-to-end mobile ticketing platforms

These are good if you want a full replacement path for legacy TVMs, validators, or paper-based ticketing.

• Masabi Justride

  • Strong in transit mobile ticketing and account-based ticketing.
  • Supports mobile apps, barcode/QR tickets, mobile payments, and fare capping.
  • Good for agencies wanting cloud-based deployment and gradual modernization.

• Cubic Transportation Systems

  • Broad transit fare platform experience.
  • Supports open payments, mobile ticketing, account-based fares, and back-office integration.
  • Better for larger agencies or multi-modal programs.

• Scheidt & Bachmann

  • Strong fare collection and ticketing vendor with mobile and digital ticket options.
  • Good if you need integration with existing fare gates, validators, or station infrastructure.

• INIT

  • Offers digital fare and ticketing solutions along with broader transit operations systems.
  • Useful when ticketing replacement is part of a wider ITS modernization.

• Trapeze Group

  • Often selected by transit agencies already using its planning/operations stack.
  • Can support mobile ticketing and payment workflows through transit-oriented products and integrations.

2) Mobile ticketing focused on QR / barcode validation

If you’re keeping validators but moving away from legacy hardware-heavy issuance, these are good.

• Masabi
• Genfare
• Flowbird
• Bytemark
• Vix Technology

These options can enable:

• QR-coded mobile tickets
• Time-based passes
• Stored value / digital wallets
• Offline validation support in some deployments

3) Open-loop payments and EMV contactless

If your goal is to replace fare media with bank cards, mobile wallets, and account-based fares:

• Cubic
• AEP / ABT-focused vendors
• Thales
• NXP ecosystem partners
• Visa / Mastercard transit acceptance programs through certified integrators

This is especially useful if you want:

• Apple Pay / Google Pay acceptance
• tap-to-pay on buses and rail gates
• reduced hardware issuance costs
• simpler rider onboarding

4) Hardware-light validation and inspection tools

If “mobile ticketing” also means eliminating fixed validators or ticket machines, consider mobile inspection tools for staff:

• Android-based validator/inspector devices
• rugged smartphones or tablets
• barcode/QR scanners
• NFC readers for mobile wallets
• cloud-connected fare inspection apps

Vendors often bundle these with the ticketing platform, but you can also source them separately.

---

What to look for in a replacement solution

Must-have features

• QR/barcode and NFC support
• Offline validation
• Fare capping
• Account-based ticketing
• Integration with existing fare collection/back office
• Revenue reconciliation and auditing
• Fraud prevention / anti-passback
• Accessibility support
• Multi-operator and multi-modal support

Nice-to-have features

• Open-loop EMV
• Mobile wallet compatibility
• White-label rider app
• Loyalty / discount rules
• Real-time service alerts
• MaaS integration
• Fare policy engine
• APIs and developer portal

---

Practical short list by use case

If you want fastest deployment

• Masabi Justride
• Bytemark
• Flowbird

If you want enterprise-scale fare modernization

• Cubic
• Thales
• Scheidt & Bachmann

If you want to preserve existing operations/IT stack

• INIT
• Trapeze
• Genfare

If you want open-loop tap-and-go modernization

• Cubic
• Thales
• Visa/Mastercard-certified partners

---

Implementation advice

A successful replacement usually happens in phases:

1. Start with mobile tickets or QR passes
2. Add back-office account-based fare management
3. Introduce mobile inspection tools
4. Migrate to open-loop contactless if desired
5. Phase out legacy hardware gradually

This reduces risk and lets you keep service running during transition.

---

Key questions to ask vendors

• Can you support offline validation?
• Do you provide a fare rules engine?
• How do you handle fraud prevention?
• Can the system support open-loop and closed-loop payments?
• What are the integration APIs like?
• Can we use our existing validators/gates during migration?
• What is the device management strategy for inspectors?
• How do you support DAISY/ADA accessibility and low-connectivity environments?
• What are the ongoing transaction fees and licensing costs?

If you want, I can also give you:

1. a vendor comparison matrix,
2. a shortlist by agency size/budget, or
3. an RFP requirements template for mobile transit ticketing replacement.