Skip to content
FairHold

Proof-backed payment workflow

Work moves forward.Payments move with proof.

Coordinate milestones, review evidence and manage payment progress with clarity at every step.

Open the guided demoOpen the dashboardStart a deal
  • Human approval required
  • Demo payments are simulated
  • AI is advisory only

Deal workspace

Website redesign

Buyer → Seller · USD

On track

Milestone 1 of 250%

  1. Discovery and scopeAccepted
  2. Responsive buildEvidence in review
  3. Handoff and sign-offNot started

Deterministic recommendation

HOLD → human review required

Evidence exists, but the latest submission has not been accepted. No payment action is available yet.

Illustrative workspace · not live data

One readable path

From agreement to outcome, nothing hides in a chat thread.

Each step produces a durable record. Evidence is attached to a milestone, decisions carry a reason, and payment state is shown as it actually is.

  1. 01

    Agreement

    Capture the scope in writing: parties, deliverables and payment terms.

  2. 02

    Payment setup

    Record an authorization hold through the configured provider. A hold is not escrow.

  3. 03

    Conditions

    Break the work into milestones with explicit, human-readable acceptance criteria.

  4. 04

    Evidence

    The seller submits notes, links and files against each milestone.

  5. 05

    Review

    The buyer or an authorised reviewer accepts, rejects with feedback, or asks for a revision.

  6. 06

    Rule-based decision

    Deterministic rules evaluate verified payment state and the recorded decision. AI never decides.

  7. 07

    Release, refund or dispute

    The outcome is recorded with reasons, and the activity trail stays readable.

  8. Illustrative pricing

    $0.00

    This workspace is a demonstration. No funds are moved by demo actions, and no revenue or savings figures are claimed.

Three roles, one record

The buyer, the seller and an authorised reviewer each see the work that belongs to them.

Buyer

Review and approve

A review queue, not a wall of notifications. Approval controls are available only to the buyer and authorised reviewers.

  • See which evidence is waiting for review
  • Accept, reject with feedback, or request a revision
  • Approve a capture only after a recorded decision
  • Read the full activity trail behind every outcome

Seller

Deliver and submit

Assigned milestones, rejected evidence and the next action, with no payment controls exposed to the seller.

  • Know which milestones are active and what is missing
  • Submit evidence with a note, link and file
  • See buyer feedback and resubmit against the same criteria
  • Track payment progress without guessing

Reviewer

Granted per deal

A third party granted access to one specific deal. The grant is checked on the server for every action, and it never widens into access to anything else.

  • Reach only the deals you were explicitly granted
  • Read the submitted evidence and the milestone criteria
  • Accept or reject with a written reason
  • Never see a payment control you were not given

Separation of responsibilities

AI may read. People decide. Rules explain.

Advisory output is labelled by source and never changes deal or payment state. A reviewer can always act without it.

AI may

  • Interpret a natural-language agreement
  • Propose structured, reviewable conditions
  • Summarise evidence against those conditions
  • Surface concerns for a human reviewer

AI may never

  • Authorize, capture, release or refund a payment
  • Modify payment or deal state
  • Bypass authentication or deal access
  • Override the rules engine
  • Invent provider success or audit records
Deterministic rules decideWAITINGRELEASEREFUNDDISPUTE

The rules engine evaluates agreed conditions against verified payment state and records the reasons behind every decision. It is not a model, and it does not infer success from a screenshot.

Payment integrity

A hold is a hold. It is never described as escrow.

FairHold uses PayPal as payment infrastructure where configured. Where a hold is shown, it reflects the capability actually being used. Simulated demo actions make no provider request.

Authorization

A provider hold, awaiting a later decision.

Capture

Only after a human approval and a recorded rule outcome.

Void / refund

A definite provider result — never inferred.

Ambiguity

Timeouts stay pending until reconciled, not reported as success.

Read the record before you move the money.

Demo workspace · signed demo sessions · simulated payments by default.

Open the guided demoDemo sign in