Mobile Parking Payment Platforms

The Vendor is required to provide a mobile and seamlessly integrated parking payment solution that provides an accessible, secure, and efficient user experience for both city stakeholders and customers.
- The system shall allow users to pay for parking via a mobile app or text message that is compatible with major mobile phone platforms (Apple, Android, etc.) and available through those platforms’ primary storefronts (App Store, Google Play, etc.)
- Users will be required to input their License Plate information and payment information (Debit Card, Credit Card, Mobile Wallet, or Payment App, such as Apple Pay, Google Pay, etc.). 
- Users will associate their account with an email or cell phone number.
- Users pay for parking by identifying a parking zone indicated on signage posted on the street alongside parking regulation signage or on the bodies of physical meters. 
- Users can type this zone number into the app, scan a QR code or navigate an in-app menu or map to find and select their zone. 
- Zone numbers within the City shall be distinct between themselves and with those in use with other cities such as to not confuse the user. 
- The signage must be clear, visible, and easily understood to a user outside of a vehicle. 
- These zones can be on-street or off-street, located within structure and can cover both single spaces and arbitrarily large zones on the order of thousands of spaces.
- That backend system shall be compatible with an open API with the City’s parking enforcement system (currently IPS Group, Inc), including handheld ticket writing devices and LPRs and provide hard real-time data for the purposes of enforcement.
- The City shall also have the ability to issue refunds, view analytics, download data, and create, modify or terminate zones via the backend system.
- Providing mobile parking payment solutions, particularly in municipal on- and off- street parking environments.
- The proposed system must include:
•    A seamless, user-friendly payment experience with multiple payment options.
•    A pricing model that includes a service fee structure covering all card merchant fees to be paid by customer.
•    Flexible rate and operational schedule programming without requiring downtime.
•    Compatibility with existing and future parking management systems and enforcement devices as used by the City. The system must also be able to integrate past payment records and metrics from the City’s current mobile pay application, ParkMobile.
•    Sharing real-time data between existing and future parking management systems, enforcement devices and applications.
•    Compatibility with major web browsers (Safari, Chrome, Edge, etc.).
•    An option for customers to make payments via call, text or the web in addition to an app.
•    Alternatively the system must offer compatibility with call, text, or web-based options provided by other vendors or services as are or may be contracted by the city.
•    Real-time notifications: Customers must be notified 15 minutes before their paid session expires.
•    Flexible time extensions: Users must be able to purchase additional time up to the maximum allowed for a given block or zone.
•    Lifetime transaction history: Customers must have full access to their entire parking payment history.
•    Unique transaction IDs: Every payment must generate a unique transaction number.
•    Account management: Users must be able to update their profile details, including payment method and vehicle information.
•    Restricted period enforcement: The system must prevent purchases during restricted parking periods (e.g., rush hours, holidays, or any such regulation as the City may set).
•    Fleet Management Program: A dedicated feature allowing businesses to manage multiple vehicles under a single account.
•    Multiple payment access points: Payments should be accessible via a dedicated mobile app, web browsers, and wearable devices.
•    Ensure the platform is secure, intuitive, and easy-to-use for new users.
•    The design should be sleek, professional, and optimized for quick transactions.
- The vendor must provide a detailed user experience overview in their app’s digital storefronts, including:
•    System requirements for iOS, Android, and web platforms.
•    Screenshots and demo accounts, if applicable.
•    A clear breakdown of all fees (meter, processing, and merchant) displayed before transaction approval.
•    A list of supported languages and how users select their preferred language.
•    Customization options for the City to adjust branding and UI elements.
- The system must provide clear and timely transaction updates to users, including:
•    Post-payment notifications via email and/or text receipts.
•    Fast and reliable payment processing with minimal latency.
•    High system availability, fail-safes, and a communication plan in case of downtime.
•    A scheduled maintenance plan that aligns with non-operational parking hours.

- Contract Period/Term: 1 year
- Questions/Inquires Deadline: October 2, 2025