Clearing & Settlement

DTCC/NSCC T+1 Clearing

Traditional CCP clearing — NSCC as central counterparty, CNS netting, T+1 settlement.

Vendors

DTCC · NSCC · Broker-Dealers

Compliance Center

NSCC as CCP at Authorization + fail management at Facilitation

PT1 — DTCC/NSCC T+1 clearing · Rails: post-trade · Protocols: NSCC CNS, DTC · Origin: United States — Federal
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
PT1 — DTCC/NSCC T+1 CLEARINGYOU ARE HERE● Trade CapturePOLICY⬣ NSCC Novation &…CODE⬣ Margin & Risk M…CODE≡ T+1 SettlementCODE● Fail Management…POLICYIntentIdentityDiscoveryNegotiationTransportAuthorizationFacilitationFinalitySTEP 1STEP 2STEP 3STEP 4STEP 5ETHEREUMVisual system: StablecoinAtlas.com · Steps mapped to 8 STP Stages
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app

Step 1 · Trade Capture (Post-Trade Handoff)Policy-EnforcedBlockchain-Native

The trade ticket arriving at the back office — the front office (Securities rail) has already executed, now post-trade processing begins.

**Cross-rail reference: Stages 1-4 fired on the Securities Trading rail.** The trade has already been executed — identity verified, price discovered, terms negotiated. This path begins at the post-trade handoff. The trade is captured in DTCC's Trade Information Warehouse. L5 Application lit only — the handoff is a recordkeeping event. All earlier compliance gates were satisfied on the originating rail.

⚠ ENHANCED-DUE-DILIGENCE triggered at USD 50,000 — 31 CFR § 1010.312 — Enhanced Due Diligence (United States — Federal)
Counterparty
DTCC Trade Information Warehouse
Latency
Instant · trade capture
Finality
N/A — post-trade processing begins
Vendors
EOA / ERC-4337 · MetaMask / Fireblocks
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
L2 CONSENSUSValidator ordering, block productionRTGS settlement engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 2 · NSCC Novation & Netting (CNS)Code-EnforcedBlockchain-Native

The clearing house stepping between buyer and seller — NSCC becomes the buyer to every seller and the seller to every buyer. Netting reduces gross obligations by ~98%.

NSCC novates the trade: it becomes the central counterparty to both sides. CNS (Continuous Net Settlement) nets all trades per security per participant, reducing gross settlement obligations by approximately 98%. L2+L3 lit: consensus (multilateral netting) and execution (novation logic) operate below the enforcement line. D9 (prudential) is primary — NSCC's risk management framework (margin requirements, clearing fund contributions) is the systemic risk control.

Counterparty
NSCC (central counterparty)
Latency
End of trade date · batch netting
Finality
Net obligations calculated · settlement pending
Vendors
Circle CCTP v2 · Ethereum PoS Validators · Uniswap v4 · Chainalysis OFAC Oracle
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 3 · Margin & Risk ManagementCode-EnforcedBlockchain-Native

A futures exchange margin call — participants must post collateral proportional to their risk exposure, or face position liquidation.

NSCC calculates margin requirements via its NSCC Rules and VaR-based risk model. Clearing members post margin (cash, Treasuries, eligible securities) to NSCC's Clearing Fund. If a member defaults, the Clearing Fund and NSCC's loss allocation waterfall absorb losses. L3 Execution lit: margin calculations and risk monitoring are code-enforced at the CCP level. This is the compliance center of gravity — NSCC's risk framework is what makes T+1 settlement systemically safe.

Active Compliance Checkpoints
C2 OFAC SDN/SSI list screening — OFAC 50 USC § 1702 (United States — Federal) · GENIUS §6
C7 Notabene IVMS101 or Chainalysis Connect — FATF Rec. 16; 31 CFR 1010.410(f) (United States — Federal) · GENIUS §7, §8
⚠ TRAVEL-RULE triggered at USD 3,000 — 31 CFR § 1010.410(f) — Funds Transfer Recordkeeping (United States — Federal)
Counterparty
NSCC risk management
Latency
Continuous · intraday margin calls possible
Finality
Pre-condition — settlement blocked if margin insufficient
Vendors
Chainalysis OFAC Oracle · Uniswap v4 · Circle CCTP v2
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
L2 CONSENSUSValidator ordering, block productionRTGS settlement engine
L1 NETWORKP2P, finality, data availabilityMessaging rail (SWIFT / Fedwire)
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 4 · T+1 Settlement (DTC Book-Entry)Code-EnforcedBlockchain-Native

The Federal Reserve's Fedwire Securities Service — book-entry transfer of securities with simultaneous payment, but at DTCC it happens one business day after trade.

Settlement occurs T+1 via DTC's book-entry system. Securities move as book entries on DTC's ledger; cash moves through the Federal Reserve's National Settlement Service. DvP is enforced — securities and cash move simultaneously. L1+L2+L3 lit — the full stack below the enforcement line. If settlement fails (insufficient securities or cash), the fail enters NSCC's fail management process with penalty charges (SEC Rule 204).

⚠ CTR triggered at USD 10,000 — 31 CFR § 1010.311 — Currency Transaction Report (United States — Federal)
Counterparty
DTC book-entry system / Fed NSS
Latency
T+1 · next business day
Finality
Final on DTC settlement confirmation
Vendors
Circle CCTP v2 · EOA / ERC-4337 · Ethereum P2P + EIP-4844 · Ethereum PoS Validators · Uniswap v4 · Chainalysis OFAC Oracle
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app

Step 5 · Fail Management & ReportingPolicy-EnforcedBlockchain-Native

The back office's end-of-day reconciliation — fails identified, buy-in notices issued, regulatory reports filed.

Settlement is final — or a fail is recorded. Failed settlements trigger SEC Rule 204 close-out requirements (buy-in within specified timeframes). NSCC tracks fails and can force close-outs. L5 Application lit only. Regulatory reporting (FINRA TRACE, CAT) captures the full trade lifecycle. **Structural note:** the T+1 compression (from T+2, effective May 2024) reduced but did not eliminate settlement fails. The Post-Trade rail exists because finality is never guaranteed — it must be managed.

Active Compliance Checkpoints
C11 SAR/CTR filing via BSA E-Filing — 31 CFR § 1010.320 (United States — Federal) · GENIUS §9
Counterparty
NSCC fail management / SEC / FINRA
Latency
T+1 (settlement) / T+3 (fail close-out deadline)
Finality
Final if settled · managed if failed
Vendors
EOA / ERC-4337 · MetaMask / Fireblocks

Resolved 5 steps across 1 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.