The basic flow
A service can challenge a client for payment before serving a resource. Accord/402 keeps that payment step, but adds a work agreement around it. The client and service can bind the request to a canonical Agreement Object before execution.
After the work is performed, a verifier emits a Verification Receipt and the rail or facilitator evidence is recorded in a Settlement Receipt.
Why this is different from access
Access control answers whether a request can proceed. Work verification answers whether the output satisfied the agreement. Those are different questions, and conflating them creates weak audit trails.
Accord/402 lets HTTP services keep simple paid-resource mechanics while making completion explicit.
Safe implementation posture
Developers should start with mock or testnet flows, log agreement hashes, verify replay protection and document facilitator assumptions. Real-value production flows require signed audit manifests and operational controls.
The current public Accord posture remains testnet-first and not certified for mainnet.
FAQ
Is Accord/402 the same as x402?
No. Accord/402 can use x402-compatible payment proof, but adds agreement and completion semantics.
Should I start with real payments?
No. Start with local or testnet architecture demos.
Read the Accord/402 spec
Map payment proof to agreement and receipt records.