SumUp
European mobile payment and POS platform with REST APIs for creating checkout links, managing card readers, processing payments, tracking transactions, and accessing payout data. SumUp serves over 4 million merchants in 37 markets with built-in fraud protection, sandbox environments for testing, and SDKs for multiple programming languages.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles SumUp the way a machine reads it — 131 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — SumUp scores 56.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile SumUp
Each block below is one kind of artifact we hold for SumUp. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SumUp Checkouts API
Checkouts represent online payment sessions that you create before attempting to charge a payer. A checkout captures the payment intent, such as the amount, currency, merchant, ...
SumUp Customers API
Allow your regular customers to save their information with the Customers model. This will prevent re-entering payment instrument information for recurring payments on your plat...
SumUp Members API
Endpoints to manage account members. Members are users that have membership within merchant accounts.
SumUp Memberships API
Endpoints to manage user's memberships. Memberships are used to connect the user to merchant accounts and to grant them access to the merchant's resources via roles.
SumUp Merchants API
Merchant account represents a single business entity at SumUp.
SumUp Payouts API
The Payouts model will allow you to track funds you’ve received from SumUp. You can receive a detailed payouts list with information like dates, fees, references and statuses, u...
SumUp Readers API
A reader represents a device that accepts payments. You can use the SumUp Solo to accept in-person payments.
SumUp Receipts API
The Receipts model obtains receipt-like details for specific transactions.
SumUp Roles API
Endpoints to manage custom roles. Custom roles allow you to tailor roles from individual permissions to match your needs. Once created, you can assign your custom roles to your ...
SumUp Transactions API
Transactions represent completed or attempted payment operations processed for a merchant account. A transaction contains the core payment result, such as the amount, currency, ...
Scroll within the panel for all 10 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Sumup Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Sumup Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Sumup Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
SumUp API Rules
SPECTRALJSON Schema 99
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Address
JSON SCHEMAAddress Legacy
JSON SCHEMAAttributes
JSON SCHEMABadRequest
JSON SCHEMABasePerson
JSON SCHEMABranding
JSON SCHEMABusinessProfile
JSON SCHEMACard
JSON SCHEMACard Response
JSON SCHEMACard Type
JSON SCHEMAChangeStatus
JSON SCHEMACheckout
JSON SCHEMACheckout Accepted
JSON SCHEMACheckout Create Request
JSON SCHEMACheckout Success
JSON SCHEMAClassicMerchantIdentifiers
JSON SCHEMACompany
JSON SCHEMACompanyIdentifier
JSON SCHEMACompanyIdentifiers
JSON SCHEMACountryCode
JSON SCHEMACreateReaderCheckoutError
JSON SCHEMACreateReaderCheckoutRequest
JSON SCHEMACreateReaderCheckoutResponse
JSON SCHEMACreateReaderCheckoutUnprocessableEntity
JSON SCHEMACreateReaderTerminateError
JSON SCHEMACreateReaderTerminateUnprocessableEntity
JSON SCHEMACurrency
JSON SCHEMACustomer
JSON SCHEMADetails Error
JSON SCHEMADevice
JSON SCHEMAELV Card Account
JSON SCHEMAEntry Mode
JSON SCHEMAError
JSON SCHEMAError Extended
JSON SCHEMAError Forbidden
JSON SCHEMAEvent
JSON SCHEMAEvent ID
JSON SCHEMAEvent Status
JSON SCHEMAEvent Type
JSON SCHEMAFinancial Payout
JSON SCHEMAFinancial Payouts
JSON SCHEMAHorizontal Accuracy
JSON SCHEMAHosted Checkout
JSON SCHEMAInvite
JSON SCHEMALatitude
JSON SCHEMALegalType
JSON SCHEMALink
JSON SCHEMAListPersonsResponseBody
JSON SCHEMALongitude
JSON SCHEMAMandate Payload
JSON SCHEMAMandate Response
JSON SCHEMAMember
JSON SCHEMAMembership
JSON SCHEMAResource
JSON SCHEMAMembershipStatus
JSON SCHEMAMembershipUser
JSON SCHEMAMembershipUserClassic
JSON SCHEMAMerchant
JSON SCHEMAMeta
JSON SCHEMAMetadata
JSON SCHEMANotFound
JSON SCHEMAOwnership
JSON SCHEMAPayment Instrument Response
JSON SCHEMAPayment Type
JSON SCHEMAPerson
JSON SCHEMAPersonal Details
JSON SCHEMAPersonalIdentifier
JSON SCHEMAPhoneNumber
JSON SCHEMAProblem
JSON SCHEMAProcess Checkout
JSON SCHEMAProduct
JSON SCHEMAReader
JSON SCHEMAReaderCheckoutStatusChange
JSON SCHEMAReaderDevice
JSON SCHEMAReaderID
JSON SCHEMAReaderName
JSON SCHEMAReaderPairingCode
JSON SCHEMAReaderStatus
JSON SCHEMAReceipt
JSON SCHEMAReceipt Card
JSON SCHEMAReceipt Event
JSON SCHEMAReceipt Merchant Data
JSON SCHEMAReceipt Reader
JSON SCHEMAReceipt Transaction
JSON SCHEMAResourceType
JSON SCHEMARole
JSON SCHEMAStatusResponse
JSON SCHEMATimestamps
JSON SCHEMATransaction Base
JSON SCHEMATransaction Checkout Info
JSON SCHEMATransaction Event
JSON SCHEMATransaction Full
JSON SCHEMATransaction History
JSON SCHEMATransaction ID
JSON SCHEMATransaction Mixin History
JSON SCHEMATransactions History Link
JSON SCHEMATransaction Status
JSON SCHEMAUnauthorized
JSON SCHEMAVersion
JSON SCHEMAScroll within the panel for all 99 ·
Examples 13
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Createcheckout Request
EXAMPLECreatecheckout Response 201
EXAMPLECreatereader Response 201
EXAMPLEGetcheckout Response 200
EXAMPLEGetreceipt Response 200
EXAMPLEProcesscheckout Request
EXAMPLEProcesscheckout Response 200
EXAMPLERefundtransaction Request
EXAMPLEScroll within the panel for all 13 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for SumUp — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sumup · machine-readable index on apis.io