XODIAK / Solutions
Solutions
Nine shapes of the same problem: value arrives once, and several parties have a claim on it.
Platforms
You take one payment from a buyer and owe money to a seller, a service provider, a referrer and yourself. Doing that as four payments in three systems is where reconciliation cost comes from. Do it as one transaction with four legs.
- Single inbound, many outbound legs
- Seller balances visible without a nightly job
- Platform fee separated from party shares in the ledger
{
"model": "platforms_waterfall_v1",
"legs": 4,
"atomic": true
}
Marketplaces
Marketplace economics live and die on take rate transparency. When the split is derived from a registered model rather than typed into a payout tool, sellers can verify their own statements without asking you to open your books.
- Take rate expressed as a model, versioned
- Seller-verifiable statements
- Disputes resolved against signed records
{
"model": "marketplaces_waterfall_v1",
"legs": 4,
"atomic": true
}
Agencies and service firms
Referral fees, revenue shares and pass-through costs are the standard shape of agency work and the standard source of partner friction. Register the terms once and let settlement read them.
- Referral terms that pay themselves
- Sub-agency and nested obligations resolved in one pass
- Pass-through costs kept distinct from margin
{
"model": "agencies_waterfall_v1",
"legs": 4,
"atomic": true
}
Energy and infrastructure
Project cash waterfalls involve a sponsor, lenders, an operator, a landowner and often a public authority, over decades. The parties change; the waterfall does not. Encode it once and let the record survive the personnel.
- Long-lived waterfalls with versioned amendments
- Milestone-conditioned escrow releases
- Reserve attestation for asset-backed instruments
{
"model": "infrastructure_waterfall_v1",
"legs": 4,
"atomic": true
}
AI agents and autonomous commerce
Software that spends money needs two things a human does not: a hard limit it cannot exceed, and a record of every decision it made. Both are protocol features here rather than application policy.
- Per-agent spend authority enforced at the executor
- Every agent action attributable to the agent
- Machine-readable receipts for machine-initiated spend
{
"model": "agents_waterfall_v1",
"legs": 4,
"atomic": true
}
Real-world assets
Registration, attestation and income settlement for 24 asset classes on one network, so the token and the cash it produces are not tracked in two different systems.
- Attested reserves weighted into consensus
- Income settles through the same waterfall engine
- Transfer restrictions tied to verification tier
{
"model": "rwa_waterfall_v1",
"legs": 4,
"atomic": true
}
Public sector
Grants, benefits and contract disbursements share a requirement that commercial payments usually do not: the public has standing to ask what happened. A hash-linked record answers that without opening the underlying case file.
- Disbursement records that are publicly verifiable
- Conditions of award recorded with the award
- Entity registry separate from natural persons
{
"model": "government_waterfall_v1",
"legs": 4,
"atomic": true
}
Media, music and IP
A royalty arrives as one number and belongs to a list of people. Splitting it correctly at the moment it lands is a smaller problem than splitting it correctly nine months later.
- Master and publishing splits as a registered model
- Rights holder statements generated from settled rows
- Licence terms recorded alongside the commercial split
{
"model": "media_waterfall_v1",
"legs": 4,
"atomic": true
}
Professional services
Retainers, milestone fees and reimbursable costs on one ledger, with the client's view and the firm's view derived from the same transactions rather than reconciled against each other.
- Retainer draw-down visible to both sides
- Milestone releases conditioned, not invoiced by hand
- Reimbursables separated from fee income
{
"model": "services_waterfall_v1",
"legs": 4,
"atomic": true
}
Enterprises
Internal transfer pricing between business units has the same shape as an external waterfall, with the added problem that nobody outside finance believes the numbers. A signed ledger the units can each read moves that argument.
- Inter-unit settlement on one ledger
- Model changes versioned and attributable
- Audit path from a unit's P&L back to individual transactions
{
"model": "enterprise_waterfall_v1",
"legs": 4,
"atomic": true
}
Ready to get started?
Create an account instantly, or talk to us about a settlement design for your business.
See what you'll pay
Per-settlement pricing tied to what actually moves. No seat licences, no hidden spread.
Pricing detailsStart building
Open an account, sign a transaction, read a block. About ten minutes end to end.
Integration options