/vendor/paypal/AgentRouting.json or
/vendor/paypal/AgentContext.json directly.
paypal.com
Overview
Does paypal.com support MCP?
No confirmed MCP support was found for paypal.com as of 2026-06-28.
What agentic protocols does paypal.com support?
As of 2026-06-28, paypal.com has confirmed support for A2A, ACP, AP2, openai_apps_sdk, proprietary, and self_declared_discovery.
Is paypal.com's API publicly accessible or partner-gated?
Access varies by protocol: partner only, platform mediated, open.
Does paypal.com explicitly prohibit automated access?
Yes. paypal.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is paypal.com agent-ready?
Yes. paypal.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.
Protocols
PayPal participated as a named launch partner for A2A (April 2025) and is demoing integration of Google Cloud A2A-based merchant chat agents with PayPal commerce/payments capabilities; scope is agentic commerce — enabling AI agents to route transactions and payments through PayPal's infrastructure.
PayPal was listed among 50+ named launch partners in Google's April 9 2025 A2A announcement (Google Developers Blog), and the PayPal Dev Days event (April 29 2025) specifically demoed A2A enabling merchant Gemini-powered agents to integrate with PayPal commerce capabilities. PayPal also co-developed the related AP2 (Agent Payments Protocol) with Google, extending A2A into payment-specific flows. No standalone publicly callable A2A endpoint for PayPal has been documented; integration appears to be demonstrated via joint Google Cloud partnership.
Payment processor / ACP server operator: PayPal acts as the merchant acquirer side, exposing its merchant network (tens of millions of small businesses) to ACP-powered ChatGPT checkout flows — not as an end merchant, but as a payment infrastructure partner enabling its merchants to transact via ACP.
PayPal is a confirmed launch partner for ACP, adopting the protocol to power payments and commerce experiences within ChatGPT. Multiple sources, including Digital Commerce 360 and PaymentsJournal, confirm PayPal's partnership with OpenAI leveraging ACP; PayPal's ACP server is expected to bring its merchant base into ChatGPT commerce. Access is platform-mediated through OpenAI/ChatGPT infrastructure, not a directly callable public endpoint.
Payment processor and launch partner supporting AP2's cryptographic mandate framework for verifiable agent-initiated payment consent; PayPal's role is on the payment execution side (processing transactions authorized via AP2 mandate artifacts), not as a mandate issuer or wallet provider.
PayPal announced support for AP2 at the time of Google's original September 2025 launch, confirmed via PayPal's own developer community blog at developer.paypal.com/community/blog/PayPal-Agent-Payments-Protocol/. The protocol has since been donated to the FIDO Alliance (April 2026). No PayPal-specific AP2 endpoint or integration documentation was publicly accessible at the time of this scan, so sketchiness and endpoint callability cannot be assessed.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence that PayPal (paypal.com) is a participant, integration partner, or launch adopter of the Machine Payments Protocol (MPP), co-developed by Stripe and Tempo. Named MPP launch and extension partners include Anthropic, OpenAI, Shopify, Visa, Mastercard, Nubank, Ramp, Revolut, DoorDash, Lightspark, Cloudflare, Alchemy, and others — PayPal does not appear in any of these lists. PayPal's name surfaces only in the context of ACP (Agentic Commerce Protocol, co-developed by OpenAI and Stripe), a structurally distinct protocol.
No evidence found of PayPal implementing NLWeb or participating in Microsoft's NLWeb launch program. Named launch partners identified in coverage include TripAdvisor, Shopify, Eventbrite, Hearst, and O'Reilly — none of which is PayPal. PayPal's developer surface is payment-processing focused and does not align with NLWeb's schema.org/content-discovery use case.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence that PayPal has implemented or announced WebMCP (Google's experimental Chrome browser-layer agent API). PayPal's developer surface is focused on a remote MCP server (documented at developer.paypal.com/tools/mcp-server/), which is a distinct protocol. WebMCP launch-partner coverage in search results names no PayPal involvement; the protocol remains a Google/Chrome preview-stage experiment with no confirmed consumer travel or payments vendor adoptions identified.
No evidence that PayPal (paypal.com) has confirmed x402 support or participation. The x402 Foundation's 22-organization launch list (per Eco's documentation) names PPRO — a PayPal-affiliated B2B payments subsidiary — but not PayPal itself. PayPal is also listed as a Google AP2 partner (a separate agentic payments protocol), and has a PYUSD/Coinbase partnership around stablecoin adoption, but neither constitutes x402 adoption. Confirmed x402 launch partners include Coinbase, Cloudflare, Stripe, Visa, Mastercard, AWS, Google, Circle, and Shopify.
Enables in-chat product discovery and PayPal wallet-based checkout within ChatGPT conversations; supports OpenAI Instant Checkout via PayPal's delegated payments API, with PayPal handling merchant routing, payment validation, and transaction orchestration for its global merchant network.
PayPal has a confirmed listing in the ChatGPT Apps directory at https://chatgpt.com/apps/paypal/asdk_app_6969249b1a948191a1a1e32116504509, identifiable by the 'asdk_' prefix. The partnership was announced October 28, 2025 via PayPal's official newsroom, with full merchant catalog rollout (product discovery for apparel, fashion, beauty, home improvement, electronics) planned for 2026. This is a genuine Apps SDK integration — not merely the underlying ACP/Agentic Commerce Protocol arrangement — as confirmed by the live directory listing.
Primary payment processing REST API covering order creation and capture, payment authorization, payouts, subscriptions, invoicing, disputes, refunds, and vault/card storage; self-serve credentials via developer.paypal.com dashboard for both sandbox and live environments
PayPal's proprietary REST API is fully publicly documented at developer.paypal.com/api/rest/ and covers a broad surface: orders, payments, payouts, subscriptions, invoicing, disputes, and webhooks. Credentials (client ID + secret) are self-issued via the developer dashboard with no partner-program gate required. A separate legacy NVP/SOAP API (documented at developer.paypal.com/api/nvp-soap/) also remains supported but is explicitly deprecated for new integrations.
Legacy Name-Value Pair (NVP) and SOAP API for classic payment operations (Express Checkout, DoDirectPayment, etc.); explicitly deprecated for new integrations but still actively supported for existing integrations
PayPal's NVP/SOAP interface is documented at developer.paypal.com/api/nvp-soap/ and predates the REST API; PayPal's own documentation labels it a legacy API and directs new integrations to the REST surface. Existing integrations remain supported. This is a structurally distinct interface from the REST API — different auth mechanism, different wire format, different endpoint URLs (api-3t.paypal.com / api.paypal.com).
Two distinct llms.txt files published: paypal.com/llms.txt covers consumer-facing features (payments, money transfers, account management) with version 1.1.8 as of January 2026; developer.paypal.com/llms.txt covers developer/API integration documentation with guidance on navigating PayPal's REST API and integration guides for LLM consumers.
PayPal publishes two separate, publicly accessible llms.txt files: one at https://www.paypal.com/llms.txt (consumer product scope, v1.1.8, updated January 2026) and one at https://developer.paypal.com/llms.txt (developer/API documentation scope, with guidance for LLMs on accessing markdown versions of docs). No AGENTS.md or /.well-known/agent files were found. Both files self-identify as part of the proposed llms.txt standard.
Summary
Has agent interface: true
Pursue integration via PayPal's publicly documented REST API (developer.paypal.com/api/rest/) using self-serve OAuth 2.0 credentials, or via the confirmed ChatGPT Apps SDK listing for in-chat checkout flows. For agentic protocol integrations (A2A, ACP, AP2), a Google Cloud or OpenAI partnership relationship is required — contact those platform partners rather than PayPal directly to initiate access.
AgentContext
Verified discrepancies
Vendor claim: PayPal's published fee pages describe currency conversion as a straightforward service; the platform presents transaction totals during checkout without prominently itemizing any additional spread charged on top of the base exchange rate.
What actually happens: Consumer complaints filed with the CFPB and FTC, and a 2025–2026 consolidated class action, allege that PayPal applies a 3–4% markup above the base exchange rate on currency conversions that is not clearly itemized to the user at the point of transaction. Separately, PayPal successfully defeated a CFPB rule that would have required it to disclose digital-wallet fees in a standardized format, leaving the existing checkout disclosure gaps in place.
Agent guidance: For any cross-currency transaction on PayPal, do not treat the displayed transaction total as the final settled amount. Before confirming, explicitly check PayPal's current fee schedule for the applicable currency conversion spread (historically 3–4% above mid-market rate), calculate the expected markup, and surface the estimated all-in cost to the user for approval prior to completing the transaction.
- A 2026 class action lawsuit summary describes high-volume CFPB and FTC complaints alleging PayPal imposes currency conversion markups of 3–4% above the base exchange rate that are not clearly itemized at the moment of transaction.
- A federal court ruled in April 2024 that PayPal was not required to comply with a CFPB rule mandating standardized fee disclosures for digital wallets, leaving PayPal's existing checkout fee presentation practices in place.
- The New Hampshire Attorney General announced a $1.75 million settlement with PayPal over unfair and deceptive practices, including misrepresentation of consumer protections — corroborating a broader documented pattern of disclosure failures on the platform.
Vendor claim: PayPal's Seller Protection program is presented as covering sellers against 'Item Not Received' (INR) claims, and the platform labels qualifying transactions as 'eligible' for Seller Protection on the Transaction Details page, implying protection applies to those transactions.
What actually happens: Effective January 16, 2024, PayPal formally excluded from Seller Protection any INR claim where the buyer bypasses PayPal's own resolution system and instead files a chargeback directly with their card issuer (an 'external chargeback') for card-funded transactions. A transaction marked 'eligible' on the Transaction Details page does NOT guarantee Seller Protection if the dispute is escalated externally to the card network. Sellers lose the chargeback dispute and bear the loss despite the 'eligible' label.
Agent guidance: When completing or advising on a sale transaction through PayPal on behalf of a seller, do not treat a transaction's 'eligible' Seller Protection label as guaranteeing protection against an Item Not Received dispute. Explicitly warn the seller that if the buyer funds via credit or debit card and then files a chargeback with the card issuer rather than through PayPal's Resolution Center, Seller Protection will not apply regardless of the 'eligible' status shown—the card issuer's decision will control the outcome. For high-value or high-risk shipments, advise the seller to require signature confirmation and retain all proof-of-delivery documentation, as this is their only recourse in the external chargeback scenario.
- PayPal's own Seller Protection legal page states that INR claims 'that result from buyers filing chargeback claims with their issuers for card-funded transactions are not eligible for PayPal's Seller Protection,' confirming the exclusion is in the live policy.
- PayPal's official help article explicitly confirms: 'Seller Protection will no longer apply to transactions received after January 16, 2024, where that transaction is subject to a card Issuer Chargeback... for INR,' while noting PayPal will still use seller information to contest the chargeback with the issuer—but the final decision rests with the card issuer.
- Independent analysis documents that the previous policy protected sellers from INR card chargebacks as long as the transaction was marked 'eligible,' and characterizes the January 2024 change as a 'major change in policy that could leave unsuspecting sellers on the hook for chargebacks they would have previously been protected from paying.'
Vendor claim: PayPal presents itself as a general-purpose payment platform capable of sending and receiving money, paying for goods and services, and processing transactions across a wide range of categories. The checkout and payment flows do not surface account-level sending limits or categorical transaction restrictions to users before they attempt a payment.
What actually happens: PayPal imposes sending and withdrawal limits on unverified accounts (and can impose them dynamically on verified accounts) that are not disclosed at the point of initiating a transaction. Account limitations — including full or partial freezes that block transaction completion — can be applied mid-flow without prior notice to the transacting party. Separately, PayPal's Acceptable Use Policy prohibits entire categories of goods and services transactions that are not surfaced to payers during checkout; a payment attempt in a restricted category may be declined or reversed after funds are committed. CFPB complaint data and active federal class action proceedings confirm that consumers routinely encounter these constraints only after attempting or completing a transaction.
Agent guidance: Before initiating any PayPal transaction on behalf of a user, an agent should: (1) verify that the account is fully verified and has no active limitations via PayPal's account summary page before committing to a payment; (2) cross-check the goods or services category against PayPal's published Acceptable Use Policy at https://www.paypal.com/us/legalhub/acceptableuse-full; and (3) if a transaction fails or is held mid-flow, treat the outcome as unresolved rather than completed — do not assume the payment succeeded without explicit confirmation from the recipient or PayPal's transaction detail page.
- PayPal's own User Agreement discloses sending and withdrawal limits that apply to unverified accounts and may be imposed on verified accounts, but these limits are not surfaced in the payment initiation flow itself.
- PayPal's Acceptable Use Policy lists prohibited goods and services categories; transactions in these categories may be declined or reversed, but the policy is not presented to payers during checkout.
- A lawfold.com report on 2026 class action proceedings notes CFPB and FTC complaints from 2021–2024 specifically citing frozen accounts with funds held for up to 180 days and undisclosed transaction fees, with federal cases active in the Northern District of California.
Human handoff required for
Escalate to a human before confirming any cross-currency PayPal transaction where the displayed checkout total does not explicitly itemize the currency conversion spread, so the user can approve the estimated all-in cost (including the historically 3–4% markup above mid-market rate) before funds are committed.
- An active 2025–2026 consolidated class action and high-volume CFPB/FTC complaints allege that PayPal applies a 3–4% markup above the base exchange rate on currency conversions without clearly disclosing it at the point of transaction.
- A 2024 federal court ruling confirmed PayPal is not required to follow a CFPB standardized fee-disclosure rule for digital wallets, leaving checkout disclosure gaps unaddressed.
Escalate to a human when a PayPal seller transaction marked 'eligible' for Seller Protection faces an Item Not Received dispute where the buyer has funded via credit or debit card and may file or has filed a chargeback directly with their card issuer rather than through PayPal's Resolution Center, because Seller Protection explicitly does not apply in that scenario regardless of the 'eligible' label.
- Effective January 16, 2024, PayPal's policy formally excluded from Seller Protection any INR claim where the buyer files a chargeback with the card issuer instead of using PayPal's own resolution system, meaning a transaction labeled 'eligible' can still result in the seller bearing the full loss.
- Independent merchant-focused reporting and PayPal's own help documentation confirm that sellers lose external chargeback disputes even when their transaction detail page shows 'eligible' for Seller Protection.
Escalate to a human when a PayPal payment attempt fails, is held, or returns an ambiguous status mid-flow — including situations where an account limitation or freeze is encountered, or where the goods/services category may be restricted under PayPal's Acceptable Use Policy — because the transaction outcome cannot be treated as confirmed or failed without explicit verification from the recipient or PayPal's transaction detail page.
- CFPB complaints and active 2025–2026 federal class action proceedings cite mid-transaction account freezes and undisclosed sending limits as recurring harms where consumers discover the constraint only after attempting or completing a transaction.
- PayPal's Acceptable Use Policy prohibits entire categories of transactions that are not surfaced during checkout, meaning a payment in a restricted category may be declined or reversed after funds are committed.
Five categories were checked for PayPal. Discrepancy_pricing: findings were present — an active class action and CFPB/FTC complaints document an undisclosed 3–4% currency conversion markup, and a 2024 court ruling confirmed PayPal is exempt from standardized fee-disclosure requirements, leaving the gap in place. Discrepancy_availability: no finding — PayPal is a payment processor rather than a marketplace with bookable inventory, and no verified bait-and-switch or ghost-inventory pattern was identified; scheduled merchant fee changes were found but do not constitute point-of-transaction availability discrepancies. Discrepancy_identity: no finding — CFPB enforcement history relates to a 2015 PayPal Credit matter, not to merchant-of-record ambiguity or counterparty confusion in current transaction flows. Discrepancy_policy: findings were present — PayPal's post-January 2024 Seller Protection exclusion for external chargebacks creates a verified gap between the 'eligible' label shown to sellers and actual protection coverage. Discrepancy_undisclosed_constraint: findings were present — PayPal's undisclosed sending limits, dynamic account freezes, and Acceptable Use Policy category restrictions are confirmed by CFPB complaint data and active federal class action proceedings as recurring mid-transaction harms not surfaced during payment initiation.