SYS / DIGITAL_SETTLEMENT_NETWORK
REG / CIRO · CSA · OSFI · FINTRAC
STRUCT / HOLDCO · OPCO · CUSTODYCO
OPERATOR / KCS_CAPITAL
Canada's regulated RWA control plane

Canada's regulated control plane for tokenized real-world assets.

4orm Finance operates the regulated perimeter inside which Canadian institutions issue, trade, settle, custody, report, and supervise tokenized real-world assets. Settlement is embedded. Compliance is embedded. The blockchain is an execution surface; the regulated controls live with the platform and the institution. Built to the standards validated by the Bank of Canada's Project Samara. Operated as a separately governed regulated entity, with technology developed by KCS Capital.

$16T
Global tokenized RWA market by 2030
BCG · ADDX (cited by BoC)
$1.5T+
Settled on JPMorgan Onyx / Kinexys rails
J.P. Morgan · 2026
$1.9B/yr
Canadian RWA infrastructure TAM
4orm Master Pro Forma
$100M
BoC Project Samara tokenized bond pilot. RBC, TD, EDC
Bank of Canada · Mar 2026
What legacy cross-bank settlement costs a mid-size Canadian regional bank
~$1.42M/ year
This is the gap 4orm Finance is built to close. Trapped liquidity, correspondent fees, compliance labour, recon-break work, and KYC duplication, all on cross-bank settlement. Illustrative model, CAD · methodology in the diagram below
The Control Plane

Settlement is one capability inside the perimeter. Issuance, trading, custody coordination, regulatory reporting, and supervisory auditability are the others. They are designed to operate as a single regulated rail.

Six embedded capabilities. One regulated perimeter.

01 · ISSUANCE

EMD-governed primary issuance

Suitability, approval, and distribution authority stay with the registered dealer. The token is minted with transfer rules embedded at genesis.

PreventsMis-sold private placements. Off-ledger exception books.
Inside the architecture →
02 · TRADING

Permissioned marketplace

Eligibility checked before match. ERC-3643 transfer rules enforced by the token contract. Institutional members only.

PreventsFailed trades from non-eligible counterparties. Unsanctioned distribution.
Inside the architecture →
03 · SETTLEMENT

Atomic DvP, embedded

Asset and cash change hands at the same instant or not at all. T+0. Both legs settle inside the perimeter, on the canonical ledger.

PreventsT+2 settlement-risk windows. Manual reconciliation breaks.
Inside the architecture →
04 · CUSTODY

Qualified Canadian custody

Underlying assets held by a CIRO-aligned qualified custodian. Custody confirmation is part of the settlement finality check, not a downstream task.

PreventsCustody-confirmation delays. Multi-custodian reconciliation drift.
Inside the architecture →
05 · REPORTING

Auto-derived regulatory reporting

FINTRAC, CSA, and OSFI obligations auto-derive from the canonical ledger. The institution keeps filing authority; the source data is no longer disputed.

PreventsLate STR / LCTR / EFTR filings. Source-of-truth disagreements between desks.
Inside the architecture →
06 · SUPERVISION

Read-only supervisory feed

OSFI, CSA, FINTRAC, BoC, FSRA, and AMF can opt into a privacy-preserving aggregate feed. Never reads core banking. Institution controls what is shared.

PreventsSurprise regulator visits over data that should have been visible.
Inside the architecture →
The architectural philosophy

The regulated operational core stays inside the platform. Everything else, chains, custodians, KYC providers, interoperability frameworks, sits in bounded integration domains, all swappable behind a single abstraction. This is how the rail stays neutral and stays regulated at the same time.

What we own. What we integrate.

INTEGRATION DOMAINS · BOUNDED · SWAPPABLE CHAINS & LEDGERS Ethereum · Stellar · ... Hyperledger family · others INTEROP PROVIDERS e.g. LayerZero · CCIP e.g. Wormhole · IBC · ... QUALIFIED CUSTODY e.g. Tetra Trust · Coinbase Canada in-house HSM · multi-custodian BANKING RAILS ISO 20022 · Lynx · SWIFT ACSS · RTR CASH SETTLEMENT e.g. tokenized deposits QCAD · regulated stablecoins KYC / AML PROVIDERS e.g. Trulioo · Verified.Me PCMLTFA s.105 reliance framework IDENTITY & CREDENTIALS e.g. reusable W3C VCs institution-attested credentials 4ORM REGULATED PERIMETER What we own. Authority that cannot be delegated. 01 Canonical ledger 02 Compliance engine 03 Settlement orchestration 04 Treasury coordination 05 Issuer governance 06 Token registry 07 Supervisory auditability Ledger of record · compliance engine · settlement logic, never delegated.

The platform never yields control of the ledger of record, the compliance engine, or the settlement logic. Everything else is an adapter. That posture is how 4orm stays provider-neutral and regulator-aligned at the same time.

The end-to-end lifecycle

One regulated rail covers every state of a tokenized real-world asset, from EMD-governed primary issuance through atomic settlement, qualified custody, regulatory reporting, and final redemption. The same controls apply to every step.

One platform. The full lifecycle.

01 Issuance EMD GOVERNED Suitability check Dealer approval ERC-3643 mint Transfer rules embedded at genesis CONTROL: ISSUER GOVERNANCE 02 Trading PERMISSIONED MARKET Eligibility check before order match Institutional members only Order book + match CONTROL: COMPLIANCE GATE 03 Settlement ATOMIC DVP · T+0 Cash leg confirm Token leg confirm Custody confirm Canonical write All atomic, or none. CONTROL: SETTLEMENT ORCH. 04 Custody QUALIFIED CANADIAN CIRO-aligned trust co Attestation chain Cash + token holding Recon + exception handling CONTROL: TREASURY COORD. 05 Reporting AUTO-DERIVED FINTRAC, CSA, OSFI auto from ledger Institution files Read-only feed to supervisors CONTROL: AUDITABILITY 06 Redemption CLOSES THE LOOP Ownership verified Token burned Fiat returned via supervised rails Recon complete CONTROL: SUPPLY INTEGRITY 4ORM REGULATED CONTROL PLANE · SAME PERIMETER, EVERY STEP

Every state of a tokenized RWA, issuance, trading, settlement, custody, reporting, redemption, happens inside one regulated rail. No drop-offs to external bridges, no handoffs to unsupervised ledgers, no off-platform exception books.

The Distinction

Most tokenization firms are building tokenized assets.

4orm Finance is building the regulated rail underneath. Canadian institutions can operate tokenized finance at scale, inside the perimeter they already live in.

"
Blockchain finality is not institutional finality. Only treasury confirmation, custody confirmation, and canonical ledger commitment together complete settlement.
The 4orm settlement principle
Pillar 03 in focus · Settlement

The whole picture, three flows.

An internal transfer that never leaves your bank, an interbank settlement through the 4orm rail, and the legacy correspondent route that 4orm replaces. Each gets its own diagram, so the architecture isn't abstract.

Switch between three flows
Legacy correspondent banking flow with full nostro and vostro account detail, per-hop SWIFT fees, ACSS deferred-net batch tray, T-timeline, dual ledgers, dual FINTRAC reporting paths, and a settlement-risk window showing customer funds at risk between trade date and T+2 final settlement Top band · each bank keeps its own books and files its own reports Bank A ledger internal record of this trade tx 18420 debit Customer A C$ 5,000,000 tx 18420 credit Nostro@Corr1 pending tx 18420 confirmation: awaited from Corr1 Bank A's view of the trade. Bank A reconciles its own. manual recon 3-6% break Bank B ledger internal record of the same trade tx 92117 debit Vostro@Corr2 C$ 5,000,000 tx 92117 credit Customer B pending tx 92117 confirmation: awaited from Corr2 Bank B's view, different tx ref. Bank B reconciles its own. Independent FINTRAC reporting two parallel statutory filings, no shared view From Bank A LCTR / EFTR / STR as applicable Bank A's record only From Bank B LCTR / EFTR / STR as applicable Bank B's record only FINTRAC receives two reports about the same trade, each filed under each institution's view of the world. No single canonical record exists for the trade. Status band · settlement risk window · funds at risk until T+2 ~T+2 of exposure · trade can break, get re-keyed, or be reversed Customer A funds debit posts quickly → green Customer B funds waits until T+2 next-morning settle Cust A Bank A SWIFT 1 Corr 1 SWIFT 2 Corr 2 SWIFT 3 Bank B Cust B Middle band · the correspondent chain, every hop has a cost Customer A sender Bank A sender bank core banking fee C$0.15-0.25 SWIFT MT103 message hop 1 Correspondent bank 1 routes Bank A traffic NOSTRO account for Bank A balance: C$ prefunded internal AML + sanctions re-screen on every hop fee C$0.15-0.25 SWIFT MT103 message hop 2 Correspondent bank 2 routes Bank B traffic VOSTRO account for Bank B balance: C$ prefunded internal AML + sanctions re-screen on every hop fee C$0.15-0.25 SWIFT MT103 message hop 3 Bank B receiver bank core banking Customer B receiver Bottom band · ACSS deferred-net batch settlement + the T-timeline ACSS deferred-net batch batches finalize next morning at the Bank of Canada tx 18420 Bank A -> Corr 1 -> Corr 2 -> Bank B pending C$ 5,000,000 tx 18419 Bank A -> Corr 1 -> Corr 2 -> Bank C pending C$ 1,250,000 tx 18418 Bank D -> Corr 1 -> Corr 2 -> Bank B pending C$ 750,000 tx 18417 Bank A -> Corr 1 -> Corr 2 -> Bank E pending C$ 98,000 All in transit, all trapped until the next-morning settlement window. Settlement window timeline Trade date T+1 T+2 recon final money leaves Bank A overnight trapped overnight trapped manual break work money arrives $ 01A $ 02A REJECTED · TX 02A +1 day · -C$45 recon cost re-keyed manually, customer notified Cycle tally · what the breaks cost 1 of 9 hops rejected · -C$45 recon
What you are seeing
01
Top band

Each bank keeps its own books and files its own FINTRAC reports. Two parallel filings about the same trade. No single canonical record.

02
Status band T+2 risk window

Yellow lights show Customer A and B funds at risk during the T+2 settlement window. Customer A's light turns green quickly when their debit posts; Customer B's stays yellow until next morning. The bouncing amber coin and red BREAK badge show the 3 to 6% recon-break rate on capital-markets cross-bank trades.

03
Middle band

The correspondent chain with each intermediary's nostro / vostro account visible inside. AML re-screening happens on every hop. Each SWIFT message above the chain carries a fee.

04
Bottom band

The ACSS deferred-net batch tray with the T-timeline alongside, showing where the money actually is at each stage.

4orm replaces this whole picture with the single rail shown in the What can 4orm do? tab.
What this costs in dollars
Illustrative for a Canadian mid-size regional bank, CAD
~$520K/ yr
Trapped liquidity

~$40M average daily cross-bank flow stuck 1.5 to 2 days at 3.5% cost-of-funds.

~$340K/ yr
Correspondent fees

~1.8M annual cross-bank payments at $0.15 to $0.25 SWIFT cost per hop.

~$230K/ yr
Compliance labour tail

Manual disposition of false-positive sanctions and AML alerts at $60/hr loaded.

~$180K/ yr
3 to 6% break rate

Manual reconciliation work on cross-bank capital-markets trades at ~$120 per break.

~$150K/ yr
KYC duplication

Re-onboarding the same client at each institution across the network.

~$1.42M / year
This is the gap 4orm is built to close. Full methodology on the What It Saves page. Click the What can 4orm do? tab above to see the same flow with the rail in place.
Settlement: T+0 atomic Compliance: shared KYC + canonical sanctions Custody: licensed Canadian trust co Oversight: aggregate read-only, never reads your core Cost: zero correspondent fees on-platform
Settlement: instant, same balance sheet 4orm involvement: none Visibility: your bank only Reconciliation: none required
Settlement: T+1 to T+2 net Trapped liquidity: prefunded nostro/vostro Fees: C$0.15-0.25 per SWIFT hop Reconciliation: manual, 3-6% break rate Reporting: each bank meets its own statutory obligations independently

Key takeaways

Why legacy cross-bank settlement is slow, expensive, and risky
~T+2
Exposure window

Funds at risk for up to two days while messages relay between banks.

3-6%
Manual recon break rate

Bank A and Bank B reconcile against their own ledger independently.

2-4 hops
Per cross-bank trade

Each charges fees ($0.15 to $0.25 per MT103 message hop).

1 in 9
Hops rejected

Re-keyed manually, customer notified, ~C$45 recon cost, 1 day delay.

2 filings
Independent FINTRAC

Two parallel statutory filings, no shared view of the transaction.

0
Canonical record

No single canonical record exists for the trade across the network.

T+0
Atomic settlement

Asset and cash change hands at the same instant or not at all.

1 ledger
Single canonical record

Both banks see the same entry. No manual reconciliation breaks.

0 hops
Correspondent chain

No MT103, no per-hop fees, no rejection cycles.

In-token
Embedded compliance

KYC and AML checks live inside the token contract. Transfers enforce them.

Live
Supervisory feed

FINTRAC and regulators can opt into read-only access on the same rail.

0 changes
Bank cores untouched

Integrate via ISO 20022 / API. Control plane stays with the bank.

Instant
On-ledger transfer

Within Bank A's perimeter the token moves between accounts in seconds.

0 risk
Settlement exposure

Both sides of the transaction live inside one regulated entity.

1 record
Replaces internal recon

One shared on-ledger entry instead of two reconciled core-banking records.

1 trail
Audit log

Debit and credit are inseparable, posted atomically. One trail, not two.

Auto
FINTRAC reporting

Reporting auto-derives from the on-ledger record. No parallel filing.

Same UX
For the customer

Branch, online, ATM, mobile all see the same instant confirmation.

For Canadian institutions

This is the picture. What does it mean for your bank?

The diagram above shows what changes at the rail level. The institutional demo walks the same flow tailored to your institution's profile, so your treasurer, risk lead, and CCO can see the dollar impact, the integration shape, and the regulatory posture in their own context.

See it tailored to your institution ↗
Live institutional sandbox No signup ~15 minutes
01
How does this interoperate with our existing core, treasury, and clearing systems?
02
What does this actually save us, in dollars per year, on our specific flow profile?
03
What is the platform actually doing under the hood, and what is it not doing?
04
How does our compliance, risk, and audit team plug in without losing oversight?
05
What does the pilot look like, what does it cost, and how do we walk away if it does not fit?
Interoperability by design

Every integration boundary is an adapter, not a hard dependency. That means the rail is portable across cash assets, custodians, ledgers, KYC providers, and the institution's existing core banking systems.

How it plugs into your institution.

Cash adapter

Tokenized CAD, your choice

Bank-issued tokenized deposit OR regulated CAD stablecoin. Adapter abstracts the cash-leg provider so the institution picks the asset that fits its posture.

e.g. Stablecorp QCAD · bank-issued tokenized deposits · regulated CAD stablecoins · future CBDC integration
Ledger + chain adapters

Multi-chain by design

Canonical write to the 4orm ledger. Execution-surface portability via swappable chain adapters. The platform never yields control of the ledger of record to a chain or a bridge.

Phase 1: Ethereum · Stellar · Phase 3: omni-chain via LayerZero · CCIP · Wormhole · IBC (all swappable)
Institution adapter

ISO 20022 / API / SFTP

Connects to your existing core banking, treasury, and payments systems. No core replacement. The control plane sits beside, not on top of, what you already run.

ISO 20022 messaging · REST API · SFTP batch · webhook listeners · bank-side core integrations
Custody adapter

Qualified custodian, your choice

Use a CIRO-qualified Canadian trust company, an in-house HSM, or a multi-custodian split. The adapter handles confirmation, attestation, and recovery.

e.g. Tetra Trust · Coinbase Custody Canada · Komainu · in-house HSM · multi-custodian splits
KYC adapter

PCMLTFA s.105 reliance

Re-use existing institution-attested KYC credentials across the network under a written reliance framework. Each FI revalidates to its own risk policy.

e.g. Trulioo · Verified.Me · Persona · institution-attested credentials · per-FI risk overlay
Supervisory adapter

Read-only feeds per regulator

OSFI, CSA, FINTRAC, BoC, FSRA, and AMF each get an aggregate, privacy-preserving read-only feed. Never reads core banking. STRs filed by the institution.

Aggregate metrics · privacy-preserving aggregation · institution-led filing
The most common technical question from a partner bank's architecture team is "how does this work with what we already have?" The honest answer is: the control plane is provider-agnostic by design, and the adapter layer is part of the architecture, not an afterthought. Full adapter inventory with version pinning is in the architecture overlay.
How it fits together

One platform. Three entry points, depending on whether you want to read the thesis, walk the product, or feel what it actually does to your balance sheet.

The platform. The product. The proof.

Learn more

Five short reads on what 4orm Finance is, who it's for, why now, how we're regulated, and who's behind it.

Dig deeper.

Behind the platform

4orm Finance is operated as a separately governed regulated entity. The legal structure follows HoldCo / OpCo / CustodyCo per the CIRO Digital Asset Custody Framework. Technology is developed by KCS Capital, the independent Canadian institutional finance and research firm that builds the platform.

Visit KCS Capital ↗  ·  Meet the leadership team →

Independent technology. Independently governed regulated entity.

Institutional waitlist

4orm Finance is in pre-seed. Onboarding is institution-by-institution as the closed-loop pilots come online. Tell us who you are and we'll get back to you about the right entry point: discovery, pilot, or partner program.

Request access. Closed-loop pilots opening throughout 2026.

We respond within five business days. Pre-seed closing Q2 2026.
Thanks, your request is in. We'll be in touch from founders@kcs-capital.com.