paybondpaybond
Sign in

Paybond Harbor

Outcome-verified settlement for agent workflows.

Harbor holds budget against a signed agreement, checks completion against agreed evidence, and records why money was released, refunded, or sent to review.

Start sandbox>See walkthrough

Make agent settlement clear enough to review.

Harbor keeps the agreement, evidence, money outcome, and dispute path in one customer-scoped record.

  • Outcome-verified settlement

    Release funds when agreed evidence proves completion. Refund or route to review when it does not.

  • One settlement record

    Agreement, evidence, payment outcome, records, and operator decisions stay together for approvals, disputes, and audits.

  • Customer data boundaries

    Each workspace sees only its own intents and records, with scope derived from authenticated credentials.

  • Disputes built in

    Escalations use the same agreement, evidence, and decision trail instead of scattered logs or screenshots.

What Harbor leaves behind

Every transaction should produce records finance, risk, operators, and partners can use without piecing together internal logs.

  • Signed agreement

    Parties, budget, deadline, completion criteria, and evidence requirements are captured before work starts.

  • Evidence trail

    Signed evidence submissions and authenticated operator actions stay attached to the transaction instead of scattered across tools.

  • Settlement record

    A reviewable record shows the release, refund, or dispute outcome and the inputs behind it.

  • Dispute packet

    Escalations carry the timeline, evidence, and operator notes a reviewer needs to make a decision.

  • Compliance export

    Exportable records support audit, partner review, underwriting, and Signal standing checks.

A settlement record people can inspect

Harbor keeps the transaction story together so the buyer, operator, finance team, and reviewer are looking at the same record.

Example Harbor record

Hotel sourcing agent booking

A buyer reserved budget for an agent to source a refundable hotel booking under a signed completion rule.

Released after evidence check

Agreement

Find refundable hotel under $1,200 by Friday

The budget, deadline, parties, and completion criteria are captured before work starts.

Budget

$1,200 reserved

Funds are authorized or held through the tenant's approved settlement configuration.

Rail

Stripe Connect, configured for this workspace

The customer can request an allowed rail; Harbor resolves the destination from server-side tenant settings.

Evidence

Booking receipt and cancellation policy submitted

Evidence stays attached to the transaction with submitter and timing context.

Decision

Release approved

The record shows whether completion passed, failed, or needed human review.

Reusable records

Settlement record, dispute case, audit export

Finance, risk, and partners can review the same transaction story outside the live console.

Product proof, not promises

Each Harbor claim should point to a working flow, shipped rail, review path, or reusable record a buyer can inspect.

  • Walkthrough you can inspect

    The public walkthrough follows an agent transaction from agreement to evidence, decision, and reviewable record.

    Open walkthrough>

  • Rails are configured, not hard-coded

    Configured Stripe Connect, Stripe ACH Direct Debit, and USDC on Base rails are available where enabled for the tenant. Harbor resolves destinations from approved server-side settings.

  • Live settlement starts on paid plans

    Free Developer workspaces are for sandbox-only guardrail integration. Production settlement requires a paid plan and configured tenant routing.

    Review plans>

  • Review path for unclear outcomes

    When evidence is incomplete or contested, Harbor moves the transaction into review with the agreement, timeline, evidence, and notes together.

  • Records beyond the console

    Settlement records, compliance exports, and Signal standing checks give finance, risk, and partner teams proof they can reuse outside the live app.

How Harbor works

A practical lifecycle from agreement to money movement and reviewable records.

  1. Step 1

    Define the agreement

    Buyer and operator agree on participants, budget, deadline, completion criteria, and required evidence.

  2. Step 2

    Reserve budget

    Funds are authorized or held through an enabled rail so the transaction has a clear release/refund path.

  3. Step 3

    Submit evidence

    The payee or agent attaches signed evidence showing what happened and who submitted it.

  4. Step 4

    Decide the outcome

    Harbor compares the evidence to the agreed completion criteria and records release, refund, or human review.

  5. Step 5

    Produce records

    Teams receive settlement records and review trails for audit, partner verification, and Signal standing.

When evidence does not prove completion

Harbor distinguishes the evidence check from the human review path, so automation and escalation stay understandable.

  • Evidence proves completion

    Harbor records the passing check and the transaction can proceed to release through the configured rail.

  • Evidence fails the agreement

    The failed check is preserved in the lifecycle, then the transaction can refund or move into review based on the agreed workflow.

  • Evidence is unclear or contested

    Harbor opens a dispute path so a human reviewer sees the agreement, evidence, timeline, and notes before resolving release/refund through Harbor or recording a non-rail case outcome in Gateway.

Controls customers can explain.

A reviewer should be able to answer who agreed, what was funded, what evidence arrived, why money moved, and who intervened.

Controls

  • Workspace boundaries are enforced from authenticated credentials, not form fields.
  • Release, refund, and dispute decisions are recorded with who/what/when context.
  • Receipts and exports give auditors and partners a replayable summary of the decision.
  • Paybond records workflow rules around supported rails; payment processors and networks move funds under their own terms unless a written agreement says otherwise.
Explore Harbor docs

Where Harbor fits

Use Harbor where an agent workflow needs reserved budget, verified completion, and a record people can trust later.

  • Agent marketplaces

    Fund tasks up front, release on verified completion, and resolve disputes against evidence instead of screenshots.

  • B2B services and milestones

    Reserve budget for service work, accept signed proof of completion, and keep human review for exceptions.

  • Programmatic procurement

    Bind agent spend to completion criteria and produce records finance, compliance, and partners can review.

Harbor FAQ

Practical questions about settlement, evidence, rails, review paths, and customer data boundaries.

What makes Harbor different from a typical escrow?

Harbor keeps the agreement, evidence, release/refund decision, and dispute path in one reviewable record. Funds move through supported payment rails because agreed evidence supports the outcome, not because a one-off integration says so.

Do teams need to build custom settlement logic?

No for the common path. Teams define completion criteria and evidence requirements, then use Harbor to reserve budget, evaluate submissions, record outcomes, and preserve the record.

What happens when the outcome is unclear?

Harbor can move the transaction into dispute review. The reviewer gets the agreement, evidence, timeline, and operator notes instead of reconstructing the story from separate tools.

Which payment rails can Harbor use?

Harbor can use configured Stripe Connect, Stripe ACH Direct Debit, and USDC on Base rails where they are enabled for the tenant. Customers and SDKs can request an allowed rail, but Harbor resolves the effective destination from approved server-side configuration.

Is Paybond a regulated escrow agent or payment processor?

No, not by default. Paybond is software for defining, verifying, and recording workflow settlement rules around supported rails. Payment processors, card networks, banks, wallet providers, or stablecoin networks move funds under their own terms unless a separate written agreement says otherwise.

How does Harbor relate to Signal and the Ledger?

Harbor runs the settlement workflow. The Ledger preserves the history behind each decision, and Signal turns completed settlement history into signed standing artifacts for partners and risk teams.

How does Harbor keep customer data separated?

Harbor derives workspace scope from authenticated credentials and applies it across views, actions, records, and exports. Customer-supplied identifiers are not treated as the source of truth.