A2B Purchases
Let an agent buy Web2 goods for the user, then inspect payment, delivery, and audit evidence in Dashboard.
A2B Purchases
A2B is agent-to-business payment execution. An agent buys gift cards, top-ups, subscriptions, or other goods from Web2 merchants for the user. The user sets budget and constraints; the protocol handles escrow, execution records, and delivery proof.
Start a Purchase
Natural language example:
Buy me a $5 Uber gift card. Do not spend more than 5.2 USDC.The agent creates an Intent that declares budget, merchant, product, deadline, and allowed tools. The transaction then advances through an on-chain checklist.
Lifecycle
Typical path:
- Create Intent.
- Deposit funds into order escrow.
- Create merchant invoice.
- Execute payment.
- Wait for merchant delivery.
- Produce Completion Proof.
- Reveal the delivered item.
If the deadline passes before completion, the contract can enter expire / refund.
What to Check in Dashboard
Open My Purchases:
- Product and merchant.
- Budget cap and actual payment.
- Status: created, paid, delivered, fulfilled, failed, expired.
- On-chain cash flow.
- Gateway audit records.
- Completion Proof.
- Redemption code or credential reveal.
Sensitive delivered items such as gift card codes should not be stored in browser localStorage. Dashboard reveal should be temporary.
How Safety Works
A2B safety depends on:
- Intent limits what the agent can spend, do, and when it must finish.
- The contract checklist controls the order of fund movement.
- ActionTrace records which tools the agent called.
- auditRoot commits execution records on-chain.
- Completion Proof gives the final verdict.
If the transaction fails or expires, Dashboard should show the reason, refund status, and verifiable records.