What you get
Pre-vetted financier pool that prices your deal on operational data, not your bank history. Comparison view of signed offers (rate, advance %, tenor, covenants), all private to you. Milestone-tied repayment that flows automatically as your TradeOS deal hits its gates. Working capital becomes a feature of the order, not a parallel workflow.
If you already run TradeOS, the listing is one step away: the order is in your Orders module, the operational signals are computed from your activity, the milestone schedule is set when you contracted the deal. The marketplace adds the matching layer; everything else is already there.
- List1Request financing from TradeOS OrdersOpen the order. Choose
Request financing. Specify advance %, tenor, currency, latest disbursement date. The signal pack attaches automatically from your TradeOS activity. Identity stays hidden.No on-chain event yet. Listing lives on the marketplace surface; you can edit terms until a financier taps Interest. - Disclose2Approve disclosure on a shortlistWithin hours to days, financiers tap Interest. You see KYB profiles, mandates, and references from other EDMA operators who funded with each. Approve a subset; identity reveals simultaneously to both sides.Disclosure receipt hashed and attestor-signed (v2).
- Compare3Read signed offers privately, pick oneApproved financiers send signed offers: rate, advance %, tenor, covenants, timeline, currency. Each offer is private to you; no financier sees what another quoted. Compare on whatever criteria matter; pick one.Acceptance signed bilaterally (v1) or as a smart-contract instance (v2).
- Fund4Buyer commits EDSD, Pre-Ship EMT mintsFinancier wires the advance. Buyer commits EDSD into the deal escrow. The Pre-Ship EMT mints; the deal enters milestone tracking. No EMT, no shipping. Your TradeOS workflow continues normally.Pre-Ship EMT mints.
edsd.commit(escrow)fires. Locked EDSD swept to T-bills, interest accrues. - Settle5Milestones release tranches, repayments auto-routeEach PASS fires
settleTrancheOnPass: routes the tranche per the signed contract (financier share, operator share, 0.5% protocol fee, 50% burn). No chasing, no invoices, no month-end reconciliation. Webhooks fire to your ERP for every release.4 EMTs mint, 4 tranches release, 4 fee burns recorded. Detail: How a deal flows.
How to list
From TradeOS Orders, open the order you want to finance. Choose Request financing. Specify the financing structure: advance percentage (how much of the order value you want funded), tenor, currency, latest disbursement date. The marketplace auto-attaches your operational signal pack (no extra work; it is already computed from your TradeOS activity).
Submit. The listing goes live to financiers whose mandate matches your corridor, value band, and signal profile. Identity stays hidden until disclosure step. You can list multiple orders at once; you can choose to list only the portion of orders you want financed (split funding); you can adjust terms before any financier has expressed interest.
How offers come back
Within hours to days (depending on corridor and value), financiers tap Interest on your listing. You see the shortlist with their KYB profiles, mandates, and references from other EDMA operators who have funded with each. You decide who gets to make an offer. Approve a subset; identity reveals simultaneously to both sides.
Approved financiers submit signed offers: rate, advance %, tenor, covenants, timeline, currency. Each offer is private to you; no financier sees another's quote. You compare on whatever criteria matter (rate, advance, financier reputation, prior relationship). Pick one. The deal moves to fund stage.
How you accept and fund
On acceptance, the deal terms are signed bilaterally (v1) or as a smart-contract instance (v2). The financier wires the agreed advance. The buyer commits the EDSD into the deal escrow; the Pre-Ship EMT mints; the deal moves to milestone tracking. From this point the rail takes over.
Your TradeOS workflow does not change. You manage production, ship, file customs, deliver, and trigger QA inspections the same way you would on any other order. The difference is that each milestone PASS releases the corresponding tranche on the rail, with repayments routed to the financier per the contract terms. Detail on what fires at each milestone: How a deal flows; detail on the rail mechanics: Settlement.
How repayments work
Each milestone PASS fires settleTrancheOnPass, which routes the tranche per the contract: a portion goes to the financier as repayment, a portion goes to the seller as net proceeds, and the protocol fee is deducted (with 50% burned in $EDM). The split is determined at funding and locked in the contract; you do not chase anyone, do not file invoices, do not reconcile at month-end.
Every release emits a Receipt v1 with PoV hash, claim_id, financial ledger, fee breakdown, and burn hash. The financier sees their repayment land in seconds (latency: PoV check + EMT mint = seconds; buyer review window = 0 to 4 hours governed). Webhooks fire: trade.milestone.passed, trade.release.posted, fee.burn.posted. Your ERP integration consumes them.
settleTrancheOnPass actually does inside the transaction. Six events fire atomically when a milestone clears the PoV Gate; the operator's repayment routing is determined at funding and locked in the contract.- 1Milestone PASS recordedAttestor evidence clears the four PoV conditions. Tranche becomes eligible for release.
proof.submit(evidence)finalises;claim_idrecorded.PoV Gate - 2
settleTrancheOnPassfiresInside the same transaction: tranche amount calculated per the funding contract, 0.5% protocol fee deducted (per-tranche cap applied if applicable).Settlement - 350% of fee burns in $EDMAtomically with settlement, half the protocol fee removes $EDM from circulating supply. Burn hash posted to the Receipt. Constitutional: cannot be reduced by governance.Burn
- 4Milestone EMT mintsThe non-transferable receipt for this milestone. Records evidence hash, attestor signatures, timestamp. The artefact downstream parties (financier, auditor, customs) read from.EMT
- 5Financier repayment + operator proceedsTranche routes per the contract: a portion to the financier as repayment, a portion to the operator as net proceeds. Split locked at funding; no chasing, no invoicing, no month-end reconciliation.Route
- 6Receipt v1 emits, integrations fireReceipt v1 emits with PoV hash,
claim_id, financial ledger, fee breakdown, burn hash. Webhooks fire to the operator's ERP and the financier's portfolio system:trade.milestone.passed,trade.release.posted,fee.burn.posted.Webhooks
Multi-financier per order
An order can be funded by multiple financiers simultaneously, with different tranches assigned to different financiers. One financier can fund the Pre-Ship + On-Board tranches; another can fund Customs + Delivered; a third can fund Arrival/QA. The marketplace orchestrates the split funding at acceptance and routes repayments to each financier as their tranches pass.
This matters for two reasons. Concentration risk: no single financier needs to underwrite the full order; smaller financiers can participate in larger deals. Pricing: different tranches carry different risk profiles (Pre-Ship is the riskiest; Arrival/QA is the safest), so they can carry different rates. The operator gets a blended cost; each financier gets a risk-priced slice.
Where it stands today
Operator-side listing launches with the Marketplace MVP in Stage 3 (Nov 2026 – Jan 2027). TradeOS Orders integration is the entry point; existing TradeOS operators get the listing surface in their familiar workflow. v1 supports single-financier per order at the menu level with multi-financier on the architecture roadmap; v2 lights up the full split funding capability.
