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 systems store attestation metadata only. Raw KYC material lives exclusively inside the issuer-side KYC boundary and never enters ZadQ databases, logs or analytics. Between the parties nothing personal changes hands unless a dispute is escalated.

An issuer-signed attestation whose standing is read from the network's proven status root: credentials signed by authorised issuers, checked against published keys. The headers, SDKs and response formats are the ones the developer docs describe.

No. ZadQ is a verification service, and it is neutral about money: it attests who answers for a payment, not what the payment is made of. It never holds, routes or settles your payments, and it issues no asset of its own. Today it covers x402 payments in USDC on Base and Solana, and its fees are priced in euros.

A legally identified company, KYC/KYB-verified, 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 micro-agents: the segment is ≥ $300/yr economic volume plus regulated B2B counterparties. Both sides of the trust perimeter are served — vendors attest their endpoints, and agent operators enrol the agents that pay.

It depends on the tier and the number of endpoints: the plans page lists what each tier includes and its amounts — the entry fee, the minimum billed annually or monthly, and the usage rule. Reading a verdict costs nothing, ever.

Per transaction, exactly one direction: the accountable party, for the work its own attestation covered. A vendor pays for the payments its attestation covered; an attested agent’s operator pays for the payments the agent’s own credential covered. The reader never pays.

No, and never as our default. Agents pay attested vendors without being attested themselves. 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.

Yes — it is your choice. Welcome and preferred are the two levels of the identity policy you attach to your 402 response; they are invitations and change nothing in the payment flow. Required means you accept attested agents only, and you decide it on your own verifier: ZadQ never decides for a vendor.

You revoke your own credential: the kill switch stays with the holder, vendor or agent operator alike, and the revocation names neither you nor the credential; your holder stops presenting at once, and within 245 seconds of the revocation being recorded the credential presents nowhere. ZadQ never revokes it for you; it keeps the state of the revocation and nothing next to it. The way back is a new verification and a fresh credential that carries nothing of the old one.

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. The network’s funded-recourse layer, when it ships, locks a principal’s own funds in a contract the principal controls on the network where those funds live; the identity network keeps the reservation state and runs no smart contracts itself. Specified and scheduled, not built. ZadQ’s guarantee deposit is a separate, ZadQ-operated mechanism under ZadQ’s terms.

The whole posture, told apart, is on the Recourse page.