Interactive demo
See Paybond decide release or refund from verified evidence.
Walk through a realistic agent booking flow: budget is reserved, agent actions are checked before spend, evidence is evaluated, and the final outcome becomes a record finance, support, risk, and partners can inspect.
Reserve budget before work starts
The demo begins with a buyer-approved agreement: parties, budget, deadline, allowed actions, and completion criteria are captured up front.
Block risky agent actions
Each guarded action is checked against the agreement before the agent can spend or call a side-effecting tool.
Settle from evidence
Signed evidence drives a release, refund, or review path, and the resulting record stays useful for finance, support, and partners.
Demo scenario
A booking agent gets budget, proves completion, and Paybond decides what happens next.
You are reviewing one agent-assisted travel booking. The buyer sets a budget and completion rule, the booking agent submits evidence, and Paybond produces a settlement record that explains the outcome without asking anyone to reconstruct it from chat logs.
- Agreement
- A travel-booking task with a $200 cap and an economy or premium-economy fare rule.
- Funding
- Choose card-funded USD, Stripe ACH Direct Debit, or USDC-on-Base to see how rail choice changes funding.
- Evidence
- Use the lab to edit the booking confirmation, fare class, and total price.
- Outcome
- Compare release, blocked spend, refund, and human-review branches from the same agreement.
1. Choose rail
Compare card-funded USD, Stripe ACH Direct Debit, and USDC-on-Base funding.
2. Pick outcome
Release, blocked spend, failed evidence, human review, or the editable lab.
3. Inspect proof
Start with the overview, then open payloads and events when you want API-level detail.
Walkthrough
Agreement is accepted
Principal signs the intent
The buyer-approved agreement captures who is doing the work, how much can be spent, which actions are allowed, what evidence is required, and when the work must finish.
- Customer view
- The buyer-approved agreement stays attached to the whole workflow.
- Paybond record
- Agreement recorded
- Why it matters
- Each transition preserves enough context for another team to review the decision later.
- Developer detail
- Open the Request and Response tabs to inspect the POST /intents payloads.
Lifecycle event feed
simulated record · Standard USD- 00:00.000Agreement recordedAgreement, budget, deadline, allowed actions, and evidence rules were recorded.
The overview tab is written for business review. Request, Response, Events, and Log keep the API-level proof available when you want to inspect the mechanics.
Continue from demo to a sandbox
This public walkthrough is simulated so anyone can evaluate the lifecycle. Start a free sandbox workspace when you want tenant-scoped test records, configured test rails, operator review, and integration credentials. Production settlement starts from paid onboarding.