The file's text, extracted by GovTribe without its formatting.
DEMONSTRATION SCRIPT
Group 2: Merchant Card Services
Vendor Instructions: Vendors determined to be both responsive and responsible to the solicitation’s requirements and shortlisted (if applicable), are required to demonstrate the below features of its offered solution (including any out-of-box, configurable, and customizable features). All Vendors will have equal time for demonstrations.
Demonstration Time: One (1) hour(s) (script and time subject to change prior to Demonstration date). Questions and Answer time is unlimited.
Technical Review Team (TRT) Instructions: During the Demonstration Meeting, each TRT member will place a mark () in the applicable column, along with a comment (if needed), for each criterion based on the vendor’s demonstration.
| No. |
| Scope of Services Section |
| Criteria |
| Demonstrated |
| Not Demonstrated |
| Comments |
| 1 |
| 1.1 |
| Demonstrate charge dispute and case management for card payment transactions by Merchant Identification Number. |
| 2 |
| 1.2 |
| Demonstrate online access to monthly merchant banking statement by Merchant Identification Number. |
| 3 |
| 1.3 |
| Demonstrate real time data on payment card processing activity by Merchant Identification Number. |
| 4 |
| 1.4 |
| Demonstrate online access to retrieve payment card processing by payment network and Merchant Identification Number. |
| 5 |
| 1.5 |
| Demonstrate electronic notification of velocity limits being breached, unusually high volume or dollar amounts. |
| 6 |
| 1.6 |
| Demonstrate secure electronic delivery of the monthly invoice with supporting details for each Merchant Indemnification Number. |
| 7 |
| 1.7 |
| Demonstrate Card payment processing equipment proposed to replace current County owned equipment. |
| 8 |
| 1.8 |
| Demonstrate disputed transaction monitoring. |
| 9 |
| 1.9 |
| Demonstrate overall merchant banking relationship reporting. |
| 10 | |
| 2.2 | |
| Display alerts or educational information on changes in payment card processing due to changes in law or Payment Card Industry standards. | |
| ☐ | ☐ |
| 11 | |
| 2.3 | |
| Demonstrate fraud protection and chargeback management services with comprehensive dispute resolution. | |
| ☐ | ☐ |
| 12 | |
| 2.4 | |
| Demonstrate fraud monitoring alerts. | |
| ☐ | ☐ |
| 13 | |
| 2.5 | |
| Demonstrate fraud reporting dashboards. | |
| ☐ | ☐ |
| 14 | |
| 2.7 | |
| Demonstrate dual approval controls for payment initiation. | |
| ☐ | ☐ |
| 15 | |
| 3.1 | |
| Demonstrate ability to process in-person credit and debit card transactions via EMV chip technology. | |
| ☐ | ☐ |
| 16 | |
| 3.2 | |
| Demonstrate online payment processing through secure web portals and SSL encryption. | |
| ☐ | ☐ |
| 17 | |
| 3.3 | |
| Demonstrate recurring payments and auto-pay functionality. | |
| ☐ | ☐ |
| 18 | |
| 3.4 | |
| Demonstrate compatibility with existing County point-of-sale equipment. | |
| ☐ | ☐ |
| 19 | |
| 4.1 | |
| Demonstrate API integration capabilities for seamless data exchange and automated processing. | |
| ☐ | ☐ |
| 20 | |
| 4.2 | |
| Demonstrate batch processing and file transmission capabilities with real-time settlement | |
| ☐ | ☐ |
| 21 | |
| 4.3 | |
| Support for multiple merchant IDs and department-specific reporting and reconciliation | |
| ☐ | ☐ |
| 22 | |
| 5.1 | |
| Demonstrate visibility into system uptime with transaction latency (round-trip under five seconds) | |
| ☐ | ☐ |
| 23 | |
| 6.1 | |
| Display monthly statements per Merchant ID summarizing all revenue and processing fees. | |
| ☐ | ☐ |
| 24 | |
| 6.2 | |
| Show access to 24/7 technical support for system-down or payment processing issues | |
| ☐ | ☐ |
| 25 | |
| 6.3 | |
| Demonstrate a "system admin" level web application for real-time viewing of logs and API errors. | |
| ☐ | ☐ |
| 26 | |
| 7.1 | |
| Demonstrate secure portal access with multi‑factor authentication for admin setup account. | |
| ☐ | ☐ |
| 27 | |
| 7.2 | |
| Demonstrate 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. | |
| ☐ | ☐ |
| 28 | |
| 7.3 | |
| Show audit logging for all user activities in the banking portal. | |
| ☐ | ☐ |
| 29 | |
| 7.4 | |
| Demonstrate portal to support user activity reporting. | |
| ☐ | ☐ |
Form Date 7/15/25 Page 2 of 2