Payout policy

TipCLI uses Stripe Connect as the primary publisher payout path, with manual fallback reserved for operator exceptions. This page explains what can count, what is excluded, and why the dashboard never shows fake payout balances.

The launch decision is explicit: 70% maintainer / 30% TipCLI by default, $25 minimum, verified delivery first, connected-account readiness before payout, and no projected money presented as owed.

What can become payable

Only approved paid campaigns served to eligible publisher projects can create payout evidence. A sponsor preview, local SDK render, or gross delivery estimate is not a payable balance.

What counts

TipCLI uses verified impressions and verified clicks from real sponsor-card delivery events. Payout records must tie back to the project, campaign, package or rate, verified delivery totals, payout status, and review notes.

What is excluded

TipCLI excludes unpaid campaigns, unapproved campaigns, ineligible projects, disabled SDK runs, CI traffic, internal fixtures, obvious duplicate events, and traffic that cannot be reasonably verified.

When payout happens

TipCLI reviews delivery evidence, confirms sponsor payment, creates a payout record, records payout status history, and requires connected-account readiness before payout through Stripe Connect.

Payout method decision

TipCLI uses Stripe Connect recipient onboarding as the launch payout path: 70% maintainer / 30% TipCLI by default and $25 minimum. If Connect is unavailable, support will contact you about the next payout path.

No fake balances

Gross delivery value is an operational estimate from campaign terms and verified impressions. It is not a wallet balance.

Verified payable appears only after TipCLI creates or updates a payout record from verified delivery evidence. Paid payout appears only after Stripe Connect or manual-fallback payment evidence exists. If there is no eligible campaign, there is no payable delivery.

TipCLI does not claim automatic tax invoices, guaranteed conversion value, or guaranteed payout timing. Stripe Connect is the intended payout rail, but account requirements must be complete before money moves.

Dashboard payout states

Gross delivery value: Operational estimate from campaign terms and verified impressions. Not money owed.
Verified payable: A payout record exists after admin verification. It is not paid yet.
Pending payout: Verified or scheduled payout awaiting transfer, Connect readiness, or final review.
Paid payout: Payment evidence exists, preferably a Stripe Connect transfer id tied to the payout record.
Held / needs info: TipCLI needs project, delivery, billing, fraud, or payout details before moving money.
Manual fallback: Support-managed payout path used only when Stripe Connect onboarding or platform verification blocks transfer execution.

Questions or payout holds

If payout evidence looks wrong, a payout is held, or your project needs support attention, use Contact TipCLI. Include the project name, campaign if known, and the payout state shown in your dashboard.