Something shifted in transit payment modernization over the past few months. Contactless fare collection stopped being the pilot program agencies mentioned in five-year plans and became the thing riders actually used on their commute this week.
NJ Transit went systemwide with tap-to-pay across its entire bus and light rail network on February 8. Two weeks later, the Puget Sound region followed with ORCA, Sound Transit, King County Metro, and five other regional operators all switching on contactless acceptance the same day. Apple Pay’s Express Mode transit support, which lets riders tap through a fare gate without unlocking their phone, expanded to twelve U.S. metros in April, from Atlanta to Seattle to Washington, D.C. In California, Clipper 2.0 went live across the Bay Area in December, and LA Metro’s TAP Plus is rolling out this spring ahead of the 2026 World Cup. That deadline alone will push roughly 95 percent of the state’s transit trips onto contactless-capable systems by summer.
None of this happened because NFC chips got better overnight. It happened because a handful of agencies finally worked through the unglamorous problems that make or break a payment modernization program, and a wave of international events gave everyone a hard deadline to work through them faster.
What’s actually new in NFC transit technology
The underlying shift is from closed-loop, agency-issued cards to open-loop, account-based ticketing, where the back end recognizes a bank card or mobile wallet credential directly instead of requiring a rider to load value onto a proprietary card first. That’s the real story behind most of these NFC rollouts: the chip in the phone or card hasn’t changed much, but the back-end architecture reading it has. APTA published a working paper on open-loop and open-data standards last year that’s worth reading if you’re scoping a procurement, because the interoperability gaps it flags are exactly the ones showing up in the field now.
Handset-side, the meaningful improvement is reliability under real-world conditions: newer iPhones hold enough power reserve to complete a transit tap for up to five hours after the battery reads empty, which matters enormously to a commuter trying to get through a fare gate at the end of a long day. That’s a small technical detail with an outsized effect on adoption, and it’s the kind of thing that only shows up in a project plan if someone on the team is paying attention to device-level constraints rather than treating “contactless” as a single monolithic capability.
The part that’s actually hard: everything around the reader
Anyone who has run one of these rollouts knows the card reader is the easy part. The MBTA’s contactless program is a good study in why. It launched subway and bus tap-to-pay in summer 2024, followed with a modernized CharlieCard and companion app in 2025, and is bringing commuter rail and ferries on this spring. That sequencing was driven as much by vendor capacity and validator hardware availability as by rider demand. On the Mattapan Line, planners had to shift to station-based validators instead of onboard readers because of power constraints on that line’s older rolling stock. That’s a legacy-infrastructure problem wearing a payment-technology costume, and it’s a reminder that a fare collection upgrade is a systems integration project first. The reader riders tap their card on is the last visible piece of a much longer supply chain.
Vendor integration adds its own layer. MBTA’s agreement with Cubic, now valued around $926 million with performance incentives tied to spring 2026 milestones, shows how these programs get structured to keep a contractor accountable across a multi-year build rather than a single go-live date. Anyone scoping a similar RFP should expect the vendor conversation to be as central to the timeline as the technology itself.
Then there’s equity and compliance, which doesn’t get resolved by procurement alone. Contactless bank card payment at ORCA currently charges adult fare only, so riders on ORCA LIFT, senior, or disability discount programs still need a physical card to get their rate. California’s Cal-ITP program has been solving for unbanked riders through partnerships that let people load a debit-style card with cash, precisely because a payment modernization program that only works for people who already have a bank-linked card isn’t actually modernizing access. And with Clipper and TAP still running as separate, non-interoperable systems, California doesn’t yet have a shared standard for something as basic as where a rider taps on and off. That gap shows up the moment someone tries to take one regional system’s card onto another’s network.
Why this matters for how people move
Every one of these programs ties back to the same operational goal: get people off the platform and onto the vehicle faster, with less friction at the point of payment. Faster boarding means shorter dwell times, shorter dwell times mean better on-time performance, and better on-time performance is what actually gets measured when a system is trying to prove a payment investment was worth it. That’s the metric conversation worth having before a single reader gets installed, not after.
The agencies handling this well are treating contactless fare collection project management as its own discipline, with dependencies (vendor delivery schedules, legacy hardware constraints, discount-fare parity, accessibility compliance, a fixed external deadline) that get sequenced deliberately rather than discovered midstream. That’s the work. If you’re building out a transit payment modernization roadmap, sitting across the table from a vendor RFP, or trying to figure out whether a candidate actually understands what a phased NFC rollout takes beyond the press release, I’m always glad to compare notes.
High Street Consulting 
Leave a comment