Back to legal center

Platform agreements

Service Levels and Support Policy

Proposed availability, measurement, support hours and service credits.

Download bilingual agreementsRead the legal center checklist
On this page

1. Covered services

This service level policy applies only to services expressly included in an order. It covers only antelopeintl-operated production hosted APIs and storefront services expressly included in the order; the covered service list is the one expressly identified in that order. It does not automatically cover the marketing website, beta functions or customer-operated deployments. Self-hosted support requires a separate scope and response agreement. Marketing must not portray targets as measured historical availability.

2. Monthly target and calculation

The monthly availability target is 99.9%. Availability equals eligible service minutes minus affected unavailable minutes, divided by eligible service minutes. Unavailability is determined from verifiable external probes and service records showing core read/write or checkout APIs cannot process valid requests; the probe locations, frequency and thresholds must be agreed in the applicable service order or measurement schedule. Measurement is by billing period, tenant and affected component. A reachable static homepage cannot conceal a failed transaction API.

3. Maintenance and exclusions

scheduled maintenance requires at least 72 hours’ notice and is excluded up to 120 minutes monthly; excess time counts as unavailable. Emergency-maintenance exclusions depend on cause and contract. Customer systems, unauthorized changes, customer connectivity or independent PSP failures may be excluded to the extent evidenced. Infrastructure selected by antelopeintl and antelopeintl payment-integration errors cannot be excluded wholesale as “third-party” events. Exclusions require an actual causal link to the affected interval.

4. Support severity and hours

P1 covers widespread core-transaction failure, data-isolation risk or major security incidents, with 24/7 intake for paid production plans and a one-hour first-response target. P2 is a significant degradation with a workaround and a four-business-hour target; P3 is a general issue with a two-business-day target. Support hours, timezone, holidays and plan differences are those expressly stated in the applicable plan or order; a response target applies only to the covered plan. Response means acknowledgment and investigation, not guaranteed resolution. Support: [email protected]. Security: [email protected].

5. Service credits

If formally adopted, monthly availability below 99.9% but at least 99% qualifies for a credit of 5% of the affected monthly service fee; below 99% but at least 95% qualifies for 10%; below 95% qualifies for 25%, without stacking in a month. Annual fees are divided by 12 for this purpose. Claims are sent to [email protected] within 30 days after month-end with affected times; customers need not re-prove events confirmed by Platform monitoring. Credits exclude PSP fees and do not reduce statutory compensation or remedies for material breach.

6. Incident communication and recovery

The Platform communicates major incidents, affected functions and recovery progress through the status channel agreed in the applicable order and effective contacts. Recovery must address data integrity, incomplete payment events, repeated submissions and refund reconciliation. Backup frequency, recovery point and recovery time objectives, and exercise evidence require a service-specific operational schedule; no “zero data loss” promise is made here. Personal-data breaches also invoke the DPA without waiting for a normal support ticket.

7. Repeated failure and changes

Two consecutive months below the target entitle the customer to request a written improvement plan. Three consecutive failures that materially frustrate the contract may permit termination of the affected service and a proportionate refund of unused prepaid fees under the executed agreement. Material adverse SLA changes apply only at the next renewal after advance notice, never retrospectively to paid periods. Targets and credits must match the order; targets not included in an applicable order are not a production availability guarantee.