Transactions

List Transactions for a User

Changed on

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). </Note>

<Note icon="fa-regular fa-circle-info"> **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 (see errors below 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 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. </Note>

get/v2.01/{ClientId}/users/{UserId}/transactions

Request

  • Base URL
    https://api.sandbox.mangopay.com
  • URL
    https://api.sandbox.mangopay.com/v2.01/{ClientId}/users/{UserId}/transactions
  • Auth
    HTTP bearer

Path parameters

ClientIdstring required

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

UserIdstring required

The unique identifier of the user.

Query parameters

ScaContextstring

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)

Sortstring

Possible values: CreationDate:ASC, CreationDate:DESC

Default value: CreationDate:ASC

Indicates the direction in which to sort the list.

per_pageinteger

Min. value: 1; max. value: 100

Default value: 10

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

pageinteger

Start value: 1

Default value: 1

Indicates the index of the page for the pagination.

Statusstring

Allowed values: CREATED, SUCCEEDED, FAILED

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

ResultCodestring

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

BeforeDateinteger

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.

AfterDateinteger

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.

Typestring

Allowed values: PAYIN, TRANSFER, CONVERSION, PAYOUT

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

Naturestring

Allowed values: REGULAR, REPUDIATION, REFUND, SETTLEMENT

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

Response

Success

Changes

  • f44a59c76515Revision changes
    • warning

      deleted the header request parameter Authorization

    • info

      the endpoint scheme security oauth2 was added to the API

  • 8e731ec4a85bRevision changes
    • info

      api operation id list_transactions_user removed and replaced with transactions_list_transactions_user