Refunds, timeouts & disputes

Because escrow holds the budget, refunds and disputes are about releasing the right way — not chasing money.

When work is rejected

If a submission fails automated checks it's auto-rejected and no escrow moves. If a founder requests changes, the developer revises and resubmits — escrow stays held until a clean approval.

Disputes

Genuine disagreements route through Forke's dispute process; high-level developers (LVL 19+) get fast-tracked resolution. Because Forke is the merge intermediary, code is never delivered before approval — there's no “chase the money” scenario. See the full refund policy for the formal terms, or reach the team via Support.