Stablique connects banks across dollarized corridors — real-time, compliant, and blockchain-settled. Purpose-built for Africa's financial infrastructure.
Infrastructure
Stablique operates a purpose-built stack — not adapted fintech tooling — designed from the ground up for wholesale correspondent banking in dollarized economies.
A Go-native HTTP API that validates ISO 20022 payment instructions, enforces three-layer maker-checker approval, and submits net settlements to the on-chain ledger atomically.
Go · REST · ISO 20022Hyperledger Besu IBFT2 private chain provides Byzantine-fault-tolerant consensus among permissioned validators. Every settlement is immutably recorded — no reconciliation ambiguity, no disputed finality.
Besu · IBFT2 · SolidityAn autonomous Go worker continuously reconciles on-chain positions against internal ledger state. Generates ISO-structured recon reports, stores them in cloud storage, and webhooks your operations team on any break.
Go · Auto-recon · WebhooksHow it works
A deterministic four-stage pipeline — every step auditable, every approval recorded on-chain.
Your ops team submits a validated ISO 20022 payment instruction via the console or REST API. All fields are schema-checked before the pipeline begins.
A second authorised user approves the instruction at the database, API, and smart-contract level. No single actor can force a settlement unilaterally.
The settlement engine calls the Solidity ledger contract on Besu. The contract enforces participant limits, net settlement rules, and emits immutable events.
The recon engine confirms on-chain finality and marks the instruction as settled. Webhook notifications fire to your systems within seconds.
For institutions
Stablique is wholesale-only. Every design decision — from role-based access to ISO 20022 instructions — is shaped around institutional operations.
Developers
REST over HTTPS, structured error codes, JWT auth, and rate limiting out of the box. Integrate your core banking system in hours, not weeks.
// Submit a bilateral settlement instruction
const response = await fetch(
"https://api.stablique.io/v1/settlements",
{
method: "POST",
headers: {
"Authorization": `Bearer ${token}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
reference: "WIRE-2026-03-001",
debtor_participant_id: "bank_ng_uba",
creditor_participant_id: "bank_gh_gcb",
amount: "250000.00",
currency: "USD",
value_date: "2026-03-16",
}),
}
);
const { settlement_id, status } = await response.json();
// settlement_id: "stl_01jq..."
// status: "pending_approval"Security
Every layer of Stablique is designed with the assumption that financial infrastructure will be targeted. Defense in depth, from the smart contract to the API gateway.
Approval enforced independently in the Solidity contract, PostgreSQL, and Go API. Compromise of one layer cannot bypass the others.
Short-lived JWTs with PKCE-based SSO. Session tokens are never stored in localStorage — httpOnly cookies only.
Fixed-window rate limiting at 200 req/min per IP. Soft limits emit structured STABLIQUE_RATE_LIMITED errors before hard rejection.
Every instruction, approval, and settlement event is written to the Besu chain. The audit log cannot be altered after the fact.
Granular RBAC — bank_ops, bank_approver, bank_compliance, regulator_observer, super_admin. Least-privilege enforced at the data layer.
gosec, govulncheck, and ESLint security plugin run on every push. CVEs in dependencies are caught before merge.
Join the pilot network. We work directly with treasury and correspondent banking teams to onboard your institution onto the Stablique settlement rail.