Payments

Split at the moment of settlement, not at the end of the month.

A conventional payment stack gives you an amount in an account and a reconciliation problem. Every downstream share becomes a second payment, initiated later, by a different system, against a number somebody typed.

XODIAK treats the split as part of the payment. The revenue model is registered on the network, the transaction references it, and the executor derives each leg at execution time. Nobody types a percentage into a payout run.

One transaction, many legs, atomic commit
Shares derived from a registered model, versioned and auditable
Nonce and balance verified before the block is built
Failure is total: no partial payout states to unwind

POST /tx/submit

{
  "type": "deal_settlement",
  "deal": "deal_8fa2c1",
  "gross": "50000.00",
  "currency": "USD",
  "model": "partner_waterfall_v3",
  "memo": "Q3 renewal, contract 8842"
}

// 202 Accepted
{
  "txHash": "0x9c41...",
  "status": "mempool",
  "legs": 4
}

Payouts

Five transaction types cover most of commerce.

The settlement ledger records what kind of movement each transaction was, so revenue recognition and partner reporting come out of the same rows the money moved through.

Type	What it settles	Typical trigger
attribution_credit	Credit to whoever sourced a contact or an opportunity, before any revenue exists.	A contact enters the system from a named source
deal_settlement	The full waterfall on a closed deal, across every contributing party.	Contract executed, or cash received
platform_fee	The network's own take, separated from the parties' shares.	Same transaction as the settlement
referral_payment	A flat or percentage referral obligation to a third party.	Referral condition met
escrow_hold / escrow_release	Funds held against a condition, then released or returned.	Milestone, delivery, or dispute window closing

A dark finance operations room at night with dim monitors and a city skyline beyond the glass.

Invoicing bridge

Your existing invoice becomes a settlement instruction.

Most businesses already have an invoice, a card processor and a bank. XODIAK does not ask you to replace them. The bridge takes a paid invoice as its trigger, resolves the waterfall, and settles the internal legs while the external rail does what it already did.

The result is one place that knows both what the customer paid and what each party earned, without a monthly export from three systems into a spreadsheet.

Card, ACH and wire rails stay where they are
Paid invoice triggers the internal waterfall
One ledger for external receipts and internal shares
Receipts and statements generated from settled rows

Ready to get started?

Create an account instantly, or talk to us about a settlement design for your business.

Start now Contact sales

See what you'll pay

Per-settlement pricing tied to what actually moves. No seat licences, no hidden spread.

Pricing details

Start building

Open an account, sign a transaction, read a block. About ten minutes end to end.

Integration options

Products

Solutions

Developers

Company