Tokenized ABS (Receivables)
On-chain receivables securitization — Centrifuge Tinlake DROP/TIN pattern with senior/junior tranches.
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
Step 1 · Pool Formation & Originator IntentPolicy-EnforcedBlockchain-Native
The deal sponsor approaches the arranger — a supply-chain finance company decides to securitize $10M in trade receivables, just as a mortgage lender would approach an investment bank to structure an MBS deal.
The asset originator (NewSilver for real-estate bridge loans, ConsolFreight for freight invoices, Fortunafi for revenue-share receivables) proposes a new Centrifuge pool. The proposal specifies collateral type, target pool size ($10M), tranche structure (senior DROP at 4% target APY; junior TIN absorbing first losses), advance rate (80–90% of receivable face value), and maturity profile. A Delaware LLC or Cayman exempted-company SPV is formed as the bankruptcy-remote entity that legally owns the receivables; a 'true sale' legal opinion confirms the receivables are isolated from the originator's balance sheet under UCC Article 9 + Delaware LLC Act §18-101. Centrifuge pool governance (or for Maple/Goldfinch, the protocol's designated pool governance body) must approve the pool before it goes live. L5 Application only — pool creation is a governance proposal, not an on-chain operation. Builder: the pool-creation transaction should include the IPFS hash of the true-sale opinion + the pool terms PDF so any investor can cryptographically verify the governance artifact set; use a CID pin service (Pinata, Web3.Storage) with a 10-year retention commitment to outlive any individual pool's maturity. For Maple-pattern pools (active manager vs. passive wrapper), the manager's advisory agreement + fee schedule also belong in the pool's IPFS bundle. Compliance officer: satisfies C5 (SPV licensing, UCC Article 9 true sale, Delaware LLC Act §18-101 bankruptcy-remoteness, Cayman exempted-company requirements for offshore variants) and C8 (governance, operational-resilience, capital adequacy — the originator's 5% Dodd-Frank §941 risk-retention commitment must be documented at pool formation). For European originators, the EU Securitisation Regulation Article 4 (definition of securitisation) and Article 5 (transparency and due diligence) requirements fire; for EU investors buying a US pool, Article 5 extraterritorial due-diligence obligations apply. GENIUS §4 (reserve-backing) applies to any stablecoin in the subscription cash flow. Honesty marker: 'true sale' opinions are routinely issued but rarely stress-tested — the 2007 SIV collapse and 2023 SVB receivership both tested whether SPV bankruptcy-remoteness would hold under stress; the tokenized-ABS market has not yet faced a comparable stress event, and legal opinions written today rely on pre-stress-test consensus.
Step 2 · Investor Accreditation & KYBCode-EnforcedBlockchain-Native
The subscription desk — the investor proves they are qualified to buy structured credit, just as a fund administrator verifies accredited-investor status before accepting a private-placement subscription.
Tokenized ABS fall under Rule 506(c) (Reg D) or Rule 144A: accredited investors only, with mandatory verification (not self-certification) for 506(c), QIB-only for 144A. Every investor must prove net worth >$1M (excluding primary residence), income >$200K ($300K joint) for two prior years, or QIB status for senior-tranche access ($100M+ in discretionary securities). Accreditation flows through Securitize iD, which issues an on-chain identity claim registered in the pool's ERC-3643 identity registry — the same standard BlackRock BUIDL, Hashnote USYC, and Apollo's tokenized credit funds use. Once registered, the wallet can receive tranche tokens; without the credential the transfer-restriction contract reverts any incoming transfer. Gate checkpoint (hexagon). On the originator side, KYB due diligence verifies legal standing, financial health, and servicing capability — policy-enforced by the pool's compliance review. L3 Execution, L4 Account, L5 Application all lit. Builder: the ERC-3643 `canTransfer` hook re-fires on every transfer attempt, not just at subscription; an expired accreditation credential turns the token non-transferable for the holder until re-attestation. Expose `isVerified(wallet)` as a public view so pre-trade UIs can filter ineligible addresses out of the market-making book before they see a price. For cross-chain subscribers (USDC on Ethereum, pool on Base), wire CCTP v2 in a single atomic flow to avoid the multi-step burn-mint-deposit pattern. Compliance officer: satisfies C1 (accreditation identity, SEC Rule 506(c), Securities Act §4(a)(2), Rule 144A), C5 (transfer agent + placement agent licensing — the transfer agent must be SEC-registered under §17A(c), the placement agent must be registered as a broker-dealer), and C16 (programmable compliance — the ERC-3643 hook is the canonical code-enforced transfer restriction). SEC Rule 15c2-12 (disclosure on municipal securities; analogous broker-dealer disclosure for private structured credit) and Volcker Rule §13 bank-affiliate considerations apply. For EU investors, AIFMD Article 23 pre-investment disclosure and MiFID II Article 24 suitability apply. GENIUS §6 (AML/BSA) program coverage on the placement agent and transfer agent fires. Honesty marker: cross-issuer interoperability of accreditation claims is not solved — an investor verified on Securitize for a Centrifuge pool does not automatically qualify on a Maple pool that uses a different identity provider; expect parallel attestations and repeated verification during 2026–2028. The obligor-side KYC is the larger structural gap: most tokenized ABS pools rely on the originator's own AML program to vet underlying obligors (the end customers whose receivables are being securitized), which is weaker than the investor-side ERC-3643 whitelist.
Step 3 · Tranche Structure & Credit AssessmentPolicy-EnforcedBlockchain-Native
The prospectus — the arranger publishes the deal's tranche structure and the rating agency assigns credit grades, just as a CMBS deal publishes its waterfall and gets rated by S&P before roadshow.
The pool's offering documents are published, defining the tranche waterfall: Senior DROP (4% target APY, first claim on cash flows, last to absorb losses) and Junior TIN (variable yield, first-loss, originator retains ≥5% per Dodd-Frank §941 risk retention). Credit enhancement mechanisms: subordination (junior absorbs first 20% of losses), overcollateralization (pool lends only 80–90% of face value), and originator skin-in-the-game via §941. DeFi-native credit assessment via Credora and RWA.xyz; institutional-grade pools may be rated by S&P / Moody's / Fitch / Kroll. The on-chain pool contract publishes real-time NAV, advance rate, and tranche prices — transparency the TradFi securitization market has never had at this granularity. L5 Application lit only — credit assessment is a published policy artifact, not a code-enforced on-chain event. Builder: publish each rating agency letter + monthly surveillance report as an on-chain attestation (IPFS CID + agency signature) so investors can cryptographically verify the rating's authenticity rather than trusting a PDF attachment; expose `getRating(trancheId)` as a read function that returns the current rating + the IPFS CID + the effective date. For DeFi-native raters (Credora, RWA.xyz), the rating is often continuous rather than discrete — decide at pool design time whether you want NRSRO-compatible discrete letter grades or a continuous credit score, and encode the choice in the pool's rating-oracle interface. Compliance officer: satisfies C8 (operational-resilience on the rating surveillance cadence), C10 (oracle/market-data integrity — the published ratings are the canonical external signal of credit quality), and C13 (market-integrity — rating agencies themselves are subject to SEC Rule 17g-5 conflict-of-interest obligations on rated structured products). Dodd-Frank §941 risk retention is the core prudential obligation; the originator's 5% retained horizontal strip (typically equity tranche) is re-verified at each monthly surveillance cycle. Securities Act §5 registration-exemption rationale is set out in the Rule 506(c) / 144A offering memorandum. Honesty marker: NRSRO ratings on most tokenized ABS pools (Centrifuge, Maple, Goldfinch) do not exist as of April 2026 — the market is dominated by DeFi-native credit oracles (Credora, RWA.xyz) whose methodology is transparent but not NRSRO-qualified under SEC Rule 17g-7. This means institutional mandates that require NRSRO ratings (most pension funds, many insurance companies) cannot yet participate directly; the market is skewed toward family offices, crypto-native funds, and accredited individuals, which limits the ultimate depth of the pool.
Step 4 · Subscription & Waterfall TermsPolicy-EnforcedBlockchain-Native
The subscription agreement — the investor commits capital and agrees to the waterfall terms, just as an institutional buyer signs the indenture for a CLO tranche.
Investor selects tranche (senior DROP or junior TIN), commits capital, and accepts waterfall terms: minimum investment ($50K senior / $100K junior on typical Centrifuge pools), 30-day epoch lock-up (Tinlake-style; early redemption subject to liquidity), and waterfall priority rules. In TradFi the indenture trustee (BNY Mellon, US Bank, Ankura Trust) holds the master trust agreement; in tokenized ABS the waterfall logic is encoded in the pool contract — but only partially. Cash-flow priority (senior before junior) is code-enforced. Credit-event determination (when is a receivable in default? what is the recovery assumption?) remains policy-enforced by the servicer. Dodd-Frank §941 risk retention fires here as an Obligation: the originator's 5% junior position must be subscribed and locked before external investors can participate. L5 Application lit only. Builder: the subscription transaction should include the IPFS CID of the investor's signed subscription agreement + the risk-retention attestation, so an auditor can verify that each subscriber acknowledged the waterfall + risk-retention structure. For pools that want a partial-redemption option (common on Maple's investment grade pools), encode the redemption queue as a sorted priority queue on-chain with the servicer's epoch-close computation deciding how much redemption each queued request gets. Compliance officer: satisfies C8 (operational-resilience on lock-up and redemption windows), C13 (market-integrity — the placement agent's book-build under SEC Rule 17Ad-22 and FINRA Rule 5131 New Issue allocations), and C14 (consumer-protection lock-up disclosure — the offering memorandum must disclose lock-up and redemption terms per Rule 144A custom + Regulation S-K §305 where applicable). For ERISA-subject pension investors, the 25% plan-asset rule under DOL Reg §2510.3-101 plus any Prohibited Transaction Class Exemption (PTCE 84-14, QPAM) must be addressed. GENIUS §9 (custody & recordkeeping) applies to the indenture trustee. Honesty marker: the 30-day epoch lock-up is a structural liquidity constraint that most tokenized-ABS investors underestimate at subscription — in stressed markets (e.g., the 2023 Celsius collapse spillover), redemption requests have exceeded pool liquidity, and investors have faced multi-epoch redemption delays; the 'liquid DeFi yield' marketing framing does not fully reflect this during-stress reality.
Step 5 · Capital Deposit & Tranche Token MintingCode-EnforcedBlockchain-Native
The wire transfer — the investor sends capital to the pool's custody account and receives their tranche certificates in return, just as an institutional buyer wires funds to the paying agent and receives definitive notes.
Investor transfers $1M USDC to the pool investment contract on Base. The contract runs three pre-checks atomically: (1) caller on ERC-3643 whitelist, (2) amount meets tranche minimum, (3) pool cap not exceeded. Any failure reverts. At epoch settlement the contract calculates DROP token price (NAV per tranche token) per the ERC-4626 vault standard, mints the proportional tokens, and transfers to the investor's wallet. DROP tokens represent a pro-rata claim on senior-tranche cash flows, priority over junior TIN. Cross-chain investors (capital on Ethereum, pool on Base) use CCTP v2 — burn on Ethereum, mint on Base, deposit into pool — single atomic flow. L2 Consensus and L3 Execution lit; fully code-enforced. Builder: the epoch-settle function should emit a `TokensMinted(investor, tranche, amount, navPrice, epochNum)` event per mint so downstream tax-reporting + NAV-tracking systems can index by epoch; include the block.timestamp + ERC-4626 `totalAssets()` snapshot in the event payload for audit reproducibility. For institutional integrations, expose an `epochSettlePreview(epochNum)` view that returns the pending mint amount + price + pre-check pass/fail state so back-offices can reconcile before the epoch closes. Compliance officer: satisfies C1 (on-chain identity verification re-fires at mint), C6 (reserve-backing on the USDC subscription — Circle's 1:1 reserves under GENIUS §4(a) apply to the in-transit amount during the ~2s Base-finality window + the epoch-lock period), and C16 (programmable compliance — the multi-tranche mint with per-tranche whitelist enforcement is the clearest example of code-enforced capital structure). For each investor's mint, Volcker §13 and BHC Act §4(k) bank-affiliate-eligibility re-fire; for EU investors, MiCA Article 68 originator-information requirements attach to the subscription USDC transfer. Honesty marker: the atomic three-check pattern is the correct engineering approach, but several production pools as of April 2026 have an off-chain epoch-close step where the servicer computes the NAV outside the chain and submits a `finalizeEpoch(nav)` transaction — this introduces a trust assumption on the servicer's NAV computation that the on-chain-native pattern would not have; institutional investors should audit which variant a pool uses before subscribing.
Step 6 · Collateral Eligibility & Compliance BatteryCode-EnforcedBlockchain-Native
The rep-and-warranty check — the pool trustee verifies that every asset in the collateral pool meets the eligibility criteria defined in the indenture, just as a warehouse lender checks each mortgage against its purchase guidelines before funding.
Densest compliance stage. Before the pool draws on investor capital to fund receivables, two parallel screens run. Collateral eligibility (partially code-enforced): pool contract validates single-obligor concentration ≤10% of pool, weighted-average maturity bounds, per-asset maximum advance rate, and total overcollateralization ratio ≥110%. The contract enforces concentration and advance-rate ceilings automatically; delinquency assessment (is this receivable performing?) requires off-chain servicer input via a trusted oracle pattern. AML/sanctions screening: OFAC on the originator, the originator's customers (obligors), and the investors — each screened independently. Chainalysis sanctions oracle fires for on-chain addresses; obligors (who may not be on-chain, e.g., trade-receivable customers in traditional channels) flow through the originator's compliance infrastructure — policy-enforced, reported to the pool's compliance monitor via a signed attestation. L3 Execution and L4 Account lit; the on-chain half is code-enforced and the off-chain obligor screen is a policy-enforced pattern. Builder: the pool's `fund(receivableNFTId, amount)` function should require a signed obligor-compliance attestation from the servicer (an EIP-712 typed message from the servicer's known compliance-signing key) plus the on-chain checks; this gives you a cryptographic link between the off-chain OFAC/AML check and the on-chain funding event for audit reconstruction. For pools that want tighter obligor scrutiny, layer a second attestation from an independent compliance verifier (Elliptic, TRM Labs) with its own signing key. Compliance officer: satisfies C2 (sanctions screening — OFAC SDN + EU consolidated + UN 1267/1373 + HMT UK, under 31 CFR Part 501 plus jurisdictional equivalents), C3 (AML pattern detection — the originator's BSA program must cover obligor-side suspicious-activity monitoring with SAR filing to FinCEN when triggered), C8 (operational-resilience on the concentration + overcollateralization ceilings), and C16 (programmable compliance — atomic pre-trade enforcement of the eligibility ceiling is the canonical pattern for machine-enforced prudential obligations). GENIUS §6 (AML/BSA) is the US anchor; FATF Recommendation 24 on beneficial ownership applies to the obligor side. Honesty marker: the obligor-side AML gap is the structural weakness of tokenized-ABS compliance as of April 2026 — the originator's compliance program is the only line of defense against money-laundering through the underlying receivables, and regulator scrutiny of this gap is rising (FinCEN's 2025 GTOs on real-estate cash transactions have set a template that could extend to receivables). Expect obligor-level transparency + independent audit to become a standard requirement by 2027.
Step 7 · Pool Funding & Collateral AcquisitionCode-EnforcedBlockchain-Native
The warehouse advance — the pool releases funds to the originator against locked collateral, just as a warehouse lender funds a mortgage originator against pledged loan files.
The state transition — capital moves from investors to originator and collateral locks in the pool. Originator submits a financing request against a specific receivable. The pool contract executes atomically: (1) the receivable's NFT (representing the off-chain asset with on-chain metadata: face value, maturity, obligor ID, origination date) transfers into pool escrow, (2) pool releases USDC to the originator at the approved advance rate (e.g., 85% of face value). The NFT sits in the pool contract until the receivable is repaid or written off, creating an auditable on-chain collateral registry — something traditional securitization lacks (MBS collateral files sit in document custodians' vaults, not on a public ledger). The contract enforces the advance-rate ceiling: it will not release more USDC than collateral face × advance rate; over-draw attempts revert. L2 Consensus and L3 Execution lit; code-enforced. Builder: the receivable NFT's metadata should include a hash of the off-chain asset documentation (invoice, loan agreement, security interest filing) plus the custodian's signing attestation that the physical documents have been filed in the UCC-1 lien registry — this is the on-chain anchor to the off-chain legal reality. Emit a `Funded(receivableId, advanceAmount, faceValue, obligorHash, blockNum)` event for downstream reporting. For cross-jurisdictional receivables (e.g., a pool backed by both US and EU trade invoices), include the jurisdiction tag in the NFT metadata so the Step 8 reporting can split obligations correctly. Compliance officer: satisfies C8 (prudential ceiling on advance rate — a hard code-enforced limit), C11 (recordkeeping — the on-chain collateral registry plus the NFT metadata hash together form an audit-grade record that outperforms traditional MBS collateral-file custody, which has been a point of litigation in every mortgage-crisis post-mortem), and C16 (atomic NFT-for-USDC swap — the truest on-chain implementation of the 'true sale' concept). For Reg AB-II registered pools (rare for tokenized ABS as of April 2026 but growing), the Rule 17g-5 NRSRO-conflict disclosure requirements apply. Honesty marker: the NFT-based collateral registry is a strict improvement over traditional MBS's document-custodian model, but it is not a legal substitute — the enforceable right to collect on the receivable still depends on the UCC-1 perfected security interest in the off-chain legal system; the on-chain NFT is evidentiary, not dispositive. In a receiver's workout scenario, the bankruptcy-remote SPV's right to the underlying receivables depends on the paper documentation surviving scrutiny.
Step 8 · Servicing, Waterfall & ReportingPolicy-EnforcedBlockchain-Native
The monthly remittance report and distribution — the servicer collects payments from obligors, runs the waterfall, and distributes cash to tranche holders, just as a mortgage servicer collects homeowner payments, applies the waterfall, and remits to certificateholders.
Three obligations run in parallel. Servicing: the originator (as servicer) collects payments from underlying obligors and reports balance, delinquency (30/60/90 DPD), defaults, recoveries, and prepayments to the on-chain registry — but the determination 'is this receivable defaulted?' is off-chain policy under the pooling and servicing agreement (PSA). Waterfall distribution each epoch cascades: (1) servicer fees + pool expenses, (2) senior DROP interest (4% APY target), (3) senior DROP principal if redemption requested, (4) junior TIN residual (variable yield); losses flow first to TIN, only reach senior DROP if TIN is exhausted. Priority logic is code-enforced; inputs (available cash, defaulted receivables) are policy-enforced by the servicer. Regulatory reporting: Form ABS-15G (asset-level data for SEC-registered ABS), Form 10-D (distribution reports), annual audited financials. Reg D / 144A private placements have lighter regulatory reporting (investor reports, K-1 tax docs, 1099-INT for US investors) but still mandatory. The on-chain pool delivers real-time NAV + composition + delinquency transparency that traditional ABS reporting provides only monthly with a 15-day lag. Obligation checkpoint (diamond). L3 Execution, L4 Account, L5 Application all lit. Builder: publish each monthly servicer report as an on-chain attestation (IPFS CID + servicer signature); the trustee + auditor can verify authenticity without an email attachment. For tax reporting, index the waterfall distributions by investor + epoch + tranche and auto-generate 1099-INT / 1099-DIV / K-1 forms — Centrifuge's back-office already does this for its pools. Expose `getDistributionHistory(tranche, epochRange)` for tax-lot reconstruction. Compliance officer: satisfies C10 (oracle/market-data integrity — the servicer's on-chain attestation is the canonical data feed for tranche pricing), C11 (recordkeeping — the full audit bundle of servicer reports, annual audited financials, and on-chain distribution events has multi-jurisdictional retention floors: 6 years SEC, 7 years FINRA, longer for ERISA-plan investors), C12 (audit/attestation — annual audit plus the on-chain verifiable distribution events), and C13 (market-conduct disclosure — SEC Rule 17g-5 for any rated tranches, Rule 17a-4 recordkeeping for the servicer and trustee). For US-taxable investors, IRS partnership K-1s (for pools structured as partnerships) or 1099-DIVs (for corporate-structured tranches); for EU investors, AIFMD Article 22 annual report and Article 23 transparency requirements apply. GENIUS §4(b) monthly attestation applies where stablecoin is used in the distribution; §9 custody & recordkeeping applies to the trustee. Honesty marker: traditional ABS investor reporting is Intex-format PDFs plus monthly XLSX trustee reports; on-chain real-time NAV is a strict improvement, but most institutional investors still consume the PDF/XLSX as the official record because their internal portfolio systems are wired to Intex and not yet to on-chain feeds — expect parallel reporting through 2027–2028. The servicer's 'is this receivable defaulted?' determination remains the single-largest off-chain trust assumption in the system, and pool performance in a real stress event will be determined by the quality of that off-chain policy far more than by the sophistication of the on-chain waterfall code.
Resolved 8 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.
Tripartite Sanctions Screen
Tokenized ABS screens all three parties — the originator, the underlying obligors, and the investors — against OFAC + EU + UN lists. The on-chain legs fire via Chainalysis; the off-chain obligor leg runs through the originator’s BSA program.
Waterfall & OC Enforcement
Compare traditional ABS waterfall (servicer + indenture trustee policy) with Centrifuge/Maple/Goldfinch code-enforced cascade — senior DROP before junior TIN, overcollateralization ceiling, Dodd-Frank §941 5% retained strip.
The pattern: Circle USYC publishes NAV on-chain at L3 — the only fund where NAV enforcement is code-enforced. BlackRock BUIDL and Franklin Templeton FOBXX rely on off-chain fund administrators. The Generic ERC-20 wrapper column shows what institutional investors see when tokenization happens without compliance architecture: empty cells. The empty cells are the point.