Rank #3 of 4 in Mobile & In-Person Payments
Install
npm install @sumup/sdkTry itExperimental
See what an agent can do with SumUp before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$mcp-probe → https://mcp.sumup.com/mcplive — run just now from our edge$ press ▶ run to send one JSON-RPC initialize from our edge
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 SumUp 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
—–
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
—–
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 · Machine-readable spec · Versioning policy · Full data export
Subscribe to events via webhooks
~4/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
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
✓8/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
~7/10
unlocks → Autonomous automations
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
n/an/a
Set up automations that run autonomously in the background
—–
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
—0/10
Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotely
~3/10
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
~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 | 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 | 7/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 | 5/10 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/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 | none | 0/10 | ||
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 | n/a | untested | none yet | |
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 | 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 | n/a | 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 | Cclaimed | |
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 | partial | 4/10 | Cclaimed | |
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 | partial | 3/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 | none | 0/10 | ||
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 | none | 0/10 | ||
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 | none | 0/10 | ||
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 | |
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 | none | untested | none yet | |
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 | |
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 | 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 | 7/10 | Cclaimed | |
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 | 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 | 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 | 5/10 | Tprobed | |
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 | |
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 | 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 | partial | 3/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 | 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 | |
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 | 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 | |
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 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
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 | none | untested | none yet | |
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 | 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 | |
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 | none | 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 | none | 0/10 | ||
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 33 stories with headroom
What would move SumUp’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
SumUp's evidence only shows it exposes an MCP server and Agent Toolkit so that external AI agents/coding assistants can call SumUp APIs — this is SumUp acting as a tool provider for other agents, not a built-in AI assistant embedded in the SumUp product itself that a user can delegate tasks to.
Disputes refunds — stories about disputes refunds in this arenaHave an agent monitor dispute deadlines via API or webhooks and draft evidence responses for my review
nonemoves PA Scoreimpact 30
SumUp's docs cover checkouts, refunds, webhooks for checkout status, and MCP/agent tooling, but there is no evidence of a disputes/chargebacks API, dispute deadline data, or evidence-submission endpoints that an agent could monitor or draft responses against.
Hardware fleet — stories about hardware fleet in this arenaHave an agent provision a new location end-to-end via API — creating the location and registering its readers
nonemoves PA Scoreimpact 30
Missing: location creation API, reader-to-location registration endpoint, any end-to-end provisioning example.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
SumUp's docs show only basic webhook notifications for checkout status changes (via return_url), not a rules engine allowing users to define custom conditions/actions across events; no evidence of any automation/rules builder.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
SumUp is a payments platform holding transaction/merchant data, and the evidence pack has no mention of any data export feature (open formats like CSV/JSON export of transactions, merchant data, or account closure/data portability tooling); it covers payment APIs, MCP/agent tooling, and checkout flows but nothing about exporting user data and leaving.
Accept payments — stories about accept payments in this arenaSign up, get approved, and order hardware from the dashboard so I am taking in-person payments the same week
nonemoves PA Scoreimpact 30
The evidence pack is entirely developer-API documentation (checkouts, SDKs, MCP servers, cloud API, refunds) and pricing claims; it contains no evidence about the merchant signup/approval workflow or ordering hardware from a dashboard, which is the core of this founder-onboarding story.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
SumUp is a payments API/platform with webhooks, an MCP server, and an agent toolkit for building agentic integrations, but there is no evidence of a native automation/workflow feature that runs autonomously in the background (e.g., scheduled jobs, triggers, rules engine) within SumUp itself — it only exposes APIs/tools that a third party would need to orchestrate.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
SumUp docs describe API keys as static, account-wide credentials ('act on behalf of the merchant account that created the key') with no mention of scopes, permissions, or least-privilege options for agents or sub-credentials.
Showing the top 8 of 33 — 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 map8 surfaces · 22 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Terminal payments docs11 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
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- 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
- 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
- Keep taking card payments when the internet drops, with transactions stored and forwarded when connectivity returns
- 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
Tools docs9 stories
- Point an agent at llms.txt or agent-oriented docs
- 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
- Operate the product with natural-language commands
- Perform bulk operations across many items at once
- 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
Online payments docs9 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Subscribe to events via webhooks
- Test against a sandbox environment without touching production data
- 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
- 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
developer.sumup.com4 stories
OpenAPI spec2 stories
Hacker News2 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
5 of 16 testable claims verified · 2 contradicted → integrity 6/100
25 distinct capability claims found in SumUp’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
5
Verified
9
Unverified
2
Contradicted
8
Undersold
Verified (10)
“Ships documentation aimed at giving coding assistants/agents up-to-date reference material”
Point an agent at llms.txt or agent-oriented docsfullproof ↗
“All documentation is available as plain-text Markdown by appending index.md to any doc URL”
Point an agent at llms.txt or agent-oriented docsfullproof ↗
“Offers three integration paths for in-person payments: Cloud API, Reader SDKs, and Payment Switch”
Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven APIfullproof ↗
“Can trigger and manage payments on Solo/Go card readers via HTTPS requests from a backend”
Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven APIfullproof ↗
“Runs a managed MCP server so MCP clients can manage accounts, create checkouts, and process payments”
“Agent Toolkit adds SumUp API tools to agentic apps built with LangChain, AI SDK, OpenAI Agents SDK, or MCP”
“Provides an API client/SDK to programmatically create checkouts (e.g. amount, reference, currency)”
“Provides an API client/SDK to programmatically create checkouts (e.g. amount, reference, currency)”
Drive the product through a documented public APIfullproof ↗
“Offers multiple checkout integration types to compare: hosted, embedded, web, and mobile”
Build a custom point-of-sale checkout that drives the terminal from my backend through a documented server-driven APIfullproof ↗
“Official @sumup/sdk package wraps the API with TypeScript types for modern JavaScript runtimes”
Unverified (14)
“Provides sandbox merchant accounts to create and verify checkouts before going live”
Test against a sandbox environment without touching production datafullproof ↗
“Provides sandbox merchant accounts to create and verify checkouts before going live”
Test my in-person integration end-to-end with a simulated reader or test card environment before going livefullproof ↗
“Lets developers set up a merchant account, device, and integration specifically for testing”
Test my in-person integration end-to-end with a simulated reader or test card environment before going livefullproof ↗
“Sandbox supports test cards to simulate successful, failed, and 3D Secure payment scenarios”
Test my in-person integration end-to-end with a simulated reader or test card environment before going livefullproof ↗
“Offers three integration paths for in-person payments: Cloud API, Reader SDKs, and Payment Switch”
Embed in-person payments into my own iOS or Android app with official mobile SDKsfullproof ↗
“Supports running simultaneous transactions across multiple Solo readers with no distance limit to the POS device”
Manage a fleet of readers and terminals via API — register devices, monitor status, and update configuration remotelypartialproof ↗
“Virtual Solo reader plus sandbox account lets developers test pairing and checkout flow before using a physical reader”
Test my in-person integration end-to-end with a simulated reader or test card environment before going livefullproof ↗
“Tap to Pay lets merchants accept contactless payments directly on a compatible phone with no separate reader”
Accept contactless card payments on an off-the-shelf phone (Tap to Pay) without buying a readerfullproof ↗
“Offline Transactions allow continued card payment acceptance when internet connectivity is unavailable or unreliable”
Keep taking card payments when the internet drops, with transactions stored and forwarded when connectivity returnsfullproof ↗
“Merchants can get notified when a checkout's status changes”
Subscribe to payment lifecycle events (authorized, captured, refunded, disputed) via webhooks to drive downstream automationspartialproof ↗
“Payments previously processed can be refunded partially or in full”
Issue full or partial refunds back to the original card from the point of sale, dashboard, or APIpartialproof ↗
“Offers multiple checkout integration types to compare: hosted, embedded, web, and mobile”
Embed in-person payments into my own iOS or Android app with official mobile SDKsfullproof ↗
“Payment acceptance can be embedded directly into a merchant's own Android or iOS app”
Embed in-person payments into my own iOS or Android app with official mobile SDKsfullproof ↗
“In-person payment products accept card payments face-to-face via physical readers or Tap to Pay”
Accept chip, contactless, and mobile-wallet (Apple Pay / Google Pay) payments in personfullproof ↗
Contradicted (2)
“Agent Toolkit adds SumUp API tools to agentic apps built with LangChain, AI SDK, OpenAI Agents SDK, or MCP”
Plug MCP servers into this product so it can use their toolsn/aproof ↗
“Docs describe methods available to a merchant and checkout for API exploration”
Explore an interactive API reference with runnable examplesnoneproof ↗
Undersold (8)
Run the product headlessly / in CI for automationpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
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 ↗
Have an agent pull transactions and payouts via API and reconcile daily takings into my ledgerpartialproof ↗
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 (4)
Real capability claims found in SumUp’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.
“Uses static API keys that let an application act on behalf of the merchant account that created them”
source ↗“No monthly minimums or hidden fees on the pricing plans”
source ↗“Higher-tier plan adds customer rewards, automated marketing, and monthly promotions beyond POS”
source ↗“Money-back guarantee protects merchant funds when investing in SumUp products”
source ↗
Business model
Flat per-transaction fees (from 2.6% + 10¢ in-person US) with no monthly subscription; card readers are bought upfront at low one-time prices.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
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 MCP 100% · llms.txt 100% (30d, checked every 6h since Sep 8 '26)
