Onboarding
You said yes. Here is everything that happens next.
Seven steps, in the order the seller dashboard runs them. None of them touches your payment code, and none of them puts identity documents in our hands.
1 · Log in with your payment wallet
Open the dashboard and connect the wallet that controls your payTo address. It signs a challenge, which proves the address is yours: nothing is typed, no account is created. Then you register your resource URL and declare your segment.
2 · KYC/KYB at the issuer boundary
The accountable operator, a person and, where there is one, the company and its beneficial owners, is verified by an identity-verification provider inside the issuer’s boundary, on the provider’s own page. Raw documents never reach ZadQ: the dashboard learns the outcome and nothing else.
3 · The terms, signed with your wallet
Once you are admitted, the dashboard shows the operator terms in full, with their version and fingerprint. You acknowledge them by signing the text with the same wallet, which shows you exactly what it signs. The attestation is issued only after you do.
4 · The guarantee deposit
A positive verdict is published only while a guarantee deposit at or above the published minimum stands behind your attestation, held in escrow for claims and dispute escalation. It is never our revenue. The dashboard reads it from the verdict itself: in place, or below the minimum with the positive claim withheld. In the same step you choose your tier and set up billing on the billing provider’s hosted page; your legal name and payment details stay there.
5 · The attestation
With the terms signed, you issue the attestation from the dashboard. The issuer signs it on the MintID identity network, binding your payTo address and resource URL to a verified operator at your assurance grade. Your middleware attaches it to every 402 response; payment logic unchanged.
6 · Your first verdict, on the published cadence
A registered verifier checks the attestation and publishes its signed verdict: verified, not verified or unknown. Buyers read it for free. It is re-checked on the published cadence, and the dashboard shows when the last check ran. State, never secrets.
7 · Re-verification, before the window ends
Your identity verification is reusable for a window, and the dashboard shows when it ends. Re-verify before then: there is no grace and no extension. Done in time, the attestation keeps its reference. Missed, the attestation is suspended and the status drops to not verified by itself, until you re-verify.
What you can do from day one
- Tell your agents: your 402 already carries the invitation to the trust perimeter.
- Choose the level you offer agents: welcome today; preferred and required once v1 opens.
- Read the verdict yourself, the same way any buyer does: for free.
Selling over x402? Let's find out if we fit.
We are onboarding our first partners: API sellers, publishers, marketplaces and regulated platforms.