PayPal agentic commerce is the set of products PayPal has shipped so that AI agents can initiate and settle payments on its rails. Three pieces define the surface today: the open-source PayPal Agent Toolkit that exposes PayPal's APIs to large language models as tool calls, the regulated stablecoin PYUSD that now sits on 13 chains, and PayPal's seat in the 60-collaborator AP2 standards group. PYUSD reached roughly $3.51 billion in market capitalization on April 24, 2026, growing 680% year over year, and PayPal serves more than 400 million consumer accounts and roughly 35 million merchant accounts. This article explains what each piece does, how the underlying mechanism works, where PYUSD currently lives, how the three competing agentic-payment standards differ, and what the design constraints are for builders evaluating the stack.
​

PayPal agentic commerce refers to AI agents acting as authenticated buyers, sellers, or settlement intermediaries on PayPal's payment rails. The category covers consumer-side checkout (an agent purchasing on behalf of a user), business-side automation (an agent issuing invoices, managing subscriptions, or filing disputes), and machine-to-machine settlement (one software service paying another for an API call, inference, or data feed). PayPal began shipping infrastructure into all three lanes in 2025.
​

The scope is wider than a single SDK. It includes (1) developer tooling that turns PayPal's REST APIs into LLM-callable functions, (2) a regulated dollar stablecoin that can settle agent payments outside PayPal's closed ecosystem, and (3) participation in cross-industry standards that define how non-PayPal agents can transact with PayPal merchants. Each component reaches different segments of the agent economy.
​

Scale matters because AI agents will not adopt a payment rail that does not already carry liquidity. PYUSD market capitalization sat at roughly $3.51 billion on April 24, 2026, with a peak above $4.3 billion earlier that month. The total stablecoin market processed about $33 trillion in volume in 2025 per Artemis data published in Bloomberg, with USDC at $18.3 trillion and USDT at $13.3 trillion. PYUSD enters that market as a smaller but rapidly growing entrant, with 680% year-on-year supply growth and Paxos-issued, NYDFS-supervised regulatory status.
​

The user-facing question is who acts on whose behalf. In a consumer flow, a ChatGPT or Claude session may invoke PayPal's checkout to buy a product on a Shopify storefront. In a developer flow, a CrewAI workflow may issue an invoice via a PayPal API. In a settlement flow, two services may exchange PYUSD on a Layer-2 network without either holding a PayPal account. Each of those mechanics has different identity and authorization requirements, which is why the standards landscape is fragmented.
​

The PayPal Agent Toolkit is an open-source SDK that wraps PayPal's REST APIs as tool definitions consumable by major agent frameworks. The toolkit ships dated releases on the public GitHub release history, where you can pin to a specific version and confirm changelog entries before upgrading. It supports LangChain, CrewAI, the OpenAI Agents SDK, Vercel's AI SDK, Amazon Bedrock, and the Model Context Protocol (MCP). Each integration exposes the same underlying API surface: invoicing, subscription management, order creation, payment capture, refund issuance, dispute filing, and shipment tracking.
​

Mechanically the toolkit registers each PayPal endpoint as a tool with a JSON schema describing its arguments and return shape. When a model decides to invoke a tool, the toolkit issues an authenticated request to PayPal's API on behalf of the developer's client credentials, intercepts the response, and returns the result to the model. The flow is identical to any other LLM tool-call pattern; the value is that PayPal's fraud and dispute machinery sits behind the call without the developer rebuilding it.
​

Authentication relies on PayPal's existing OAuth client-credentials grant. The agent does not hold the user's PayPal password. For consumer-side checkout the user typically authorizes the agent through a one-time PayPal flow that returns a token with constrained scope and lifetime. The dispute and refund pathways then route through the same channels a human-initiated PayPal transaction would use, which preserves chargeback rights and fraud protection.
​

The constraint is that both ends of the transaction must touch PayPal. The toolkit excels when an agent acts on behalf of a PayPal account holder transacting with a PayPal merchant. It does not address agent-to-agent settlement or payments to a counterparty that has no PayPal account. That gap is the design reason PYUSD and the AP2 / x402 standards exist alongside the toolkit.
​

PYUSD is the settlement asset PayPal expects agents to use when transactions need to leave PayPal's closed-loop network. The token launched on Ethereum in August 2023, expanded to Solana in May 2024, added Stellar and Tron in 2025, and reached Arbitrum in July 2025 as its first Layer-2 deployment. A LayerZero-issued variant called PYUSD0 then expanded the footprint to nine additional chains during the second half of 2025 and into 2026.
​

Liquidity distribution is uneven. As of April 2026, Ethereum still holds roughly 70% of the total PYUSD supply, with Solana the second-largest venue at around a fifth of supply. Solana holds the next-largest share at several hundred million dollars and is the chain where PYUSD sees its most active DeFi usage. Arbitrum, Stellar, and Tron each carry smaller balances primarily used for payments and remittance corridors.
​

Ethereum carries the bulk of PYUSD supply because that is where institutional custody, large-balance treasuries, and most regulated counterparties already operate. Average transaction fees on Ethereum mainnet ranged from $0.50 to several dollars during 2025 depending on network congestion. That cost structure suits low-frequency transfers between large balances but not the per-call or per-inference micropayments typical of agent workflows.
​

Solana is the most active venue for PYUSD in DeFi. Per Blockworks reporting on Kamino's PYUSD incentives, the lending protocol Kamino Finance was a major PYUSD venue on Solana, with PYUSD ranking among the larger stablecoin markets on the platform. Solana fees typically settle below one cent per transaction, which makes it a candidate venue for agent-driven settlement at high volume.
​

Arbitrum became PYUSD's first Layer-2 deployment on July 17, 2025 per the PayPal newsroom announcement. The integration relied on LayerZero's Omnichain Fungible Token standard for canonical issuance. Per-transfer fees typically run under one cent, comparable to Solana, and the deployment opened access to Arbitrum's deep DeFi liquidity around USDC, USDT, and DAI.
​

The PayPal-LayerZero partnership introduced a permissionless variant called PYUSD0 minted via LayerZero's Omnichain Fungible Token (OFT) standard. PYUSD0 is now live on Abstract, Aptos, Avalanche, Ink, Sei, Stable, Tron, Berachain, Flow. LayerZero reports that 733 OFTs in total have moved more than $166.9 billion in cross-chain volume across its mesh.
​

Stellar carries PYUSD primarily for cross-border remittance corridors and B2B payouts. PayPal's Xoom remittance product is the primary distribution channel. Settlement times typically clear in seconds at sub-cent fees, which fits the remittance use case but not high-frequency DeFi or agent micropayment workloads.
​

The summary view is that PYUSD has the broadest multi-chain footprint of any major US-issued stablecoin, but most of the supply concentrates on the chain with the least agent-friendly economics. Agents that need per-call settlement gravitate toward Solana and Arbitrum; treasuries and institutional flows stay on Ethereum.
​

Three standards are competing to define how agents transact, and they overlap less than the names suggest. Each addresses a different layer of the problem: consumer checkout, payment authorization, and machine-to-machine settlement. PayPal participates directly in one and indirectly through PYUSD in the others.

Table 1. The three agentic-commerce standards differ on launch sponsor, license, chain coverage, current shipping status, and merchant adoption.
​

The Agentic Commerce Protocol is Stripe and OpenAI's joint specification for consumer agent checkout, released under Apache 2.0 and hosted on GitHub. The core primitive is a Shared Payment Token (SPT) that lets an agent like ChatGPT initiate a purchase without exposing the user's card credentials to the merchant. Stripe described the design and reference implementation in its September 2025 blog post on developing an open standard for agentic commerce, published alongside the protocol's initial release.
​

Salesforce announced ACP support on October 14, 2025, with merchants Shopify, Etsy, Glossier, Vuori, Spanx, SKIMS named as live integrations. ACP solves the merchant-facing checkout problem: an agent can complete a purchase across the participating commerce backends without each merchant building a bespoke agent integration. It does not address stablecoin settlement, machine-to-machine flows, or non-card payment methods.
​

AP2 is Google Cloud's broader authorization and accountability framework, announced on September 16, 2025. Unlike ACP, AP2 is payment-agnostic: card networks, bank transfers, and stablecoins all route through the same authorization model. The 60-plus initial collaborators include PayPal, Mastercard, American Express, Coinbase, Adyen, Ant International, Worldpay, Mysten Labs, and the Ethereum Foundation.
​

The protocol introduces signed mandates that record what an agent is authorized to do on a user's behalf, what conditions must be met before a payment can settle, and how disputes attribute liability when an autonomous agent acts outside its mandate. The crypto wing of AP2 is the A2A x402 extension, co-developed with Coinbase and MetaMask, which allows AP2-compliant agents to settle in stablecoins via the x402 protocol described next. As of April 2026 the AP2 specification is published but production integrations remain limited.
​

The x402 protocol is Coinbase's HTTP-native stablecoin payment standard, named for the rarely used HTTP 402 status code reserved in 1997 for "Payment Required." When a client requests a paid resource, the server responds with a 402 status containing payment instructions; the client signs a stablecoin payload, retries the request with the payment attached, and receives the resource. The reference materials, including the x402 whitepaper and a facilitator implementation, sit at the x402 GitHub repository.
​

The Coinbase-operated facilitator settles ERC-20 stablecoin payments on Base, Polygon, Arbitrum, World, and Solana. The protocol gives developers 1,000 free transactions per month before a metered price applies. Across projects integrating the standard, x402 has processed more than 15 million transactions. Unlike ACP and AP2, x402 has no concept of consumer accounts or merchant onboarding; the unit of authentication is a wallet that signs a payment, which is why it suits machine-to-machine workflows where neither party has a human in the loop.
​

PayPal sits on the AP2 collaborator list but has not announced a direct x402 facilitator. PYUSD is supported by the x402 reference implementation as one of several ERC-20 stablecoins, which means PayPal's stablecoin can serve as the unit of account for x402 payments without PayPal operating the rail itself.
​

The benefits of agent-initiated payments cluster around three categories: programmable consumer checkout, machine-to-machine settlement, and continuous treasury automation. Each unlocks workloads that were previously impractical with card networks alone.
​

Programmable consumer checkout means an agent can complete a purchase on the user's behalf without that user manually entering card details, addresses, or shipping preferences for each transaction. The Agent Toolkit and ACP both target this lane. PayPal's distribution advantage is real: more than 400 million consumer accounts already authenticated, and integration patterns the developer ecosystem has used for over two decades. The dispute and chargeback rights that accompany a PayPal payment carry through to agent-initiated transactions, which preserves consumer-protection norms regulators expect.
​

Machine-to-machine settlement covers software services paying each other for API calls, inference time, data feeds, or compute. The x402 protocol is the most mature instance, with 15 million transactions processed and reference facilitators on five chains. PYUSD slots into x402 as one of several supported ERC-20 stablecoins. Settling on Solana or Arbitrum keeps per-call costs at fractions of a cent, which is the price point at which metered AI workloads become commercially viable.
​

Continuous treasury automation describes long-running agents that rebalance balances across chains, route incoming payments to working-capital wallets, and pay vendors automatically. PYUSD's multi-chain footprint suits this pattern because the same asset can sit in custody on Ethereum, in operational balance on Solana, and in working capital on Arbitrum without the agent rebuilding accounting per chain.
​

The risks fall into four buckets. The first is liquidity concentration. About 70% of PYUSD sits on Ethereum, where transaction fees defeat the per-call economics agents need. Moving balance to Solana or Arbitrum requires a bridge or burn-and-mint flow, each of which introduces non-atomic states. A bridge that fails mid-transfer leaves the agent holding either no asset or two assets, depending on the failure mode.
​

The second is standards fragmentation. ACP, AP2, and x402 cover different layers, and a single agent stack may need to implement parts of all three: ACP for consumer merchant checkout, AP2 mandates for authorization audit trails, and x402 for machine-to-machine flows. Standards alignment is improving but production deployments still require glue code.
​

The third is regulatory uncertainty around agent authorization. AP2's signed-mandate concept attempts to address what an autonomous agent is allowed to do on a user's behalf, but enforcement and liability assignment in disputed transactions remain open questions. The OpenAI Instant Checkout product launched in September 2025 and was discontinued in March 2026 after roughly 12 Shopify merchants ever went live, illustrating that even well-resourced agent-checkout deployments face onboarding and dispute-handling friction.
​

The fourth is operational complexity in cross-chain agent workloads. An agent holding PYUSD across Ethereum, Solana, and Arbitrum has to maintain accounting, reconcile bridge transfers, handle partial-failure recovery, and route around chain congestion. The composite of these tasks is harder than the sum of single-chain agent design, which is one reason intent-based execution layers have emerged as a category.
​

For agents that hold PYUSD across multiple chains and need to move balance to where the next payment must settle, the cross-chain execution problem is non-trivial. Eco Routes is an intent-based cross-chain execution protocol that takes an agent's expressed outcome ("deliver PYUSD to address X on Solana, source from any chain I hold") and routes it through solvers to atomic settlement across 15 supported chains, including Ethereum, Solana, Arbitrum, Base, HyperEVM, and Plasma. Either the intent clears end-to-end or it reverts, which removes the partial-failure recovery code from the agent's surface area. For builders constructing a PayPal-plus-onchain stack, Eco Routes complements rather than replaces the PayPal Agent Toolkit: identity, dispute handling, and merchant relationships stay with PayPal, while cross-chain stablecoin movement is handled by the routing layer. The atomicity write-up details the underlying mechanism, and the stablecoin rebalancing overview covers the continuous-loop patterns that apply directly to agent treasuries.
​

PayPal agentic commerce is the set of products PayPal has shipped to let AI agents act as buyers, sellers, or settlement intermediaries on its rails. The surface includes the open-source PayPal Agent Toolkit, the PYUSD stablecoin live on 13 chains, and PayPal's collaborator status in the AP2 standards group.
​

PYUSD is live on Ethereum (about 70% of supply), Solana, Arbitrum, and Stellar. The LayerZero PYUSD0 variant adds Abstract, Aptos, Avalanche, Ink, Sei, Stable, Tron, Berachain, Flow. Movement between them uses bridges, burn-and-mint flows, or an intent-based router.
​

The Agent Toolkit handles consumer checkout where a PayPal account holder transacts with a PayPal merchant. The x402 protocol handles machine-to-machine settlement where neither side needs an account. The Agent Toolkit covers identity and dispute handling; x402 covers HTTP-native stablecoin micropayments.
​

ACP is Stripe and OpenAI's checkout standard for consumer agents on participating merchants like Shopify and Etsy. AP2 is Google's broader authorization framework that records what an agent is allowed to do, signed by the user, and is payment-agnostic across cards, bank transfers, and stablecoins.
​

Agent treasuries often custody on Ethereum, settle on Solana for cost, and earn yield on Arbitrum. Counterparties sit on whichever chain they prefer. Bridging each hop manually creates partial-failure states. An intent-based routing protocol collapses those into one atomic operation.
​