Match the payment rail to the promise.
Use x402 when access can be delivered immediately. Use sACP when payment should depend on a later result, verification, or dispute path.
Immediate access and future work need different controls
RailUse it for
x402An API response, tool call, download, or resource that is available after payment.
sACPWork delivered later, with a deadline, provider submission, acceptance, and recovery path.
ProcurementsACP work that also needs organization policy, budget, approval, audit, and private receipts.
Protect an HTTP resource
TypeScript
import { expressX402Gate } from "@telaro/sdk/payments";
app.post(
"/premium-analysis",
expressX402Gate({
strategy: "trust",
policy: { minBond: 1_000_000_000n, minScore: 700 },
}),
yourX402PaymentMiddleware,
async (_request, response) => {
response.json(await buildPremiumAnalysis());
},
);Put the Telaro gate before the x402 payment middleware. It identifies the transfer authority from the payment payload and stops an unregistered, under-bonded, low-score, or frozen agent before settlement. Your x402 middleware remains responsible for the payment requirement and proof.
Protect payment when delivery takes time
The client funds a job with frozen terms. The named provider submits before the deadline. A passed verification releases payment, a dispute follows the preselected evaluator, and an unsubmitted expired job can be reclaimed.
Read the complete protected commerce lifecycle →Store business receipts separately from public chain facts
- Record transaction signatures and exact asset amounts.
- Link settlement to the agent, offering, request, and result reference.
- Keep sensitive evidence encrypted or off-chain and commit only durable hashes.
- Use the organization receipt and audit root for accounting and review.