ACH File Service Sample Clauses

ACH File Service. 4.4.1. Upon request by Company, American Express will create a Nacha-compliant file containing the details of the payment requested by Company (the “ACH File”) that is made available for the Company to download through the Portal (the “ACH File Service”). Once downloaded, Company can then submit the ACH File to its bank for processing on the Company’s bank account. American Express does not initiate or process any ACH Payments through the ACH File Service. 4.4.2. Company is solely responsible for providing complete and accurate information required for American Express to create the ACH File, including, but not limited to, required authorizations. Company acknowledges and agrees that American Express assumes no liability for any communication from Company to American Express or for any communication to Suppliers on Company’s behalf or at the direction of Company. American Express is not responsible for the content or format of ACH Files. Company agrees that it shall indemnify American Express from and against any and all losses arising directly or indirectly from any errors contained in any ACH File or an inability to process payments by any third party due to errors contained in any ACH File prepared in accordance with information provided by Company. 4.4.3. Stop Payment, Reversals and Recalls – Company acknowledges and agrees that American Express does not have any ability or obligation to honor any request for a stop payment, reversal or recall of ACH Files or payments once an ACH File has been submitted by Company to its bank.
View SourceView Similar (2)
ACH File Service. Upon your request, we will create a Nacha-compliant file containing the details of the payment requested by you (the “ACH File”), which ACH File shall be made available for you to download through your Account (the “ACH File Service”). Once downloaded, you can submit the ACH File to your bank for processing on your bank account. We do not initiate or process any ACH Payments through the ACH File Service. You are solely responsible for providing complete and accurate information required for us to create ACH Files, including but not limited to, required authorizations. You acknowledge and agree that we assume no liability for any communication from you to us or for any communication to Suppliers on your behalf or at your direction. We are not responsible for the content or format of ACH Files. You agree that you shall indemnify us from and against any and all losses arising directly or indirectly from any errors contained in any ACH File or an inability to process payments by any third party due to errors contained in any ACH File prepared in accordance with information provided by you. You acknowledge and agree that we do not have any ability or obligation to honor any request for a stop payment, reversal or recall of ACH Files or payments once you have submitted an ACH File to your bank. You consent and authorize us: (i) to enable the ACH File Service set forth in this Section 3 as a Payment Method for you; and (ii) to share, release, communicate and provide to third parties, all relevant information and documentation pertaining to you, your Users and Suppliers that is necessary to effect the ACH File Service to you and/or to provide new benefits, products or services. You acknowledge that it may be necessary for a third party to have access to such information in order to effectively provide you with the ACH File Service. You agree that except as otherwise expressly set forth in this Agreement, we will not provide notification to you or your Users with respect to delivery of such information to third parties and we have no responsibility or liability to verify what such third parties will do with information provided by us. If you elect to use the ACH Payment Service, you may use such service to make ACH Payments to your Suppliers in the United States. Your use of the ACH Payment Service is subject to the terms and conditions relating to ACH Payments set forth in Section B of your Payment Services Agreement. You agree to be bound by the terms and conditi...
View Source

Related to ACH File Service

  • COMPUTER GRAPHICS FILES The Engineer agrees to comply with Attachment G, Computer Graphics Files for Document and Information Exchange, if determined by the State to be applicable to this contract.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Processing of Customer Personal Data 3.1 UKG will: 3.1.1 comply with all applicable Data Protection Laws in the Processing of Customer Personal Data; and 3.1.2 not Process Customer Personal Data other than for the purpose, and in accordance with, the relevant Customer’s instructions as documented in the Agreement and this DPA, unless Processing is required by the Data Protection Laws to which the relevant UKG Processor is subject, in which case UKG to the extent permitted by the Data Protection Laws, will inform Customer of that legal requirement before the Processing of that Customer Personal Data. 3.2 Customer hereby: 3.2.1 instructs UKG (and authorizes UKG to instruct each Subprocessor) to: (a) Process Customer Personal Data; and (b) in particular, transfer Customer Personal Data to any country or territory subject to the provisions of this DPA, in each case as reasonably necessary for the provision of the Services and consistent with the Agreement. 3.2.2 warrants and represents that it is and will at all relevant times remain duly and effectively authorized to give the instructions set out in Section 3.2.1 on behalf of each relevant Customer Affiliate; and 3.2.3 warrants and represents that it has all necessary rights in relation to the Customer Personal Data and/or has collected all necessary consents from Data Subjects to Process Customer Personal Data to the extent required by Applicable Law. 3.3 Schedule 1 to this DPA sets out certain information regarding UKG’s Processing of Customer Personal Data as required by Article 28(3) of the GDPR (and equivalent requirements of other Data Protection Laws).

  • Database File The Servicer will provide the Successor Servicer with a data file (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Cutoff Date, (ii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Servicing Transfer, and (iii) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Servicing Transfer.

  • Computer Files Marked The Seller shall, at its own expense, on or before the Closing Date, indicate in its computer files that the Receivables have been sold to the Purchaser pursuant to this Receivables Purchase Agreement and deliver to the Purchaser the Receivable Schedule, certified by an officer of the Seller to be true, correct and complete.