links.arjun.tv/docs/end-user/use-cases/uc-13-creator-connect-earnings

UC-13: Creator Connect and Earnings

Role-gated control-plane steps are intentionally excluded from this public guide; use support escalation when those operations are required. Shared company context: Gharart.com Company Context Need operator help? Escalate through Troubleshooting and Support with request IDs and repro artifacts.

Developer Outcome

Ship creator connect and earnings for Gharart.com with reproducible API steps, operational limits, and clear debugging playbooks.

Prerequisites

  • A valid handle and environment access for Gharart.com.
  • JWT and/or PAT credentials with required scope for this use case.
  • Access to logs, support escalation endpoints, and test workspace.

Gharart Scenario

Marketplace creator payout onboarding.

Persona: Partnership operations manager

Business goal: Onboard storefront collaborators to Stripe Connect and reconcile earnings with billing state.

Step-by-Step Flow (UI + API)

  1. Open the relevant Gharart workflow in the dashboard and confirm actor role access.
  2. Execute route calls in sequence for this use case and capture response IDs.
  3. Validate expected state in UI and API after each step before moving forward.
  4. Record artifacts (request ID, run ID, deployment ID, slug, or token) for support handoff.

Primary API Routes

MethodPath
GET/v2/billing/summary
GET/v2/handles/{handle}/connect/status
GET/v2/handles/{handle}/earnings
GET/v2/platform-admin/creator-economy
POST/v2/billing/checkout-session
POST/v2/billing/manual-plan
POST/v2/billing/portal-session
POST/v2/handles/{handle}/connect/dashboard-link
POST/v2/handles/{handle}/connect/onboarding
POST/v2/public/stripe/connect-webhook
POST/v2/public/stripe/webhook

Limits and Quotas

  • Respect per-route throttles and daily write limits before bulk operations.
  • Use idempotency-safe retries for write endpoints to avoid duplicate business actions.
  • Schedule high-volume workflows outside peak campaign windows where possible.

Where This Breaks

  • connect status stuck in onboarding due incomplete KYC
  • webhook signature mismatch blocking payout events
  • billing plan mismatch hiding creator economy controls

How Gharart Debugs It

  1. Check connect/status response for onboarding blockers
  2. Verify webhook secret and signature header parity
  3. Compare earnings endpoint output with billing summary

Escalation

Use end-user escalation path:

  • Submit POST /v2/support/report.
  • Include summary, details, and when available handle, sessionId, requestId, reproArtifact.

Audience boundaries:

  • POST /v2/operator/escalations is an internal operator workflow and not an end-user escalation action.
  • POST /v2/public/content-report is for public abuse moderation reports, not product incident escalation.