Mobility as a Service (MaaS): Is the U.S. Ready?
MaaS: Is the U.S. Ready?

What Is Mobility as a Service?

Mobility as a Service, universally abbreviated as MaaS, is a model in which a single digital platform aggregates multiple transportation options—public transit, ride-hailing, bike-share, scooter-share, car-share, and even intercity rail—into one unified interface for trip planning, booking, and payment. Rather than maintaining separate apps and payment accounts for each mode, a traveler uses one MaaS application to receive a door-to-door route, compare cost and travel time across options, pay with a single transaction, and receive consolidated trip receipts. In its most mature form, MaaS can also offer subscription-style bundles, somewhat analogous to a mobile phone plan, where users pay a monthly fee for a set number of transit rides, ride-hail credits, and bike-share minutes.

Integrated Planning and Payment: The Technical Core

The backbone of any MaaS platform is application programming interface (API) integration between the MaaS operator and each mobility provider. Transit agencies must expose real-time schedule, capacity, and fare data through standardized APIs, while ride-hail and shared-mobility providers must allow the MaaS platform to initiate bookings and process payments on behalf of users. Two open data standards have become foundational to this work in the United States: the General Transit Feed Specification (GTFS), which covers fixed-route schedule and fare data, and the emerging Mobility Data Specification (MDS), maintained by the Open Mobility Foundation, which governs data exchange between cities and shared-mobility operators. Without common standards, each integration becomes a bespoke engineering project, raising costs and slowing deployment.

Payment integration is equally critical and arguably harder to achieve. Public transit agencies in the United States typically operate proprietary fare collection systems—contactless smart cards, mobile ticketing apps, or legacy magnetic-stripe machines—that were procured independently and are not designed to accept external payment initiation. Achieving true single-tap or single-account payment across a bus, a subway, a docked bike, and an Uber requires either a neutral payment intermediary or the consent of every provider to open their payment rails to a third party.

How MaaS Works in Practice: Overseas Examples

The most frequently cited MaaS deployment in the world is Whim, launched in Helsinki, Finland, by MaaS Global in 2016. Whim allows Helsinki residents to access the city's public transit network (HSL), city bikes, taxis, and rental cars through a single app, with subscription tiers ranging from pay-as-you-go to an unlimited monthly plan covering local transit and a generous taxi allowance. Helsinki's success rested on a deliberate policy decision by HSL to open its ticketing API to third-party operators—a step that most U.S. transit agencies have not yet taken. MaaS Global subsequently expanded Whim to Antwerp, Belgium; Birmingham, United Kingdom; Tokyo, Japan; and Vienna, Austria, though commercial results have been mixed and the company restructured in 2023.

Singapore's Land Transport Authority (LTA) has taken a government-led approach, integrating MaaS capabilities directly into its MyTransport.SG ecosystem and mandating data sharing from private mobility operators as a condition of operating licenses. Germany's Deutsche Bahn launched the Moovel platform (later rebranded to reach.now) to aggregate regional rail, local transit, car-share, and bike-share, leveraging the national rail operator's existing ticketing infrastructure as a foundation. These examples share a common thread: a willing anchor institution—either a dominant transit operator or a national transport authority—that controls enough of the mobility market to make a unified platform genuinely useful from day one.

U.S. MaaS Pilots: Progress and Limitations

The United States has not been entirely absent from the MaaS landscape. The Federal Transit Administration (FTA) has funded several mobility-on-demand and MaaS-adjacent pilots through its Mobility on Demand (MOD) Sandbox Program, which was launched in 2016. Projects funded under MOD explored first-and-last-mile connections, demand-responsive transit, and limited multimodal fare integration in cities including Dallas, Denver, and the Los Angeles region. The FTA's broader Mobility Innovation initiatives, documented on the agency's public website, continue to support research into integrated mobility.

More recently, the Los Angeles County Metropolitan Transportation Authority (LA Metro) piloted TAP-to-ride integrations with bike-share and tested a unified mobility wallet concept. The Denver Regional Transportation District (RTD) has collaborated with the Colorado Department of Transportation on integrated trip-planning tools. However, as the U.S. Department of Transportation's own research has noted, these pilots tend to be partial—covering trip planning but not unified payment, or covering payment but only for a limited set of providers. A true end-to-end MaaS product, commercially available and broadly marketed, has yet to emerge from a major American metropolitan area at scale.

Structural Barriers: Fragmented Agencies

The most fundamental obstacle to MaaS in the United States is institutional fragmentation. A typical American metropolitan area contains dozens of independent transit operators—city bus systems, county bus systems, commuter rail authorities, light-rail districts, ferry operators—each governed by its own board, operating under its own enabling legislation, and accountable to its own political constituency. The Chicago metropolitan area, for example, is served by the Chicago Transit Authority, Metra commuter rail, and Pace suburban bus, coordinated loosely under the Regional Transportation Authority (RTA) but each retaining independent fare systems and separate apps. In the San Francisco Bay Area, riders navigate a patchwork of BART, Muni, Caltrain, AC Transit, SamTrans, and more than two dozen other operators.

This fragmentation creates a coordination problem that is as much political as it is technical. For a MaaS platform to function, every participating agency must agree on data-sharing terms, revenue-allocation formulas for bundled passes, liability arrangements, and customer service protocols. Negotiating these agreements across multiple independent governmental bodies—each with its own legal counsel and labor agreements—can take years. European systems that succeeded often did so because a single dominant operator controlled the majority of trips, making the MaaS platform instantly useful even before secondary providers joined.

Structural Barriers: Fare Integration

Even within a single metropolitan transit network, fare integration remains elusive in the United States. Most agencies price trips based on their own zone maps, transfer policies, and fare media—systems that were designed for single-operator use and do not naturally accommodate revenue sharing with other agencies or private operators. When a rider transfers from a city bus to a commuter rail line, they frequently pay a full second fare rather than a discounted transfer, because the two agencies have not agreed on how to split the revenue from a discounted combined fare. Extending that logic to a private bike-share or ride-hail operator introduces even greater complexity around regulatory authority, state public utility laws, and the treatment of subsidized fares for low-income riders.

The absence of a national fare integration standard compounds the problem. The United Kingdom's Transport for London (TfL) achieved seamless fare integration across bus, tube, rail, and river services through Oyster and contactless payment because a single authority controlled all of those services. In the U.S., no federal authority currently has the mandate or the legal tools to compel fare harmonization across state and local transit agencies. The Bipartisan Infrastructure Law (BIL) of 2021 (Public Law 117-58) did include provisions to advance data standards and mobility innovation, and the FTA has used those funds to encourage voluntary coordination, but voluntary coordination moves slowly when agencies face competing budget pressures and political priorities.

The Private Sector Role and Its Limits

Some observers have argued that a private MaaS operator—a technology company willing to absorb the integration costs and negotiate with agencies—could cut through the institutional gridlock that governments cannot resolve. Google Maps and Apple Maps already provide multimodal trip planning that surfaces transit, walking, cycling, and ride-hail options in a single interface, and Google has integrated real-time transit data from hundreds of U.S. agencies. However, neither platform offers unified payment or subscription bundles, and neither has the contractual relationships with agencies necessary to sell transit tickets directly at scale across the country. Startups that attempted to build U.S. MaaS platforms—including Routematch (acquired by Google) and Transit App—have focused primarily on planning and real-time information rather than integrated payment, in part because agencies have been reluctant to cede ticketing revenue and customer data to private intermediaries.

What Would It Take to Move Forward?

Transportation industry professionals and policy analysts generally identify several preconditions for meaningful MaaS progress in the United States:

  • Open API mandates or incentives: Federal or state policy that conditions capital funding on agencies exposing standardized, real-time fare and schedule APIs to accredited third parties.
  • Regional fare compacts: Voluntary or legislatively mandated agreements among agencies within a metropolitan area to establish unified fare zones, transfer discounts, and revenue-sharing formulas.
  • Account-based ticketing (ABT) modernization: Migration away from proprietary smart-card systems toward open, account-based fare collection that can accept payment from multiple front-end apps.
  • Equity safeguards: Explicit policies ensuring that MaaS platforms serve unbanked and low-income riders through cash-equivalent onramps and subsidized access tiers, so that the platform does not inadvertently exclude the riders most dependent on public transit.
  • Designated regional coordinators: Metropolitan Planning Organizations (MPOs) or Regional Transportation Authorities empowered—and funded—to act as neutral conveners for MaaS governance agreements.

Summary

Mobility as a Service represents a compelling vision for American transportation: a world in which a traveler in any city can open a single app, find the fastest or cheapest route from home to work using a combination of bus, train, and shared mobility, pay once, and receive a seamless experience regardless of how many operators are involved. The technology to deliver this vision largely exists today. What has proven harder to build is the institutional architecture—the data-sharing agreements, fare integration compacts, open payment rails, and regional governance structures—that would allow that technology to function across the highly fragmented landscape of American public transit. Overseas examples from Helsinki to Singapore demonstrate that MaaS can work when a willing anchor institution controls enough of the market to make a unified platform immediately valuable. In the United States, replicating that success will require deliberate policy choices at the federal, state, and regional levels, sustained investment in open data standards, and a willingness among independent transit agencies to trade some autonomy for the passenger experience gains that true integration can deliver.

References

← Back to News