HomeMy WebLinkAbout20242333.tiffCo ivad tb Y(i Lele
BOARD OF COUNTY COMMISSIONERS
PASS AROUND REVIEW
PASS -AROUND TITLE:
DEPARTMENT:
PERSON REQUESTING:
Chase Merchant Payment Processing Contract for Tyler Recording Access
Information Technology
Ryan Rose
DATE: 7/10/2024
Brief description of the problemlissue:
IT project CR-1434 Recording Access Documents is for The Clerk & Recording office to implement the
Recording Access module from Tyler Technologies to enables citizens to electronically record documents. In
order to implement this technology Weld County must purchase Merchant ID's from Chase Merchant Services
What options exist for the Board?
ructerk & Recorder is requesting the Board authorize the Chair to sign the attached Chase Merchant Payment Processing Contract to purchase
Merchant ID's and proceed with the project.
Consequences:
This is new functionality, but will expand electronic services available to citizens.
Impacts:
Tyler Recording Access Documents will enable citizens and other County Departments to electronically record documents (departments
will still be charged the recording fee to a House account). a
Cost (Current Fiscal Year/Ongoing or Subsequent Fiscal Years:
$0- all fees are passed through to the persoMcompany which is using the service.
Recommendation:
Legal has reviewed the agreement and Information Technology recommends approval of the agreement.
Perry L. Buck, Pro-Tem
Mike Freeman
Scott K. James
Kevin D. Ross, Chair
Lori Seine
Sunaort Recommendation Schedule
Place on BOCC Agenda Work Session Other/Comments:
4a1`
)47
Cpn5tni. ncyziop„ CC: Onb0.Se ( Il0
2024-2333
eirze05
ITOOt3
CHASE!) J.P.Morgan
SUBMITTERMERCHANT
PAYMENT PROCESSING INSTRUCTIONS AND GUIDELINES
These terms and conditions, the application, forms, and other documents provided by you herewith constitute the Agreement
between Paymentech, LLC, JPMorgan Chase Bank, NA, and Merchant.
Paymentech, LLC, also known as Chase Merchant Services ("CMS", "we", or "us"), for itself and on behalf of JPMorgan Chase Bank,
N.A. ("Chase"), is excited about the opportunity to join Tyler Technologies, Inc (referred to herein as "Submitter") in providing you,
the Merchant signing below (hereinafter referred to as "you" or "Merchant") with state-of-the-art payment processing services.
When you use the services of Submitter to receive payments for Transactions initiated by Card or by ECP, those Transactions are
processed by us through systems and networks owned by the Networks, each of which maintains its own set of Network Rules
goveming Transactions processed over such Network.
The Network Rules, generally require that we have a direct contract with each merchant for which we process payment transactions
through the Network, and this agreement (this "Agreement") contains certain contractual commitments required by the Network Rules
to be contained in each such contract.
1. Compliance with Network Rules, Applicable Law and User Guide; Network Liabilities.
You agree to comply with the Network Rules (including the Security Standards) of each Network, as they pertain to the Transactions
you submit to us (directly or via Submitter) for processing through Submitter. You shall not, through actor omission, cause CMS or
Chase to violate any Network Rules. You shall perform your obligations under this Agreement in compliance with all applicable
federal, state and local laws and regulations and shall not submit any Transaction that it knows to be illegal. CMS reserves the right
to temporarily suspend funding or refuse to process any Transaction if we reasonably suspect that it was prepared in violation of any
provision of this Agreement, applicable law, or the Network Rules. You agree to pay any and all fines, fees, penalties, liabilities,
charges and other amounts which may be imposed or assessed by the Networks on you, Chase or CMS as a result of your actions,
omissions, Transactions, Chargebacks or Returns, including without limitation, your failure to comply with the Network Rules, this
Agreement or any Security Standards (the "Network Liabilities").
2. Your Transactions; Chargebacks and Returns.
You represent and warrant that you will only use our services and submit Transactions for processing which represent the sale or
lease of goods or the provision of services by you to a Customer and not on behalf of any third -party seller. You shall have full
liability for all Chargebacks (with respect to Card Transactions) and all Returns (with respect to ECP Transactions), as may be
assessed in accordance with the applicable Network Rules, provided, however, that in the event that any Chargeback or Return is
ultimately reversed by the applicable Network in your favor, CMS shall refund you for the amount thereof.
3. Settlement and Funding.
(a) CMS will submit your Transactions to the applicable Network for processing, and thereafter will provisionally fund the
Settlement Account (as defined below).
(b) You must designate at least one bank account for the deposit and settlement of funds and the debit of any fees and costs
associated with CMS's processing of the Transactions (all such designated bank accounts shall be collectively referred to herein as
the "Settlement Account"). You authorize CMS to initiate electronic credit entries, debit entries, and adjustments to your Settlement
Account for amounts due to or from you in connection with this Agreement. CMS will not be liable for any delays in receipt of funds
or errors in Settlement Account entries caused by third parties, including but not limited to delays or errors by Submitter, the Networks,
or your bank.
(c) Unless otherwise agreed, the dollar amount payable to you for your Transactions will be equal to the amount submitted by you in
connection with your sale Transactions, minus the sum of amounts due from you, including Refunds, Chargebacks, Retums, Network
Liabilities, and all applicable charges and adjustments; provided, however, that in the event we fail to withhold any such amounts from
Submitter Madtant Payment Processing Instructions and Guidelines - CR419 Nov
INTrE LvcL PvvvcsoECH USE
Merchant Name:
Rev. November 2019
Page 1 of 5
Date Printed
your Transaction proceeds, we may debit your Settlement Account for such amounts ;
(d) If we fail to withhold any Refunds, Returns, Chargebacks, Network Liabilities or other charges or amounts due from the proceeds
payable to the Settlement Account (including where such proceeds are insufficient to cover such obligations), or if the Settlement
Account does not have a sufficient balance to pay amounts due from you under these guidelines, we may pursue one or more of the
following options: (i) demand and receive immediate payment for such amounts; (ii) debit the Settlement Account for the amount of
the negative balance; (iii) withhold settlement payments to the Settlement Account until all amounts are paid, (iv) delay
presentation of refunds until a payment is made to us of a sufficient amount to cover the negative balance; and (v) pursue any remedies
we may have at law or in equity.
4. Specific Requirements, Representations and Warranties Relating to ACH Transactions.
(a) The NACHA Operating Rules ("NACHA Rules") are the applicable Network Rules governing your ECP Transactions that utilize
the ACH network, including, without limitation, ACH, ARC, TEL and WEB Transactions ("ACH Transactions"). You are
responsible for complying with the NACHA Rules as set forth in Section 1 of this Agreement. The originating depository financial
institution which CMS uses (currently Chase) to originate and process your ACH Transactions (the "ODFI", as that term is further
defined in the NACHA Rules) retains the right to reject or delay any ACH Transaction, to execute an ACH Transaction through any
clearing house or channel it deems appropriate, to terminate or suspend your right to originate ACH Transactions, or to audit your
compliance with the NACHA Rules.
(b) Any credit made to your Customer's account as a result of an ACH Transaction originated by you (e.g., an issuance of a refund)
is provisional until your Customer's receiving depository financial institution (the "RDFI", as further defined in the NACHA Rules)
receives final settlement for such entry through a Federal Reserve Bank. If final settlement is not received by the RDFI, the RDFI
will receive a refund from your Customer, and your Customer will not be deemed to have been paid by you.
(c) You represent and warrant that: (i) each ACH Transaction you originate will comply with all applicable laws and NACHA Rules;
(ii) you will not originate any ACH Transaction as a Third Party Sender (as that term is defined in the NACHA Rules) and will not
allow any third party to originate an ACH Transaction through your account under this Agreement; (iii) all ACH Transactions
resulting in a debit to the Customer will be authorized by the Customer in writing and signed or similarly authenticated in a manner
that complies with the NACHA Rules; (iv) you will obtain and retain proper authorization, in accordance with all applicable laws
and the NACHA Rules, for each initiation of an ACH debit or credit to a Customer's account, and will make copies thereof available
to us upon request; and (v) you hereby make to us, and certify compliance with, all warranties that we or the ODFI make, or are
deemed to make, under the NACHA Rules, in connection with any ACH Transaction you originate.
5. Safeguarding Account Information; Security Standards.
(a) By accepting Card and ECP payments from your Customers, you acknowledge and understand the importance of protecting
Transactions and Account Information and complying with the applicable Network Rules, Security Standards, and applicable law.
You also acknowledges the heightened risk associated with access to Transactions and Account Information, and, to the extent you
do have access to Transactions and Account Information, you must establish policies and procedures to protect such information in
conformity with the Network Rules, Security Standards, and applicable law, including the storage and disclosure of such information.
You shall exercise reasonable care to prevent use or disclosure of Transactions, Account Information, other than as necessary to
complete a Transaction or as otherwise specifically permitted by the Network Rules or required by applicable law. If at any time
you determine or suspect that Transactions or Account Information have been compromised, you must notify CMS immediately and
assist in providing notification to such parties as may be required by law or Network Rules, or as CMS otherwise reasonably deems
necessary. You further agree to provide CMS, upon its request, with information related to your compliance with the Network Rules
and Security Standards as may from time to time be required by the Networks or reasonably requested by us.
(b) You acknowledge that failure to comply with the Network Rules, including the Security Standards, or the occurrence of a Data
Compromise Event, may result in assessments, fines and/or penalties by the Networks. In the event CMS or Chase incurs any damage,
loss, liability or expense as a result of any such failure or occurrence, including, without limitation, any Network Liability, you shall
reimburse CMS and Chase, as applicable, immediately for all such amounts. Furthermore, if any Network requires a forensic
examination of you or any of your agents, business partners, contractors, or subcontractors due to a Data Compromise Event, you
agree to cooperate with such forensic examination until it is completed, including, without limitation, the engagement of an examiner
acceptable to the relevant Network. Notwithstanding the foregoing, the Networks may directly, or demand that CMS, engage an
examiner on your behalf in order to expedite the investigation of the Data Compromise Event.
Submitter Merchant Payment Processing Instructions and Guidelines —CR419 Nov
INTERNALPAYMENTECH USE
Merchant Name:
Date Printed
Rev. November 20 19
Page 2 of 51
6. Merchant Taxpayer Certification and CMS Reporting Obligations.
Upon request from time to time, Merchant shall provide CMS with the appropriate taxpayer certification documentation, via Internal
Revenue Service (IRS) Form W-9 (or the appropriate versions of Form W-8, if applicable). Merchant shall promptly notify CMS if
there are any changes in this information. CMS may deduct withholding taxes, if any, from proceeds payable to Merchant or any entity
that is a party to this agreement where required under applicable law. CMS may, in accordance with applicable law and from time to
time during the term of this Agreement, request Merchant to recertify its taxpayer certification hereunder. Furthermore, Merchant shall
be responsible for any penalties related to the reporting obligations of CMS hereunder to the extent such penalties accrue based on the
actions or inactions of Merchant despite reasonable notice from CMS.
7. Amendments and Updates.
We reserve the right to update or amend this Agreement from time to time, including as may be required to ensure compliance with
the Network Rules, applicable law, or the policies, procedures or requirements of the ODFI. In such event, we will provide you with
the changes, or with an updated copy of this Agreement, and your continued use of our processing services after your receipt of such
changes shall constitute your agreement to comply with the Agreement as so amended.
8. Data Security and Privacy
By signing below, you represent to us that you do not have access to any Account Information (such as the Customer's primary
account number, expiration date, security code or personal identification number) and you will not request access to such Account
Information from Submitter. In the event that you do happen to receive Account Information in connection with the processing
services provided by Submitter or CMS under these guidelines, you agree that you will not use it for any fraudulent purpose or in
violation of any Network or applicable law and you will comply with all applicable Network Rules and Security Standards. If at any
time you believe that Account Information has been compromised, you must notify us promptly and assist in providing notification
to the proper parties. You must insure compliance with all Security Standards that are applicable to you and which may be published
from time to time by the Network. If any Network requires an audit of you due to a Data Compromise Event or suspected event,
you agree to cooperate with such audit. You may not use Account Information other than for the sole purpose of completing the
Transaction authorized by the Customer for which the information as provided to you, or as specifically allowed by Network Rules,
or required by law. In the event of your failure, including bankruptcy, insolvency or other suspension of business operations, you
shall not sell, transfer or disclose any materials that contain Transaction information or Account Information to third parties.
9. Definitions.
(a) "Account Information" is information related to a Customer or the Customer's Card or any bank account, depository account,
or other account maintained by the Customer, and that is obtained by you or Submitter from the Customer's Card or any check
provided by the Customer, or that is otherwise obtained by you from the Customer in connection with a Transaction (for example,
an account number, a security code, a PIN number, or the customer's zip code when provided as part of an address verification
system). Without limiting the foregoing, such information may include the Card account number, the bank account number, the
card expiration date, the Customer's name or date of birth, PIN data, security code data (such as CVV2 and CVC2) and any data
read, scanned, imprinted, or otherwise obtained from the Card or any check printed thereon, or magnetically, electronically or
otherwise stored thereon.
(b) "ACH" means Automated Clearing House.
(c) "Card" means a physical or virtual credit, debit card, pre -paid card, or stored value card, or any evidence thereof (e.g. account
number, access number, token, code, payment credential, or other form factor or access device), or any device, mobile
application, digital wallet or other technology, medium or method (regardless of form) used to access an account or account
number associated therewith and through which Network payment services are delivered, authorized and established between
a Customer and a Network, or representatives or members of a Card Network that Merchant accepts from Customers as
payment for goods or services.
(d) "Chargeback" is a rejection, reversal or retum of a Transaction you previously presented to CMS, as permitted and governed by
the applicable Network Rules. The term Chargeback shall include any Return of an ECP Transaction.
(e) "Chase" is JPMorgan Chase Bank, N.A. or other entity providing sponsorship to CMS as required by all applicable Networks.
Your acceptance of Network products is extended by the Chase.
(f) "CMS", "we", "our", and "us" is Paymentech, LLC, a Delaware limited liability company, having its principal office at 8181
Communications Parkway, Plano, Texas 75024.
(g) "Customer" is the person or entity to whom a Card is issued or who is otherwise authorized to use a Card and who initiates a
Submitter Merchant Payment Processing Instructions and Guidelines — CR419 Nov
IINTeRNA4 PAYMENTECH USE
Merchant Name:
Date Printed
Rev. November 2019
Page 3of5l
payment with you relating to a Transaction.
(h) "Data Compromise Event" means an occurrence that results, or could result, directly or indirectly, in the unauthorized access
to or disclosure of Transactions and/or Account Information.
(i) "ECP" means electronic check processing as a means of receiving or making payment in connection with a Transaction or
Refund. ECP includes various products of a type supported by CMS, including, without limitation, ACH, ARC, CCD, EFT,
POP, PPD, TEL, WEB and Facsimile Draft.
6) "Network" is any payment method provider whose payment method is accepted by you from your Customers and which is
accepted by CMS for processing, including, but not limited to, Visa, Inc., MasterCard Intemational, Inc., Discover Financial
Services, LLC and other credit and debit card providers, debit network providers. Network also includes the National Automated
Clearing House Association ("NACHA"), with respect to Transactions involving any credit or debit entry processed over the
ACH network, and any other network or clearing house over which any ECP Transactions may be processed.
(k) "Network Rules" are the standards, bylaws, rules, and operating regulations, as they exist from time to time, of the various
Networks, and includes the Security Standards.
(I) "Refund" means any refund or credit issued for any reason, including, without limitation, for a return of merchandise or
cancellation of services, and any adjustment of a Transaction.
(m) "Return" means any rejection, reversal or return of an ECP Transaction or ACH debit entry you previously presented to CMS,
as permitted and governed by the applicable Network Rules.
(n) "Security Standards" are all rules, regulations, standards or guidelines adopted or required by the Networks or the Payment
Card Industry Security Standards Council relating to privacy, data security and the safeguarding, disclosure and handling of
Account Information, including but not limited to the Payment Card Industry Data Security Standards ("PCI DSS"), Visa's
Cardholder Information Security Program, Discover's Information Security & Compliance Program, American Express's Data
Security Operating Policy, MasterCard's Site Data Protection Program, MasterCard's POS Terminal Security program and the
Payment Card Industry PIN Entry Device Standard, in each case as they may be amended from time to time.
(o) "Transaction" is a transaction conducted between a Customer and you utilizing a Card or ECP for payment in connection with
the sale of goods or the lease or provision of services by you (either directly or through Submitter). Transaction may also be used
to refer to the written or electronic record of such a transaction, including, without limitation, an authorization code, settlement
record, ECP file, or a credit or debit entry pursuant to and consistent with NACHA Rules which is submitted to CMS to initiate
or evidence a Transaction.
(p) "Transaction Receipt" means an electronic or paper record of a Transaction generated upon completion of a sale or Refund, a
copy of which is presented to the Customer.
1, the undersigned, individually and on behalf of Merchant, certify, represent and warrant that:
I am an owner, officer, partner or other authorized representative of the Merchant ("Authorized Representative"), duly
authorized to:
- enter into legally binding agreements on behalf of the Merchant;
- execute and submit this document on behalf of Merchant;
- provide all information contained herein (including, as applicable, banking or financial information, and personal
information relating to owners, officers, partners or Merchant contacts), on behalf of the Merchant;
• all information contained within this document or submitted in connection herewith is true, complete and not misleading.
• to the extent any bank account information is being provided in connection with this document, Merchant owns such bank
account, and such account is being maintained solely for business purposes and not for personal, family, or household purposes
• Chase Paymentech and Member may:
- investigate and verify the credit and financial information of Merchant, and
- obtain credit reports on Merchant from time to time in connection with establishing Merchant's account and maintaining
the Agreement.
If I have identified myself as an Owner of Merchant in this document, by signing below I authorize and instruct Chase
Paymentech, Member, or their designee(s) to conduct the following in connection with establishing Merchant's account and
maintaining the Agreement:
• obtain and use consumer credit reports (or other information derived therefrom) on me from time to time; and
• investigate and verify personal credit and financial information about me or any other owner identified herein or in the
Application, the Agreement, or any other document provided by me or Merchant in connection with any of the foregoing.
Subminer Merchant Payment Processing Instructions and Guidelines — CR419 Nov
11NTERNAL PAYMENTECH USk
Merchant Name:
Date Printed
Res. November 2019
Page 4of51
Merchant, intending to be legally bound, hereby agrees to the terms and conditions of the above Payment Processing
Instructions and Guidelines.
Agreed and Accepted by:
BOARD Or COUNTY COMMISSIONERS
WELD COUNTY, COLORADO
Merchant Legal Name
1150 O STR,T G 0631
Legal A
By (authorized signature)
KEVIN D. ROSS; SLiAIR
By, Nante, Title
SEA' 0 4 2024
Date
ATTEST:
the flt>ard
Deput k to the
Boar
ddad V' ,
Subnutter Pruacssmg Inmuchons and Gurdebnes — l R4 1,, \us cm. 2019
Pace )ofSi
I,1;c1; :.>L Pir�\i ENrECH iJcE
ibieflhanl �aI11C
Date Printed
za4- Z333
Houstan Aragon
From:
Sent:
To:
Cc:
Subject:
Byron Howell
Tuesday, September 3, 2024 10:28 AM
Jacob Mundt; Houstan Aragon; Esther Gesick
Karin McDougal; Ryan Rose; Skyler Whitmore; Cierra Howard
RE: Contract ID #8666
Houstan,
In light of Jacob's additional information, in my opinion, this contract could go before the
BOCC on the consent agenda.
Byron
From: Jacob Mundt <jmundt@weld.gov>
Sent: Friday, August 30, 2024 4:48 PM
To: Houstan Aragon <haragon@weld.gov>; Esther Gesick <egesick@weld.gov>
Cc: Byron Howell <bhowell@weld.gov>; Karin McDougal <kmcdougal@weld.gov>; Ryan Rose <rrose@weld.gov>; Skyler
Whitmore <swhitmore@weld.gov>; Cierra Howard <choward@weld.gov>
Subject: RE: Contract ID #8666
All,
I'll try add context to this thread. I don't believe we need any additional agreements or signatures as everything with
Wells Fargo, Banner, and Tyler software is already in place, we are just replacing the payment gateway technology that
processes the transactions. This is a required change from Tyler, who requested we sign this document. This new
agreement (8666) may best be related to 20112237.pdf (weld.co.us), which is our master agreement for Tyler Records
Management, where the software will be embedded and deployed.
If I can help fill in any gaps, please let me know.
WELD COUNTY, CO
Jake Mundt
Director of App & DB Sys — Information Technology
R. Desk: 970-400-2521
Technical Support Center: 970-400-4357
imundt@weld.gov
P.O. Box 758, 1401 N 170 Ave., Greeley, CO 80632
IMPORTANT: This electronic transmission and any attached documents or other writings are intended only for the person or entity to which it is addressed and
may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this communication in error, please
immediately notify sender by return e-mail and destroy the communication. Any disclosure, copying, distribution or the taking of any action concerning the
contents of this communication or any attachments by anyone other than the named recipient is strictly prohibited.
From: Skyler Whitmore <swhitmore@weld.gov>
Sent: Friday, August 30, 2024 4:28 PM
To: Jacob Mundt <imundt@weld.gov>
Subject: Fwd: Contract ID #8666
Jake, do you want to weigh in on this one?
Skyler Whitmore
From: Houstan Aragon <haragon@weld.gov>
Sent: Friday, August 30, 2024 4:22:41 PM
To: Byron Howell <bhowell@weld.gov>; Karin McDougal <kmcdougal@weld.gov>
Cc: Esther Gesick <egesick@weld.gov>; Cheryl Hoffman <choffman@weld.gov>; Ryan Rose <rrose@weld.gov>; Skyler
Whitmore <swhitmore@weld.gov>; Cierra Howard <choward@weld.gov>
Subject: RE: Contract ID #8666
Good afternoon,
Thank you for all of this additional information. If am understanding you correctly, this is not ready for prime
time just yet, based on the need for an application and supplementing documents that the County provided to
the other parties that constitute the full picture. I have searched Tyler for such records existing and I have
come up empty handed; therefore, I will need to rely on the IT and/or Clerk and Recorder staff to provide those
additional documents to proceed forward in getting this executed.
Houstan Aragon
Deputy Clerk to the Board
Clerk to the Board's Office
Weld County
1150 O Street
Greeley, CO 80631
Tel: (970) 400-4224
Email: haragon(a�weld.gov
Confidentiality Notice: This electronic transmission and any attached documents or other writings are intended
only for the person or entity to which it is addressed and may contain information that is privileged, confidential
or otherwise protected from disclosure. If you have received this communication in error, please immediately
notify sender by return e-mail and destroy the communication. Any disclosure, copying, distribution or the
taking of any action concerning the contents of this communication or any attachments by anyone other than
the named recipient is strictly prohibited.
From: Byron Howell <bhowell@weld.gov>
Sent: Thursday, August 29, 2024 11:47 AM
To: Houstan Aragon <haragon@weld.gov>; Karin McDougal <kmcdougal@weld.gov>
Cc: Esther Gesick <egesick@weld.gov>; Cheryl Hoffman <choffman@weld.gov>; Ryan Rose <rrose@weld.gov>
Subject: RE: Contract ID #8666
Houstan,
2
In my opinion, the substance of this agreement is fine and needs BOCC approval as BOCC Chair
is authorized representative of Merchant (Weld County) to enter into legally binding
agreements (see page 4 requirements).
This document is Payment Processing, Instructions, Guidelines. On page one at the top of the
document, it also says these "terms/conditions, the application forms, and other docs
provided by you constitute the agreement" between Paymentech LLC, JP Morgan Chase, NA,
and Merchant (Weld County).
In answer to your question regarding the one signature block, I think we need to look at the
application form and any other documents submitted by Weld County to contracting
parties. The application itself may contain required signatures and approvals and should be
attached to this payment processing document for review.
Also to note, is that 3b of this processing document requires a "settlement account" (bank
account). The Clerk and Recorder charges fees for recording docs using this
processing. Likewise, it seems the Clerk and Recorder would handle things like chargebacks,
etc. much like Sonja handles the credit card transactions at the jail, so the Clerk and Recorder
would deal with transactions with this bank account. I could not find anything in our county
code where finance or IT would handle an individual account of this nature.
Byron
From: Houstan Aragon <haragon@weld.gov>
Sent: Wednesday, August 28, 2024 4:28 PM
To: Byron Howell <bhowell@weld.gov>; Karin McDougal <kmcdougal@weld.gov>
Cc: Esther Gesick <egesick@weld.gov>; Cheryl Hoffman <choffman@weld.gov>
Subject: Contract ID #8666
Good afternoon,
I just received this contract through CMS intended for Wednesday, September 4, 2024, Consent Agenda. This
attached is an agreement among Paymentech, LLC, and JPMorgan Chase Bank, NA, and the Merchant (Weld
County).
At first glance I was concerned to find only one signature block, but I am not certain from a legalese stance if
this is proper, or if this needs to be held off for staff to work with these vendors for additional signature blocks
to be added?
Please Advise — Thanks,
Houstan Aragon
Deputy Clerk to the Board
Clerk to the Board's Office
Weld County
1150 O Street
3
Greeley, CO 80631
Tel: (970) 400-4224
Email: haragon(a)weld.gov
Confidentiality Notice: This electronic transmission and any attached documents or other writings are intended
only for the person or entity to which it is addressed and may contain information that is privileged, confidential
or otherwise protected from disclosure. If you have received this communication in error, please immediately
notify sender by return e-mail and destroy the communication. Any disclosure, copying, distribution or the
taking of any action concerning the contents of this communication or any attachments by anyone other than
the named recipient is strictly prohibited.
4
Contract Form
Entity Information
Entity Name*
PAYMENTECH LLC
Entity ID*
@00015822
Contract Name*
CHASE MERCHANT PAYMENT PROCESSING CONTRACT
FOR TYLER RECORDING ACCESS
Contract Status
CTB REVIEW
Q New Entity?
Contract ID
8666
Contract Lead*
CHOWARD
Contract Lead Email
choward@weld.gov
Parent Contract ID
Requires Board Approval
YES
Department Project #
Contract Description*
IT PROJECT CR-1434 RECORDING ACCESS DOCUMENTS IS FOR THE CLERK & RECORDING OFFICE TO IMPLEMENT
THE RECORDING ACCESS MODULE FROM TYLER TECHNOLOGIES WELD COUNTY MUST PURCHASE MERCHANT ID'S
FROM CHASE MERCHANT SERVICES AKA PAYMENTECHLLC
Contract Description 2
Contract Type*
CONTRACT
Amount*
50.00
Renewable*
NO
Automatic Renewal
NO
Grant
IGA
Department
INFORMATION
TECHNOLOGY-GIS
Department Email
CM-
InformationTechnologyGI
S@weldgov.com
Department Head Email
CM-
InformationTechnologyGI
5-
DeptHead@weldgov.com
County Attorney
GENERAL COUNTY
ATTORNEY EMAIL
County Attorney Email
CM-
COUNTYATTORNEY@WEL
D.GOV
Requested BOCC Agenda Due Date
Date* 08/31/2024
09/04/2024
Will a work session with BOCC be required?*
NO
Does Contract require Purchasing Dept. to be
included?
NO
If this is a renewal enter previous Contract ID
If this is part of a MSA enter MSA Contract ID
Note: the Previous Contract Number and Master Services Agreement Number should be left blank if those contracts
are not in OnBase
Contract Dates
Effective Date
Termination Notice Period
Contact Information
Review Date*
05/01/2025
Committed Delivery Date
Renewal Date
Expiration Date*
08/30/2025
Contact Info
Contact Name Contact Type Contact Email Contact Phone 1 Contact Phone 2
Purchasing
Purchasing Approver Purchasing Approved Date
CONSENT 08/28/2024
Approval Process
Department Head Finance Approver Legal Counsel
RYAN ROSE CONSENT CONSENT
DH Approved Date Finance Approved Date Legal Counsel Approved Date
08/28/2024 08/28/2024 08/28/2024
Final Approval
BOCC Approved Tyler Ref #
AG 090424
BOCC Signed Date Originator
CHOWARD
BOCC Agenda Date
09/04/2024
Hello