Zettle (PayPal Point of Sale) — can an agent use it?
Solid developer portal and free API, but the core action — taking a payment — lives in native SDKs, not the REST API. PayPal's MCP server does not cover Zettle operations.
FIND & RETRIEVE · 7.0
ACT & TRANSACT · 4.3
TRUST & DURABILITY · 6.5
FIND & RETRIEVE7.0/10Can an agent get correct information?
Machine-readable surface6.5/10
Sitemap present and fresh (lastmod 2026-08-11), semantic HTML (H1, main, nav), Organization JSON-LD, robots.txt allows all crawlers. But no llms.txt, no markdown negotiation, no RSS/feeds, and pricing page lacks schema.org Offer markup — agents must parse prose to extract the 1.75% transaction fee. source
Information retrieval quality7.5/10
Pricing is specific and current: 1.75% per card transaction, hardware from £29/€29, no monthly fees, no contracts. Terms updated April 2026 with clear conditions. Available across 12 markets. Funds arrive in PayPal Business account within minutes. One gap: 'Payment Links temporarily unavailable for new sellers.' source
Documentation for machines7/10
developer.zettle.com documents 9 APIs (Finance, Gift Card, Image, Inventory, OAuth2, Product Library, Purchase, Pusher, Gift Card) with OAuth 2.0 + PKCE flow. Supergood.ai grades it A. Free developer signup. However: no sandbox environment, token lifecycle thinly documented, GitHub repo deprecated in 2022 (docs migrated to portal), and rate limits stated only as 'some resources have rate limiting' without published numbers beyond a 4 req/s default. source
ACT & TRANSACT4.3/10Can an agent do the job?
Action coverage4.5/10
API covers purchase history, product catalog, inventory, gift cards, finance/payouts, images, and real-time events via Pusher. But the core POS action — accepting a card payment — is not available via REST API; it requires the native Zettle Payments SDK for iOS/Android. POS folder management is also UI-only. An agent can read sales data and manage products but cannot take a payment. source
Agent protocol support2/10
No Zettle-specific MCP server, no .well-known/mcp.json, no agent skills, no WebMCP. PayPal parent has an official MCP server (paypal/agent-toolkit, 30+ tools) covering invoicing, orders, subscriptions, disputes, and shipments — but none of those tools map to Zettle POS operations (product catalog, purchases, inventory). An agent wanting to operate Zettle would need to build a custom wrapper around the REST API. source
Access & auth friction6.5/10
OAuth 2.0 with authorization code grant and PKCE for mobile apps. Self-hosted single-merchant apps can sign up freely and get credentials within minutes. Multi-merchant (partner-hosted) apps require partner approval. Token refresh semantics and expiry are thinly documented compared to peer APIs. Scoped permissions (READ:PURCHASE, WRITE:PRODUCT, etc.) provide granular access control. source
Agent payment capability1.5/10
Zettle charges merchants per transaction (1.75%) and sells hardware. No support for any agent payment protocol (ACP, AP2, MPP, x402). PayPal parent announced ACP adoption for ChatGPT commerce in 2026 and supports MCP-based checkout, but this applies to PayPal checkout, not Zettle POS. The physical card-present payment model is inherently agent-hostile — the entire transaction requires a human with a card terminal. source
Cost & rate fairness7/10
API usage is free with no paid tiers. Rate limit is 4 requests/second (FAQ-documented), with elevated limits available on request. No agent-vs-human price discrimination. Reasonable for an SMB POS back-office integration. No sandbox means testing costs nothing but is also riskier (live data only). source
TRUST & DURABILITY6.5/10Will it still work next quarter?
Permission & ToS stance6/10
Terms (updated April 2026, FCA-regulated) do not explicitly prohibit automation or API-driven access. robots.txt allows all crawlers with only minor query-param blocks. No hostile enforcement history found. However, terms do not explicitly welcome agent usage either — they are standard merchant terms with no bot-specific language. PayPal upstream account actions can cascade into Zettle access loss. source
Reliability & continuity7/10
Public status page (status.zettle.com, Atlassian Statuspage) covers 12 country markets individually — all operational 2026-08-23. FCA-regulated (firm ref 994790). Ongoing rebrand from 'Zettle by PayPal' to 'PayPal Point of Sale' creates naming uncertainty. GitHub API docs deprecated 2022 (migrated to developer portal). API has been stable since iZettle acquisition (2018), but the PayPal dependency means upstream account or pricing decisions can cascade without independent appeal. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- zettle.com — home (redirects to /fr from evidence location) (accessed 2026-08-23)
- zettle.com/gb/pricing — pricing (accessed 2026-08-23)
- zettle.com/gb/legal/general-terms-and-conditions — terms (accessed 2026-08-23)
- zettle.com/robots.txt — robots (accessed 2026-08-23)
- zettle.com/sitemap.xml — sitemap (accessed 2026-08-23)
- status.zettle.com — status page (accessed 2026-08-23)
- developer.zettle.com/docs/api — API documentation overview (accessed 2026-08-23)
- developer.zettle.com/docs/faq — developer FAQ (rate limits, no sandbox, payment SDK requirement) (accessed 2026-08-23)
- supergood.ai/api-report-card/zettle — third-party API grade (A) (accessed 2026-08-23)
- github.com/paypal/agent-toolkit — PayPal MCP server / agent toolkit (does not cover Zettle) (accessed 2026-08-23)
- developer.paypal.com/community/blog/paypal-model-co… — PayPal MCP rollout announcement (accessed 2026-08-23)