The questions from integrators, platforms and lawyers.

No. A small middleware attaches the attestation header to your 402 responses; your payment logic is untouched. The client checks the issuer's signature on its own machine and pays as usual.

No. x402 processes payments without us; ZadQ is an optional layer on top. If we are unavailable, the badge reads unknown and the transaction continues under the buyer's own settings.

It never enters the flow. ZadQ holds each client's verification records encrypted; between parties nothing personal changes hands unless a dispute is escalated.

Today: credentials signed by authorised issuers, checked against published keys. Later: validity also anchored to a distributed public record. Same headers, same SDKs, same response formats.

A legally identified company, verified by ZadQ, runs the endpoint; a deposit at or above the named level is held in escrow; the attestation is current. Nothing more.

Hobby agents, low-volume endpoints, and anyone wanting controls over their own buying agents. The design assumes roughly US$300 or more of annual activity per agent, or a regulated business.

It depends on the tier and the number of endpoints; the plans page lists what each tier includes, and entry fee and annual minimum are on request. One thing never changes: you pay to be attested, never to be checked, and whoever reads the verdict pays nothing.

Per transaction, exactly one direction: the accountable party, for the work its own attestation covered. Today that is the vendor. Once agent attestation opens with v1, an attested agent pays for the payments its credential covered. The reader never pays.

No, and never as our default. Agents pay attested vendors without being attested themselves, today and always. Once v1 opens you may choose to prefer or require attested agents; that choice is yours.

The set of vendors and agents whose accountability is verified. Inside it every payment has an accountable human or organisation at both ends, and nobody reveals who. Your attestation puts your endpoints inside; reading who is inside is free to everyone.

With v1, yes: required is a level you can set in the identity policy you already attach to your 402. Welcome and preferred change nothing in the payment flow. The free verdict on your endpoint stays free to everyone regardless of the level you choose.

Today: tell us, and the attestation is suspended through the network’s status machinery; from the next status root on, verifiers read not verified. With v1 you hold your own credential and revoke it yourself, without naming it; from the next status root on it presents nowhere, including any copy taken before. Never instantly: it lands with the next root.

For a vendor’s buyers, the guarantee deposit is what a claim is made against. For agents: the link between an agent and the accountable party behind it is sealed with the issuer, readable by nobody at ZadQ. Release exists only through the network’s dispute process, which is not yet activated; until then every request is refused and recorded.