Settlement and delivery

An order can finish matching while settlement is still in progress. External delivery, when applicable, adds another independent track.

APIAcknowledgedA request was accepted
ORDERFilledMatching completed
CHAINSettledFinality observed
DELIVERYPaidIf external delivery applies

Independent observations. Success on one track does not establish success on the next.

Acknowledged#

An HTTP acceptance confirms processing was acknowledged. It is not proof of a fill, spendable output or final settlement.

Filled#

A fill records matched execution with exact quantities and fees. A cancelled remainder does not erase earlier fills. Preserve each fill and its settlement-operation reference.

Settled#

Ledger effects, settlement inclusion and finalization must be observed separately. Provisional output is not proof of finality. Do not derive a settlement deadline or SLA from a quote timestamp.

Delivered#

A withdrawal may be requested, included, finalized, claimable, claim-submitted or paid. Claim issuance and root import are not token delivery. A claim requires an explicit payment transaction.

Supported withdrawal chains and custody routes must be established by the released environment contract. Arbitrary destination-chain support and bank-payout services are not specified.

Reconciliation checklist#

Retain account, exact asset, order, fill, operation and movement identities.
Record accepted economic terms and fee denominations.
Distinguish order state from ledger and settlement state.
Preserve a completed conversion if a later movement fails.
Reconcile any external delivery independently.

See orders and fills, funding and balances and recovery.