S⁴ DeveloperDocumentation

Integrate your platform with the financial infrastructure of the Sanaa Sanifu Economy: identity, wallet, ledger, settlement and treasury. Read the guides first; the interfaces below are a sketch, not yet a published API.

Ask about sandbox access S⁴ Architecture
Component Map
S.I. · Trusted identitySpecified
Sanaa Wallet · HoldingSpecified
Ledger · Authoritative recordSpecified
Settlement · Movement & finalitySpecified
Treasury · Monetary executionSpecified
APIs · InteroperabilitySpecified

These are the six components of S⁴. Live service status will appear here once S⁴ is in service. Nothing on this page reports a live system.

Quickstart§ 01

Four steps to participation

Proposed process

  1. Register your platform

    Obtain an S.I., trusted identity, for your organisation.

  2. Receive sandbox access

    Sandbox credentials are issued against the registered identity; production follows review.

  3. Integrate the APIs

    Verification, ledger reads, settlement and measurement data, with finality handled correctly.

  4. Enter production

    Settlement, ledger publication and SSI™ reporting apply from the first production transfer.

Guides§ 02

Integration guides

Concepts first. Each guide explains one part of S⁴ with diagrams, tables and the questions integrators ask.

Integration noteS4 for IntegratorsThe financial platform, seen from the outside.1 min readIntegration noteS.I.: Why Identity Comes FirstTrusted identity is the precondition for everything else in S4.2 min readIntegration noteThe LedgerOne authoritative record, and why there can only be one.2 min readIntegration noteSettlement and FinalityThe moment value stops moving — and why it matters most to those with least margin.2 min readIntegration noteBecoming a Participating PlatformThe integration path, in the same order as the economy itself.2 min readIntegration noteInteroperability by DesignWhat the S4 APIs are for — and what they are not for.2 min read
Reference§ 03

Interface sketch Illustrative

An illustrative sketch of the five capabilities an S⁴ interface would expose. Paths and names will change; the published API will be the authority.

Illustrative S⁴ interface sketch
MethodPath (sketch)Purpose
POST/v1/verification/claimsSubmit creative production for verification and recognition.
GET/v1/ledger/accounts/{id}Authoritative account record from the S⁴ ledger.
POST/v1/settlement/transfersMove S₵ between participants, with explicit finality.
GET/v1/ssi/gcp?period=Published GCP series with provisional and ratified states.
GET/v1/ssi/piParticipation Index and its components.
Example§ 04

A settlement transfer Illustrative

The host name uses the reserved .example domain: nothing here connects to a live service.

# initiate a transfer; the response states finality curl -X POST https://api.sanaasanifu.example/v1/settlement/transfers \ -H "Authorization: Bearer $S4_SANDBOX_KEY" \ -d '{ "source": "si_demo_1", "destination": "si_demo_2", "amount": "1250.00", "asset": "S₵" }' # → 201 Created { "status": "settled", "finality": "final" }
SDKs & Support

Planned SDK targets Not yet released

JavaScript / TypeScriptPythonJavaOpenAPI
StandardS⁴ Settlement StandardsCorpus SupportIntegration questionsContact MonetarySanaa Wallet gatewayS₵