Skip to content
CenterFuze
Legal Version Archive

Service Level Agreement

Publication date: January 1, 2026 · Effective date: January 1, 2026 · Version 1.0

This immutable archive preserves the exact published version. View the current document.

CenterFuze Service Level Agreement

Effective date: January 1, 2026

Version: 1.0

This Service Level Agreement (“SLA”) is part of the CenterFuze Customer Subscription Agreement and applies to all paid production CenterFuze Services, excluding beta, trial, sandbox, development, and free services.

1. Availability commitment

CenterFuze will make the Covered Services available with a Monthly Uptime Percentage of at least 99.99% during each calendar month.

“Monthly Uptime Percentage” means 100% minus the percentage of total minutes in the month during which a Covered Service is Unavailable, excluding Excluded Downtime. “Unavailable” means substantially all valid users of an affected customer tenant are unable to log in to or submit valid requests to the core production Service, as determined by CenterFuze's production monitoring and incident records. Isolated user, feature, integration, or performance issues that do not materially prevent use of the core Service are not Unavailability.

2. Maintenance

CenterFuze may perform routine maintenance daily using deployment and maintenance procedures designed to avoid or minimize disruption. CenterFuze will give at least 24 hours' notice for scheduled maintenance reasonably expected to cause Unavailability, except emergency maintenance. Scheduled disruptive maintenance will ordinarily occur outside U.S. Eastern Time business hours and will not exceed four hours in a calendar month without additional notice.

CenterFuze may perform emergency maintenance when reasonably necessary to address a material security vulnerability, legal requirement, data-integrity issue, provider requirement, or threat to the Services. CenterFuze will provide notice as soon as reasonably practicable.

3. Excluded Downtime

“Excluded Downtime” means Unavailability caused by:

  • scheduled or emergency maintenance meeting Section 2;
  • Amazon Web Services or another hosting, cloud, internet, telecommunications, or infrastructure provider outside CenterFuze's reasonable control;
  • CardPointe, Worldpay, or another customer-selected or third-party integration;
  • Customer's or an Authorized User's systems, devices, network, identity provider, credentials, data, configuration, instructions, misuse, or failure to follow Documentation;
  • suspension permitted by the Customer Agreement;
  • beta, trial, preview, free, sandbox, development, or non-production functionality;
  • denial-of-service attacks or other malicious acts that CenterFuze could not reasonably prevent through its maintained safeguards;
  • force majeure events under the Customer Agreement; or
  • use beyond documented capacity or limits or contrary to the Customer Agreement.

CenterFuze remains responsible for reasonable provider selection, configuration, monitoring, escalation, and recovery within its control, but provider-caused Unavailability remains excluded from the percentage calculation.

4. Service credits

If CenterFuze does not meet the availability commitment, Customer may request the following credit against the monthly recurring subscription fee for the affected Covered Service:

Monthly Uptime PercentageCredit
Below 99.99% but at least 99.9%5%
Below 99.9% but at least 99.0%10%
Below 99.0%25%

Credits in a month will not exceed 25% of the monthly recurring fee for the affected Service. If Customer pays annually, the monthly fee is one-twelfth of the annual fee allocated to the affected Service. Credits apply to a future invoice, have no cash value, are not transferable, and are Customer's sole and exclusive monetary remedy for failure to meet this SLA, except where prohibited by law or expressly changed in a signed Order Form.

5. Claims

Customer must email legal@centerfuze.com within 30 days after the end of the affected month. The claim must identify Customer, tenant, affected Service, date and time, observed impact, and relevant incident or request identifiers. CenterFuze will evaluate the claim against production monitoring and incident records and apply an approved credit within two billing cycles. Failure to submit a timely complete claim waives the credit to the extent permitted by law.

6. Scope

This SLA addresses availability only. It does not create a separate RTO, RPO, data-loss, support-response, incident-notification, or restoration commitment. An Order Form may provide different terms and will control for the identified Service.

Next step

Ready to map a clearer revenue operations path?

Choose which optional technologies CenterFuze may use. Necessary technologies cannot be disabled.

Changing choices stops future optional activity and removes CenterFuze-controlled optional storage where possible. Third parties may retain data under their own policies.