MagicPay SLA

Service Level Information

See how measurement sources, support hours and responsibilities define service levels. No unverified uptime or response-time commitments are made.

Highlights

An approach that fits your needs

Consider business workflows, technical scope and operational requirements together.

01

Measurement

Define the components and data sources.

02

Support

Approve hours and priority definitions.

03

Boundaries

Separate external provider responsibilities.

This page is not an approved service level commitment. Availability, support hours, incident response times and remedy terms must be defined in your business's contract. Without a verified SLA text, the page remains in preparation and is excluded from indexing.

Measurement scope

Define clearly which measurements apply to gateway, reporting or notification components. The scope of bank and external provider outages needs separate treatment. Platform availability does not mean every card transaction will be approved.

Support and incident management

Document priority levels, working hours, notification channels and responsible teams. Initial response time and final resolution time are different measures.

Checks before contracting

Legal and operational owners should approve the measurement source, maintenance windows, excluded events and any service remedies. This page does not promise a specific uptime percentage or uninterrupted service.

Related solutions and resources

FAQ

Frequently asked questions

Short answers to help you assess the scope.

What uptime percentage is committed? +

No approved percentage is published on this page. The SLA applicable to your business must be defined in the contract.

Are initial response and resolution times the same? +

No. Receiving an incident, starting an investigation and resolving it are different measures and should be defined separately in the contract.