Mobile Ticketing and Electronic Fare Collection System

A. Payment Solutions:
1. An account-based fare system that completes the following but is not limited to:
• Manage customer payment accounts, associated sub accounts and payment products,
• Manage payment transactions and funds processing,
• Provides third party integrations,
• Supports apportionment/settlements and reconciliation with third parties,
• Supports web-based public, institutional, and discount/benefits portals,
• Uses centralized server/account-based processing in which fare calculation and payment are completely carried out in the back-office,
• Provides an external API or SDK that meet or are substantially similar to Transit App’s requirements.
2. Payment media will include CARTA/TCL-issued contactless smartcards, third partyissued contactless smartcards, mobile phones, and wearables. Third party smartcards may include identification cards issued by the State, businesses and institutions such as local public schools, universities and colleges. Other payment media may include open contactless credit or debit cards, digital wallets like Apple Pay and Google Wallet.
3. On-board readers/validators must read contactless smartcards and validate mobile tickets using Near Field Communications (NFC), Bluetooth and mobile ticketing validation using barcodes/QR codes or flash pass approach.
4. Account-based fare system must provide integration with future on-demand transportation billing software to support integration with state agency programs such as Medicaid, Non-Emergency Medical Transportation (NEMT), in order to deliver seamless, paperless billing for all providers and mobility managers.
5. Account-based fare system should support account replenishment in partnership with retail merchants, if applicable.
6. Account-based fare system should support the loading by participating agencies of their client’s accounts, in addition to the client themselves.
7. Account-based fare system should support integration with third party payment systems such as fixed route transit, demand response transit (including ADA complementary paratransit), human services transportation, ridesharing services, taxis, transit network companies (TNC), docked and dock-less bike share, car share services, scooters, parking meters, parking garages, and other current or future alternative mobility modes to pay for trips booked using the MaaS platform.
8. Account-based fare system should support gamification of mobility modes and associated fares.
9. On-board solution should support boarding on all transit vehicles as well as a fully integrated mobile solution fare payment reader that can be made available to not-forprofit and other coordinating mobility providers and an off-vehicle platform installation.
10. The solution should provide fare capping functionality to ensure that customers pay the “guaranteed lowest fare”, which will be expanded beyond CARTA/TCL fixed route and paratransit services so all customers can choose the best mobility modes for their single trip and know they’ll pay a reasonable price.
11. Reduce dwell time and operating costs, and achieve cost efficiencies through contactless payments.
12. Reduce on-board fare processing time to improve on-time performance and make the boarding process easier and more convenient for customers.
13. Allow retrieval of accurate and timely ridership and revenue data which can be used for detailed analysis and reporting to determine transit trends among riders.
14. Protect customer privacy and transaction security by complying with Payment Card Industry (PCI) standards, ensuring the security and confidentiality of Personally Identifiable Information (PII).
15. Support open-source architecture and be extensible to support new technologies as they mature in the industry.
16. Provide configuration and operational flexibility by providing upfront and understood costs associated with changes to the fare system so long-term operational investments are fully understood.
17. Provide fully reconciled, auditable and accurate revenue deposits and reports.
18. Control fare evasion and prevent fraud.
19. Provide a secure communications network to exchange data.
20. Meet the needs of and provide increased access to low-income, older adults, persons with disabilities, and other disadvantaged groups as it relates to the fares and MaaS.
21. System-wide interoperability and compatibility across all manufacturers, software systems, participating transit agencies, other modes of mobility as outlined in the vision statement.
22. Cards and readers are durable for the transit environment but affordable options are provided to connect with mobility providers within MaaS.