Skip to main content
GET
/
v2.01
/
{ClientId}
/
users
/
{UserId}
/
transactions
// GET has no body parameters

[
    {
        "Id": "payin_m_01HSJVEP9KCCQK6FKC7973B3TZ",
        "Tag": "Created using the Mangopay API Postman collection",
        "CreationDate": 1711103498,
        "AuthorId": "user_m_01HSDQD2RPPQ8NMM36EDGYBMEY",
        "CreditedUserId": "user_m_01HSDQD2RPPQ8NMM36EDGYBMEY",
        "DebitedFunds": {
            "Currency": "EUR",
            "Amount": 6732
        },
        "CreditedFunds": {
            "Currency": "EUR",
            "Amount": 6732
        },
        "Fees": {
            "Currency": "EUR",
            "Amount": 0
        },
        "Status": "SUCCEEDED",
        "ResultCode": "000000",
        "ResultMessage": "Success",
        "ExecutionDate": 1711103498,
        "Type": "PAYIN",
        "Nature": "REGULAR",
        "CreditedWalletId": "wlt_m_01HSDQGSRYK3CXPA5RBJ08R2XJ",
        "DebitedWalletId": null,
        "DepositId": null
    }
]
This call returns transactions with the same AuthorId.
Caution - ScaContext default value changingOn 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 endpointThis 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.

​
Path parameters

​
UserId
string
required
The unique identifier of the user.

​
Query parameters

​
ScaContext
string
Possible values: USER_PRESENT, USER_NOT_PRESENTThe 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)
​
Status
string
Allowed values: CREATED, SUCCEEDED, FAILEDThe status of the transaction. You can filter on multiple values by separating them with a comma.
​
ResultCode
string
The code indicating the result of the operation. You can filter on multiple values by separating them with a comma.
​
BeforeDate
Unix timestamp
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.
​
AfterDate
Unix timestamp
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.
​
Type
string
Allowed values: PAYIN, TRANSFER, CONVERSION, PAYOUTThe type of the transaction. You can filter on multiple values by separating them with a comma.
​
Nature
string
Allowed values: REGULAR, REPUDIATION, REFUND, SETTLEMENTThe 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

​
Array (Transactions)
array
The list of transactions created by the platform.

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:
401 response header
WWW-Authenticate: PendingUserAction redirectUrl=https://sca.sandbox.mangopay.com/?token=0193cf51ed367151a0cb1c59def21e13
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 →
[
    {
        "Id": "payin_m_01HSJVEP9KCCQK6FKC7973B3TZ",
        "Tag": "Created using the Mangopay API Postman collection",
        "CreationDate": 1711103498,
        "AuthorId": "user_m_01HSDQD2RPPQ8NMM36EDGYBMEY",
        "CreditedUserId": "user_m_01HSDQD2RPPQ8NMM36EDGYBMEY",
        "DebitedFunds": {
            "Currency": "EUR",
            "Amount": 6732
        },
        "CreditedFunds": {
            "Currency": "EUR",
            "Amount": 6732
        },
        "Fees": {
            "Currency": "EUR",
            "Amount": 0
        },
        "Status": "SUCCEEDED",
        "ResultCode": "000000",
        "ResultMessage": "Success",
        "ExecutionDate": 1711103498,
        "Type": "PAYIN",
        "Nature": "REGULAR",
        "CreditedWalletId": "wlt_m_01HSDQGSRYK3CXPA5RBJ08R2XJ",
        "DebitedWalletId": null,
        "DepositId": null
    }
]  

// GET has no body parameters