List Transactions for a User
This call returns transactions with the same AuthorId.
Note – SCA triggered by this endpoint
This endpoint requires the user to complete SCA to authenticate the access to their wallet, unless SCA for wallet access was successfully completed in the last 180 days (read more about SCA on wallet access).
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.
Path parameters
The unique identifier of the user.
Query parameters
Possible values: USER_PRESENT, USER_NOT_PRESENT
Default value: null
The SCA context of the request, which should be considered required if the user’s UserCategory is OWNER:
USER_PRESENT– The user is initiating the wallet access request and is actively present. The platform must redirect the user for SCA using thePendingUserAction.RedirectUrlreturned, unless a successful SCA session for wallet access occurred in the last 180 days.USER_NOT_PRESENT– No user is present: the access is automated by the platform as part of their declared and authorized workflow. On these requests, SCA redirection is not initially required, but in future Mangopay may be required to override the request.
Both values may technically result in the need for SCA redirection, because an exemption may be applied by Mangopay or (in future) Mangopay may be required to override a given request.
Note: ScaContext is a temporary mechanism to introduce SCA on existing endpoints and workflows. New integrations should consider the parameter required and send USER_PRESENT by default. Read more about SCA on wallet access →
Allowed values: CREATED, SUCCEEDED, FAILED
The status of the transaction. You can filter on multiple values by separating them with a comma.
The code indicating the result of the operation. You can filter on multiple values by separating them with a comma.
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.
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.
Allowed values: PAYIN, TRANSFER, CONVERSION, PAYOUT
The type of the transaction. You can filter on multiple values by separating them with a comma.
Allowed values: REGULAR, REPUDIATION, REFUND, SETTLEMENT
The nature of the transaction, providing more information about the context in which the transaction occurred. You can filter on multiple values by separating them with a comma.
Responses
200
200
The list of transactions created by the platform.
401 - SCA required
401 - SCA required
When SCA is required for wallet access, this endpoint returns a 401 - Unauthorized response code with the redirectUrl in the WWW-Authenticate response header:
In this case, your platform needs to retrieve the URL value, encode and add a returnUrl query parameter, and redirect the user.
Read more about SCA redirection and SCA on wallet access →