Availability and support

SET-SEC-040 · Version 1.0 · 2026-11-09

1. Current status

simpleeasytransactions.com/status checks the live services each time it is opened: the SET Wallet application, and the SET API and SET Direct Deposit API that run with it. It also shows up to 90 days of history: the share of ten-minute checks each service answered, with a missed check counted against the service.

2. How the service is built to stay up

• SET runs on Cloudflare's global network, with no single server or region of its own to fail.
• Each product has its own switch. A fault in one can be contained without taking the others down.
• Money movement does not depend on SET staying up once it is instructed. The licensed provider completes a payment it has accepted, and SET's ledger catches up from the provider's signed events, which are retried.
• A scheduled job re-checks pending deliveries every ten minutes, so a missed event is corrected without anyone acting.
• Blockchain reads fall back to a second and third endpoint when the first refuses or fails.

3. Dependencies

A payment through SET depends on SET's licensed infrastructure provider, the destination bank rail, and the blockchain the stablecoin moves on. Bank payouts follow the rail's own cut-off times and banking days. SET cannot be more available than these.

4. Service levels

SET's public terms do not carry an uptime percentage or service credits. A platform that needs them agrees them in its order form: the uptime measure, the measurement window, the exclusions, the credits, and the support hours and response times.

5. Planned changes

• The API is versioned. Each answer carries SET-Version, and a breaking change ships under a new version.
• Database changes are applied as versioned migrations; the database supports point-in-time recovery.
• Platforms under contract are told in advance of a change that needs action from them.

6. Support

Support is by email. Response times and an escalation contact are set per platform in its order form.