PayPal vs Stripe for AI agents
As of 2 Nov 2026, Stripe gets an AI agent further than PayPal: L3 (Does the work) against L1 (Needs a person).
AgentDrives StudyPayPal: 4 drives, last 2 Nov 2026 (80 attempts). Stripe: 3 drives, last 2 Nov 2026 (129 attempts). Method v50.
- Find Docs it can act on
- Get in Can't sign up
- Use Work not reached
- Pay Payment not reached
- Leave Leaving not reached
Stopped at sign-up: blocked. Next: let an agent sign up on its own
Our agent stopped at sign-up: the live sign-up pages returned a DataDome block page (403, "You have been blocked"), the sandbox sign-up asks for a phone number, and the Braintree sandbox form shows a visible reCAPTCHA. Credentials and the first call were not reached: REST keys come from the developer dashboard, which needs a paypal.com login. The docs work well for agents: llms.txt, Markdown pages and OpenAPI specs on GitHub. No work was done. Our MCP sign-in registered an OAuth client that has no delete endpoint.
Driven 2 Nov 2026 · The drive and its evidence- Find Docs it can act on
- Get in Try first, claim later
- Use 67% of the work
- Pay No payment made
- Leave Nothing to cancel
In on its own; 67% of the work done. Next: do 80% of the core work (now 67%)
A documented CLI command made an anonymous claimable sandbox and a restricted key, with no form, email check or card. Claiming the sandbox in the Dashboard showed a visible hCaptcha picture puzzle, and our agent made no full account. With the key it created customers, products, prices, PaymentIntents, payment links, Checkout sessions, subscriptions and invoices through the API, each read back. Terminal, usage billing and Connect sat outside that key. No agent route deletes an unclaimed sandbox, and the key hit a request limit with no word on when to retry.
Driven 2 Nov 2026 · The drive and its evidenceThe two summaries: written with AI from each product's drive.
Step by step
What our agent got done at each step, and what it saw there.
Find
PayPalDocs it can act on
Done without a browser: developer.paypal.com/llms.txt (10 section indexes), .md versions of the pages, an API reference per product, and OpenAPI 3.0.x specs in PayPal's GitHub repo linked from the docs. There is no llms.txt at www.paypal.com.
StripeDocs it can act on
Docs read without a browser: docs.stripe.com/llms.txt (525 links) and stripe.com/llms.txt, Markdown pages (.md and Accept: text/markdown on the pages tried), the public OpenAPI 3.0.0 spec (612 operations), and an MCP server at mcp.stripe.com that answers MCP (the 28 Jul 2026 spec).
Get in
PayPalCan't sign up
Blocked. www.paypal.com/bizsignup/ and /signup returned a DataDome block page ("You have been blocked. We couldn't load the security challenge.", HTTP 403), both in the browser and without a browser. The sandbox business sign-up asks a phone number, and its banner says it does not create an account.
StripeTry first, claim later
The sandbox command returns a restricted key, used for API, CLI and as Bearer on MCP. The docs give no API or CLI route to create, scope or revoke a key: that is Dashboard-only.
Use
PayPalWork not reached
Not reached: no account and no token.
Stripe67% of the work
Created a customer, products, prices, PaymentIntents, payment links, Checkout sessions, subscriptions and invoices without a browser, each read back.
Pay
PayPalPayment not reached
StripeNo payment made
No self-serve purchase.
Leave
PayPalLeaving not reached
One OAuth client registration stays: our MCP sign-in registered a dynamic client at mcp.sandbox.paypal.com/register, and there is no endpoint to delete it. No PayPal account or data was created, so there was no account to delete.
StripeNothing to cancel
No agent route deletes an unclaimed sandbox: `stripe sandboxes delete` needs a live-account `stripe login`, there is no API or MCP delete, and the Dashboard is behind the claim. Per the docs, Stripe deletes an unclaimed sandbox after 60 days. Test objects were left in it (the API key was throttled and MCP has no delete tools).
Where each one stops
PayPalStopped at sign-up: blocked
StripeIn on its own; 67% of the work done
| Checkpoint | PayPal | Stripe |
|---|---|---|
| Docs | On its own | On its own |
| Sign up | Blocked | Not needed |
| Verify | Not reached | Not needed |
| Key | Not reached | On its own |
| First call | Not reached | On its own |
| First action | Not reached | On its own |
| Pay | Not reached | Not tried |
| Cancel | Not reached | Not needed |
| Delete | Not reached | Blocked |
On its own, or in a browser
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| PayPal | Stripe | |
|---|---|---|
| Passed on its own | 1 | 4 |
| Passed in a browser | 0 | 0 |
| Needed a person | 0 | 0 |
| Blocked | 1 | 1 |
| Work done | Not measured | 67% of the core |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | Yes | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed
| PayPal | Stripe | |
|---|---|---|
| Bot check | DataDome stopped it at sign up, with a visible challenge | hCaptcha stopped one way in at sign up; it got in another way |
| Wall type | A check of our network and browser | A challenge on the form |
| First wall | Sign-up returned a block page served by DataDome | None |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connected from and its browser, not a person. Our agent, working on its own from a data center, didn't get through; the owner can open the check to agents. How agents in a person's own browser fare isn't measured yet. A challenge on the form: It asks every visitor to prove they are human. Our agent doesn't solve these, and its signature didn't change that: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores
| PayPal | Stripe | |
|---|---|---|
| Level | L1 · Needs a person | L3 · Does the work |
| Holds up | Not measured | 84 of 100, good |
| Docs match | Not measured | 84 of 100, fair |
| Standards | MCP client registration (behind) | MCP discovery (current) · MCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind) |
| Security | Reported privately to the owner | No review in this drive |
Pay, cancel and delete
| PayPal | Stripe | |
|---|---|---|
| Pay | Payment not reached | No payment made |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | Blocked |
How each one takes payment
- PayPal: Payment not reached.
- Stripe: No payment made: paying needs an account.
PayPal vs Stripe: the short answers
Which can an AI agent use, PayPal or Stripe?
Stripe gets an AI agent further than PayPal: L3 (Does the work) against L1 (Needs a person). With PayPal our agent was stopped at sign-up (blocked); with Stripe it got in on its own and did 67% of the work. Both driven 2 Nov 2026.
Can an AI agent sign up for PayPal and Stripe on its own?
PayPal: no, blocked. Stripe: not needed.
Do PayPal and Stripe have an MCP server?
PayPal: yes (official). Stripe: yes (official).
Can an AI agent delete its PayPal or Stripe account?
PayPal: not reached. Stripe: blocked.
The drives and the category
Put your own shortlist side by side
A Tool comparison drives the tools you're choosing between and shows which ones your agents can use.