What Happens When Agents Hire Agents That Hire Agents
Single-agent payment is well-understood: an agent transacts on behalf of a principal, payment settles on a card network or on-chain. Multi-hop is harder. When agent A hires agent B to research a topic, and agent B subcontracts agent C to fetch a specific data source, who pays whom, when, and under what dispute rules? This page consolidates the cross-agent payment flow patterns in production as of May 2026.
The Five Production Multi-Hop Patterns
| Pattern | Mechanism | Typical Use |
|---|---|---|
| Pass-Through Settlement | Each hop settles independently to its caller; caller absorbs cost | Simple subagent flows; default in most agent frameworks |
| Aggregated Invoice | Originating agent receives single invoice covering all sub-hops | Vertical agent platforms (Sierra, Decagon) hide internal costs |
| Escrowed Multi-Party | Funds held by escrow service; distributed on completion per pre-agreed split | Complex multi-vendor delegations with quality-dependent payment |
| Mandate-Chained AP2 | Each hop signs a sub-mandate from the parent mandate; settlement flows top-down | AP2-native enterprise flows where audit chain matters |
| x402 Atomic Multi-Hop | On-chain transaction settles all hops atomically | Crypto-native flows with smart-contract settlement |
Dispute and Chargeback Handling
| Failure Mode | Resolution Path |
|---|---|
| Sub-agent failed to deliver, parent already paid downstream | Parent agent files dispute; AP2 mandate revocation propagates downward; refund via originating settlement rail |
| Sub-agent over-charged (price gouging) | Mandate scope-limit was exceeded; AP2 mandate-bound spending cap reverts transaction |
| Sub-agent delivered but quality below threshold | Escrowed-multi-party patterns release reduced payment; pass-through patterns require dispute |
| Identity spoofing in sub-agent chain | Verified-agent + reputation-system filters block at discovery; chargeback against responsible verified principal |
| Sub-agent delivered to wrong principal (key compromise) | AP2 mandate revocation + new key issuance; affected funds clawed back via card-network rules (Visa TAP) or on-chain governance (x402) |
Six Things the Multi-Hop Picture Tells You
- Pass-Through Settlement is the default but the most fragile. Each hop settles independently, which keeps the protocol simple but means failures propagate poorly. The originating agent absorbs cost for sub-failures unless dispute flows are run separately. Acceptable for simple delegations; insufficient for high-value commercial flows.
- Aggregated Invoice is the consumer-facing standard. Vertical agent products (Sierra customer support, Decagon resolution, Harvey legal research) charge the principal once and absorb the internal subcontracting. This is the simplest UX and the dominant pattern for end-user-facing agentic products.
- Escrowed Multi-Party is rising for B2B agent commerce. When two businesses transact via agents and quality is uncertain, escrow services hold funds and distribute on outcome. Stripe's agent-toolkit, Visa TAP, and emerging x402-native escrow services all support the pattern. Adoption is small but growing.
- Mandate-Chained AP2 is the audit-friendly enterprise standard. Each hop signs a sub-mandate referencing the parent. Audit trails reconstruct the full chain of authorisation, which matters for regulated industries (financial services, healthcare, legal). AP2 specification supports this natively; enterprise adoption is the largest source of AP2 traffic in 2026.
- x402 atomic multi-hop is the most innovative pattern. Smart contracts on x402-compatible chains settle entire multi-agent flows atomically: either every hop is paid or none are. Eliminates partial-failure ambiguity at the cost of requiring on-chain settlement. Niche today but expanding in crypto-native agent commerce.
- Cross-rail settlement is still missing. An agent flow that starts on a Visa TAP authorisation but needs to subcontract to an x402-native specialist agent currently requires the parent agent to operate in both ecosystems. Cross-rail settlement bridges (AP2 + x402 interop) are in development but not shipping at scale as of May 2026.
What This Means for AI Visibility Programmes
Brands selling agent-mediated services need to declare the payment flow they support. A brand offering a vertical agent product on aggregated-invoice settlement is a different procurement decision from a brand offering an open API on pass-through settlement, and parent agents pick differently based on which pattern their downstream commercial flow requires. Brands tracking AI visibility should monitor brand presence inside each payment-pattern flow separately because the parent-agent decision logic differs across patterns.
Methodology
Pattern descriptions synthesised May 15, 2026 from Google AP2 specification, Coinbase x402 RFC, Stripe agent-toolkit documentation, and production case studies. Dispute and chargeback flows from Visa TAP documentation and AP2 working-group publications. Refreshed quarterly as multi-hop settlement infrastructure matures.
How Presenc AI Helps
Presenc AI tracks brand-mention rates inside agent-mediated commerce flows, including the multi-hop settlement patterns above. When your brand surfaces in a parent agent's sub-contracting decision, our instrumentation captures the recommendation outcome alongside the payment-pattern context.