# View card transactions

Track and manage customer card transaction data

## Card Transactions 

It is recommended to subscribe to [card transaction state change webhook events](/guides/developer/webhooks/event-types#cards-transaction-state-change) to
receive card transaction data to build your card transaction page.

To retrieve more information related to the card transaction, use the [get card transaction by ID](/api-reference/card-transaction#get) endpoint using the transaction ID received in the webhook. You can also use the [list card transactions](/api-reference/card-transaction#list) endpoint to list the recent transactions for a card. Note that only transactions created in the past 90 days can be accessed for V4 endpoints. You should mostly rely on webhook information to build your transaction page for real-time updates.

The possible `state` values are:

- `IN_PROGRESS` - The transaction has been authorized but not captured.
- `COMPLETED` - The transaction has been captured and/or settled.
- `DECLINED` - The transaction has been declined.
- `CANCELLED` - The transaction has been cancelled.
- `UNKNOWN` - Default fallback status if the state can't be confirmed.


The transition from `CANCELLED` to `COMPLETED` is an edge case. Wise will release user
funds after 7 days (30 days for pre-authorization) if the merchant has not captured the transaction and the state is moved to `CANCELLED`.
After this, the merchant can decide to capture the transaction after the release of funds, the state will then be moved to `COMPLETED`.

For a detailed list of decline reasons see [here](/api-reference/card-transaction#card-transaction-decline-reasons).

To receive webhook events on changes in a user's balance, see [balance update events](/guides/developer/webhooks/event-types#balance-update-event).

For the V4 endpoints to get transaction by ID and list transactions for a card, only transactions created in the past 90 days can be accessed. A 422 error code will be returned otherwise.

The V4 card transaction endpoints should be used in conjunction with the [V2.1.0 card transaction state change webhook](/guides/developer/webhooks/event-types#cards-transaction-state-change), while the V3 get card transaction endpoint should be used in conjunction with the V2.0.0 card transaction state change webhook. Existing partners looking to upgrade versions for card transaction endpoints and webhook should perform the upgrade together, for both API and webhook.

Card transaction state transitions
Transaction state flow
## Activities API 

For a simple solution to display all actions that have been performed on a user account, see the [activity API](/api-reference/activity).