The shortest distinction
x402 verifies payment. Accord verifies completion.
That sentence is the cleanest way to separate the two. x402 gives HTTP services a standard way to request payment for a resource. Accord gives agents a standard way to record the work terms and the result of that work.
Where x402 stops
A paid HTTP response can prove that a buyer satisfied a payment challenge, but it does not by itself define the acceptance criteria for a complex task. If the task is a repository audit, model evaluation, data transformation or multi-step research job, the buyer still needs a record of what was promised and how the output was judged.
This is where Accord sits. It can reference payment authority or payment proof while keeping the agreement and receipts explicit.
How they work together
In an Accord/402 flow, the HTTP payment step is one part of a broader lifecycle. The Agreement Object defines the task. The payment proof or authority references that agreement. The executor performs the work. A verifier signs a Verification Receipt. A Settlement Receipt records the closeout on the chosen rail.
This composition lets developers keep x402 for what it does well while adding machine-readable completion semantics.
FAQ
Does Accord replace x402?
No. Accord can use x402-compatible payment flows as one rail or transport component.
Can x402 prove work quality?
Not by itself. Work quality depends on agreement terms, verifier design and receipt policy.
Read the Accord/402 flow
See how x402 payment proof composes with Accord completion records.