MERIDIAN GLOBAL FINANCE

The ESTC Codex — every settlement code range, in one place.

SWIFT runs on roughly 11 message categories, largely unchanged since the 1970s. ESTC — the Echelon Settlement & Transfer Codex — is built to replace that with 238+ blockchain-native codes, compliance embedded at the protocol level rather than checked after the fact. This page is the reference: the twelve code ranges, what each one carries, and the specific codes already in active use across the working demos on this site.

238+ codes across 12 ranges Faithful to the documented specification Targets pending independent audit Not the production network

Code ranges

The twelve ranges that structure every ESTC code, exactly as specified in the Meridian technical documentation.

These codes are compared against a retired standard

The comparisons below are against SWIFT MT message categories. SWIFT's MT/ISO 20022 coexistence period for cross-border payments ended on 22 November 2025; ISO 20022 is now the exclusive standard, and several MT types cited here have been removed entirely. The MT comparison is retained because it is how most readers still recognise these functions, but the current mapping is set out on the ISO 20022 alignment page → and that is the one to read.

RangeCategoryExample codes
100sCustomer credit transfersECH100–199
200sFinancial institution transfersECH200–299
300sFX & derivativesECH300–399
400sCollections & cash lettersECH400–499
500sSecurities & capital marketsECH500–599
600sPrecious metals & commodities (ASC)ECH600–699
700sDocumentary credits / trade financeECH700–799
800sTravellers cheques & specialECH800–899
900sCash management & reportingECH900–949
950sPriority security protocolsECH950–969
B-seriesBlockchain-native (smart contracts, tokens)ECHB001–055
AAA-seriesEchelon-exclusive (MSaaS, FEC, Noble)ECHAAA001+

Codes in detail

A working set within each range — representative, not the full enumerated 238. Several are already live on this site's other demos, cross-referenced below.

100s Customer credit transfers

Citizen-to-citizen and citizen-to-institution payments — the everyday transaction, ESTC's equivalent of SWIFT's MT1xx series.
CodePurpose
ECH100Request for transfer — instruction to execute, distinct from the transfer itself
ECH101Single customer credit transfer
ECH102Multiple / batch customer credit transfer
ECH104Direct debit / recurring mandate
ECH110Advice of cheque
ECH111Cheque stop order
ECH190Customer transfer advice

200s Financial institution transfers

Bank-to-bank movements where the institution itself is the party, not a citizen behind it — this is the range the Institutional Settlement demo runs on. Cover payments (ECH201) are the actual mechanism most cross-border transfers use today, distinct from and easy to overlook next to the payment instruction itself.
CodePurpose
ECH200Financial institution transfer for own account
ECH201Cover payment — funds an underlying customer transfer routed through a correspondent, sent separately from the payment instruction itself
ECH202General financial institution transfer
ECH205Financial institution transfer execution
ECH210Notice to receive
ECH256Advice of non-payment
ECH292Request for cancellation

300s FX & derivatives

Currency conversion and rate-linked instruments — the ECH301 code is what actually runs the GBP→ASC→USD bridge on the Institutional Settlement demo.
CodePurpose
ECH300FX confirmation
ECH301Currency→ASC→currency settlement bridge (live on the Institutional Settlement demo)
ECH305FX option confirmation
ECH320Fixed loan / deposit confirmation
ECH330Call / notice loan / deposit confirmation
ECH340Forward rate agreement confirmation
ECH360Single currency interest rate derivative confirmation

400s Collections & cash letters

Instrument-based collection instructions and their acknowledgements.
CodePurpose
ECH400Advice of payment
ECH410Acknowledgement
ECH412Advice of acceptance
ECH416Advice of non-payment / non-acceptance
ECH420Tracer
ECH430Amendment of instructions

500s Securities & capital markets

Trading, settlement, and custody of securities — the Nexus Meridian capital-markets layer's native range.
CodePurpose
ECH502Order to buy / sell
ECH503Tokenised bond issuance
ECH515Client confirmation of purchase / sale
ECH516Tokenised bond coupon / interest payment
ECH517Tokenised bond maturity / redemption
ECH535Statement of holdings
ECH540Receive-free confirmation
ECH541Receive-against-payment confirmation
ECH548Settlement status / fail advice
ECH564Corporate action notification

600s Precious metals & commodities (ASC)

Everything gold-anchored — ASC's native range, where the unit of account itself lives on the codex. ECH610 has no SWIFT equivalent at all — SWIFT has never needed to track physical metal provenance, because it never anchors a currency to allocated gold the way ASC does.
CodePurpose
ECH600Confirmation of a precious metal trade
ECH601Instruction to settle a precious metal trade
ECH604Loan / deposit precious metal confirmation
ECH605Vault movement, allocated / unallocated metal
ECH606Precious metal option
ECH609Statement of allocated metal holdings
ECH610Vault chain-of-custody / provenance attestation — ties the ASC unit of account to a specific audited, allocated bar

700s Documentary credits / trade finance

Letters of credit, guarantees, and the paperwork that underwrites physical trade.
CodePurpose
ECH700Issue of a documentary credit
ECH707Amendment to a documentary credit
ECH710Advice of a third bank's documentary credit
ECH734Advice of discrepancy / refusal — the single most common real-world documentary credit dispute
ECH742Reimbursement claim
ECH760Guarantee / standby letter of credit
ECH799Free-format trade finance message

800s Travellers cheques & special

A smaller, legacy-adjacent range kept for instrument types SWIFT still carries.
CodePurpose
ECH800Traveller's cheque advice
ECH801Traveller's cheque(s) sold notification
ECH890Advice of loss or damage

900s Cash management & reporting

Statements, balances, and the ongoing account-reporting messages behind every current account — this is what powers the balance figures on the Beit banking app.
CodePurpose
ECH900Confirmation of debit
ECH910Confirmation of credit
ECH920Request message
ECH935Rate change advice (the live gold-price update shown across every demo)
ECH940Customer statement message
ECH941Balance report
ECH942Interim transaction report

950s Priority security protocols

Fraud, compliance escalation, and court-order enforcement — this range is what the freezing-order mechanism on the Institutional Settlement demo actually runs on.
CodePurpose
ECH950Priority freeze order (live — see Institutional Settlement)
ECH951Freeze order extension
ECH952Freeze order auto-expiry / lapse
ECH953Post-settlement reversal / clawback, court-order authorised — recovers funds that already moved, distinct from a freeze which only blocks future outbound
ECH955Priority KYC/AML escalation
ECH960Sanctions list match alert
ECH965Law-enforcement evidence request
ECH969Emergency network-wide suspension

B-series Blockchain-native

Smart-contract and token operations with no SWIFT analogue at all — this range is where the mint-and-burn ASC settlement tokens actually live. ECHB040 is arguably the single biggest "beyond SWIFT" code on this whole page: SWIFT's own comparison table above says partial settlement failure is "possible; needs reconciliation" — this code is the proof that didn't happen.
CodePurpose
ECHB001Smart contract deployment
ECHB010Settlement token mint (live — see Institutional Settlement)
ECHB011Settlement token burn on arrival (live — see Institutional Settlement)
ECHB020Multi-signature authorisation
ECHB030Atomic swap
ECHB040Settlement finality / atomicity confirmation — proof a transfer could not have partially failed
ECHB050Chain-of-custody attestation
ECHB060Real estate tokenisation / title transfer — registers via a CAM marker
ECHB055Cross-network bridge / interoperability, for settlement outside the Echelon Chain itself

AAA-series Echelon-exclusive

Sovereign and system-level operations with no counterpart in any legacy messaging standard — MSaaS, PAM lifecycle events, Noble reference-price updates, and insurance all live here. Insurance in particular has no SWIFT equivalent whatsoever — it's never been a SWIFT-messaging vertical, so this isn't a gap being filled so much as a market SWIFT never addressed.
CodePurpose
ECHAAA001MSaaS national currency issuance instruction
ECHAAA002Noble (ASC) reference-price update (live across every demo on this site)
ECHAAA010Sovereign Debt Token (SDT) restructuring instruction
ECHAAA015Recurring payment / standing instruction mandate — a gap in SWIFT itself, which has no clean dedicated message for this
ECHAAA020PAM lifecycle event — open / contribute / draw / transfer (live — see Multi-citizen demo)
ECHAAA030CAM / SAM marker registration
ECHAAA040Insurance premium payment — SWIFT has no messaging standard for this at all; insurance runs on ACORD, not MT
ECHAAA041Insurance claim payout

Settlement performance (targets)

How quickly a transfer is expected to finalise, by how far apart the two ends are — pending independent audit.
ScenarioTarget timeExamples
Same jurisdiction~15 secondsUK–UK, UAE–UAE
Same regional bloc~15 min – 1 hrEU–EU, GCC–GCC
Cross-regional~1 – 4 hrUK–UAE, EU–Dubai
Intercontinental~4 – 6 hrUK–Brazil, Singapore–US
Physical metal settlementT+1 to T+3Vault-to-vault, auditable

ESTC vs SWIFT

Comparative figures for legacy messaging are broad characterisations, not precise audited statistics.
FeatureSWIFT (legacy)ESTC (target)
Built forMessaging era (1973)Blockchain settlement (2026)
Codes~11 message categories238+ blockchain-native codes
SettlementOften T+2 to T+515 sec to 6 hr by jurisdiction (target)
AML / KYCLargely post-hoc / manualEmbedded at protocol level
SecurityTLS (classical)Standardised post-quantum cryptography
Partial failurePossible; needs reconciliationRemoved at settlement layer by atomic finality
CostPer-message fees~0.05% flat velocity fee (target)
Asset classesLargely fiatFiat, metals, tokenised assets

ASC integration

ESTC codes are native to the ASC monetary system, not bolted on.

The 600-series handles ASC precious-metal transactions directly. The B-series handles tokenised operations — including the mint-on-send, burn-on-arrival settlement tokens used on the Institutional Settlement demo. The AAA-series handles MSaaS and sovereign operations, including PAM lifecycle events and the Noble reference-price updates that every demo on this site pulls from the live gold price. Each code carries a reference conversion value for cross-metal accounting, with settlement targeted at 15 seconds to 6 hours by jurisdiction.

What this page is, and isn't

What's real here

The twelve range categories, the 238+ total, the five-tier settlement performance targets, and the ESTC-vs-SWIFT comparison are all taken directly from Meridian's own technical documentation, not invented for this page. Several specific codes shown are already genuinely operating on this site's live demos — the currency bridge, the mint/burn settlement tokens, the freeze-order mechanism, the PAM lifecycle, and the live gold-price update are all real, working mechanics you can go test right now, each one clearly marked above with which demo it runs on. Every range was checked against real SWIFT MT message categories for gaps — cover payments, discrepancy notices, and settlement-fail advices were genuinely missing on an earlier pass and have been added; a few codes with no SWIFT equivalent at all (gold provenance, atomicity confirmation) are marked as such rather than implied to be industry-standard. Bonds, insurance, and real estate tokenisation were reviewed against a two-year-old draft codex and selectively incorporated in the existing range format — a separate proposed 4–5 letter scheme and its rune-conversion layer from that same draft were deliberately left out, since neither matches what's actually live on this site.

What's simulated

The specific codes listed within each range are a representative working set, not the full enumerated list of 238+ — the source documentation specifies the ranges and the total precisely, not every individual code's exact definition, so what's shown here is illustrative and consistent with that structure rather than a claim of completeness. Throughput, settlement-time, and reliability figures are stated as engineering targets pending independent audit, exactly as the source documentation itself states — not benchmarks already achieved. No message on this page has actually travelled a real network; this is a reference table, not a live transaction log.