GET
/
v2.01
/
{ClientId}
/
wallets
/
{WalletId}
// GET has no body parameters

{
    "Description": "Description of the user's wallet",
    "Owners": [
        "user_m_01J18HZSACR1EMYNY1TBS8KTJD"
    ],
    "Id": "wlt_m_01J18J1SQGG6KXNM3F8GD674TP",
    "Balance": {
        "Currency": "EUR",
        "Amount": 99800
    },
    "Currency": "EUR",
    "FundsType": "DEFAULT",
    "Tag": "Created using Mangopay API Postman collection",
    "CreationDate": 1719348029
}
Note – SCA triggered by this endpointThis 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

​
WalletId
string
required
The unique identifier of the wallet.

​
Query parameters

​
ScaContext
string
Possible values: USER_PRESENT, USER_NOT_PRESENTDefault value: nullThe SCA context of the request, which is 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 the PendingUserAction.RedirectUrl returned, 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. Platforms integrating for the first time should consider the parameter required and send USER_PRESENT by default. Read more about SCA on wallet access →

​
Responses

​
Description
string
Max. length: 255 charactersThe 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
array
stringThe unique identifier of the user owning the wallet.Note: Only one owner can be defined; this array accepts only one string.
​
Id
string
Max length: 128 characters (see data formats for details)The unique identifier of the object.
​
Balance
object
The current balance of the wallet.
​
Currency
string
Returned values: The three-letter ISO 4217 code (EUR, GBP, etc.) of a supported currency (depends on feature, contract, and activation settings).The currency of the wallet.
​
FundsType
string
Returned values: DEFAULT, FEES, CREDITThe 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.
​
Tag
string
Max. length: 255 charactersCustom 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
Unix timestamp
The date and time at which the wallet was created.

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 →
{
    "Description": "Description of the user's wallet",
    "Owners": [
        "user_m_01J18HZSACR1EMYNY1TBS8KTJD"
    ],
    "Id": "wlt_m_01J18J1SQGG6KXNM3F8GD674TP",
    "Balance": {
        "Currency": "EUR",
        "Amount": 99800
    },
    "Currency": "EUR",
    "FundsType": "DEFAULT",
    "Tag": "Created using Mangopay API Postman collection",
    "CreationDate": 1719348029
}

// GET has no body parameters