Architecture deep-dive

Signal is the standing layer behind Kit — optional reputation snapshots derived from verified release, refund, and dispute outcomes.

How standing is derived from verified outcomes.

Paybond Signal

Most teams integrate Paybond Kit and never land here. This page is for partners who need standing-receipt or scoring detail behind the SDK.

Start with Kit>Explore Kit Read the scoring model

Standing snapshot

Trusted

842

/ 1000

Reliability: 98%
Settlement success: 94%
Disputes: 0.4%
Consistency: High

Intent released+3 pts · fulfillment confirmed
Dispute avoidedTerminal outcome verified
Receipt signedLedger position 18,492

Verified by Paybond

What Signal produces

A signed standing receipt, grounded in verified settlement outcomes.

Instead of a public rating or a new evidence-review system, Signal summarizes the outcomes already verified through Paybond. The receipt explains its score without revealing raw logs or private review notes.

Verified settlements
Dispute history
Fulfillment consistency
Reliability score

A standing receipt partners can verify.

Signal packages verified Paybond outcomes into a compact, signed artifact: who performed the work, how reliably they settled, and why the score looks the way it does.

Example standing receipt

842 / 1000

Signal Score

VerifiedTrusted

Generated July 5, 2026

A portable snapshot a partner or auditor can check without access to your systems.

Operator

Atlas Fulfillment Agent

The accountable agent behind the verified Paybond activity.

Outcome profile

94% released · 3% refunded · 3% disputed

Settlement outcomes that explain reliability, not self-reported KPIs.

Reason codes

High completion · Low dispute rate

Plain-language explanations for the current score and recent movement.

Freshness

Ledger position 18,492

The point in Paybond settlement history used to generate the receipt.

Verification

Signed by Paybond Signal

Signature material lets a partner confirm the receipt has not been altered.

Read scoring docs Signal API reference Explore Kit

How Kit and Signal fit together

Kit is what you write against; Signal is optional standing derived from verified Kit outcomes. Most teams never integrate Signal as a separate product.

Kit
SDK you integrate — proof-gated release and signed receipts.
Signal
Standing snapshots derived from those verified outcomes.

Standing with reasons, not ratings.

Signal is outcome-driven: every claim points back to verified settlement activity a reviewer can trust.

Trust built from verified outcomes
Every successful settlement strengthens an agent's standing—no reviews or self-reported claims required.
Signal scoring>
Explainable standing
Every score includes the verified events and reason codes that contributed to it.
Signal API reference>
Portable receipts
Carry a signed standing snapshot across customers and platforms when you choose to share it.
Ledger and provenance>
Privacy by default
Reveal only the proof required for a decision—never raw logs or private customer data.
Selective disclosure>

How verified history becomes standing

Signal follows the settled record: work, outcome, signed provenance, standing, and partner verification.

How a Signal score is calculated

The score is derived from signed settlement outcomes—nothing self-reported. Verified results move it up; friction and thin history move it down.

What increases a score

Successful settlements
Released intents that ended in payment to the payee carry the largest positive weight.
Low dispute and refund rates
Fewer refunds and disputes across terminal outcomes raise the score.
Consistent completion
A steady pattern of released outcomes signals dependable fulfillment.
Confirmed released volume
Verified released value contributes additional confidence up to a cap.
Fast terminal resolution
Shorter time from intent to terminal settlement improves the latency component.

What decreases a score

Disputes
Intents frozen into dispute review lower the score until resolved.
Refunds
Refunded outcomes reduce the settlement-success contribution.
Sparse history
With no terminal outcomes yet, the score is 0—meaning 'not yet established,' not bad behavior.
Slow resolution
Long time-to-terminal outcomes weaken the latency component.

How to read a Signal score

Bands are reviewer guidance for interpreting a score, not a fixed product grade. Each reviewer still decides the threshold that fits their own policy.

Exceptional
900–1000
Consistently released outcomes with very low dispute and refund activity.
Trusted
800–899
Strong settlement history with dependable completion. Example receipt: 842.
Example receipt: 842
Reliable
700–799
Solid performance with occasional friction worth a quick review.
Needs improvement
600–699
Elevated refunds, disputes, or slower resolution warrant closer diligence.
High risk
Below 600
Sparse or weak settlement history; apply stricter review before relying on it.

Range	Label	How to read it
900–1000	Exceptional	Consistently released outcomes with very low dispute and refund activity.
800–899	Trusted842	Strong settlement history with dependable completion. Example receipt: 842.
700–799	Reliable	Solid performance with occasional friction worth a quick review.
600–699	Needs improvement	Elevated refunds, disputes, or slower resolution warrant closer diligence.
Below 600	High risk	Sparse or weak settlement history; apply stricter review before relying on it.

Signal in the Paybond stack

Standing is built on identity and evidence—not in isolation. Signal reads verified history rather than inventing new claims.

Harbor — Agent identity & settlement
Ledger — Transaction evidence
Signal — Standing snapshots
Partners — Independent verification

What a Signal score reflects

Each component maps to verified settlement behavior, so a reviewer can see exactly what drives standing.

Reliability: How consistently the agent reaches a released settlement outcome.
Consistency: Whether performance holds steady across many settled transactions.
Settlement success: The share of terminal outcomes that released to the payee.
Dispute rate: How often outcomes fell into dispute review relative to volume.
Verification status: Whether the receipt is signed and independently checkable.
Historical trend: How standing has moved over time across the settlement record.

Step 1

Agent completes work

An agent fulfills a task and produces completion evidence Paybond can evaluate.

Intent lifecycle>

Task
Fulfillment
Outcome

Step 2

Rail releases or refunds

Customer-owned rails execute release, refund, or dispute review after evidence evaluation.

How settlement works>

Authorize
Evaluate
Release

Step 3

Paybond verifies outcome

The signed release or refund result is recorded as evidence tied to the accountable operator.

Ledger and provenance>

Outcome
Evidence
Operator

Step 4

Signal score updates

Verified outcomes recompute the deterministic score and its reason codes.

Signal scoring>

Metrics
Score
Reason codes

Step 5

Partners verify standing

A partner or auditor checks the signed receipt without touching your systems.

Signal API reference>

Receipt
Signature
Trusted

When scores change

Signal recomputes standing from new verified outcomes. It never rewrites history silently—every change points back to a settlement event.

After a settlement
A released or refunded intent updates settlement-success and volume components.
On a dispute
An intent frozen into dispute review lowers standing until it resolves.
On a reversal
A refund or reversal reduces the settlement-success contribution.
On verification
A newly signed receipt captures the current standing at a fixed ledger position.
On stale history
As newer outcomes accrue, older activity carries proportionally less weight.

How partners verify a receipt

A Signal receipt is built for outside review. A partner confirms integrity without database access or raw operational logs.

How to verify

Fetch the signed receipt from the Paybond Gateway reputation API.
Check the signature against Paybond's published Signal signing keys.
Match the receipt ID and operator to the claim under review.
Confirm the ledger position and timestamp show the receipt is current.

Signal API reference

Why Signal instead of traditional reputation?

Reviews and star ratings are subjective and easy to game. Signal is grounded in verified settlement outcomes a partner can check.

Source
Traditional reputation
Reviews
Paybond Signal
Verified outcomes
Visibility
Traditional reputation
Public history
Paybond Signal
Selective disclosure
Integrity
Traditional reputation
Easy to manipulate
Paybond Signal
Cryptographically verified
Basis
Traditional reputation
Subjective
Paybond Signal
Settlement-based

Dimension	Traditional reputation	Paybond Signal
Source	Reviews	Verified outcomes
Visibility	Public history	Selective disclosure
Integrity	Easy to manipulate	Cryptographically verified
Basis	Subjective	Settlement-based

Verify standing in code

Retrieve a signed standing receipt for one operator through the Paybond Gateway with `GET /reputation/{operator_did}`—scoped to the authenticated tenant.

reputation.ts

Code exampleSwipe to inspect long lines

// GET /reputation/{operator_did}
const receipt = await paybond.reputation.retrieve(
  "did:paybond:atlas-fulfillment",
);

console.log(receipt.score, receipt.standing, receipt.verified);

Sample response

GET /reputation/{operator_did}

{
  "operator_did": "did:paybond:atlas-fulfillment",
  "score": 842,
  "standing": "Trusted",
  "verified": true,
  "updated_at": "2026-07-05T14:32:00Z"
}

Read Signal API docs

Standing you can stand behind

Settlement verified
Cryptographically signed
Tamper resistant
Portable across platforms
Privacy preserving

Clear boundaries for sensitive standing data

Signal is useful because it travels, but the sharing model stays explicit.

Private to the customer workspace
Signal artifacts are scoped to the customer that owns the Paybond activity. They are not published into a global reputation feed.
Receipts, not raw telemetry
Partners receive signed summaries and verification material, not unrestricted access to databases, logs, or private review notes.
Policy stays separate from the score
Manual review states, fraud checks, and partner thresholds can route a decision, but they do not secretly change the signed score.

Where this architecture shows up

Signal supports diligence and reporting that happens outside the Paybond console.

Partner diligence
Give partners a verified view of completion rates, refund behavior, dispute history, and score movement.
Partner onboarding
Reduce manual diligence by sending a signed standing snapshot for the operators a partner needs to trust.
Compliance reporting
Give auditors a stable receipt that connects standing claims back to the Paybond settlement record.

Private standing, shared on purpose.

Signal is built for controlled sharing. Receipts are private by default, tied to a customer workspace and operator, and shared only in the scope the customer authorizes.

Controls

No public leaderboard or cross-customer reputation feed.
Scores come from Harbor release, refund, and dispute outcomes; review workflow context stays separate.
Review controls and fraud indicators do not silently rewrite the signed score.
Standing receipts stay private to the authenticated workspace unless you explicitly share them.

Start with Kit