Skip to main content
A transaction (txn_*) is one money movement recorded from your party’s point of view. Payments, transfers, refunds and chargeback debits that touch your party each produce one, so the transaction list is the single feed to reconcile against. Transactions are read-only. To learn more, see Track a payment.

Example

GET /transactions/{transactionId}
The object is everything inside data. The field names below are relative to it: attributes.amount is data.attributes.amount in the response.

Fields

string
required
Resource type. Always transaction.
string
required
Transaction ID (txn_*).
object
required
The transaction’s details.
object
required
Related resources, each by type and ID.

Internal transfers

A transfer between two of your own wallets appears once in the party-wide list. Filter by walletId to see that wallet’s leg.

Connected customers

The list includes activity you started for a connected customer, when your credential holds that activity’s read permission. A user or an API key keeps seeing it after you disconnect; an agent’s credential does not. Seeing a payment doesn’t let you refund it.

Events

This resource sends no webhook events.

Errors

See the error codes these endpoints return.

Sandbox simulations

None.