Skip to main content
A transaction (txn_*) is one money movement recorded from your party’s point of view. Every Payment, Transfer, Refund, and chargeback debit that touches your party produces one, so the transaction list is the single feed to reconcile against. Transactions are read-only: you create payments, transfers, and refunds. Read them with GET /transactions; see Track a payment.

​
Reading a transaction

Each transaction says what kind of movement it was (transactionType), which direction the money went relative to you (INBOUND or OUTBOUND), and which payment, transfer, or card payment produced it. Movements that settle asynchronously, like ACH deposits, carry a projected funds-available time in expectedAvailableAt. relationships.sourceParty identifies the party money leaves, not the party whose credentials initiated the request. For a payment made on a customer’s behalf it is the customer. An external deposit has no Natural source party, so sourceParty.data is null and destinationParty is the customer. Read direction with both party relationships. The agent that initiated the movement is never the source of funds.

​
Customer card activity

Your transaction history includes card payments and refunds initiated for a connected customer by your users, API credentials, or agents. The recorded customer relationship determines which activity is visible. Disconnecting a customer does not erase that history, but your current read permissions still apply. Historical visibility does not grant permission to refund a payment or access the customer’s live payment links. The dashboard’s Connect customer view includes this activity. Your Accept tab remains scoped to your own merchant activity. The public delegated=true transaction filter remains agent-only.

​
Internal transfers

A transfer between two of your own wallets is one movement with two legs. It appears once in the party-wide list; filter by walletId to see that wallet’s leg.

​
Chargebacks

When a card payment you received is charged back, Natural debits the disputed amount from your wallet and records an OUTBOUND transaction with transactionType chargeback. relationships.chargeback links the chargeback case, and relationships.cardPayment links the disputed payment when you have card_payments.read. The amount is the disputed amount only. It does not include a chargeback fee. A chargeback transaction is COMPLETED once the amount is debited. It becomes RETURNED if the amount is released back to your wallet, as when you win the case. Chargeback transactions require chargebacks.read. Without it, the list leaves them out, type=chargeback returns an empty page, and getting one by ID returns 404.