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: your own wallet signs and pays, ZadQ never asks for a seed or a private key, and it takes no cut out of a payment; its fees are invoiced separately. Today it covers x402 payments in USDC on Base and Solana, and its fees are priced in euros.

An accountable, identity-verified person stands behind the endpoint; the issuer's guarantee deposit is at or above the published minimum; 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.

For a vendor, it depends on the tier and the number of endpoints: the plans page lists what each tier includes and its amounts, excl. VAT. For the people who run agents, Personal and Premium are priced in your account, before VAT; from 6 agents, Enterprise is by contract.

Up to 5 agents: Premium. From 6, or agents you run for others: Enterprise, by contract — write to us and propose a time for a call.

Personal includes 1 agent; a 2nd means Premium, which holds up to 5. You can move at any time, and the unused part of your Personal plan is credited. From 6 agents, let's talk about your enterprise account.

Some services ask for grade A3, a stronger identity check. It is included in both plans when a service asks for it, at no extra cost. An A3 check lasts 6 months.

No. Prices are before VAT; VAT is added at checkout for your country, and EU businesses with a valid VAT number are reverse-charged.

Conectia OÜ (Estonia), which operates ZadQ.

Each accountable party pays for its own side. A vendor pays for the payments its attestation covered; the person who answers for an agent pays a plan that covers their agents: Personal, Premium or an Enterprise contract. Whoever reads the verdict is not a customer.

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 operator behind the endpoint is identified and answers at law; ZadQ runs no claims procedure and pays no compensation. For agents: the link between an agent and the accountable party behind it is sealed with the issuer, readable by nobody at ZadQ. The accountable principal is the recourse: the network’s dispute process runs notice and private settlement, an arbiter’s offer, and identity only under the arbiter’s certified finding. So that a claim reaches an agent that no longer answers, every agent presentation is specified to carry an encrypted reference to the agent that only its issuer and the network’s Foundation together can open, and only for a recorded claim; the verifier keeps it, unreadable, for the claim window. It is specified, not built; until it is activated every request for release is refused and recorded. Nobody in it holds anyone’s money: neither the network nor ZadQ holds, locks or moves funds.

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