Rank #2 of 4 in Mobile & In-Person Payments
Install
npm i -s squareShowcase


Products
Block, product by product →Block 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 |
|---|---|---|---|---|
| Square Payments | Online Payments | #3/10 | 43/100 | 71/100 |
| Square Point of Salethis page | Mobile & In-Person Payments | #2/4 | 32/100 | 58/100 |
| Buzz | Team Chat | #3/5 | 26/100 | 28/100 |
Not yet judged (3 — no arena where they compete): Cash App · Afterpay · Square AI
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 Square 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
~4/10
Payment methods
Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a reader
✓8/10
Configure tipping prompts (percentages, smart amounts, custom tips) collected on the reader or terminal
~6/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
✓8/10
unlocks → Scoped API keys · Versioning policy · Official CLI
Subscribe to events via webhooks
✓8/10
Build against official SDKs
✓8/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
~6/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
✓8/10
Explore an interactive API reference with runnable examples
~4/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
~4/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
~3/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
~4/10
Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotely
—0/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
~6/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
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 | full | 8/10 | Tprobed | |
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 | 8/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± | 0/10 | ||
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 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
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 | partial | 6/10 | Tprobed | |
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 | 6/10 | Cclaimed | |
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 | partial | 4/10 | Tprobed | |
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 | 4/10 | Tprobed | |
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± | 3/10 | Tprobed | |
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 | |
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 | untested | none yet | |
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 | untested | none yet | |
Use an official CLI G Agent access | 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 | 8/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 | 8/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 | 8/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 | 8/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 | full | 7/10 | Tprobed | |
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 | 6/10 | Cclaimed | |
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 | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 4/10 | Cclaimed | |
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 | partial | 4/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 | 4/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 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | 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 | |
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 | Cclaimed | |
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 | full | 8/10 | Cclaimed | |
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 | partial | 6/10 | Cclaimed | |
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 | 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 | 6/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 | partial | 6/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 | |
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 | partial | 5/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 | 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 | 5/10 | Cclaimed | |
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 | partial | 5/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 | |
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 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 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 | |
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 | none | 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 | partial | 6/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 36 stories with headroom
What would move Square’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 Square offers an MCP server for external AI agents to call Square APIs (square-docs-14, square-probe-4), but this is the reverse of the story—no evidence of a built-in AI assistant inside Square's own product (Dashboard/POS) that users can delegate tasks to.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses AI training data usage, opt-out controls, or privacy policy language about model training for Square products; this is an applicable axis for any data-handling platform but no supporting documentation exists.
Hardware fleet — stories about hardware fleet in this arenaManage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotely
nonemoves PA Scoreimpact 30
The pack shows Square has physical hardware (Terminal API for payments, Tap to Pay) but no evidence of a device-fleet management API for registering devices, monitoring status, or remotely updating terminal/reader configuration — the only terminal-related doc (square-docs-26) covers payment/tip flows, not fleet administration.
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
Missing: any documentation of built-in AI analytics, insight dashboards, or suggestion features within Square's product surface.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
No evidence in the pack mentions an official Square CLI; the docs reference SDKs, APIs, sandbox, and an MCP server but nothing about a command-line tool for developers or AI-native workflows.
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 documents Square's APIs, SDKs, sandbox testing, and an MCP server, but contains no mention of OAuth scopes, restricted/scoped API keys, or any mechanism for issuing least-privilege credentials specifically for an AI agent.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Missing: explicit versioning documentation, deprecation/EOL policy, changelog or migration guides.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
partialq3/10moves Built-in AIimpact 21
Missing: evidence of a first-party automation/workflow engine, scheduling or trigger-action system, and confirmation that MCP server actions can run unattended in the background.
Showing the top 8 of 36 — 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 map7 surfaces · 34 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs31 stories
- 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
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Build against official SDKs
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Test against a sandbox environment without touching production data
- Define rules that trigger actions automatically on events
- Manage an item catalog with inventory counts that stay in sync across registers and channels
- 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
- Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automations
- Test my in-person integration end-to-end with a simulated reader or test card environment before going live
- 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 provision a new location end-to-end via API — creating the location and registering its readers
- 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
- Export all of my data in open formats and leave
- See when each payout lands and speed it up (next-day or instant) when I need the cash
- Have an agent pull transactions and payouts via API and reconcile daily takings into my ledger
- Reconcile daily takings against payouts with itemized transaction and fee reports
- 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
GitHub README9 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Test against a sandbox environment without touching production data
- Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven API
- Have an agent pull transactions and payouts via API and reconcile daily takings into my ledger
- 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
Us docs9 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
- Manage an item catalog with inventory counts that stay in sync across registers and channels
- Embed in-person payments into my own iOS or Android app with official mobile SDKs
- Pair a card reader with the POS app or register it to my account and take a payment within minutes
- See when each payout lands and speed it up (next-day or instant) when I need the cash
- Reconcile daily takings against payouts with itemized transaction and fee reports
- 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
llms.txt3 stories
OpenAPI spec3 stories
Hacker News3 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
3 of 16 testable claims verified · 0 contradicted → integrity 19/100
29 distinct capability claims found in Square’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
3
Verified
13
Unverified
0
Contradicted
18
Undersold
Verified (3)
“Process in-person or online payments using Square hardware or any internet-connected device”
Accept chip, contactless, and mobile-wallet (Apple Pay / Google Pay) payments in personfullproof ↗
“Provides a documented public API (e.g. payments.create) that developers can call directly to process payments”
Drive the product through a documented public APIfullproof ↗
“Official Square Model Context Protocol (MCP) server lets AI agents connect and use Square's tools”
Unverified (19)
“Accept contactless cards, Apple Pay, and other wallets using Tap to Pay directly on an iPhone, no extra hardware needed”
Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a readerfullproof ↗
“Official Mobile Payments SDK lets developers embed in-person card payments into their own iOS/Android apps”
Embed in-person payments into my own iOS or Android app with official mobile SDKsfullproof ↗
“Supports offline payments, storing transactions and forwarding them once connectivity is restored”
Keep taking card payments when the internet drops, with transactions stored and forwarded when connectivity returnspartialproof ↗
“Catalog design tools let sellers structure and manage their item catalog”
Manage an item catalog with inventory counts that stay in sync across registers and channelsfullproof ↗
“Inventory API lets developers track and update stock counts programmatically”
Manage an item catalog with inventory counts that stay in sync across registers and channelsfullproof ↗
“API and dashboard tools to update, retrieve, and review multi-location seller information, including creating new locations”
Run multiple locations with per-location devices, settings, and reportingpartialproof ↗
“Sellers can review and edit each location's information directly in the Square Dashboard”
Run multiple locations with per-location devices, settings, and reportingpartialproof ↗
“Dedicated flow to process disputes/chargebacks”
Get notified of chargebacks and submit dispute evidence before the deadlinepartialproof ↗
“Webhooks let developers subscribe to Square events (e.g. payment lifecycle) for automation”
Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automationspartialproof ↗
“Sandbox environment available to test integrations without touching live/production data”
Test against a sandbox environment without touching production datafullproof ↗
“Official TypeScript client library provides convenient access to Square APIs”
“Pre-built client libraries available in multiple languages for developers”
“Track inventory across the business”
Manage an item catalog with inventory counts that stay in sync across registers and channelsfullproof ↗
“Manage cash flow, including visibility into payouts”
See when each payout lands and speed it up (next-day or instant) when I need the cashpartialproof ↗
“Accounts can have multiple locations created beyond the default single location”
Run multiple locations with per-location devices, settings, and reportingpartialproof ↗
“List Payouts endpoint lets developers retrieve payout records for reconciliation”
Reconcile daily takings against payouts with itemized transaction and fee reportspartialproof ↗
“Supports collecting tips as money at checkout, with a separate tip screen before signature and custom tip amounts”
Configure tipping prompts (percentages, smart amounts, custom tips) collected on the reader or terminalpartialproof ↗
“Sellers can customize receipts with custom text fields (e.g. disclaimer, promotional message, thank-you note)”
Issue digital (email/SMS) or printed receipts that meet card-network requirementspartialproof ↗
“Tap to Pay on iPhone is offered as a distinct product/feature for contactless acceptance”
Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a readerfullproof ↗
Undersold (18)
Sign up, get approved, and order hardware from the dashboard so I am taking in-person payments the same weekpartialproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)partialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven APIfullproof ↗
Test my in-person integration end-to-end with a simulated reader or test card environment before going livepartialproof ↗
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 readerspartialproof ↗
Pair a card reader with the POS app or register it to my account and take a payment within minutespartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Have an agent pull transactions and payouts via API and reconcile daily takings into my ledgerfullproof ↗
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 obligationspartialproof ↗
Claims outside our story set (7)
Real capability claims found in Square’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.
“API to create and manage orders”
source ↗“Team management features including staff scheduling, timecards, and payroll”
source ↗“Securely manage customer data and run engagement programs to keep customers coming back”
source ↗“Manage all orders from one central place”
source ↗“Schedule staff and pay them (payroll) from within the product”
source ↗“Provides guidance and tooling to help sellers migrate/switch their business to Square”
source ↗“eCommerce application building blocks help sellers manage key aspects of their online business”
source ↗
Business model
Free POS software with per-transaction fees (2.6% + 15¢ in-person US); paid Plus/Premium software plans and hardware (readers, terminals, registers) sold separately.
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)
