---
title: "Transactions"
description: "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.\n\nIn 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:\n- `PAYOUT`: the payment being prepared for payout or included in a payout to the merchant\n- `REFUND`: money returned to the payer\n- `CHARGE_BACK`: money reversed after the original payment\n- `PAYOUT_DEDUCTION`: an amount deducted from a payout to cover a refund or chargeback\n\nFrom an integrator's perspective, transactions are the authoritative record of payment outcomes. Use this tag to:\n- list transactions for reporting, reconciliation, and customer support workflows\n- retrieve a single transaction when you need the latest payment details\n- inspect `simple_status` for the current merchant-facing outcome of the payment\n- inspect `events` or `transaction_events` when you need refund, payout, or chargeback history\n\nTypical workflow:\n- create and process payments through the Checkouts endpoints\n- use the Transactions endpoints to read the resulting payment records\n- use the returned statuses and events to update your own order, accounting, or support systems"
image: "https://developer.sumup.com/og/index.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://developer.sumup.com/llms.txt
> Use this file to discover all available pages before exploring further.

Path: SumUp REST 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, 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

## Operations

- [Refund a transaction](/api/transactions/refund/)
- [Retrieve a transaction](/api/transactions/get/)
- [List transactions](/api/transactions/list/)


Source: https://developer.sumup.com/api/tags/transactions/index.md