UPS® Address Validation API (XML) and UPS Street Level Address Validation API (XML and Web Services Clause Samples

UPS® Address Validation API (XML) and UPS Street Level Address Validation API (XML and Web Services. Any request to the UPS Address Validation API or UPS Street Level Address Validation API shall be solely for the purpose of validating an address in connection with tendering a package intended for delivery via services offered by UPSI. You shall design the Application(s) such that the following language, or such other language provided by UPS from time to time, is conspicuously displayed on the same visible screen as, and in reasonable proximity to, the Information informing the user of an invalid address: “NOTICE: UPS assumes no liability for the information provided by the address validation functionality. The address validation functionality does not support the identification or verification of occupants at an address.” Further, You shall design the Application(s) such that the following language, or such other language provided by UPS from time to time, is conspicuously displayed on the same visible screen as, and in reasonable proximity to, Information returned from the UPS Address Validation API or Street Level Address Validation API informing the user either (at Your option): (a) with respect to a P.O. Box address or (b) with respect to any address: “NOTICE: The address validation functionality will validate P.O. Box addresses. However, UPS does not deliver to P.O. Boxes. Attempts by customer to ship to a P.O. Box via UPS may result in additional charges.”
View SourceView Similar (3)

Related to UPS® Address Validation API (XML) and UPS Street Level Address Validation API (XML and Web Services

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, and ▇▇- ▇▇▇-▇▇▇, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Real and Reactive Power Control and Primary Frequency Response 9.5.1 Power Factor Design Criteria.

  • Customer Services Customer Relationship Management (CRM): All aspects of the CRM process, including planning, scheduling, and control activities involved with service delivery. The service components facilitate agencies’ requirements for managing and coordinating customer interactions across multiple communication channels and business lines. Customer Preferences: Customizing customer preferences relative to interface requirements and information delivery mechanisms (e.g., personalization, subscriptions, alerts and notifications).

  • Contact Points Each Party shall designate a contact point to facilitate communications between the Parties on any matter covered by this Agreement.

  • Gold Open Access Articles May be shared according to the author-selected end-user license and should contain a CrossMark logo, the end user license, and a DOI link to the formal publication on ScienceDirect. Please refer to Elsevier's posting policy for further information.