Seller KYC API for accounts, identity checks, and trust limits

Seller KYC APIs cover seller accounts, identity checks, documents, and trust limits—the boring work that keeps marketplace payouts from becoming a support crisis. If your product lets strangers sell, you need a verification path your policy team can defend in writing to partners and auditors. ChefSphere exposes that as a module on the same prepaid token balance as commerce and wallets, so trust is not a bolted-on spreadsheet.

This guide is about seller trust workflows, not marketplace listings detail and not wallet ledger mechanics, even though all three meet at payout time. Marketplace moves goods; wallets move balances; KYC decides who may receive money and at what limits under your product policy. Keep those intents distinct when you write specs and when you forecast prepaid burn for seller onboarding weeks before launch.

Seller accounts need ownership, status, and a place for verification state that operators can reason about without tribal knowledge in Slack threads. Document collection needs clear acceptance and rejection reasons so sellers know what to fix instead of guessing forever. Trust limits should rise with successful checks—not with hope—and payouts should respect the same policy engine your compliance narrative describes.

Seller KYC submit operations sit among the heavier token weights because verification work is costly and risk-bearing compared with catalog browsing. Budget for that when every new seller triggers a submit during a launch campaign or regional expansion week. Buyer browse traffic lives on different rows of the published weight table; do not average KYC into a vague API usage line.

During early access, tell us your seller types—home cooks, restaurants, brands—and which markets you launch first so expectations stay honest. Regional identity realities differ; we align at onboarding rather than promising a universal check for every jurisdiction on day one. That honesty protects your roadmap more than a fake claim that every KYC path is identical worldwide on day one of a pilot.

Calls use Firebase-style X-API-Key authentication and burn prepaid tokens from one shared balance across marketplace, wallets, and the rest of the platform. Packs start at $29 for 200,000 tokens once access is granted; model KYC submit weight explicitly if you onboard many sellers per week. Growth and Scale packs exist when seller onboarding coincides with checkout, live, or AI traffic in the same prepaid month.

Request early access, name seller KYC and marketplace if both matter, and wait for our email when onboarding opens. Illustrative docs help you plan shapes; production contracts arrive with access so you are not integrating against fiction forever.

Decide what unauthenticated browsing can see, what a soft-verified seller can list, and what a fully verified seller can withdraw before you market payouts. Those product rules matter more than endpoint trivia and more than any illustrative OpenAPI sample in the docs hub. Encode the ladder before promising instant payouts you cannot support without chargeback and fraud exposure your team will own.

Related guides on marketplace, wallets, and prepaid tokens help finance and risk share one model instead of three conflicting spreadsheets. Request early access with a short trust policy sketch—even a paragraph beats silence when we prioritize onboarding. We respond when onboarding is ready for your seller markets and risk posture with concrete next steps.