Upgrading a Limited Account
A limited (simplified) account is opened with fewer data and documents than a full account, and it has usage limits. This page explains how to complete a limited account by converting it into a full account with the UpdatePersonData method. The fields of the method are in the table below. The method also receives the general fields Method, PartnerId and BusinessUnitId.
Which path to follow
| Situation of the limited account | What to do |
|---|---|
| The required registration data were already sent and only documents are missing | Send the pending documents with ResendDocuments. See Sending Documents. |
| Registration data and documents for the full account are missing | Convert the account with UpdatePersonData, as explained on this page. |
How to convert the account (UpdatePersonData)
UpdatePersonData converts a limited account into a full account. The BU sends the complete registration and the documents required for the full account, and Fits runs a new KYC and AML analysis. The end customer accepts the same terms as in the opening of a full account.
Request fields
In the Requirement column, Mandatory means the field must always be sent, Optional means it can be omitted, and Conditional means it depends on another field, with the condition stated in the Description.
| Field | Requirement | Description |
|---|---|---|
| Personal data | Conditional | Required for an individual. |
| Income | Conditional | Required for an individual. |
| Politically exposed person (PEP) | Conditional | Required for an individual. Informs whether the person is politically exposed. |
| IsCompany | Conditional | Required for a company. Informs that the person is a company. |
| Company type | Conditional | Required for a company. |
| Company activity | Mandatory | Required for a company. |
| Constitution date | Conditional | Required for a company. |
| Addresses | Mandatory | Addresses of the person. |
| Documents | Mandatory | Documents required for the full account, listed in Required Documents. |
| People linked to the company | Conditional | Required for a company. List of the people linked to the company, each one with their role (PersonRoleType). For an individual partner, the monthly income (Persons.MonthlyIncome) is mandatory and must be greater than zero. |
| PersonRoleType | Conditional | Required for a company, in each linked person. Role of the person, as a number. Values in Code Mapping, section Role of the person. |
The response only brings Success (text "true" or "false") and Message, with the success message described in the Success Catalogue.
The documents required for each account type are in Required Documents.
Only limited or legacy accounts can be converted. If the account is already a full account, the method returns the error EXE0169.
The errors returned by this method are listed in the Error Catalogue, in the section "UpdatePersonData and ChangePersonInfo".
flowchart TD
A["Limited account"] --> B{"Only documents are missing?"}
B -- Yes --> C["Resend the documents with ResendDocuments"]
B -- No --> D["The BU calls UpdatePersonData with complete registration and documents"]
C --> E["Fits runs the analysis"]
D --> E
E --> F{"Result"}
F -- Approved --> G["Account Verified, without the limited account restrictions"]
F -- Divergent data --> H["The BU corrects it with ChangePersonInfo"]
F -- Disapproved --> I["The BU evaluates the reason and guides the end customer"]
While the account remains limited, outgoing transactions are allowed only to accounts of the same ownership.
How to track the result
A successful API response only confirms that the request was received. The result arrives through webhooks:
| Webhook | What it brings | What the BU must do |
|---|---|---|
| Account webhook | The account condition changed, for example from Limited to Verified. | Update the condition in the BU system. The restrictions of the limited account stop applying only when the account is Verified. |
| UpdatePersonCondition | The result of the KYC and AML analysis. | If divergent data arrive (classification 0), correct them with ChangePersonInfo. See Updating Registration Data. |
| Documents webhook | The status of each document sent. | Resend what is rejected. |
The meaning of each value is in Webhooks and in Account Status.
How to handle the conversion
- Query the account and confirm that it is limited before calling the method.
- Send the complete registration and documents at once, to avoid new pending items.
- Store the USN and relate it to the original request, together with the TaxNumber, the account, the method, the payload, the response and the webhooks.
- Update the account condition in the BU system only with the final result.
- At the final activation, Fits may query BC Protege+. If there is an active restriction, the flow may be interrupted, and the customer must check and regularize the protection on gov.br before a new request.
Updated 11 days ago

