---
title: "View the SCA status of a User"
method: GET
path: "/v2.01/{ClientId}/sca/users/{UserId}/sca-status"
tags: ["Users"]
---

# View the SCA status of a User

`GET /v2.01/{ClientId}/sca/users/{UserId}/sca-status`

Retrieve SCA and consent information for a Natural or Legal User.

This endpoint returns information for an `OWNER` user relating to:
- Whether or not they are enrolled in SCA – but if they never triggered an SCA enrollment, the endpoint returns a 404
- Their consent for your platform to take [SCA-triggering actions by proxy](/guides/sca/proxy-management), if activated for your platform

## Path parameters

- `ClientId` string, required
- `UserId` string, required

## Headers

- `Authorization` string, required

## Response `200`

Success

- ViewTheSCAStatusOfAUserResponse
  - `UserStatus` string — **Returned values:** `PENDING_USER_ACTION`, `ACTIVE`, `CLOSED` The status of the user: - `PENDING_USER_ACTION` – The user must enroll in SCA before they can become `ACTIVE`. - `ACTIVE` – The user account is active and the user can access Mangopay features. - `CLOSED` – The user account is permanently closed. This value is used by Mangopay to close an account following the procedure outlined in the terms and conditions.
  - `IsEnrolled` boolean — Whether or not the User has been enrolled in SCA. This value is `false` before the User enrolls successfully for the first time. Once enrolled, this value remains `true` during re-enrollment (but the `UserStatus` changes to `PENDING_USER_ACTION`).
  - `LastEnrollmentDate` string, nullable — The date and time of the last successful SCA enrollment, whether for the first time or a re-enrollment. Not returned if the user has not yet completed enrollment
  - `LastConsentCollectionDate` string, nullable — The date and time of the last modification to any of the 4 scopes, whether to give or revoke consent.
  - `ConsentScope` ConsentScope — Whether or not the user has given consent to the [proxy action scope](/guides/sca/proxy-management) via the SCA hosted experience: - `ACTIVE` - The user has given consent by checking the corresponding checkbox. - `INACTIVE` - The user has not yet given consent or has revoked consent. - `null` – The corresponding scope does not have proxy management configured for your platform. If a scope is `ACTIVE`, your platform can call the relevant endpoint with `ScaContext` set to `USER_NOT_PRESENT` to take the action under proxy. If a scope is `INACTIVE`, your platform has two options: - Call the relevant endpoint with the user on session to complete SCA by redirecting them using the returned `PendingUserAction.RedirectUrl`. - Ask the user to give consent using the `PendingUserAction.RedirectUrl` returned by the [POST Manage proxy consent for a User](/api-reference/users/manage-proxy-consent) endpoint, then re-try the action with `ScaContext` set to `USER_NOT_PRESENT`.
    - `ContactInformationUpdate` string, nullable — The status of the user's consent for your platform to update their SCA contact information on their behalf using: - [PUT Update a Natural User (SCA)](/api-reference/users/update-natural-user-sca) to modify the `PhoneNumber`, `PhoneNumberCountry`, or `Email` - [PUT Update a Legal User (SCA)](/api-reference/users/update-legal-user-sca) to modify the `PhoneNumber`, `PhoneNumberCountry`, or `Email` of the `LegalRepresentative` **Possible values:** `ACTIVE`, `INACTIVE`, `null`
    - `RecipientRegistration` string, nullable — The status of the user's consent for your platform to register an external bank or payment account on their behalf using: - [POST Create a Recipient](/api-reference/recipients/create-recipient) **Possible values:** `ACTIVE`, `INACTIVE`, `null`
    - `Transfer` string, nullable — The status of the user's consent for your platform to initiate a transfer to another `OWNER` user on their behalf using: - [POST Create a Transfer](/api-reference/transfers/create-transfer) **Possible values:** `ACTIVE`, `INACTIVE`, `null`
    - `ViewAccountInformation` string, nullable — The status of the user's consent for your platform to retrieve wallet and transaction data on their behalf using: - [GET View a Wallet](/api-reference/wallets/view-wallet) - [GET List Wallets for a User](/api-reference/wallets/list-wallets-user) - [GET List Transactions for a User](/api-reference/transactions/list-transactions-user) - [GET List Transactions for a Wallet](/api-reference/transactions/list-transactions-wallet) **Possible values:** `ACTIVE`, `INACTIVE`, `null`

## Other responses

- `400` — Bad Request
- `404` — Not Found

---

[API](https://skmtc.net/mangopay/apis/api-reference.md) · [All operations](https://skmtc.net/mangopay/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mangopay/api-reference/versions/795281070285/schema)