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.
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.
Hide attributes
integer
required
Amount in cents. On a chargeback row, the disputed amount, without the chargeback fee.
string
required
Uppercase currency code, such as USD.
string
required
Transaction status. A chargeback row is COMPLETED once the disputed amount is debited from your wallet, and RETURNED if that amount is released back to you, as when you win the case.
string
required
RFC 3339 timestamp when this transaction was created.
string
required
Transaction type. A chargeback row is the disputed amount of a card payment chargeback, debited from your wallet. One of: payment, transfer, refund, chargeback.
string
required
Direction relative to your party. One of: INBOUND, OUTBOUND.
string | null
required
Transaction description.
string | null
required
RFC 3339 timestamp when this transaction was last updated, or null.
string | null
required
RFC 3339 timestamp when the funds are expected to be available, or null when unknown.
object
required
Related resources, each by type and ID.
Hide relationships
object
required
Agent that initiated this resource, or null when no agent can be reliably attributed.
Hide initiatorAgent
object | null
required
Related resource identifier.
Hide data
string
required
Resource type. Always agent.
string
required
Agent ID (agt_*).
object
required
Party the money leaves, not the party whose credentials made the request: the customer for a payment made on a customer’s behalf, and null for an external deposit.
Hide sourceParty
object | null
required
Related resource identifier.
Hide data
string
required
Resource type. Always party.
string
required
Party ID (pty_*).
object
required
Destination party.
Hide destinationParty
object | null
required
Related resource identifier.
Hide data
string
required
Resource type. Always party.
string
required
Party ID (pty_*).
object
Related payment, when accessible.
Hide payment
object
required
Related resource identifier.
Hide data
string
required
Resource type. Always payment.
string
required
Payment ID (pay_*).
object
Related card payment, when accessible. On a chargeback row, the disputed payment.
Hide cardPayment
object
required
Related resource identifier.
Hide data
string
required
Resource type. Always cardPayment.
string
required
Card payment ID (cpy_*).
object
Related refund, when accessible.
Hide refund
object
required
Related resource identifier.
Hide data
string
required
Resource type. Always refund.
string
required
Refund ID (rfd_*).
object
The chargeback case a chargeback row debits for.
Hide chargeback
object
required
Related resource identifier.
Hide data
string
required
Resource type. Always chargeback.
string
required
Chargeback ID (cbk_*).
object
Related transfer, when accessible.
Hide transfer
object
required
Related resource identifier.
Hide data
string
required
Resource type. Always transfer.
string
required
Transfer ID (trf_*).
object
Wallet through which this transaction is visible.
Hide wallet
object
required
Related resource identifier.
Hide data
string
required
Resource type. Always wallet.
string
required
Wallet ID (wal_*).
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.