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, and optional customer or redirect settings, and then moves through its lifecycle as you process it.Use this tag to:- create a checkout before collecting or confirming payment details- process the checkout with a card, saved card, wallet, or supported alternative payment method- retrieve or list checkouts to inspect their current state and associated payment attempts- deactivate a checkout that should no longer be usedTypical workflow:- create a checkout with the order amount, currency, and merchant information- process the checkout through SumUp client tools such as the [Payment Widget and Swift Checkout SDK](https://developer.sumup.com/online-payments/checkouts)- retrieve the checkout or use the Transactions endpoints to inspect the resulting payment recordCheckouts are used to initiate and orchestrate online payments. Transactions remain the authoritative record of the resulting payment outcome.
SumUp Checkouts API is one of 10 APIs that SumUp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Checkouts. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 7 operations across 4 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://api.sumup.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
SumUp Checkouts API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (apiKey).
It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows, exposing 8 scopes.
apiKey— API keys allow you easily interact with SumUp APIs. API keys are static tokens. You can create API keys from the [Dashboard](https://me.sumup.com/settings/api-…oauth2— SumUp supports [OAuth 2.0](https://tools.ietf.org/html/rfc6749) authentication for platforms that want to offer their services to SumUp users. To integrate via…
Paths & Operations 7
Across 4 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
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, an…
Schemas 23
The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are Checkout (14 properties), CheckoutCreateRequest (11 properties), ProcessCheckout (9 properties), TransactionBase (8 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from SumUp 9
Other APIs SumUp publishes across the network.
This is an independent, third-party profile of SumUp Checkouts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.