sales-marketplace-payouts

What this skill does

# Marketplace Payouts Strategy

This skill is tool-agnostic. It covers how to pick and operate the payout-side payment infrastructure for a two-sided marketplace — Stripe Connect, Hyperwallet, Adyen for Platforms, Trolley, Tipalti, Routable, dots.dev, Branch, and others.

## Step 1 — Gather context

If `references/learnings.md` exists, read it first.

1. **Where are you in the marketplace?**
   - A) Pre-launch / first 10 payouts — manual is still ok
   - B) Small scale (10-200 workers, US-only) — picking your first payout API
   - C) Scaling (200-5K workers, possibly multi-state) — picking the system that grows
   - D) Multi-country (any non-US recipients) — multi-currency is now table stakes
   - E) Already on a payout API and considering switching

2. **What's the worker relationship?**
   - 1099 contractor / gig worker (most marketplaces)
   - W-2 employee (Bluecrew-style)
   - Mixed
   - Outside-US recipients (different tax + currency rules)

3. **What's the payout cadence the supply side expects?**
   - Daily / on-demand (gig economy default)
   - Weekly
   - Bi-weekly / monthly (rarer for marketplaces)

4. **What's the marketplace vertical?** (cleaning, courier, food delivery, home services, pet care, creator/seller marketplace, multi-vertical) — drives which platforms fit.

Skip-ahead rule: if the user's prompt already has these details, skip to Step 2.

## Step 2 — Route or answer directly

| If the question is about... | Route to... |
|---|---|
| Buyer-side checkout, cart abandonment, payment collection | `/sales-checkout [question]` |
| Affiliate commissions tracking (NOT marketplace worker payouts) | `/sales-affiliate-program [question]` |
| The marketplace GTM strategy layer (cold-start, supply recruiting) | `/sales-two-sided-marketplace [question]` |
| Door-to-door / field outbound for marketplace demand | `/sales-field-sales [question]` |
| Hourly worker hiring + onboarding (not payouts) | `/sales-two-sided-marketplace [question]` for Workstream coverage |
| Tax filing deep-dive (not selection) | No skill yet — flag as a gap |
| W-2 payroll (not marketplace 1099 payouts) | No skill yet — outside scope |

If the question is genuinely about marketplace payout infrastructure selection or operation, continue to Step 3.

## Step 3 — Payout platform reference

**Read `references/platforms.md`** for per-platform notes on Stripe Connect (Standard / Express / Custom), PayPal Hyperwallet, Adyen for Platforms, Trolley, Tipalti, Routable, dots.dev, Branch, Nium, Wise Business, and Tremendous. Each entry covers what it's best for, marketplace stage fit, fee structure, KYC/onboarding flow, multi-currency reach, 1099-K/1099-NEC handling, and the embedded vs custom UX trade-off.

Answer using only the relevant sections. Don't dump the full file.

## Step 4 — Actionable guidance

The payouts decision has four pillars. Work them in order.

### 4.1 Selection criteria

Pick the platform based on **the dimension that will break first** if you pick wrong:

| Dimension | When it dominates the choice |
|---|---|
| **Onboarding burden** (KYC docs, identity verification, payout-method setup) | If supply churns at the onboarding step. Stripe Express / dots.dev minimize this. |
| **Payout speed** (daily / on-demand vs weekly) | If competing on supply recruiting in a tight labor market. Branch and Stripe Instant Payouts unlock <24hr. |
| **Multi-currency / multi-country** | If ANY worker is outside the US. Wise, Hyperwallet, Trolley, Nium dominate; Stripe Connect is good in 50+ countries but with caveats. |
| **Hold / release for disputes** | If buyer disputes drive chargebacks. Stripe Connect, Adyen handle this natively; per-payout APIs don't. |
| **Tax form generation** (1099-K, 1099-NEC, W-9, W-8) | If you'll cross 1099 thresholds. Trolley, Tipalti, Stripe Connect handle 1099 forms; Wise and Tremendous don't. The 1099-K threshold dropped to $5K starting 2024 — affects more marketplaces than before. |
| **Embedded vs custom UX** | If branded onboarding matters. Stripe Custom + Adyen Custom = full white-label; Stripe Standard = co-branded. |
| **Worker classification risk** | If payment design contributes to misclassification (see 4.4). |

The right answer is usually a stack of 2: a primary payouts layer (Stripe Connect or Adyen for Platforms or Hyperwallet) plus an on-demand pay layer (Branch) bolted on if you need it for supply retention.

### 4.2 Decision matrix by marketplace stage

| Stage | Default pick | Why |
|---|---|---|
| Pre-PMF, <50 payouts/month | Manual via Wise Business / Stripe Standard payouts | Don't build infra you'll throw away |
| Small US-only marketplace, 50-500/mo | **Stripe Connect Express** | Best onboarding/KYC UX, free until you scale, the embedded flow keeps supply on-platform |
| Scaling US-only, 500-5K/mo | **Stripe Connect Express OR Standard** + Branch for on-demand pay if supply churns | Stripe scales, Branch handles the "I need money today" supply objection |
| Multi-country, any volume | **Hyperwallet OR Adyen for Platforms** | Stripe Connect covers most countries but has gaps; Hyperwallet built for this |
| Mass payouts with tax handling | **Trolley** | Multi-currency mass payouts + 1099 / W-9 / W-8 generation is its core product |
| AP-style approvals + payouts | **Tipalti** | If payouts go through approval chains (creator marketplaces, vendor marketplaces) |
| Embedded gig-specific SDK | **dots.dev** | If you want a payout SDK purpose-built for gig platforms — fewer features but tighter fit |
| Rewards / gift cards as payout option | **Tremendous** | If supply has a choice between cash and gift cards |

### 4.3 Integration patterns

**Connected-account model** (Stripe Connect, Adyen for Platforms):
- The supply worker has their own account inside your platform's account hierarchy
- KYC happens at account creation, not per payout
- You can hold funds, dispute, refund, and have full visibility
- Best for: most US marketplaces with ongoing relationships

**Custodial / mass-payout model** (Trolley, Routable, Hyperwallet partial mode):
- You hold the money; you send batch payouts to a list of recipients
- Simpler integration; less compliance overhead per worker
- Best for: high-volume one-off-ish payouts, multi-currency, tax-form-heavy use cases

**On-demand pay overlay** (Branch):
- Sits ALONGSIDE your primary payout API
- Workers can advance earned-but-not-yet-paid wages
- Reduces supply churn in tight labor markets

**Webhook handling** — every payout API has events; the critical ones are:
- `payout.created`, `payout.paid`, `payout.failed`
- `account.updated` (KYC status change)
- `transfer.failed` / `payout.canceled`
- Always handle idempotently; payment retries are real.

### 4.4 Compliance and worker classification risk

**The single biggest gotcha** in marketplace payouts isn't picking the wrong API — it's that **how you pay workers becomes evidence in a 1099 misclassification suit**.

The ABC test (used in California and many states) asks:
- A: Is the worker free from your control? (If you set the schedule, you fail A.)
- B: Is the work outside your usual business? (If you're a cleaning marketplace and they clean for you, you usually fail B.)
- C: Does the worker have an independent trade? (Most gig workers fail C.)

Payment-design factors that worsen the classification picture:
- Hourly pay (vs per-job)
- Mandatory pay rates (vs worker-set)
- Payment timing you control fully (vs they can withdraw on demand)
- No 1099-NEC issued (so it looks like W-2)

Payment-design factors that improve it:
- Per-completed-job payments
- Worker chooses their own rate (or accepts/rejects offered rate)
- Worker controls payout timing (Branch / Stripe Instant Payouts)
- Clean 1099-NEC issued every year above threshold

**The 1099-K shift to $5K threshold** (effective tax year 2024, ramping further) means many small marketplaces now hit the threshold who didn't before. Pick a platform that handles 1099-K generation natively (Trolley, Stri