Card activities

An activity is a single movement on a card: a purchase, a repayment, a fee. List card activities returns them newest first across all cards in the business.

`type`

Value	Meaning
`CHARGE`	A card payment
`REPAYMENT`	A repayment toward the card balance
`ADJUSTMENT`	A correction, such as a fee or waiver
`REBATE`	Money credited back, such as a refund or rebate
`INTEREST`	An interest charge

`status`

Value	Meaning
`PENDING`	Authorized but not settled, so the amount can still change. It already counts against the account’s `availableCredit` and, on a top-up card, against that card’s balance
`CLEARED`	Settled and final
`DECLINED`	Refused. `declineReason` says why (below)
`VOIDED`	Reversed after authorization

Decline reasons

On a DECLINED activity, declineReason carries the card-network decline code, for example 51 for insufficient balance. Codes come from the upstream card processor; treat them as opaque and surface them to your users with the declineReason message.

Filters and privacy

from/to filter on the activity date as inclusive UTC calendar days.
Filter by cardId, type and status to narrow results.
Activities don’t carry cardholder names; join on cardId to map an activity back to a person through List cards.
category on a charge is the card’s category; transactionCategory is the spend classification of the transaction itself (from List transaction categories). See Understanding Card Categories and Transaction Categories in the Help Center.
hasReceipt flags whether a receipt is attached. Receipts are attached in the dashboard or by email; see Matching Receipts to Transactions via Email Forwarding in the Help Center.

Uploading receipt notes and updating categories are coming soon. Coming soon

Getting started

Use cases

Concepts

`type`

`status`

Decline reasons

Filters and privacy

​type

​status

​Decline reasons

​Filters and privacy

​Related endpoints

`type`

`status`

Decline reasons

Filters and privacy

Related endpoints