---
title: "TransactionEvent"
description: "High-level transaction event details."
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

High-level transaction event details.

## Fields

- `id` (`TransactionEvent.id`; integer, optional) — Numeric identifier of a transaction event. Use it as `tx_event_id` when requesting receipt details for a specific event. This is separate from the transaction ID and the transaction history pagination references.
  - format `int64`; example `9567461191`
- `transaction_id` (`TransactionEvent.transaction_id`; string, optional) — Unique identifier of the transaction.
  - example `"410fc44a-5956-44e1-b5cc-19c6f8d727a4"`
- `type` (`TransactionEvent.type`; string, optional) — Financial event associated with a transaction. - `PAYOUT`: Funds from the transaction being prepared for or included in a merchant payout. Check the event status to determine whether they have been paid out. - `REFUND`: Money returned to the payer. - `CHARGE_BACK`: A reversal of the payment following a chargeback. - `PAYOUT_DEDUCTION`: An amount deducted from a merchant payout, for example to cover a refund or chargeback.
  - one of `"PAYOUT"`, `"CHARGE_BACK"`, `"REFUND"`, `"PAYOUT_DEDUCTION"`; example `"REFUND"`
- `status` (`TransactionEvent.status`; string, optional) — Status of the transaction event. Not every value is used for every event type. - `PENDING`: The event has been created but is not final yet. Used for events that are still being processed and whose final outcome is not known yet. - `SCHEDULED`: The event is planned for a future payout cycle but has not been executed yet. This applies to payout events before money is actually sent out. - `RECONCILED`: The underlying payment has been matched with settlement data and is ready to continue through payout processing, but the funds have not been paid out yet. This applies to payout events. - `PAID_OUT`: The payout event has been completed and the funds were included in a merchant payout. - `REFUNDED`: A refund event has been accepted and recorded in the refund flow. This is the status returned for refund events once the transaction amount is being or has been returned to the payer. - `SUCCESSFUL`: The event completed successfully. Use this as the generic terminal success status for event types that do not expose a more specific business outcome such as `PAID_OUT` or `REFUNDED`. - `FAILED`: The event could not be completed. Typical examples are a payout that could not be executed or an event that was rejected during processing.
  - one of `"FAILED"`, `"PAID_OUT"`, `"PENDING"`, `"RECONCILED"`, `"REFUNDED"`, `"SCHEDULED"`, `"SUCCESSFUL"`; example `"SUCCESSFUL"`
- `amount` (`TransactionEvent.amount`; number, optional) — Amount associated with the transaction event, in major units.
  - format `float`; example `10.1`
- `timestamp` (`TransactionEvent.timestamp`; string, optional) — The timestamp of when the transaction event occurred.
  - format `date-time`; example `"2020-05-25T10:49:42.784Z"`
- `fee_amount` (`TransactionEvent.fee_amount`; number, optional) — Fee associated with the transaction event, in major units.
  - format `float`; example `0.25`
- `installment_number` (`TransactionEvent.installment_number`; integer, optional) — Consecutive number of the installment associated with the event.
  - example `1`
- `deducted_amount` (`TransactionEvent.deducted_amount`; number, optional) — Amount deducted from the merchant for the event, in major units.
  - format `float`; example `10.1`
- `deducted_fee_amount` (`TransactionEvent.deducted_fee_amount`; number, optional) — Fee deducted from the merchant for the event, in major units.
  - format `float`; example `0.25`


Source: https://developer.sumup.com/api/schemas/TransactionEvent/index.md
