Payment unlock is only one layer
x402-style flows are useful when a client needs to satisfy payment before an HTTP resource is served. That is a powerful building block for paid APIs and agent tools.
But paid agent work often has a longer lifecycle. The buyer may need acceptance criteria, verifier identity, output references, refund logic, dispute context or a settlement record that survives beyond the HTTP exchange.
Where Accord wraps the flow
Before payment, an Accord Agreement states the task, price, verifier and rail assumptions. During payment, x402 can provide the payment proof or facilitator-backed access control. After execution, Accord records the Verification Receipt and Settlement Receipt.
This keeps the x402 payment proof valuable without forcing it to carry every work-completion claim.
The composition pattern
A provider can expose a paid endpoint, require x402 payment and include an Accord agreement hash in the request context. The handler then returns or stores output evidence that the verifier can evaluate.
The final receipt bundle can reference the x402 payment identifier, the agreement hash, the verifier verdict and any rail-specific settlement proof.
Replay and mismatch risks
The dangerous failure is a valid payment proof being reused for a different task, provider, chain, rail or output. The agreement hash and domain-separated identifiers should prevent that reuse.
Providers should also reject payment proofs that do not match the expected amount, asset, seller, deadline and agreement context.
A practical mental model
x402 verifies payment. Accord verifies completion. That sentence is intentionally simple because it stops builders from treating paid access as proof of work quality.
The best implementation uses each layer for what it is good at and records the handoff between them.
FAQ
Does Accord replace x402?
No. Accord can compose with x402 by adding agreement and receipt records around the paid resource flow.
What should the x402 proof reference?
At minimum, it should be bound to the agreement, expected provider, amount, asset, rail and replay identifier.
Can Accord work without x402?
Yes. Accord is rail-agnostic and can bind to mock, Ergo, Base/EVM, x402-compatible or other payment flows.
Sources and references
Accord/402 flow
The public Accord explanation of HTTP paid-resource composition.
Accord Protocol vs x402
High-level comparison page for search and onboarding.
Settlement Receipt schema
Schema for recording payment and settlement evidence.
Read Accord vs x402
Use x402 for payment unlock and Accord for work receipts.