Every national compliance programme eventually collides with the same wall: the systems asked to report on the economy are owned and operated by the participants being measured. When a switch, a fintech core, or a ledger database is the source of truth, the truth is only as durable as the incentives of whoever holds the write permission.
Onshorify's position is deliberately different. It does not sit inside the payment rail. It observes the transport beneath it.
What "out-of-band" actually means
In-line systems intercept traffic and must therefore add latency, add failure modes, and add a party that can block settlement. Out-of-band systems copy. A mirror port, a reverse-proxy hook, or an edge worker duplicates the metadata of a transaction handshake and forwards it asynchronously to an independent node. The production transaction is never held, never inspected for content, and never delayed.
The result is a second, parallel record that no participant in the transaction can edit, because it was never written into their infrastructure.
The three properties that make this defensible
- Non-rival. The observed institution keeps its systems, its vendors, and its performance envelope. Nothing is replaced.
- Non-intrusive. Only structural metadata is captured, routing coordinates, handshake frequency, tokenised references. Personally identifiable fields are stripped at the edge before the packet leaves the institution's boundary.
- Non-erasable. A rollback inside an institutional database does not travel backwards through a mirror that already left the building.
A minimal mirror hook
The mirroring surface is intentionally small. At an edge worker it is a few lines:
// Edge mirror: duplicate metadata, never the payload.
export default {
async fetch(request, env, ctx) {
const response = await fetch(request); // production path is untouched
ctx.waitUntil(
fetch(env.STIN_NODE, {
method: "POST",
headers: {
"content-type": "application/json",
"x-onshorify-signature": env.HMAC_SIGNATURE,
},
body: JSON.stringify({
ts: Date.now(),
route: new URL(request.url).pathname,
status: response.status,
corridor: request.headers.get("cf-ipcountry"),
ref: env.TOKENISER(request.headers.get("x-txn-ref")),
}),
}),
);
return response;
},
};
Nothing in that hook can slow, block, or alter settlement. That is the whole point.
Why this matters at national scale
A state that can only see what its regulated entities choose to report is negotiating with summaries. A state that holds an independent transport-layer record is negotiating with evidence. The difference is not incremental, it changes who carries the burden of proof.
Onshorify captures structure, not content. Sovereignty is achieved by holding the shape of the economy, not by reading its citizens' messages.