Integration with Client’s Billing System Sample Clauses

POPULAR SAMPLE Copied 1 times
Integration with Client’s Billing System. At no cost to Client, Paymentus will develop one (1) file format interface with Client’s billing system using Client’s existing text file format currently used to post payments to Client’s billing system. Client will be responsible to provide Paymentus with the one file format specification and will fully cooperate with Paymentus during the development of the said interface. If Client chooses to create an automated file integration process to download the posting file, due to Paymentus security requirements, Client will use Paymentus specified integration process. Paymentus platform is an independent full service fully hosted platform per PCI-DSS requirements for a fully hosted solution. As such, Paymentus platform does and can function independent of any billing system integration. A payment posting file can be emailed or downloaded from Paymentus Agent Dashboard. If Client chooses to have Paymentus platform integrated with its billing system, Paymentus offers two options: (i) Paymentus standard integration specification that Client can use to integrate its billing systems with Paymentus platform (“Standard Integration”); (or) (ii) Paymentus to either customize or configure its platform to integrate with Client using file specification or APIs supported by Client’s billing system (“Client Specific Integration”) If Client chooses Standard Integration, Paymentus agrees to fully cooperate with Client and provide its specification to Client. Paymentus also agrees to participate in meetings with Client’s software vendor to provide any information or clarifications needed to understand Standard Integration. If Client chooses Client Specific Integration, Paymentus agrees to develop such integration at no cost to Client, provided however, Client agrees to fully cooperate with Paymentus and cause its software vendors to fully cooperate with Paymentus. Client agrees to provide all specification required for Client specific integration. Client further agrees to participate in testing with Paymentus and if needed, cause its billing software vendors to participate in testing. Based on Client’s use of Paymentus platform and respective modules selected under this Agreement, Paymentus will require the following integration points: (i) For one time Payment Module: a. Customer Information – Text File or Real- time b. Payment Posting – Text File or Real-time (ii) For Recurring Payment Module a. Text File (iii) For E-billing Module a. Billing Data - Text File or Real-time li...
View SourceView Similar (7)
Integration with Client’s Billing System. At no cost to Client, Paymentus will develop and maintain a real-time interface to interact with the MUNIS (“Client’s Supplier”) IVR Gateway, provided Client cooperates fully with Paymentus and causes Client’s Supplier to fully cooperate. Paymentus shall be responsible for maintaining compatibility with the MUNIS IVR Gateway or other real-time integrated non-custom standard MUNIS module without additional cost to what is agreed upon in this Agreement. If this compatibility is not fully implemented or fails, solely due to Paymentus’ acts or omissions despite full cooperation from Client and Client’s Supplier, the Client, at its discretion, may deem it a Material Breach as provided in Section 9.2.
View SourceView Similar (3)
Integration with Client’s Billing System. At no cost to Client, Paymentus will develop one (1) file format interface with Client’s billing system using Client’s existing text file format currently used to post payments to Client’s billing system. Client will be responsible to provide Paymentus with the one file format specification and will fully cooperate with Paymentus during the development of the said interface. If Client chooses to create an automated file integration process to download the posting file, due to Paymentus security requirements, Client will use Paymentus specified integration process.
View Source

Related to Integration with Client’s Billing System

  • Contact with Customers and Suppliers Until the Closing Date, the Buyer shall not, and shall cause its Affiliates and direct its other Representatives not to, contact or communicate with the employees, customers, suppliers, distributors or licensors of the Acquired Entities, or any other Persons having a business relationship with the Acquired Entities, concerning the transactions contemplated hereby or any of the foregoing relationships without the prior written consent of the Seller.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Billing Services 6 SECTION 3.01.

  • Interconnection Customer (1) Interconnection Customer shall construct and, unless otherwise indicated, shall own, the following Interconnection Facilities: None (2) In the event that, in accordance with the Interconnection Construction Service Agreement, Interconnection Customer has exercised the Option to Build, it is hereby permitted to build in accordance with and subject to the conditions and limitations set forth in that Section, the following portions of the Transmission Owner Interconnection Facilities which constitute or are part of the Customer Facility: None Ownership of the facilities built by Interconnection Customer pursuant to the Option to Build shall be as provided in the Interconnection Construction Service Agreement.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.