Holdback, refunds & fee-on-refund

Three questions every settlement system must answer honestly: when is a payment final, who gets made whole when work fails, and who eats the fee on refunded money. Dynamo's answers are mechanical.

Status: Preview on a core: the holdback dial, refunds and fee netting run on the verified runtime (CORE_VERIFIED=1), which is off by default.

Who decides a refund

AI inference (text, image, video or raw compute time) carries no refunds, as is the industry norm: a delivered result is final. Refunds exist only on services that developers build on Dynamo, and only where the developer chooses to offer them: the developer writes objective terms into the budget (what counts as a failure, how much is returned, by when), and the user sees and accepts them before using the service. Dynamo enforces exactly those terms and never judges or decides a refund itself; terms and verified-value settlement are Preview and off by default. Unspent budget that returns to the payer when a budget closes or a branch stops is not a refund: that money was never spent. Everything below is the mechanism a developer opts into.

Finality: the holdback window

A settlement becomes final when its holdback window closes - a per-stream dial on cores running the verified runtime (CORE_VERIFIED=1; default CORE_HOLDBACK_DEFAULT_SECONDS, 300 unless set, or, for a stream under catalogue terms, its longest term window plus 900 seconds; accepted range 0-86,400 seconds; zero is legal). On contract version 2 the holdback is also enforced on chain, at most 90 days. Until then the settled funds are reachable: refundable by rule, without anyone's cooperation. After finality, funds are the payee's - the protocol never claws back a final settlement.

Checkpoint cadence tunes the same trade-off from the other side: sparse checkpoints keep a larger unsettled buffer (payer-protective), frequent checkpoints finalize faster (payee-protective). A stream's holdback is fixed when it opens; nothing changes it mid-stream.

Refunds: buyer whole first, always

When an attested SLA break-point (or, on a stream under catalogue terms, an accepted signed breach report) creates a refund obligation:

  1. The buyer is made 100% whole first, from held funds - the unsettled

envelope and any settlements still inside their holdback window. The refund executes fail-closed against reachable funds. On contract version 2, value delivered after an attested breach of a stream's accepted terms is refunded from unmatured held value only. On contract version 1 settled value has already been paid to the payee, so the refund is pulled back from the payee's approved balance and fails closed, moving nothing, if the payee has not approved or funded it. A refund is booked only once its outside effect is done (the card refund and transfer reversal, or the chain's recorded refund). If the chain refunds less than the computed obligation, the ledger books what was refunded and the operator is alerted (settlement.failed with code refund_shortfall).

  1. Refunds attested after finality are refused at the protocol level.

Recourse moves to the payee's published terms, armed with the evidence export - the protocol does not pretend to a power it deliberately does not have.

Fees: fee finality rides unit finality

No Dynamo fee is earned before its units are final. When units are refunded:

never earned.

settled balance first, then as a negative-balance obligation against future settlements.

fee** - revenue Dynamo does not collect, capped by construction, never booked as a loss and never socialized onto the buyer.

Every fee is its own explicit ledger row tied to the settlement that produced it - accrual, reversal, and netting are each visible, auditable entries, never implicit adjustments. The session view carries them all.

Failed work is free, everywhere

The refund machinery is the last line, not the first: refused ticks, failed deliveries, and cancelled reservations are never billed at all. No cost is incurred, paid, or passed through for failed actions - the refund path exists for work that was paid for and then attested degraded, not as a substitute for failing closed up front.

Run the whole ladder - SLA terms → attested degradation → throttle → hard stop → break-point → buyer-whole-first refund → fee reversal + netting → final reconciled ledger - with make demo-sla, on every backend.