Protected hold
Escrow exists to separate commitment to pay from immediate release of funds.
Escrow Terms
Draft rules for how protected funds should be held, released, paused, or refunded on Craeftmann.
Escrow is one of the product's most important trust mechanisms. These terms outline the expected behavior around funding, completion, release, cancellations, and disputes.
Draft legal scaffold
This document is a launch-stage draft. Production use should follow review by legal, operations, and payment stakeholders.
- money is moved into protected state before release
- Funding
- completion review is a real release checkpoint
- Approval
- holds can apply while facts are reviewed
- Disputes
Release conditions
Clear completion and approval states help both parties understand when money can move.
Dispute intervention
Where the work outcome is contested, the release path should pause long enough for review.
Section 01
Funding and hold logic
When a job is funded through Craeftmann, the payment should enter an escrow-backed state rather than flowing directly to the artisan. This gives both sides a more reliable structure for work commencement.
Section 02
Completion, approval, and release
Funds should only be released after the relevant completion and approval conditions are met. The exact model may vary by job structure, but the core principle is that approval matters.
Section 03
Cancellations, disputes, and refunds
Cancellation and dispute behavior should be documented with clarity around who can trigger review, what evidence may be requested, and when partial or full refunds are possible. Operational specifics still need final review.
This page should be refined alongside the actual payment provider behavior and dispute operations playbook.
Next move
Need the broader legal context?
Use the general terms page for account and marketplace rules, and the safety page for trust principles across the product.