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

# List Wallets for a User

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

Retrieve wallets based on `UserId`.

<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
- `per_page` integer
- `page` integer
- `Sort` string

## Headers

- `Authorization` string, required

## Response `200`

Success

- ListWalletsForAUserResponse
  - `Array (Wallets)` ListWalletsForAUserResponseArrayWalletsItems[] — The list of wallets created by the platform.
    - `Object (Wallet)` ListWalletsForAUserResponseArrayWalletsItemsObjectWallet — The Wallet object created by the platform.
      - `Description` string — The description of the wallet. It can be a name, the type, or anything else that can help you clearly identify the wallet on the platform (and for your end users).
      - `Owners` string[] — The unique identifier of the user owning the wallet. **Note:** Only one owner can be defined; this array accepts only one string.
      - `Balance` ListWalletsForAUserResponseArrayWalletsItemsObjectWalletBalance — The current balance of the 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`.
      - `Currency` string — **Returned 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 wallet.
      - `FundsType` string — **Returned values:** `DEFAULT`, `FEES`, `CREDIT` The type of funds in the wallet: - `DEFAULT` – Regular funds for user-owned wallets. Wallets with this `FundsType` cannot have a negative balance. - `FEES` – Fees Wallet, for fees collected by the platform, specific to the Client Wallet object. - `CREDIT` – Repudiation Wallet, for funds for the platform's dispute management, specific to the Client Wallet object. **Note:** The Fees Wallet and Repudiation Wallet are created automatically by Mangopay for each currency.
      - `Id` string — Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object.
      - `Tag` string — Custom data that you can add to this object. For wallets, you can use this parameter to identify the corresponding end user in your platform.
      - `CreationDate` integer — Unix timestamp (UTC) of the date and time the wallet was created.

## 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)