Service Level Agreement

Reliability you can build on.

Version 1.0 · Effective 19 June 2026

These are AsterPay's standard service-level objectives (SLOs). Contractual SLAs with financial service credits are available as part of an enterprise agreement. Free read endpoints and pay-per-call usage are provided on a best-effort basis under these same targets, without credits. To discuss an enterprise SLA, contact [email protected].

1. API availability

Target monthly availability for the production API (api.asterpay.io / x402.asterpay.io):

Tier	Monthly availability target	Max downtime / month
Enterprise (contracted)	99.9%	~43 minutes
Standard / pay-per-call	99.5% target (best-effort)	~3.6 hours

Availability is measured against the GET /health endpoint, excluding scheduled maintenance and the exclusions in section 6. Live component status is on the status page.

2. EUR settlement timing

Once a payment is confirmed and the recipient passes compliance checks, settlement is initiated over SEPA Instant.

Metric	Target
SEPA Instant settlement (typical)	Funds in beneficiary account in seconds (often <10s)
Settlement initiation after confirmation	< 60 seconds
Fallback (beneficiary bank not SEPA-Instant reachable)	Standard SEPA, next business day

Settlement is executed through licensed EU partner rails. Timing depends on the beneficiary bank's reachability and is outside AsterPay's direct control once funds leave the partner; the targets above describe the AsterPay-controlled portion.

3. Support response times

Severity	Description	Target first response
Sev 1 — Critical	Production API down or settlement halted; no workaround.	1 hour (24/7, enterprise)
Sev 2 — High	Major feature degraded or partial outage; workaround exists.	4 business hours
Sev 3 — Normal	Minor issue, question, or non-blocking bug.	1 business day

Enterprise support: [email protected]. General: [email protected]. Security: [email protected].

4. Incident communication

During a Sev 1 or Sev 2 incident we post and update status on the status page and notify contracted enterprise customers directly. A root-cause summary is shared after Sev 1 resolution.

5. Scheduled maintenance

Maintenance that may cause downtime is announced at least 48 hours in advance where practical and scheduled in low-traffic windows. Maintenance windows do not count against availability targets.

6. Exclusions

Factors outside AsterPay's control: upstream chain congestion or reorgs, beneficiary bank availability, third-party facilitators (Coinbase CDP), DNS/CDN provider incidents, and force majeure.
Misuse, traffic exceeding published rate limits, or use that violates the Terms.
Beta/preview features and endpoints explicitly marked as such.

7. Service credits

For contracted enterprise customers, if monthly availability falls below the committed target, service credits apply per the terms of the signed agreement. Credits are the exclusive remedy for missed availability targets and must be requested within 30 days.