HomeMy WebLinkAboutCatalis Payments, LLC - Payment Processing Services Statement of WorkDocuSign Envelope ID. 6E499E31 -341A-423E-8845-74088E52C:026
ADVANCING GOVERNMENT, ENGAGING CI IRENS
PAYMENT PROCESSING SERVICES STATEMENT OF WORK
between
Cataiis Payments, ',LC
("Provider")
having its principal place of business at:
3025 Windward Plaza Suite 200
Alpharetta, GA 30005
and
City of Yakima
("Merchant")
having its principal address at:
200 S 3rd St 42
Yakima, WA 98901
DocuSPgn Envelope ID: 6E499B1B-341A-423E-8845-74088E52CO26
THIS PAYMENT PROCESSING SERVICE STATEMENT OF WORK (this "SOW') is made and entered into as of the day of
20 "E(Tective Dale") by and between Catalis Payments, LLC ("Provider") and City of Yakima ("Merchant Merchant
and Provider may each be referred to individually as a "Party" and together as the "Parties%"
The Terms and Conditions located at https://govcontract,wpengin.e.com/payment_proeessing/ are incorporated by reference
TERM
This SOW will commence upon the Effective Date and continue for three (3) years, at which point in time the SOW will automatically
renew for successive one ( I) year periods unless either party, at least sixty (60) days prior to the expiration of the then applicable term,
provides the other with written notice of its desire to terminate this SOW.
STRATEGY
After the contracting process has ended, Provider will build and the maintan payment channel(s), as defined below, to allow Merchant
to securely accept, validate, and track payment data from its Customers. Where Web E-Payment System is in scope, an initial test site
will be built to load all data received from Merchant and JIS. On this test site, Provider will build logic and business rules to govern the
hosted data. Once the web services have been properly built, tested, and reviewed, Provider will establish Merchant Identification.
credentials. Web services and Merchant Identification credentials will be applied and integrated into the hosted site and data backed
payments will be tested. Once the payments are tested,. Provider will initiate training for all Merchant personnel, done remotely. Upon
successful training, the hosted website will be moved into a production environment and undergo a subsequent round of testing, After
testing and validation of the data, Merchant 'will direct Provider to launch the site..
The date of System launch ("Go -Live") will be targeted during an implementation kickoff call with all relevant stakeholders. The
successful completion of this Statement of Work is dependent on Merchant reviewing test content, data, and functionality in a timely
manner, and providing an appropriate level of operational and strategic engagement to participate in training, deploy the solution into
production environments, and follow 'through ‘vith the responsibilities listed below.
SCOPE
For good and valuable consideration, the receipt and adequacy of which is hereby acknowledged,. the parties agree as follows:
1. Merchant will make resources available to assist Provider in the timely launch of the payment processing program. Provider cannot
be held accountable for unreasonable Merchant delays and may choose to delay the implementation should Merchant not be able
to provide appropriate resources. If system does not launch within 'twelve (12) months of .signature date due to Merchant delays,
the full implementation fee will become due. Otherwise there Os not cost for the implementation or services provided unless
specified herein.
.Payments are deposited daily into a custodial account and transferred by ACH electronic transfer to Merchant daily. The payment
will be accompanied by a reconciliation detailing thepayments included, Any money transfer fees will be .absorbed by Provider.
2. E-Payment System Utilization
2,1.
2.3.
Merchant will make Provider's Services available to its Customers through various means of communication, including a)
through billing statements, invoices and other payment notices; b) by providing IVR and Web payment details on the
Merchant's website including a "Pay Now" or similar link on a mutually agreed prominent place on the web site; c) through
the Merchant's general IVR/Phone system and d) other channels deemed appropriate by the Merchant.
/.2. Provider shall provide the Merchant with logos, graphics, and other marketing materials for use in its communication with its
Customers regarding the payment services provided by Provider. Both parties agree that Provider will be presented as the
primary payment method option. Merchant will communicate the Provider payment Service option to its Customers wherever
the Merchant generally communicates its other payment methods.,
Payments types shall be processed through the payment channels defined in this SOW as marked (Z):
Tax El Parks & Recreation
CI Utilities
El Court Fees & Fines
El Licenses
EJ Child Support
El Miscellaneous
3. Provider Deliverables: Provider shall deliver the .following, included as marked (N):
Pq1'07e,,r1 .S;YrViei!,,* SIGW MCIO" la in? „1/4micipo/ Cowl
DocuSign Envelope ID: 6E499B1B-341A-423E-8645-74088E52CO2
3.1. Web E-Payment System
3.1.1. Provider shall build, host and maintain Merchant -specific website(s) for City of Yakima. Provider will purchase a
www.TBD,com
3.1.2. Provider will provide a secure website that will allow payers to enter their pertinent information, e.g., citizen name
or other unique identifier, and then proceed to pay with a credit or debit card.
3.13. System will collect and transmit payment information for authorization and settlement.
3.1.4. System will provide method of transferring transaction data back to Merchant.
3.1.5. The payer will be simultaneously advised via automated email that the transaction has been completed and will
receive further notification when the Merchant processes the payment,
3.2. Counter E-Payment System
3.2.1. Provider shall deliver and configure 2 EMV device(s).
3.2.2. Provider shall deliver an administrator portal for counter payments.
3.2.3. Provider shall remotely upgrade EMV devices as appropriate.
3.2,4, Provider shall provide one (1) remote, web based training session covering setup and use of EMV devices.
3.3. Eg Phone / Call Center E-Payment System
3.3.1. Provider shall provide a toll -free telephonic customer service function to ensure that Customers utilizing the
Program have a satisfactory experience that does not require the technological assistance of Merchant personnel.
3.4. E IVR - E-Payment System
3.4.1. IVR solution shall be hosted and maintained by Provider.
3.4.2. Provider shall configure call scripts according to industry best practices.
3.4,3. IVR functionality shall only include search/retrieval and payment processing of Case payments in full.
3.5. Text and Ernail Payment System
3,5,1, Provider will deliver functionality to allow Customers to set up text (SMS) and/or email payment and notification
preferences through their E-Payment System profile. Customers will be required to (i) have a valid payment
method stored within their profile and (ii) verify their cell phone number prior to completing registration.
3.6. 2g eCheck/ACH E-Payment System
3.6.1. Provider will configure web E-Paymem System to accept eCheck/ACH Payments.
3.7. Integrations
3.7.1. Provider will create/maintain an integration with record management or other system. System integration
Statement of Work is in Exhibit B.
E-Payment System Training
3.8.1. Provider will provide support and training to Merchant personnel via live, web -based session(s), A training
schedule will be shared during implementation,
4. Merchant's Responsibilities: In order for Provider to provide the Services outlined in this SOW, the Merchant shall deliver the
following, included as marked (N):
4.1. IZ General
4.1.1. Attend client care calls as requested.
4.1.2. Notify Provider of changes to any state, county, or municipal mandates or laws.
4.1.3. Revoke system access of terminated Merchant employees at time of termination.
4,2. 1Z Web E-Payment System
4.2.1. For the duration of this SOW, Merchant will maintain an active link connecting the Merchant website and the
Provider payment portal in a prominent and mutually agreed location on the Merchant website.
4.3. Counter E-Payment System
4,3,1. Merchant will keep all point of sale terminals in good order and repair except for normal wear and tear in the
DocuSgn Envelope ID: 6E499131B-341A-423E-8845-74068E52G026
ordinary course of business,
4A. 14 Integrations
4,4.1. The Merchant, via their record management system, .11S, will update Provider's payment program on a near real-
time basis, with data on all open and payable records from the Merchant's server. Upon exchange of the data, the
information may be accessed, and payment made by the Customer. Record management system integration
Statement of Work is in Exhibit B.
45. El PayPai setup details required:
Merchant Bank Account Information:
Name of Bank:
ABA No,:
Account No.:
Account Name:
Reference:
SIGNATURES
In witness whereof, the Parties have executed this SON16 their duly authorized representatives as of the date first above written.
Signed:
Name: <
Title:
CITY CONTRPr T
RESOLUTION NO -
Catalis Payments, LLC:
DocuSIgned by
ftAkt, to-sfre)
signed: 4rAr346PO4FA-
Steve astroff
Name.
Title: Executive vice President and GM
Date: 2/22/2023
...1111,:acrealfracessiric.31.0yittes'Stittertritt.talVork: f..1,ztaltr..fttyttiletit.E::L.LCAI.Yrtkitnrtidtritharaf 11:1:161411...1.
DocuSign Envelope ID; 6E499B1B-341A-423E-8845-74088E52CO26
EXHIBIT A: FEES
The expected processing volume in the Program is estimated at ,$ 315,500 per month.
2. E-Payment System
In consideration for the provision of the development, hosting, application, customer service, and processing fees related to the E-
Payment System, Customers will pay applicable fees .('Convenience Fees") andlor Merchant will be billed applicable fees
("Merchant Absorbed Fees") associated with payment transactions marked () as follows:
Payment Type
Payment Channel
Transaction Type
Fee Structure*
Merchan
Absorbed
E Online
(via web or mobile device,
Counter
(in -office via PCI compliant,
EMV ready card readers)
Credit Cards
X Visa
E Mastercard
Discover
.American Express
Debit Cards
M Visa
X Mastercard
Discover
LJ PayPal / PayPal Credit / Venmo
E-Check ACHI
CE Credit Cards
21 Visa
Mastercard
Discover
1 American Express
Debit Cards
E Visa
• Mastercard
Discover
For each transaction,
5.00% per transaction
$2.95 minimum fee per transaction
51.95
For each transaction, the higher of:
3.50% per transaction.
or
52.95 minimum fee per transaction
1:1 E-Check ACH
X1 Call Center
(via live, bilingual call
center agent)
Credit Cards
fEJ Visa
Mastercard
Discover
CZ American Express
E Debit Cards
Visa
E Mastercard
Z Discover
I-7or each transaction,
7.00% per transaction
Or
52.95 minimum fee per transaction
E-Check ACH
IVR
(via automated phone
system)
Credit Cards
O Visa
LJ Mastercard
0 Discover
O American Express
Debit Cards
O Visa
O Mastercard
0 Discover
E-Check / ACH
Cash
1"aymen1 PIO,TSSing SekTiCO3; Swtement ollrork: Cotaii'sf vAlum'cipat Court I Page 5 c.y:8
DocuSgn EnvOope UJ 6E49981B-341A-423E-8845-14088E52CO26
(at participating locations)
*Fee structure includes indemnified transaction processing for credit and debit transactions.
3. Itnplenientation Services
Only the services marked (E) Will be implemented, Fees will be waived if Merchant implements L-Payment System within twelve
(12) months:
lementation Service Fee Recurrence
• E-payment System Deployment & One-time
Program Implementation
El IVR Implementation
• Web Services or API Implementation
• File Integration
• Support & Training
hour(s))
Custom Programming
( hour(s))
One-time
One-time
One -tittle
Per hour
Per hour
Waived
Waived
Waived
• POS Terminals
terminal(s))
Per unit
4. Ongoing Services
Payment processing and development services to be funded by Merchant, as marked (Z):
Sers,ice
El Address Verification
Chargeback Processing
LJ Statement Fee
Fee Recurrence
Per occurrence
Per occurrence
Per occurrence
Waived
Fee
8
DowSign Envelope ID. 6E4996113-341A-423E-8845-74088E52CO26
EXHIBIT Bt INTEGRATION SCOPE
COURTS INTEGRATION (General Templat)
1. Merchant will make JIS (Codesmart) ("Software Vendor") aware of the requirement to integrate with the Provider E-Payment
system and of the anticipated Go -Live date contemplated herein. Merchant will compel Software Vendor to assist in setting up
direct data interface, including providing all file descriptions or API and/or FTP documentation.
2. If Provider is delivering a web service or API service, Provider will need access and resources from. the Merchant to ensure both
systems from each company can interface and exchange data appropriately. Failure to grant Provider access or a Merchant resource
to help support this step of the implementation process will result in delays to the Merchant's Go -Live date,
3. Provider Responsibilities
3.1. .A11. payment transactions will update the Merchant's J IS (Codesmart) system on a predetermined cadence.
3.2. If there are designated payments which are ineligible for online payment, Merchant will be able to omit those records from
being paid through Provider via their „PIS system.
3.3. Dependent on information from Software Vendor, data ma:‘,,, be searched by the following fields. or similar identifying
characteristic of the Customer,.
3.3.1.
3.3.2.
3..3,3,
3.3.4.
3.3,5,
3.3.6.
First Name
Last Name
Driver's License Number
Ticket Number
Citation Number
Case Number
4. Merchant Responsibilities
4..1. Merchant will supply Provider with Software Vendor contact information
4,7, Merchant will actively participate in accomplishing the Go -Live of the Program in the specified timeframe outlined herein.
4.3. Merchant shall provide access to a dedicated test and production environment for the implementation lifecycle.
4.4. Merchant will provide the file 'format specification currently used to post its payments to the JIS system, Merchant will fully
cooperate with Provider and provide the information required to integrate with the Merchant's system.
4.5. Merchant to provide multiple copies of bills and or receipts to Provider, if in project scope.
4.6. Merchant is responsible for determining and notifying Provider if (i) defendant shall be allowed the option(s) to select Traffic
School or proof of corrections, or (ii) a partial or full payment by the defendant shall be allowed. This notification must take
place prior to completion of the Design Document and the beta version of the Merchant site, and no later than thirty (30) days
after the Effective Date.
4.7. Merchant acknowledges that Counter is embedded in Merchant's JIS (Codesmart) system and all transactions will stay within
Merchant's J1S system.
4.8. Merchant will compel Software Vendor to supply Provider with a CSV file containing the following information. Provider
shall confirm file receipt.
Citation Number (Required)
4,82, Case Number (Required)
4.83, Defendant's Name (Required)
4,8.4. Date of Birth (Required for IVR)
4.8,5, Amount Due (Required)
Payability / Must Appear Flag (Required)
4,8,7, Address
4.8.8. Offense
4,8.9. Violation Date
4.8,10, Court Date
4.9, Merchant shall supply Provider with the following:
4„9,1, Payment information
4.9.2. W9 with Employer identification Number (EIN)
4.9,3., Financial Disbursement Agreement (FDA) for each judge in scope
4.9..4. Any applicable test case scenarios
PaYineIIr 7.417I'S SICEVInent C,ItatiII Lif' 4 YL,,I,Wwa .illuni,?friai 14w?
Doeu Ign Envelope ID: 6E499B1B-341A 423E-8845-74088E52G026
.9. Applicable cc is ti lcls logic
4i9,6i Applicable c st r1 verbiage to be included by record
p