Skip to main content

Prerequisites

1

Install dependencies

2

Configure forwardToArbiter()

Add the forwardToArbiter() hook to your x402 resource server. After every successful auth-capture settlement, it POSTs to your arbiter service fire-and-forget:
The hook POSTs to {arbiterUrl}/verify with:
The helper reconstructs PaymentInfoWire from the verified SettleResultContext. The arbiter consumes req.body.paymentInfoWire and runs it through PaymentInfo.fromWire(...) to recover the bigint-typed struct expected by SDK actions. See forwardToArbiter() docs for the full payload shape.
forwardToArbiter() is fire-and-forget. If the arbiter service is unreachable, funds stay in escrow until timeout. Add monitoring for arbiter availability.
3

Share addresses with the arbiter

The arbiter service needs operatorAddress and escrowPeriodAddress from your deployment to construct its SDK client. Share these via config, environment variables, or a shared registry.

Next Steps

Arbiter Setup

Build the service that evaluates responses and releases funds.

Deploy Operator

Full deployment config and condition slot details.