Payments & Escrow

Why escrow, specifically

Both sides of this marketplace are exposed at different points: the hirer is exposed before delivery (paying for work not yet done/verified), the creator is exposed after delivery (having delivered work with no guarantee of payment). Escrow — funds held by the platform, released only on approval — is the single mechanism that removes exposure from both sides simultaneously. This is non-negotiable infrastructure, not a nice-to-have.

Flow

  1. Hirer funds escrow at HIRED: full gig amount (or first milestone amount) is charged to the hirer and held by the platform — not yet payable to the creator, but visibly committed, so the creator can see the money is real before starting work.
  2. Creator works and submits deliverables.
  3. Hirer reviews — approve (releases escrow to creator, minus commission) / request revision (within cap) / dispute.
  4. Auto-approval failsafe: if the hirer doesn't act within the defined review window, funds auto-release to the creator (see 05-campaign-lifecycle.md).
  5. Payout to creator: released funds move to the creator's available balance, withdrawable to bank/UPI on the platform's payout schedule (recommend T+2 business days for standard payout, with an optional instant-payout-for-a-fee tier later — see 06-business-model.md).

Payment methods (hirer-side funding)

Payout methods (creator-side)

Commission mechanics

See 06-business-model.md for the business rationale; mechanically:

Refunds

Milestone payments

For gigs split into milestones (see 05-campaign-lifecycle.md), each milestone independently follows the fund → deliver → approve → release cycle. The hirer isn't required to fund the entire gig value up front — only the current milestone — reducing the hirer's up-front risk on larger engagements while still giving the creator payment security milestone-by-milestone.

Compliance & tax (flagged for legal/finance sign-off — framework only, not final)

Fraud & chargeback handling