My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Paymentus Corporation 4/16/2019
>
Contracts
>
Agreement
>
Technology
>
Paymentus Corporation 4/16/2019
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/23/2019 10:24:19 AM
Creation date
4/23/2019 10:24:14 AM
Metadata
Fields
Template:
Contracts
Contractor's Name
Paymentus Corporation
Approval Date
4/16/2019
Council Approval Date
3/13/2019
Department
Public Works
Department Project Manager
Matt Welborn
Subject / Project Title
Electronic Bill Payment Gateway Services
Tracking Number
0001726
Total Compensation
$151,000.00
Contract Type
Agreement
Contract Subtype
Technology
Retention Period
6 Years Then Destroy
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
10
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Paymentus <br /> function independent of any billing system integration. <br /> A payment posting file can be emailed or downloaded (i) Paymentus Fully Hosted Solution ;or <br /> from Paymentus Agent Dashboard. If Client chooses (ii) Any other configuration <br /> to have Paymentus platform integrated with its billing <br /> system, Paymentus offers two options: To substantially reduce or eliminate any PCI <br /> (i) Paymentus standard integration compliance risks and to render all Client systems out <br /> specification that Client can use to integrate its billing of scope from PCI compliance requirements, Client <br /> systems with Paymentus platform ("Standard agrees to use Paymentus'fully hosted service where <br /> Integration"); (or) Paymentus uses its own platform to capture <br /> (ii) Paymentus to either customize or Payments and to manage the entire(end to end)user <br /> configure its platform to integrate with Client using file experience from all channels for Payment <br /> specification or APIs supported by Client's billing acceptance: Web, Mobile, IVR, POS devices, <br /> system ("Client Specific Integration") recurring payments, Ebill Presentment ("Paymentus <br /> Fully Hosted Solution"). If Client chooses any other <br /> If Client chooses Standard Integration, integration such as third party web pages integrated <br /> Paymentus agrees to fully cooperate with Client and with Paymentus APIs, third party gateway pages, or <br /> provide its specification to Client. Paymentus also its own IVR systems or POS solution not provided by <br /> agrees to participate in meetings with Client's Paymentus, or a cashiering module from third party, <br /> software vendor to provide any information or Client expressly agrees that Client shall not be <br /> clarifications needed to understand Standard exempt from PCI requirements and shall be liable for <br /> Integration. any data breaches occurring at its own systems as <br /> Client's recognizes that Client systems are <br /> If Client chooses Client Specific Integration, participating in the transactions and are in scope for <br /> Paymentus agrees to develop such integration at no PCI compliance. Under such circumstances, <br /> cost to Client,provided however, Client agrees to fully Paymentus shall not be responsible for any PCI <br /> cooperate with Paymentus and cause its software obligations outside of Paymentus own Platform and <br /> vendors to fully cooperate with Paymentus. Client Paymentus expressly disclaims any PCI or security <br /> agrees to provide all specification required for Client obligations related to Client systems or any third party <br /> specific integration. Client further agrees to systems that participate in the payment transactions. <br /> participate in testing with Paymentus and if needed, <br /> cause its billing software vendors to participate in Paymentus highly recommends that Client <br /> testing. uses Paymentus Fully Hosted Solution to <br /> substantially reduce its PCI compliance and data <br /> Based on Client's use of Paymentus platform breach risks. <br /> and respective modules selected under this <br /> Agreement, Paymentus will require the following If Client chooses to use any other option <br /> integration points: other than Paymentus Fully Hosted Solution, Client <br /> (i) For one time Payment Module: agrees and warrants that Client shall remain PCI <br /> a. Customer Information—Text File or Real- compliant throughout the term of this Agreement. For <br /> time clarity, just because Client uses PCI compliant <br /> b. Payment Posting—Text File or Real-time applications such as its billing software, it does not <br /> (ii) For Recurring Payment Module eliminate the need for Client to be PCI compliant. <br /> a. Text File For clarity, if Client systems are participating <br /> (iii) For E-billing Module in payment transactions in any form, Client systems <br /> a. Billing Data -Text File or Real-time link fall within PCI compliance scope. <br /> to billing data <br /> (iv) For ECM Module 4.3 Explicit User Confirmation <br /> a. Audience File — Text File for customer <br /> engagement messages Paymentus shall confirm the dollar amount of <br /> all Payments to be charged to a Card and <br /> Each of these can be based on Standard electronically obtain the User approval of such <br /> Integration or Client Specific Integration. charges prior to initiating Card authorizations <br /> transaction. Paymentus will provide User with <br /> 4.2 PCI Compliance electronic confirmation of all transactions. <br /> For PCI Compliance, Client has two options 4.4 Merchant Account <br /> for using Paymentus platform: <br /> Master Services Agreement—Absorbed Page 3 of 8 <br /> 100205 <br />
The URL can be used to link to this page
Your browser does not support the video tag.