List Transactions for a Wallet

GET

/v2.01/:ClientId/wallets/:WalletId/transactions

GET

/v2.01/:ClientId/wallets/:WalletId/transactions

$ curl https://api.sandbox.mangopay.com/v2.01/{ClientId}/wallets/{WalletId}/transactions \
>      -H "Authorization: Bearer <token>"

1 [
2   {
3     "AuthorId": "user_m_01HSDQD2RPPQ8NMM36EDGYBMEY",
4     "CreationDate": 1727081808,
5     "CreditedFunds": {
6       "Amount": 490,
7       "Currency": "EUR"
8     },
9     "CreditedUserId": "user_m_01HSDQD2RPPQ8NMM36EDGYBMEY",
10     "CreditedWalletId": "wlt_m_01HT03YR6YRBT1EGK1FYDDBZM9",
11     "DebitedFunds": {
12       "Amount": 500,
13       "Currency": "EUR"
14     },
15     "DebitedWalletId": "wlt_m_01HW8AS48VH6MRXVT44RKK5RW1",
16     "DepositId": null,
17     "ExecutionDate": 1727081809,
18     "Fees": {
19       "Amount": 10,
20       "Currency": "EUR"
21     },
22     "Id": "xfer_m_01J8F1J0KBFTRP5CMYMFFTG4W4",
23     "Nature": "REGULAR",
24     "ResultCode": "000000",
25     "ResultMessage": "Success",
26     "Status": "SUCCEEDED",
27     "Tag": "Created using Mangopay API Postman Collection",
28     "Type": "TRANSFER"
29   },
30   {
31     "AuthorId": "user_m_01HSDQD2RPPQ8NMM36EDGYBMEY",
32     "CreationDate": 1727081839,
33     "CreditedFunds": {
34       "Amount": 500,
35       "Currency": "EUR"
36     },
37     "CreditedUserId": null,
38     "CreditedWalletId": "wlt_m_01HW8AS48VH6MRXVT44RKK5RW1",
39     "DebitedFunds": {
40       "Amount": 490,
41       "Currency": "EUR"
42     },
43     "DebitedWalletId": "wlt_m_01HT03YR6YRBT1EGK1FYDDBZM9",
44     "DepositId": null,
45     "ExecutionDate": 1727081840,
46     "Fees": {
47       "Amount": -10,
48       "Currency": "EUR"
49     },
50     "Id": "refund_m_01J8F1JZ6XCEFCZ71W34N9DWRR",
51     "Nature": "REFUND",
52     "ResultCode": "000000",
53     "ResultMessage": "Success",
54     "Status": "SUCCEEDED",
55     "Tag": "Created using Mangopay API Postman Collection",
56     "Type": "TRANSFER"
57   }
58 ]

Retrieve the transactions (pay-in, transfers, conversions, and payouts) of a given wallet.

Caution - ScaContext default value changing

On this endpoint, the default value for ScaContext is changing to USER_PRESENT on Dec 15, 2025 (Dec 1 in Sandbox).

From this date, if the PendingUserAction.RedirectUrl value is returned, then 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).

Note – SCA triggered by this endpoint

This endpoint requires the user to perform SCA to authenticate 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).

When SCA is required, this endpoint returns a 401 - Unauthorized response.

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 guide.

In Sandbox, you can bypass SCA by including the word accept in the Email value of the Natural User or the LegalRepresentative.Email value of the Legal User – for example accept@example.com or john.doe+accept@example.com.

Retrieve the transactions (pay-in, transfers, conversions, and payouts) of a given wallet. <Warning icon="fa-regular fa-triangle-exclamation"> **Caution - ScaContext default value changing** On this endpoint, the default value for `ScaContext` is changing to `USER_PRESENT` on **Dec 15, 2025** (Dec 1 in Sandbox). From this date, if the `PendingUserAction.RedirectUrl` value is returned, then 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)). </Warning> <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. 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>

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.

Bearer authentication of the form `Bearer <token>`, where token is your auth token. If your platform is using a [proxy](/guides/sca/proxy-management) to take SCA-triggering action on behalf of users, you also need to integrate [mTLS authentication](/guides/sca/platform) and use the `api-mtls` base URL.

Path parameters

ClientIdstringRequired

Platform's API account identifier, associated with the API key.

WalletIdstringRequired

The unique identifier of the wallet.

Query parameters

ScaContextstringOptional

Possible values: USER_PRESENT, USER_NOT_PRESENT

The SCA context of the request, which is required if the user’s UserCategory is OWNER:

USER_PRESENT – The user is taking the SCA-triggering action of accessing their wallet. The platform must redirect the user using the PendingUserAction.RedirectUrl returned so that the user can complete the SCA session (unless exempted because a successful SCA session for wallet access occurred in the last 180 days, so no redirection link was returned).
USER_NOT_PRESENT – The platform is taking the action under proxy from the user and the user has previously given consent to Mangopay (via the SCA hosted experience) to allow the action. If the user has not given (or has revoked) their consent, then USER_NOT_PRESENT returns a 403 error.

Read more about managing proxy and user consent →

Note: For existing platforms, the parameter is technically optional if the User is an OWNER, and the default value will become USER_PRESENT from Dec 15, 2025 (Dec 1 in Sandbox)

**Possible values:** `USER_PRESENT`, `USER_NOT_PRESENT` The SCA context of the request, which is **required** if the user's `UserCategory` is `OWNER`: - `USER_PRESENT` – The user is taking the SCA-triggering action of accessing their wallet. The platform must [redirect the user](/guides/sca/session) using the `PendingUserAction.RedirectUrl` returned so that the user can complete the SCA session (unless exempted because a successful SCA session for wallet access occurred in the last 180 days, so no redirection link was returned). - `USER_NOT_PRESENT` – The platform is taking the action under proxy from the user and the user has previously given consent to Mangopay (via the SCA hosted experience) to allow the action. If the user has not given (or has revoked) their consent, then `USER_NOT_PRESENT` returns a 403 error. Read more about [managing proxy and user consent](/guides/sca/proxy-management) **→** **Note:** For existing platforms, the parameter is technically optional if the User is an `OWNER`, and the default value will become `USER_PRESENT` from **Dec 15, 2025** (Dec 1 in Sandbox)

SortstringOptional

Possible values: CreationDate:ASC, CreationDate:DESC

Default value: CreationDate:ASC

Indicates the direction in which to sort the list.

per_pageintegerOptional

Min. value: 1; max. value: 100

Default value: 10

Indicates the number of items returned for each page of the pagination.

pageintegerOptional

Start value: 1

Default value: 1

Indicates the index of the page for the pagination.

StatusstringOptional

Allowed values: CREATED, SUCCEEDED, FAILED

The status of the transaction. You can filter on multiple values by separating them with a comma.

ResultCodestringOptional

The code indicating the result of the operation. You can filter on multiple values by separating them with a comma.

BeforeDateintegerOptional

The date before which the transaction was created (based on the transaction’s CreationDate parameter). You can filter on a specific time range by using both the AfterDate and BeforeDate query parameters.

AfterDateintegerOptional

The date after which the transaction was created (based on the transaction’s CreationDate parameter). You can filter on a specific time range by using both the AfterDate and BeforeDate query parameters.

TypestringOptional

Allowed values: PAYIN, TRANSFER, CONVERSION, PAYOUT

The type of the transaction. You can filter on multiple values by separating them with a comma.

NaturestringOptional

Allowed values: REGULAR, REPUDIATION, REFUND, SETTLEMENT

The nature of the transaction, providing more information about the context in which the transaction occurred.

Response

Success

Array (Transactions)list of objects

The list of transactions created by the platform.

Errors

401

Unauthorized Error