Four agents, one hold. Principal, buyer, oracle, seller.

Agents buy from agents.
The money waits for proof.

pyFides is the fiduciary layer for AI agents. It sets the buyer’s money aside on a PayPal hold and releases it only when what was promised really arrives.

A blue coin held inside an open frosted-glass capsule
Held $28.00Waiting for the delivery to match
Run a purchaseAbout a minute, sandbox funds
AP2 v0.2 mandatesPayPal Orders v2Authorize → captureSHA-256 delivery proofSD-JWT signaturesAgent-to-agent negotiationPYUSD (pending confirmation)Settlement ledger

Proof, from sandbox demo data

186 / 186Releases

Paid out only after the delivered file’s fingerprint matched the one promised.

42Quarantined

blocked by the signed . $0.00 moved.

140 msCapture time

From a matching fingerprint to the seller being paid.

$30.00Signed cap

The most agent.alpha can spend on this mandate. Anything above is refused.

Sandbox demo data · Open the ledger

How a purchase runs

Five steps, one record. The money moves last.

The console narrates each step as it happens, so a person can follow an agent’s purchase the way they would read a statement.

  1. The person in charge sets a spending limit and signs it.

  2. The buying and selling agents settle a price and a deadline, and the seller names the file’s fingerprint.

  3. The buyer’s money is set aside. The seller can see it is there but cannot touch it.

  4. An automatic checker compares what arrived with what was promised.

  5. If they match, the seller is paid and a receipt is issued. If not, nothing moves.

Checkout mandateAP2 · open
Cap
$30.00 USD
Scope
Compute, datasets
Expires
24 h
Signed by
ops@demo
Ops PrincipalSigned
Agent to agent
  1. agent.alphaRequesting H100-BURST-100U within a $30.00 cap. Delivery hash required.
  2. seller.betaOffer $28.00. 99.9% uptime, delivery under 90 s, hash committed.
  3. agent.alphaAccepted. Requesting a hold.
PayPal authorizationHeld
$28.00USD
Order
ORD-DEMO-7Q2K
Intent
AUTHORIZE
Honor period
3 days
Promised fingerprint 8f43 4346 648f 6b96 df89 dda9 01c5 176b Delivered fingerprint 8f43 4346 648f 6b96 df89 dda9 01c5 176b Match · release
Record of settlementTX-DEMO-4MX6
$28.00USD

agent.alpha → seller.beta

Verified and settled

Fig 1.0 One purchase, step by step. Tap a step, or let it play.

Guarantees

An agent can spend. It can’t overspend, prepay or be talked out of the rules.

Four objects carry the whole promise. Each one is checked before the next step can happen.

Signed spend cap#1
Checkout mandateAP2 · open
$28.00 of $30.00Within cap
ComputeDatasets24 h

The limit is signed, not suggested.

The person in charge signs a cap, a scope and an expiry. The agent can spend inside it and nothing above it.

Two-phase hold#2
ORD-DEMO-7Q2KPayPal
Holding...

Authorize now. Capture after delivery.

The money is reserved on the buyer’s PayPal account but not moved. The seller can see it, not touch it, for up to three days.

Delivery proof#3
  • Mandate signature valid
  • Amount within the cap
  • Delivered hash matches
All checks passed3 of 3 · release the hold

Released only when two hashes agree.

The seller states the file’s fingerprint up front. The checker fingerprints what really arrives. Money moves only if they’re identical.

On the record#4
ledger · sandbox
20:41:07 mandate.verified20:41:07 hold.authorized   $28.0020:41:10 delivery.received20:41:10 oracle.match20:41:11 capture.completed

Every step leaves a line.

Who signed, what was held, what arrived and when the money moved, all written to a ledger anyone on the team can read.

Try it · tamper with the delivery#5

Change one character. Watch the payment decision.

The seller promised the file below. Edit it as if it were altered on the way. The fingerprint is recomputed in your browser.

Promised fingerprint
Delivered fingerprint
The gap, and the fix

Release on proof.

Today an agent either pays first and hopes, or a person approves every purchase. Neither scales. With pyFides the money waits where everyone can see it, and moves only when the file that arrived is the file that was promised.

Pay first

The file is wrong, or never comes.

Funds have already moved. Getting them back is a support ticket, not a protocol.

Trust the agent

One injected prompt, one bad purchase.

Without a signed limit, the agent’s own judgement is the only control.

With pyFides

Capped, held, released on proof.

The limit is signed, the money waits, and it moves only when the hashes agree.

Four agents, one hold. Principal, buyer, oracle, seller.

Our Agents

Four parties take part in every purchase. Each one can only do its own job, and every step leaves a record.

The Principal

Person in charge

Signs the cap, scope and expiry the agents work inside.

The PrincipalPerson in charge

Steps in only at real decisions. Everything else follows the signed mandate.

Agent Alpha

Buying agent

Shops inside the signed cap and never pays before proof.

Agent AlphaBuying agent

Requests holds, checks every offer against the mandate, and refuses injected instructions.

The Oracle

Delivery checker

Fingerprints what arrives and compares it with what was promised.

The OracleDelivery checker

Releases the hold only when the delivered SHA-256 matches the seller’s commitment.

Seller Beta

Selling agent

Commits a fingerprint in its offer, delivers, and is captured when they match.

Seller BetaSelling agent

Commits a fingerprint in its offer, delivers, and is captured when they match.

Hover, tap or tab through the cards.

Compare protocols

Every protocol caps spend. Only one waits for proof.

The difference shows up when something goes wrong. Pick a problem and see where the buyer’s $28.00 ends up.

  1. AP2Google · FIDO Alliance

  2. ACPOpenAI and Stripe

  3. x402x402 Foundation

  4. pyFidesBuilt on AP2

The detailsTrust model, caps, holds, governance and rails
AP2ACPx402pyFides
Trust modelUser- and agent-signed mandates (SD-JWT)PSP-issued, seller-scoped, revocable tokenSigned authorization per request, settled by a facilitatorAP2 mandates as evidence for every step
Spend capsBudget, price and expiry, signed by the userMax amount, currency and expiry on the tokenExact or upper bound per requestMandate cap checked before any hold
Disputes and holdsEvidence only; resolution outside the specCard and PSP chargebacksIrreversible by default; optional auth-capture escrowAuthorize, verify hash, then capture or void
GovernanceOriginated by Google; developed in the FIDO AllianceApache-2.0; OpenAI and Stripex402 Foundation (Linux Foundation); Apache-2.0Open-source hackathon build
RailsCards, bank transfers, stablecoinsCards, wallets, BNPL via a PSPStablecoins on Base, Solana, Polygon and othersPayPal Orders v2; PYUSD pending confirmation

Simplified for the default flow of each protocol, as of November 2026. Sources: AP2 v0.2 specification, Stripe Shared Payment Token docs, x402 Foundation docs, PayPal developer docs.

Watch one purchase, start to finish.

Sandbox funds, real flow: mandate, hold, hash check, release. About a minute.