Rank #1 of 4 in Mobile & In-Person Payments
vs Square
vs SumUp
vs Adyen In-Person PaymentsProducts
Stripe, product by product →Stripe ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| Payments | Online Payments | #1/10 | 55/100 | 89/100 |
| Terminalthis page | Mobile & In-Person Payments | #1/4 | 32/100 | 59/100 |
| Atlas | Startup Legal & Incorporation | #6/7 | 11/100 | 32/100 |
| Clerkyacquired | Startup Legal & Incorporation | #4/7 | 14/100 | 37/100 |
| Billing | Billing & Subscriptions | #3/7 | 28/100 | 65/100 |
| Metronomeacquired | Billing & Subscriptions | #5/7 | 21/100 | 28/100 |
| Connect | Marketplace & Platform Payments | #2/6 | 31/100 | 65/100 |
| Radar | Payment Fraud Prevention | #2/5 | 22/100 | 50/100 |
| Tax | Sales Tax Automation | #1/6 | 22/100 | 43/100 |
| TaxJaracquired | Sales Tax Automation | #6/6 | 13/100 | 26/100 |
| Issuing | Card Issuing Platforms | #1/5 | 33/100 | 65/100 |
| Treasury | Banking as a Service | #4/6 | 17/100 | 44/100 |
| Identity | Identity Verification & KYC | #3/6 | 24/100 | 47/100 |
| Financial Connections | Banking Data APIs | #4/7 | 22/100 | 54/100 |
| Crypto & Stablecoins | Stablecoin Payments | #6/6 | 19/100 | 39/100 |
| Agentic Commerce | Agentic Commerce | #1/7 | 37/100 | 80/100 |
Not yet judged (10 — no arena where they compete): Invoicing · Capital · Revenue Recognition · Sigma · Data Pipeline · Managed Payments · Lemon Squeezy · Directory · Projects · Climate
Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Accept payments — stories about accept payments in this arenaAccept paymentsevidence →
Stories about accept payments in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Catalog receipts — stories about catalog receipts in this arenaCatalog receiptsevidence →
Stories about catalog receipts in this arena
Checkout integration — stories about checkout integration in this arenaCheckout integrationevidence →
Stories about checkout integration in this arena
Disputes refunds — stories about disputes refunds in this arenaDisputes refundsevidence →
Stories about disputes refunds in this arena
Hardware fleet — stories about hardware fleet in this arenaHardware fleetevidence →
Stories about hardware fleet in this arena
Offline reliability — stories about offline reliability in this arenaOffline reliabilityevidence →
Stories about offline reliability in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Payouts reconciliation — stories about payouts reconciliation in this arenaPayouts reconciliationevidence →
Stories about payouts reconciliation in this arena
Pci compliance — stories about pci compliance in this arenaPci complianceevidence →
Stories about pci compliance in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Stripe Terminal stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Accept payments — stories about accept payments in this arenaAccept payments
Stories about accept payments in this arena
Sign up, get approved, and order hardware from the dashboard so I am taking in-person payments the same week
~5/10
Payment methods
Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a reader
✓9/10
Configure tipping prompts (percentages, smart amounts, custom tips) collected on the reader or terminal
✓8/10
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓9/10
unlocks → Scoped API keys · Versioning policy · Full data export
Subscribe to events via webhooks
✓7/10
Build against official SDKs
✓8/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
~6/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓8/10
unlocks → Interactive API docs
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
✓7/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—0/10
Operate the product with natural-language commands
~3/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
—–
Set up automations that run autonomously in the background
~4/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Catalog receipts — stories about catalog receipts in this arenaCatalog receipts
Stories about catalog receipts in this arena
Checkout integration — stories about checkout integration in this arenaCheckout integration
Stories about checkout integration in this arena
Disputes refunds — stories about disputes refunds in this arenaDisputes refunds
Stories about disputes refunds in this arena
Hardware fleet — stories about hardware fleet in this arenaHardware fleet
Stories about hardware fleet in this arena
Have an agent provision a new location end-to-end via API — creating the location and registering its readers
✓7/10
Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotely
✓8/10
Run multiple locations with per-location devices, settings, and reporting
~6/10
Pair a card reader with the POS app or register it to my account and take a payment within minutes
✓8/10
Offline reliability — stories about offline reliability in this arenaOffline reliability
Stories about offline reliability in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Payouts reconciliation — stories about payouts reconciliation in this arenaPayouts reconciliation
Stories about payouts reconciliation in this arena
Pci compliance — stories about pci compliance in this arenaPci compliance
Stories about pci compliance in this arena
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Sorted by importance (agentic first) (high → low) · 52/52 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none± | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 7/10 | Cclaimed | |
Accept chip, contactless, and mobile-wallet (Apple Pay / Google Pay) payments in person C Payment methods | merchant-ops user | Accept payments — stories about accept payments in this arenaAccept payments | 3 | full | 9/10 | Xcommunity | |
Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a reader C Tap to pay | founder | Accept payments — stories about accept payments in this arenaAccept payments | 3 | full | 9/10 | Cclaimed | |
Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven API C Custom checkout | developer | Checkout integration — stories about checkout integration in this arenaCheckout integration | 3 | full | 9/10 | Xcommunity | |
Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotely C Fleet api | developer | Hardware fleet — stories about hardware fleet in this arenaHardware fleet | 3 | full | 8/10 | Xcommunity | |
Have an agent provision a new location end-to-end via API — creating the location and registering its readers C Ai fleet ops | ai-native user | Hardware fleet — stories about hardware fleet in this arenaHardware fleet | 3 | full | 7/10 | Tprobed | |
Have an agent pull transactions and payouts via API and reconcile daily takings into my ledger C Reconciliation | ai-native user | Payouts reconciliation — stories about payouts reconciliation in this arenaPayouts reconciliation | 3 | partial | 6/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Sign up, get approved, and order hardware from the dashboard so I am taking in-person payments the same week C Onboarding | founder | Accept payments — stories about accept payments in this arenaAccept payments | 3 | partial | 5/10 | Cclaimed | |
Have an agent monitor dispute deadlines via API or webhooks and draft evidence responses for my review G Disputes | ai-native user | Disputes refunds — stories about disputes refunds in this arenaDisputes refunds | 3 | partial | 4/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Configure tipping prompts (percentages, smart amounts, custom tips) collected on the reader or terminal C Tipping | merchant-ops user | Accept payments — stories about accept payments in this arenaAccept payments | 2 | full | 8/10 | Cclaimed | |
Embed in-person payments into my own iOS or Android app with official mobile SDKs G Custom checkout | developer | Checkout integration — stories about checkout integration in this arenaCheckout integration | 2 | full | 8/10 | Xcommunity | |
Issue full or partial refunds back to the original card from the point of sale, dashboard, or API C Refunds | merchant-ops user | Disputes refunds — stories about disputes refunds in this arenaDisputes refunds | 2 | full | 8/10 | Cclaimed | |
Keep taking card payments when the internet drops, with transactions stored and forwarded when connectivity returns G Offline | merchant-ops user | Offline reliability — stories about offline reliability in this arenaOffline reliability | 2 | full | 8/10 | Cclaimed | |
Pair a card reader with the POS app or register it to my account and take a payment within minutes C Readers | merchant-ops user | Hardware fleet — stories about hardware fleet in this arenaHardware fleet | 2 | full | 8/10 | Xcommunity | |
Test my in-person integration end-to-end with a simulated reader or test card environment before going live C Testing | developer | Checkout integration — stories about checkout integration in this arenaCheckout integration | 2 | full | 8/10 | Tprobed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 7/10 | Xcommunity | |
Run multiple locations with per-location devices, settings, and reporting C Multi location | merchant-ops user | Hardware fleet — stories about hardware fleet in this arenaHardware fleet | 2 | partial | 6/10 | Cclaimed | |
Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automations G Payment events | developer | Checkout integration — stories about checkout integration in this arenaCheckout integration | 2 | partial | 6/10 | Cclaimed | |
Get notified of chargebacks and submit dispute evidence before the deadline C Disputes | merchant-ops user | Disputes refunds — stories about disputes refunds in this arenaDisputes refunds | 2 | partial | 5/10 | Cclaimed | |
Reconcile daily takings against payouts with itemized transaction and fee reports C Reconciliation | merchant-ops user | Payouts reconciliation — stories about payouts reconciliation in this arenaPayouts reconciliation | 2 | partial | 4/10 | Cclaimed | |
See when each payout lands and speed it up (next-day or instant) when I need the cash C Payouts | founder | Payouts reconciliation — stories about payouts reconciliation in this arenaPayouts reconciliation | 2 | partial | 4/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 3/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Keep my PCI scope minimal because card data is captured end-to-end by certified readers and vendor systems, with vendor guidance on my remaining obligations C Pci | developer | Pci compliance — stories about pci compliance in this arenaPci compliance | 2 | none | untested | none yet | |
Manage an item catalog with inventory counts that stay in sync across registers and channels C Catalog | merchant-ops user | Catalog receipts — stories about catalog receipts in this arenaCatalog receipts | 2 | n/a | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Split a single sale across multiple payment methods or payers C Payment methods | merchant-ops user | Accept payments — stories about accept payments in this arenaAccept payments | 2 | none | untested | none yet | |
Issue digital (email/SMS) or printed receipts that meet card-network requirements C Receipts | merchant-ops user | Catalog receipts — stories about catalog receipts in this arenaCatalog receipts | 1 | full | 8/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 27 stories with headroom
What would move Stripe Terminal’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
Evidence shows Stripe offers an MCP server so external AI agents can call the Stripe API, and general 'Agents and AI on Stripe' agent-first tooling, but nothing indicates Stripe Terminal itself embeds a built-in AI assistant that a user can delegate tasks to within the product.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Stripe Terminal's evidence pack covers payments, hardware, receipts, offline mode, and Connect integration, but contains no mention of bulk data export in open formats (e.g., CSV/JSON exports of transaction/customer data) or any facility for a user to extract all their data and migrate away from the platform.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
No evidence that Stripe Terminal surfaces AI-generated insights or suggestions from transaction/business data inside its dashboard or SDKs.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
The evidence pack covers Terminal's POS/hardware features, MCP server availability, and general agent commerce framing, but contains no mention of restricted/scoped API keys, granular permissions, or any mechanism for issuing least-privilege credentials specifically for an AI agent using Terminal's API.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
The evidence pack shows extensive Terminal docs, SDKs, and an OpenAPI spec repo, but nothing describes an interactive API reference with runnable/executable examples (e.g., a live 'try it' console); a probe even shows openapi.json endpoints returning 404 at the docs site, suggesting no readily discoverable interactive spec integration.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
The evidence pack includes general Terminal docs, SDKs, CLI, and MCP references, but nothing documents API versioning conventions or a deprecation policy for the Stripe API/Terminal endpoints (e.g.
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
partialq3/10moves Built-in AIimpact 21
Missing: terminal-specific natural-language command support, agent-driven reader/payment control examples, independent corroboration of MCP-driven Terminal operations.
Automation depth — how much of the product can run unattendedPerform bulk operations across many items at once
nonemoves PA Scoreimpact 20
Missing: batch/bulk API endpoints for Terminal, evidence of programmatic bulk operations on payments or readers, AI-agent-oriented bulk automation examples.
Showing the top 8 of 27 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map13 surfaces · 34 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Terminal docs21 stories
- Sign up, get approved, and order hardware from the dashboard so I am taking in-person payments the same week
- Accept chip, contactless, and mobile-wallet (Apple Pay / Google Pay) payments in person
- Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a reader
- Configure tipping prompts (percentages, smart amounts, custom tips) collected on the reader or terminal
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Test against a sandbox environment without touching production data
- Issue digital (email/SMS) or printed receipts that meet card-network requirements
- Embed in-person payments into my own iOS or Android app with official mobile SDKs
- Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven API
- Test my in-person integration end-to-end with a simulated reader or test card environment before going live
- Issue full or partial refunds back to the original card from the point of sale, dashboard, or API
- Have an agent provision a new location end-to-end via API — creating the location and registering its readers
- Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotely
- Run multiple locations with per-location devices, settings, and reporting
- Pair a card reader with the POS app or register it to my account and take a payment within minutes
- Keep taking card payments when the internet drops, with transactions stored and forwarded when connectivity returns
- Do everything through the API that I can do in the UI
- Reconcile daily takings against payouts with itemized transaction and fee reports
Hacker News8 stories
- Accept chip, contactless, and mobile-wallet (Apple Pay / Google Pay) payments in person
- Drive the product through a documented public API
- Build against official SDKs
- Embed in-person payments into my own iOS or Android app with official mobile SDKs
- Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven API
- Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotely
- Pair a card reader with the POS app or register it to my account and take a payment within minutes
- Do everything through the API that I can do in the UI
Webhooks docs8 stories
- Drive the product through a documented public API
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automations
- Have an agent monitor dispute deadlines via API or webhooks and draft evidence responses for my review
- Get notified of chargebacks and submit dispute evidence before the deadline
- Have an agent pull transactions and payouts via API and reconcile daily takings into my ledger
MCP docs7 stories
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Have an agent monitor dispute deadlines via API or webhooks and draft evidence responses for my review
- Have an agent provision a new location end-to-end via API — creating the location and registering its readers
- Have an agent pull transactions and payouts via API and reconcile daily takings into my ledger
Agents docs5 stories
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Have an agent monitor dispute deadlines via API or webhooks and draft evidence responses for my review
CLI docs5 stories
Disputes docs5 stories
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automations
- Have an agent monitor dispute deadlines via API or webhooks and draft evidence responses for my review
- Get notified of chargebacks and submit dispute evidence before the deadline
GitHub README4 stories
Refunds docs4 stories
- Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automations
- Issue full or partial refunds back to the original card from the point of sale, dashboard, or API
- Do everything through the API that I can do in the UI
- Have an agent pull transactions and payouts via API and reconcile daily takings into my ledger
Payouts docs3 stories
OpenAPI spec2 stories
Stripe CLI docs2 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
11 of 21 testable claims verified · 0 contradicted → integrity 52/100
26 distinct capability claims found in Stripe Terminal’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
11
Verified
10
Unverified
0
Contradicted
13
Undersold
Verified (13)
“Build a custom POS integration using API-based approach plus SDKs for Android, iOS, JavaScript, and React Native”
Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven APIfullproof ↗
“Build a custom POS integration using API-based approach plus SDKs for Android, iOS, JavaScript, and React Native”
Embed in-person payments into my own iOS or Android app with official mobile SDKsfullproof ↗
“Register a reader by serial number remotely, before physically having it in hand”
Pair a card reader with the POS app or register it to my account and take a payment within minutesfullproof ↗
“Built-in simulated card reader lets developers build and test without physical hardware”
Test my in-person integration end-to-end with a simulated reader or test card environment before going livefullproof ↗
“Terminal JS SDK can be used as an ES module”
“Register smart readers via registration code, serial number, or order number”
Pair a card reader with the POS app or register it to my account and take a payment within minutesfullproof ↗
“Order, register, configure, and monitor readers from the Dashboard”
Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotelyfullproof ↗
“Deploy a custom Android POS app directly onto Stripe smart readers”
Embed in-person payments into my own iOS or Android app with official mobile SDKsfullproof ↗
“Accept contactless card/mobile-wallet payments via SDK on a compatible iPhone or Android device”
Accept chip, contactless, and mobile-wallet (Apple Pay / Google Pay) payments in personfullproof ↗
“MCP server lets AI agents interact with the Stripe API and search Stripe's knowledge base”
“Agent-first developer tools support building agentic commerce and usage-based billing for AI features”
Point an agent at llms.txt or agent-oriented docsfullproof ↗
“Stripe CLI lets you build, test, and manage your integration from the terminal”
“Publishes OpenAPI specifications for Stripe's API”
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Unverified (12)
“Accept contactless in-person payments using Tap to Pay on a compatible iPhone, no reader required”
Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a readerfullproof ↗
“Manage multiple readers across sites using locations and zones”
Run multiple locations with per-location devices, settings, and reportingpartialproof ↗
“Store payments locally on device/reader during connectivity loss and auto-forward once reconnected”
Keep taking card payments when the internet drops, with transactions stored and forwarded when connectivity returnsfullproof ↗
“Card reader can suggest tip amounts to customers before collecting payment”
Configure tipping prompts (percentages, smart amounts, custom tips) collected on the reader or terminalfullproof ↗
“Use prebuilt email receipts or generate custom on-brand receipts from API receipt data”
Issue digital (email/SMS) or printed receipts that meet card-network requirementsfullproof ↗
“Collect tips from customers either before or after authorizing a payment”
Configure tipping prompts (percentages, smart amounts, custom tips) collected on the reader or terminalfullproof ↗
“Issue refunds using either the Refunds API or the Dashboard”
Issue full or partial refunds back to the original card from the point of sale, dashboard, or APIfullproof ↗
“Must provide customers a physical or email receipt option when accepting Terminal payments”
Issue digital (email/SMS) or printed receipts that meet card-network requirementsfullproof ↗
“Register an HTTPS webhook endpoint to receive real-time event data from Stripe”
“Register an HTTPS webhook endpoint to receive real-time event data from Stripe”
Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automationspartialproof ↗
“Instant Payouts send funds to your bank account anytime, usually within 30 minutes”
See when each payout lands and speed it up (next-day or instant) when I need the cashpartialproof ↗
“Smart Disputes automates evidence collection and submission for eligible disputes”
Get notified of chargebacks and submit dispute evidence before the deadlinepartialproof ↗
Undersold (13)
Sign up, get approved, and order hardware from the dashboard so I am taking in-person payments the same weekpartialproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Test against a sandbox environment without touching production datafullproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Have an agent monitor dispute deadlines via API or webhooks and draft evidence responses for my reviewpartialproof ↗
Have an agent provision a new location end-to-end via API — creating the location and registering its readersfullproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Read the product's source under an open licensepartialproof ↗
Have an agent pull transactions and payouts via API and reconcile daily takings into my ledgerpartialproof ↗
Reconcile daily takings against payouts with itemized transaction and fee reportspartialproof ↗
Claims outside our story set (3)
Real capability claims found in Stripe Terminal’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Integrate Terminal into existing stack via no-code third-party POS, hardware, and commerce integrations”
source ↗“Manage in-person and online payments together in a unified Dashboard”
source ↗“Use Terminal with Connect to support connected accounts / platforms”
source ↗
Business model
Per-transaction pricing (2.7% + 5¢ for in-person US cards) with no monthly fee; readers and smart terminals are bought outright from the dashboard.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)