API and Dashboard Sample Clauses

API and Dashboard. Stripe has developed and provides access to the API that may be used to access the Services. You may use the API solely as described in the Documentation to use the Services on websites and through the applications identified in your Stripe Account. You may manage your Stripe Account, connect with other service providers, and enable additional features through the Stripe management dashboard (“Dashboard”). You may not use the API for any purpose, function, or feature not described in the Documentation or otherwise communicated to you by us. Due to the nature of the Services, we will update the API and Documentation from time to time, and may add or remove functionality. We will provide you Notice in the event of material changes, deprecations, or removal of functionality from the API so that you may continue using the Services with minimal interruption. We will make publishable and secret API keys for live and test Transactions available to you through the Dashboard. Publishable keys identify Transactions with your Customers, and secret keys permit any API call to your Stripe Account. You are responsible for securing your secret keys – do not publish or share them with any unauthorized persons. Failure to secure your secret keys will increase the likelihood of fraud on your Stripe Account and potential losses to you or your Customers. You should contact us immediately if you become aware of any unauthorized use of your secret key or any other breach of security regarding the Services. We provide more details on proper use of publishable and secret API keys in the Documentation. Information on securing your Stripe Account is available in Section D.
AutoNDA by SimpleDocs
API and Dashboard. (a) Swifter has developed and provides access to the API that may be used to access the Services. You may use the API solely as described in the Documentation to use the Services on websites and through the applications identified in your Swifter Account. You may manage your Swifter Account, connect with other service providers, and enable additional features through the Swifter dashboard (“Dashboard”).
API and Dashboard. NihaoPay has developed and provides access to the API that may be used to access the Services. You may use the API solely as described in the Documentation to use the Services on websites and through the applications identified in your NihaoPay Account. You may manage your NihaoPay Account, connect with other service providers, and enable additional features through the NihaoPay management dashboard (“Dashboard”, “Transaction Management System”, and “TMS”). You may not use the API for any purpose, function on, or feature not described in the Documentation or otherwise communicated to you by us. Due to the nature of the Services, we will update the API and Documentation from time to time and may add or remove functionality. We will provide you Notice in the event of material changes, deprecations, or removal of functionality from the API so that you may continue using the Services with minimal interruption. We will make publishable and secret API keys for live and test Transactions available to you through the Dashboard. Publishable keys identify Transactions with your Customers, and secret keys permit any API call to your NihaoPay Account. You are responsible for securing your secret keys – do not publish or share them with any unauthorized persons. Failure to secure your secret keys will increase the likelihood of fraud on your NihaoPay Account and potential losses to you or your Customers. You should contact us immediately if you become aware of any unauthorized use of your secret key or any other breach of security regarding the Services. We provide more details on proper use of publishable and secret API keys in the Documentation.
API and Dashboard. Fyiro has developed and provides access to the API that may be used to access the Services. You may use the API solely as described in the Documentation to use the Services on websites and through the applications identified in your Fyiro Account. You may manage your Fyiro Account, connect with other service providers, and enable additional features through the Fyiro management dashboard (“Dashboard”). Fyiro will use the Dashboard to provide you with information about your Fyiro Account. Fyiro will also provide you with access to monthly summary reports which will include all your Fyiro Account activity, grouped by month, up to the most recent full day. The information may be provided in your language, and if not, it will be provided in English. Further detail about the information provided to you through the Dashboard is available in the Account Reporting section of the Documentation. You may not use the API for any purpose, function, or feature not described in the Documentation or otherwise communicated to you by us. Due to the nature of the Services, we will update the API and Documentation from time to time, and may add or remove functionality. We will provide you Notice in the event of material changes, deprecations, or removal of functionality from the API so that you may continue using the Services with minimal interruption. We will make publishable and secret API keys for live and test Transactions available to you through the Dashboard. Publishable keys identify Transactions with your Customers, and secret keys permit any API call to your Fyiro Account. You are responsible for securing your secret keys — do not publish or share them with any unauthorised persons. Failure to secure your secret keys will increase the likelihood of fraud on your Fyiro Account and potential losses to you or your Customers. You should contact us immediately if you become aware of any unauthorised use of your secret key or any other breach of security regarding the Services. We provide more details on proper use of publishable and secret API keys in the Documentation. Information on securing your Fyiro Account is available in Section D.
API and Dashboard. Reap has developed and provides access to the API that may be used to access the Program, either directly or through a Platform Provider. You may use the API solely as described in the Documentation. You may manage your Program Account and enable additional features through the Reap dashboard, or if you are a Platform Company, through your Platform Provider's dashboard ("Dashboard" refers to the Reap Dashboard unless you are a Platform Company accessing the Program Services through your Platform Provider's dashboard, in which case "Dashboard" refers to your Platform Provider's dashboard). Platform Providers may offer Program Services through a Dashboard provided by the Platform, in which case the Platform Provider will connect to the Reap API, rather than the Platform Company connecting directly to the Reap API and accessing the Reap Dashboard. You may not use the API for any purpose, function, or feature not described in the Documentation or otherwise communicated to you by us. Due to the nature of the Program, we will update the API and Documentation from time to time, and may add or remove functionality. We (or your Platform Provider, if applicable) will provide you Notice in the event of material changes, deprecations, or removal of functionality from the API so that you may continue using the Program with minimum interruption. We (or, in the case of a Platform Company, your Platform Provider) will make API keys available to you through the Dashboard. You are responsible for securing your API keys. Failure to secure your API keys will increase the likelihood of fraud on your Program Account and potential losses to you. You should contact us (or, in the case of a Platform Company, your Platform Provider) immediately if you become aware of any unauthorized use of your API key or any other breach of security regarding the Program. We provide more details on proper use of API keys in the Documentation.

Related to API and Dashboard

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Web Hosting If Customer submits a Service Order(s) for web hosting services, the following terms shall also apply:

  • Helpdesk Customers must contact LightEdge Support to report service trouble or an outage with LightEdge Technical Support. LightEdge Technical Support will be available seven (7) days per week; twenty-four (24) hours per day; three hundred sixty-five days (365) days per year. LightEdge Technical Support provides support for network monitoring, trouble ticket resolution, and fault isolation up to the termination point of LightEdge provided Equipment. LightEdge Technical Support will accept trouble and outage related support calls from any customer representative. LightEdge will not perform any requested activity which may cause Service disruption or perform any changes to Service unless request is initiated by an Authorized Contact. LightEdge reserves the right to delay response on support tickets opened by anyone other than the Authorized Contact. Communication between Customer and LightEdge not initiated by Authorized Contact will not be subject to SLA remedies. All communications with Customer will be in the English language.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

  • 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 §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, 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.

  • Support Services HP’s support services will be described in the applicable Supporting Material, which will cover the description of HP’s offering, eligibility requirements, service limitations and Customer responsibilities, as well as the Customer systems supported.

Time is Money Join Law Insider Premium to draft better contracts faster.