PAYMENT RELIABILITY,
WITH RULES
YOU CAN READ.

Commit. Observe. Resolve.

A provider registers, selects a standard SLA template, and locks USDC against a commitment. A covered SEP-31 payment carries that commitment’s reference. The Stellar ledger supplies the objective start time; a signed completion event supplies the payout time. An observer builds the evidence and identifies breaches.

A valid claim reserves its penalty from the provider’s bond. The provider has a proposed 48-hour challenge window. If there is no challenge, anyone can resolve after the deadline. Challenged claims follow the observer attestation process. The default beneficiary is the sending client.

Testnet first. One measurable promise.

V0 focuses on time to completion for inbound SEP-31 USDC payments. The launch scope is testnet USDC stake, one reference observer, and a pilot with two payment providers. V0 does not promise exchange rates, insure losses, or require penalties to reach end users.

Bank holidays and explicitly declared compliance or information holds can pause the clock. Exceptions must be auditable and visible in the provider’s record.

Make reliability queryable.

The planned explorer shows provider profiles, commitments, corridor rankings, payout latency, on-time rates, exception rates, stake, and claim outcomes. Aggregates are computed off-chain and anchored with signed batches so others can recompute them.

The proposed headline score considers punctuality, exception usage, and coverage. Providers with fewer than 100 tagged payments in 30 days show “insufficient data” rather than a score. No live provider metrics are presented on this preview.

Prove the loop before expanding it.

1. V0 — Testnet MVP. Three contracts, shared verdict logic, SDK, reference observer, indexer, API, explorer, and two pilot integrations.
2. V1 — Mainnet pilot. Independent security audit, a permissioned observer quorum, capped stake, and a wallet willing to use the reliability record.
3. V2 — Scale. More payment flows, broader observer set, richer penalties, and proposed penalty pass-through to users.
4. V3 — Open network. Permissionless observers and a more mature evidence model.

Progress is gated by evidence of adoption and safety, not fixed dates. Provider willingness to stake and wallet willingness to route on reliability are the key open questions.

A preview of the protocol.

This local website explains the design and demonstrates illustrative interactions. The contracts, observer, API, wallet connection, and pilot onboarding are not live. All interfaces and testnet parameters remain proposals.