Sellers

Merchant-facing: register or match a seller after the MERCHANT has verified them. See docs/business/glossary.md "Identity federation" — sellers never call this directly.

Merchant-facing: create a headless Seller (Phase 27) — a trade participant with no linked TBBN account, gated by the calling Merchant's plan tier.

Register a Merchant's account-linking OAuth client (Phase 28)

List a Merchant's OAuth clients

Rotate an OAuth client's secret — the clientId is unchanged

Revoke an OAuth client

Public client metadata — used by apps/account-dashboard's consent screen to validate redirect_uri and render "Merchant X wants to link your TBBN profile" before showing Approve/Deny.

Step 1 of the OAuth account-linking handshake (Phase 28) — the logged-in member approves. Creates a short-lived, single-use authorization code; the caller (the consent page) performs the actual redirect.

Step 2 of the OAuth account-linking handshake — the Merchant's backend exchanges the code for a link. No access/refresh token is issued; this only ever establishes a seller_merchant_links row. See docs/business/conflict-resolution-log.md item 22.

Resolve a marketplace member with all linked merchant accounts (internal/ops use)

Ops-only unlink of a merchant link (fraud/dispute remediation)