Source
Accounting handoff, DATEV & data export — found from sitemap — SumUp POS
Checked for SumUp POS on 29 Oct 2026
- Page
- https://developer.sumup.com/api/
- Checked
- 29 Oct 2026, 22:09 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:962a2bbc7cc3ef76183e632c78f57be3473477cb691a79f001f800d592032aca
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Rest API capabilities Report an error
“SumUp's REST API lets you create and process payments, manage saved customers and payment instruments, and retrieve transactions, payouts, and receipt details. It uses resource-oriented URLs and standard HTTP response codes.”
-
Sandbox environment Report an error
“You can experiment and work on your integration in a sandbox that doesn't affect your regular data and doesn't process real transactions. To create a sandbox merchant account visit the dashboard.”
-
Openapi spec download Report an error
“Download the OpenAPI specification.”
-
Base URL Report an error
“Base URL https://api.sumup.com”
-
Checkouts lifecycle Report an error
“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.”
-
Checkouts apple pay Report an error
“Create an Apple Pay session PUT /v0.2/checkouts/{checkout_id}/apple-pay-session”
-
Saved cards Report an error
“To save a card, create a checkout for that customer with purpose = SETUP_RECURRING_PAYMENT, then process it with the payer's consent and mandate details.”
-
Transaction events Report an error
“a transaction can contain related events that describe what happened after the original payment attempt”
-
Payouts list Report an error
“You can receive a detailed payouts list with information like dates, fees, references and statuses, using the List payouts endpoint.”
-
Receipts json Report an error
“Retrieve structured receipt data for a transaction, including payment, merchant, and acquirer details. Use this data to display a receipt in your application. The response is JSON, rather than a rendered receipt document.”
-
Readers inperson Report an error
“A reader represents a device that accepts payments. You can use the SumUp Solo to accept in-person payments.”
-
Members beta Report an error
“Endpoints to manage account members. Members are users that have membership within merchant accounts. Beta.”
-
Memberships beta Report an error
“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. Beta.”
-
Custom roles beta Report an error
“Endpoints to manage custom roles. Custom roles allow you to tailor roles from individual permissions to match your needs.”
-
Merchant token expiry Report an error
“Tokens expire 15 minutes after creation. Use expires_in to determine the remaining lifetime and create a new token when needed. This endpoint does not return a refresh token.”
-
Sdks Report an error
“Getting started: Authorization, SDKs, CLI, and API errors.”
-
AI markdown Report an error
“Copy as Markdown | View as Markdown | Set up AI assistant”
Scores citing this record
- The Café Owner Accounting handoff, DATEV & data export
- The Fee-Conscious Merchant Inventory, tables, staff & locations
- The Fee-Conscious Merchant Accounting handoff, DATEV & data export
- The Hospitality Operations Manager Accounting handoff, DATEV & data export
- The Retail Shop Owner Accounting handoff, DATEV & data export
- The Skeptic Accounting handoff, DATEV & data export
- The Tax Adviser Accounting handoff, DATEV & data export