2-ATTACHMENT A - Scope Mobile Payment Provider Compliance Form.pdf
PDF 93 KB Posted
- Attached to
- Mobile Payment Provider
- Solicitation number
- 265X901121
- Issued by
- Hamilton County, Cleveland City, Ohio
About this file
The document is an Offeror Compliance Form for a Mobile Payment Provider issued by the City of Cincinnati, seeking a comprehensive Pay-by-Cell (PBC) mobile payment system for on-street parking. The solicitation requires a hosted, integrated, real-time mobile payment system that can integrate with the city's existing parking meter and citation management systems. The mobile payment solution must support multiple payment methods including mobile app, text-to-pay, QR code, web application, and IVR, while providing robust features such as fraud detection, transaction reporting, administrative portals, and 24/7/365 customer support.
The compliance form outlines extensive technical and operational requirements, including system uptime of 99.9%, acceptance of major credit and debit cards, compliance with PCI-DSS and EMV standards, support for digital wallets, and provision of marketing materials and signage. Additional requirements include providing a comprehensive Acceptance Testing Plan, conducting a 30-day post go-live operational test, offering on-site staff training, and complying with the city's Equal Employment Opportunity, Small Business, and Living Wage requirements. The document serves as a detailed checklist for potential vendors to demonstrate their ability to meet the city's mobile payment system specifications, with each specification requiring a clear "Yes" or "No" response and the option to provide comments.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Offeror Compliance Form – Mobile Payment Provider City of Cincinnati
Indicate compliance with each of the following specifications. This document will be used to assist in scoring, and this document may become part of the binding procurement contract; as the Offeror is indicating whether or not they comply with each specification. By answering "Yes", Offeror indicates full compliance with the specification as written. "Yes" answer shall not be qualified in any way, as “Yes" shall mean full compliance.
Specification Yes or No Comments Provide hosted, integrated, real-time Pay-by-Cell (PBC) mobile payment system for on-street parking.
Integrate with City’s parking meter system and Citation Management system.
Serve as Merchant of Record for credit card processing.
Support payment methods: mobile app, text-to-pay, QR code, web application, IVR, etc.
Provide fraud detection and mitigation for all payment methods.
Provide design and installation of complete mobile payment signage refresh (City-approved).
Provide all raw data and reporting to City, including transactions, occupancy, and utilization data.
Provide real-time dashboard for City access to system activity and financial data.
Provide downloadable reports in PDF, Excel, and CSV formats with sortable fields.
Provide transaction reports including date/time, duration, payment amount, customer, plate, location/zone, etc.
Provide daily and monthly financial reconciliation reports.
Provide administrative portal with role-based access for City staff, including read-only, enforcement, and admin roles.
Provide ability to manage parking zones, rates, time limits, and rate structures (graduated, event, residential, holiday, etc.).
Ensure system implements rate changes within three (3) business days of City request.
Provide 24/7/365 toll-free customer support for end users.
Ensure customer registration is available 24/7/365 via phone, app, or web page.
Prohibit unrequested communication with customers and sharing/selling of customer data.
Obtain City approval for all PBC terms and conditions, end-user agreements, and any added service fees.
Provide system uptime of 99.9%.
Notify City immediately of any system errors or outages with estimated time of resolution and workarounds.
Provide pro-rated credits for outages lasting more than four consecutive hours.
Accept Visa, MasterCard, American Express, Discover, and bank-issued debit cards.
Comply with PCI-DSS and EMV standards for all credit card transactions.
Credit card gateway must be PCI P2PE and Visa Level 1 Service Provider certified.
Support digital wallets (Google Pay, Apple Pay, Samsung Pay, PayPal) with secure TLS 1.2+ encryption.
Provide accurate and FACTA-compliant receipts via SMS or email.
Provide comprehensive Acceptance Testing Plan demonstrating full system functionality and compliance.
Conduct 30-day operational test post go-live for final acceptance.
Provide on-site and hands-on training for City staff, including user manuals (print and electronic).
Include detailed project plan covering design, implementation, migration, testing, and training.
Provide marketing materials and signage (18”x24” reflective aluminum signs and stickers).
Include detailed price proposal showing all costs to City and to end users.
Provide documentation of company qualifications, key personnel, and five municipal references.
Provide complete list of exceptions and substitutions, if any.
Comply with City’s Equal Employment Opportunity, Small Business, and Living Wage requirements.
Be a Taxpayer in Good Standing with the City of Cincinnati.
Any exceptions to Scope specifications?
File details come from the government source that posted it. Updated .