Transactions | SumUp Developer

Transactions represent completed or attempted payment operations processed for a merchant account. A transaction contains the core payment result, such as the amount, currency, payment method, creation time, and current high-level status.

In addition to the main payment outcome, a transaction can contain related events that describe what happened after the original payment attempt. These events provide visibility into the financial lifecycle of the transaction, for example:

PAYOUT: the payment being prepared for payout or included in a payout to the merchant
REFUND: money returned to the payer
CHARGE_BACK: money reversed after the original payment
PAYOUT_DEDUCTION: an amount deducted from a payout to cover a refund or chargeback

From an integrator's perspective, transactions are the authoritative record of payment outcomes. Use this tag to:

list transactions for reporting, reconciliation, and customer support workflows
retrieve a single transaction when you need the latest payment details
inspect simple_status for the current merchant-facing outcome of the payment
inspect events or transaction_events when you need refund, payout, or chargeback history

Typical workflow:

create and process payments through the Checkouts endpoints
use the Transactions endpoints to read the resulting payment records
use the returned statuses and events to update your own order, accounting, or support systems

Refund a transactionPOST/v1.0/merchants/{merchant_code}/payments/{transaction_id}/refunds
Refunds a transaction identified by its SumUp transaction ID. Omit the request body to request a full refund, or provide amount for a partial refund in the transaction's currency.

Retrieve the transaction afterwards to inspect its refunded amount and refund events. The transaction must be eligible for a refund; see the error responses for invalid amounts, permissions, and processing failures.

OAuth scopes: Requires one of: payments, refunds.write.
Retrieve a transactionGET/v2.1/merchants/{merchant_code}/transactions
Retrieves the full details of an identified transaction. The transaction resource is identified by a query parameter and one of following parameters is required:
- id
- transaction_code
- foreign_transaction_id
- client_transaction_id
OAuth scopes: Requires one of: transactions.history, transactions.read.
List transactionsGET/v2.1/merchants/{merchant_code}/transactions/history
Lists transaction history for the merchant, with optional filters for payment type, status, and date range. The response contains the current page in items and pagination query strings in links.

To request another page, use the query string from the relevant link's href with this history endpoint. Use changes_since when retrieving transactions modified since a previous synchronization, including transactions created earlier whose status has changed.

OAuth scopes: Requires one of: transactions.history, transactions.read.