# Transactions

A transaction represents a payment from a payer into a beneficiary's account, recorded against either a collection link or a channel.

A transaction is the record of money actually moving, as distinct from the request for it. A [collection](/products/collections/concepts/collections) or [channel](/products/collections/concepts/channels) is the instrument that invites payment; the transaction is what exists once a payer acts on it. One collection produces at most one transaction, while a channel produces one per payment received.

Transactions carry the detail you need for reconciliation: amounts, currencies, fees, timestamps, and status. Each transaction also carries a `settlement_id` once it has been included in a settlement, which is how you cross-reference received funds against payouts.

## How transactions relate to other resources

- A transaction is credited to an [account](/products/collections/concepts/accounts)'s sub-ledger.
- It originates from a [collection](/products/collections/concepts/collections) or a [channel](/products/collections/concepts/channels).
- Its `settlement_id` links it to the [settlement](/products/collections/concepts/settlements) that paid it out.
- Status changes emit `TRANSACTION_STATUS_CHANGED` [webhook](/products/collections/concepts/webhooks) events.


## API operations

- [List transactions](/products/collections/api/collections/transactions/listtransactionsv1): Retrieve a list of all transactions, which can be filtered by `id`, `payer_id`, or `beneficiary_id`.
- [Get transaction details](/products/collections/api/collections/transactions/gettransactionbyidv1): View the full details and current status of a single transaction.