46-Functionality Checklist, Merchant Card Services (Group 2), GEN2131264P1.xlsx
XLSX spreadsheet 22 KB Posted
- Attached to
- Master Banking Services
- Solicitation number
- GEN2131264P1
- Issued by
- Broward County, Florida
About this file
This is a Functionality Checklist for Solicitation No. GEN2131264P1 issued by Broward County, Florida for Merchant Card Services (Group 2) as part of a Master Banking Services procurement. The checklist requires vendors to indicate whether their proposed solutions provide specified functionality either out-of-the-box, through configuration, or not at all. Vendors must complete and submit the checklist by the solicitation's closing date and time, with failure to submit potentially resulting in no points awarded. The checklist covers seven primary sections: Customer Service (merchant banking management, online access to statements and processing data, velocity limit notifications, invoice delivery, equipment displays, transaction monitoring, and relationship reporting); Protection Services (Payment Card Industry compliance, fraud protection, chargeback management, fraud alerts and dashboards, dual approval controls, data breach procedures, and compliance with Visa, MasterCard, American Express, Discover, and Florida privacy laws); Technical Processing Capabilities (EMV chip technology, secure web portal processing with SSL encryption, recurring payments, and point-of-sale compatibility); Technical Integration Requirements (API capabilities, batch processing, and multi-merchant ID support); System Availability (99.99% uptime with transaction latency under five seconds); Reporting (monthly statements, 24/7 technical support, and system administration tools); and Technical Requirements (multi-factor authentication, Single Sign-On integration with Microsoft Entra ID using OIDC, OAuth 2.0, or SAML 2.0, audit logging, and user activity reporting).
The checklist serves as an evaluation tool for Broward County to assess vendor capabilities against the county's technical and operational requirements for merchant card processing services. Vendors may propose for one or multiple banking service groups and must perform all work without subcontracting. The county reserves the right to award each banking service to a single vendor or multiple vendors at its sole discretion. All required and optional documents should be submitted to enable timely and comprehensive review, with submission through the designated procurement portal by the specified deadline.
View the file
Other files
Show all 48
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
Solicitation No. GEN2131264P1
| Functionality Checklist |
| Solicitation No. GEN2131264P1 |
| Group 2: Merchant Card Services |
| Indicate if the proposed solution provides the functionality and whether any configuration is required. |
Complete the Functionality Checklist (mark an "X" for applicable answer) and use the comments column to provide any additional explanation that will assist the County in its evaluation. Vendors that fail to submit completed checklist by solicitation’s closing date and time may receive no points (if applicable).
| Section | Functionality | YES | ||||
| (out-of-the-box) | YES | |||||
| (configurable) | Not Available | Vendor Comments | ||||
| SECTION 1: CUSTOMER SERVICE | ||||||
| Sample | This is an example line for Vendors showing how to complete this form. | X | X | Notes can be left here. If additional documentation is supplied, use the same numbering scheme to allow for cross-referencing. | ||
| 1.1 | Provide Merchant banking management services including charge dispute and case management for card payment transactions by Merchant Identification Number. | |||||
| 1.2 | Provide online access to monthly merchant banking statement by Merchant Identification Number. | |||||
| 1.3 | Provide real time data on payment card processing activity by Merchant Identification Number. | |||||
| 1.4 | Provide online access to retrieve payment card processing by payment network and Merchant Identification Number. | |||||
| 1.5 | Provide electronic notification of velocity limits being breached, unusually high volume or dollar amounts. | |||||
| 1.6 | Provide secure electronic delivery of the monthly invoice with supporting detail for each Merchant Identification Number. | |||||
| 1.7 | Display Card payment processing equipment proposed to replace current County owned equipment. | |||||
| 1.8 | Provide disputed transaction monitoring. | |||||
| 1.9 | Provide overall merchant banking relationship reporting. | |||||
| SECTION 2: PROTECTION SERVICES | ||||||
| 2.1 | Have Payment Card Industry compliance management. | |||||
| 2.2 | Provide alerts or educational information on changes in payment card processing due to changes in law or Payment Card Industry standards. | |||||
| 2.3 | Provide fraud protection and chargeback management services with comprehensive dispute resolution. | |||||
| 2.4 | Provide fraud monitoring alerts. | |||||
| 2.5 | Provide fraud reporting dashboards. | |||||
| 2.6 | Provide dual approval controls for payment initiation. | |||||
| 2.7 | Provide data breach notification and response procedures in accordance with industry standards. | |||||
| 2.8 | Comply with current card network rules and regulations from Visa, MasterCard, American Express, and Discover. | |||||
| 2.9 | Comply with Federal and state data protection requirements including Florida privacy laws. | |||||
| SECTION 3: TECHNICAL: PROCESSING CAPABILITIES | ||||||
| 3.1 | Ability to process in-person credit and debit card transactions via EMV chip technology | |||||
| 3.2 | Provide online payment processing through secure web portals and SSL encryption | |||||
| 3.3 | Allow recurring payment and auto-pay functionality | |||||
| 3.4 | Provide compatibility with existing County point-of-sale equipment | |||||
| SECTION 4: TECHNICAL: INTEGRATION REQUIREMENTS | ||||||
| 4.1 | Supports API integration capabilities for seamless data exchange and automated processing | |||||
| 4.2 | Allows batch processing and file transmission capabilities with real-time settlement | |||||
| 4.3 | Support for multiple merchant IDs and department-specific reporting and reconciliation | |||||
| SECTION 5: SYSTEM AVAILABILITY | ||||||
| 5.1 | Maintain 99.99% uptime with transaction latency (round-trip under five seconds) | |||||
| SECTION 6: REPORTING | ||||||
| 6.1 | Provide monthly statements per Merchant ID summarizing all revenue, processing fees. | |||||
| 6.2 | Provide 24/7 technical support for system-down or payment processing issues | |||||
| 6.3 | Provide a "system admin" level web application for real-time viewing of logs and API errors. | |||||
| SECTION 7: TECHNICAL REQUIREMENTS | ||||||
| 7.1 | Support secure portal access with multi‑factor authentication for admin setup account. | |||||
| 7.2 | Support secure portal access with County managed Single Sign On (SSO) using modern authentication protocols compatible with Microsoft Entra ID, such as OpenID Connect (OIDC), OAuth 2.0 (authorization framework), or SAML 2.0. | |||||
| 7.3 | Provide audit logging for all user activities in the banking portal. | |||||
| 7.4 | Provide portal to support user activity reporting. | |||||
| Form Date 7/16/25 |
&10Functionality Checklist &A &P of &N
&P of &N
File details come from the government source that posted it. Updated .