Skip to main content
In the delivery protection model, the arbiter evaluates every transaction. The arbiter or a satisfied payer can capture funds. If the arbiter issues a FAIL verdict, it can trigger an immediate refund without waiting for escrow expiry. If nobody acts, funds return to the payer once escrow expires. This differs from the marketplace model where the merchant releases funds and the arbiter only gets involved when a payer files a dispute.
MarketplaceDelivery Protection
Who releases fundsMerchant (after escrow)Arbiter or payer
Refund during escrowReceiver or arbiterEscrow expiry, receiver, or arbiter
Dispute processPayer files refund requestNo disputes needed
Arbiter involvementOnly on disputesEvery transaction
Contracts deployed~8 (Operator, EscrowPeriod, RefundRequest, Evidence, Freeze, etc.)6 (Operator, EscrowPeriod, SAC, 2x OrCondition, HookCombinator)
Deploy presetdeployMarketplaceOperator()deployDeliveryProtectionOperator()
Use this when every response needs programmatic quality checks: AI content verification, garbage detection, schema validation.

Merchant Setup

Deploy the operator and configure forwardToArbiter().

Arbiter Setup

Build the service that evaluates responses and releases funds.