Laserfiche WebLink
Payment Processing Services Statement of Work: Catalis Payments, LLC & Everett Municipal Court | Page 7 of 17 <br />EXHIBIT B: INTEGRATION SCOPE <br />1. Merchant will make JIS / Codesmart (“Software Vendor”) aware of the requirement to integrate with the Provider E-Payment <br />system and of the anticipated Go-Live date contemplated herein. Merchant will compel Software Vendor to assist in setting up <br />direct data interface, including providing all file descriptions or API and/or FTP documentation. <br />2. If Provider is delivering a web service or API service, Provider will need access and resources from the Merchant to ensure both <br />systems from each company can interface and exchange data appropriately. Failure to grant Provider access or a Merchant resource <br />to help support this step of the implementation process will result in delays to the Merchant’s Go-Live date. <br />3.Provider Responsibilities <br />3.1. All payment transactions will update the Merchant’s case management system on a predetermined cadence. <br />3.2. If there are designated payments which are ineligible for online payment, Merchant will be able to omit those records from <br />being paid through Provider via their case management system. <br />3.3. Dependent on information from Software Vendor, data may be searched by the following fields, or similar identifying <br />characteristic of the Customer. <br />3.3.1. First Name <br />3.3.2. Last Name <br />3.3.3. Driver’s License Number <br />3.3.4. Ticket Number <br />3.3.5. Citation Number <br />3.3.6. Case Number <br />4.Merchant Responsibilities <br />4.1. Merchant will supply Provider with Software Vendor contact information <br />4.2. Merchant will actively participate in accomplishing the Go-Live of the Program in the specified timeframe outlined herein. <br />4.3. Merchant shall provide access to a dedicated test and production environment for the implementation lifecycle. <br />4.4. Merchant will provide the file format specification currently used to post its payments to the Codesmart system. Merchant <br />will fully cooperate with Provider and provide the information required to integrate with the Merchant’s system. <br />4.5. Merchant to provide multiple copies of bills and/or receipts to Provider, if in project scope. <br />4.6. Merchant is responsible for determining and notifying Provider if (i) defendant shall be allowed the option(s) to select Traffic <br />School or proof of corrections, or (ii) a partial or full payment by the defendant shall be allowed. This notification must take <br />place prior to completion of the Design Document and the beta version of the Merchant site, and no later than thirty (30) days <br />after the Effective Date. <br />4.7. Merchant acknowledges that Counter is embedded in Merchant’s JIS system and all transactions will stay within Merchant’s <br />JIS system. <br />4.8. Merchant will compel Software Vendor to supply Provider with a CSV file containing the following information. Provider <br />shall confirm file receipt. <br />4.8.1. Citation Number (Required) <br />4.8.2. Case Number (Required) <br />4.8.3. Defendant’s Name (Required) <br />4.8.4. Date of Birth (Required for IVR) <br />4.8.5. Amount Due (Required) <br />4.8.6. Payability / Must Appear Flag (Required) <br />4.8.7. Address <br />4.8.8. Offense <br />4.8.9. Violation Date <br />4.8.10. Court Date <br />4.9. Merchant shall supply Provider with the following: <br />4.9.1. Payment information <br />4.9.2. W9 with Employer Identification Number (EIN) <br />4.9.3. Financial Disbursement Agreement (FDA) for each judge in scope <br />4.9.4. Any applicable test case scenarios <br />4.9.5. Applicable collections logic <br />4.9.6. Applicable custom verbiage to be included by record type