Reviewed October 17, 2026. This operational guide replaces an earlier general overview. The original publication date and URL are retained.
An embedded platform’s uptime percentage means little without the measurement boundary. Compare the promised service, excluded events and response clock with the business process that actually needs to work.
Ask what is being measured
NIST’s glossary describes a service-level agreement as covering specific service commitments, responsibilities, performance and related reporting or resolution requirements. For an embedded payment product, identify whether an availability figure covers the application screen, payment API, capture submission or another defined component. Do not assume it covers the full route from a customer’s action to usable bank funds.
Compare two clocks in one incident
In an illustrative interruption, a support ticket is acknowledged in ten minutes but payment capture resumes after three hours. A ten-minute response commitment and a three-hour restoration outcome answer different questions. Record detection, acknowledgment, workaround and restoration separately. Ask when each clock starts, which hours count and whether the customer must submit a ticket through a particular route.
Translate a percentage into an operating question
A hypothetical 99.9% monthly availability commitment over 30 days corresponds arithmetically to 43.2 minutes outside availability if every minute counts equally: 43,200 minutes multiplied by 0.1%. An actual agreement may define the denominator and exclusions differently. Obtain its calculation rather than treating the arithmetic as a promise. Forty minutes during a peak sales period can have a different business effect from forty minutes overnight.
Separate service credits from continuity planning
Read the remedy, claim deadline, reporting evidence and limits in the actual agreement with appropriate professional review. A credit against a future software bill should not be assumed to reimburse lost sales, payroll or every downstream consequence. Design an approved operating fallback even when the vendor offers a service commitment. The completed comparison should name the measured component, each clock, excluded conditions and the business owner for an interruption.
Sources and next steps
Primary reference: NIST’s service-level agreement definition. Examples are illustrative analysis, not client results or provider quotes.
Continue with the embedded-payment incident ownership guide and the AMS New York merchant reading path.
Use the merchant technology decision worksheet to document the expected output, responsible person and acceptance evidence.
