The open-source People’s Court SDK binds published dispute terms and a payer’s explicit acceptance to an ordinary x402 payment. If a dispute follows, the integration can produce a canonical evidence packet for an authorized filing.
Public TypeScript SDK · Apache-2.0 · Package version 0.1.0
Protocol flow
The extension adds an integrity-checkable record around the transaction. It does not replace the facilitator, hold funds, or change ordinary x402 settlement.
The seller publishes the forum, Rules, claim scope, evidence expectations, filing window, and execution owner with the payment requirement.
The payer explicitly accepts those exact terms and binds the acceptance to the resource and payment.
The payment continues through the ordinary x402 verification and settlement flow. People’s Court is not the facilitator.
The integration builds a canonical packet that binds the parties, amount, terms, acceptance, and signed payment artifacts.
If a dispute arises, an authorized integrator submits the packet through the controlled Partner API path.
People’s Court applies the recorded consent and Rules, closes the Record, and serves the Award artifact required by the pinned procedure to the actual execution owner.
Verified paths
Two captured payments and refund requests opened production cases under an earlier Rules version. In each, both parties filed and an assigned human arbitrator attested to neutrality, reviewed the draft, and signed the Award. A merchant-win Award closed through x402r’s on-chain refusal. A payer-win award was satisfied by the merchant’s post-capture refund; People’s Court verified the receipt and automatically closed the case.
Both transactions succeeded and were independently observed beyond 12 confirmations. They demonstrate the settlement handoff under the historical procedure then in force. New verified agent-to-agent cases use the separately disclosed agent-only procedure with no internal human appeal and settlement immediately after the Award is served.
A dedicated payer sent 0.01 test USDC to a separate merchant through an x402 facilitator. The resulting packet passed integrity checks, the acceptance wallet signature was recovered, and altered resource, transaction, and amount bindings were rejected.
Composition
For ordinary x402, the extension preserves a dispute record around a settled payment. The merchant or platform that controls the funds remains responsible for carrying out any award.
x402r is a separate refundable-payment protocol with its own referral and execution semantics. A supported x402r integration can refer the payment record and refund request, receive a signed award, and either execute a merchant-funded post-capture refund or close a denied request through the protocol. People’s Court offers that path alongside this independent extension for ordinary x402 integrations. One path does not pretend to be the other.
The SDK is public. We provision and scope hosted Partner API credentials for each integration so authority, consent, and filing boundaries are explicit. Before we accept a filing, the integration must present a configured authority record, records of both parties’ consent, and a second confirmation of the exact filing.
Review the Rules, Terms, and Privacy Notice.