---
title: "List Transactions for a User"
method: GET
path: "/v2.01/{ClientId}/users/{UserId}/transactions"
tags: ["Transactions"]
---

# List Transactions for a User

`GET /v2.01/{ClientId}/users/{UserId}/transactions`

This call returns transactions with the same `AuthorId`.

<Note icon="fa-regular fa-circle-info">
**Note – ScaContext default value is USER_PRESENT**

On this endpoint, the default value for `ScaContext` is `USER_PRESENT`. If the `PendingUserAction.RedirectUrl` value is returned, you need to redirect the user to perform SCA.

With approval from Mangopay, your platform may be able to use the `USER_NOT_PRESENT` value provided you also have a legal proxy in place with the user and the user's consent to access wallet balances and transactions on their behalf (read more about [proxy management](/guides/sca/proxy-management)).
</Note>

<Note icon="fa-regular fa-circle-info">
**Note – SCA triggered by this endpoint**

This endpoint requires the user to [perform SCA to authenticate](/guides/sca/wallets) the access to their wallet, unless SCA for wallet access was successfully completed in the last 180 days (or unless your platform is using a [proxy and user consent](/guides/sca/proxy-management)).

When SCA is required, this endpoint returns a **401 - Unauthorized** response (see [errors below](#response.error) for details).

To let the user complete the SCA session on the Mangopay-hosted webpage, your platform needs to retrieve the `RedirectUrl` from the `WWW-Authenticate` response header, add an encoded `returnUrl` query parameter, and redirect the user. Read more about how to redirect them in the [SCA session](/guides/sca/session) guide.

In Sandbox, you can bypass SCA by including the word `accept` in the `Email` value of the [Natural User](/api-reference/users/natural-user-object-sca) or the `LegalRepresentative.Email` value of the [Legal User](/api-reference/users/legal-user-object-sca) – for example `accept@example.com` or `john.doe+accept@example.com`.
</Note>

## Path parameters

- `ClientId` string, required
- `UserId` string, required

## Query parameters

- `ScaContext` string
- `Sort` string
- `per_page` integer
- `page` integer
- `Status` string
- `ResultCode` string
- `BeforeDate` integer
- `AfterDate` integer
- `Type` string
- `Nature` string

## Headers

- `Authorization` string, required

## Response `200`

Success

- ListTransactionsResponse
  - `Array (Transactions)` ListTransactionsResponseArrayTransactionsItems[] — The list of transactions created by the platform.
    - `Object (transaction)` TransactionResponse
      - `Id` string — Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object.
      - `Tag` string — Max. length: 255 characters Custom data that you can add to this object. For transactions (pay-in, transfer, payout), you can use this parameter to identify corresponding information regarding the user, transaction, or payment methods on your platform.
      - `CreationDate` integer — Unix timestamp (UTC) of the date and time the object was created.
      - `AuthorId` string — The unique identifier of the user at the source of the transaction.
      - `CreditedUserId` string — **Default value:** The unique identifier of the owner of the credited wallet. The unique identifier of the user whose wallet is credited.
      - `DebitedFunds` TransactionResponseDebitedFunds — Information about the debited funds.
        - `Currency` string — **Allowed values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings). The currency of the amount.
        - `Amount` integer — The amount of the currency in its minor unit. For example, EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`.
      - `CreditedFunds` TransactionResponseCreditedFunds — Information about the credited funds (`CreditedFunds` = `DebitedFunds` - `Fees`).
        - `Currency` string — **Allowed values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings). The currency of the amount.
        - `Amount` integer — The amount of the currency in its minor unit. For example, EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`.
      - `Fees` TransactionResponseFees — Information about the fees taken by the platform for this transaction (and hence transferred to the Fees Wallet).
        - `Currency` string — **Allowed values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings). The currency of the amount.
        - `Amount` integer — The amount of the currency in its minor unit. For example, EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`.
      - `Status` string — **Returned values:** `CREATED`, `SUCCEEDED`, `FAILED` The status of the transaction.
      - `ResultCode` string — The code indicating the result of the operation. This information is mostly used to <a href="/errors/codes">handle errors</a> or for filtering purposes.
      - `ResultMessage` string — The explanation of the result code.
      - `ExecutionDate` integer — Unix timestamp (UTC) of the date and time the status changed to `SUCCEEDED`, indicating that the transaction occurred. The statuses `CREATED` and `FAILED` return an `ExecutionDate` of `null`.
      - `Type` string — **Returned values:** `PAYIN`, `TRANSFER`, `CONVERSION`, `PAYOUT` The type of the transaction.
      - `Nature` string — **Returned values:** `REGULAR`, `REPUDIATION`, `REFUND`, `SETTLEMENT` The nature of the transaction, providing more information about the context in which the transaction occurred: - `REGULAR` – Relative to most of the transactions (pay-ins, payouts, and transfers) in a usual workflow. - `REPUDIATION` – Automatic withdrawal of funds from the platform's repudiation wallet as part of the dispute process (when the user has requested a chargeback). - `REFUND` – Reimbursement of a transaction to the user (pay-in refund), to a wallet (transfer refund), or of a payout (payout refund, only initiated by Mangopay). - `SETTLEMENT` – Transfer made to the repudiation wallet by the platform to settle a lost dispute.
      - `CreditedWalletId` string — The unique identifier of the credited wallet.
      - `DebitedWalletId` string — The unique identifier of the debited wallet.

## Other responses

- `401` — SCA required to retrieve data because no successful SCA session for wallet access occurred in the last 180 days. In this case, the user needs to authenticate the action. The 401 response includes a `WWW-Authenticate` header with the `RedirectUrl` value needed.

---

[API](https://skmtc.dev/mangopay/apis/api-reference.md) · [All operations](https://skmtc.dev/mangopay/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mangopay/api-reference/revisions/fafbd0c69654/schema)