Updating Registration Data

This page explains how to correct or update the registration data of a person after the opening (ChangePersonInfo) and how to add the first address to an account that has none (RegisterAddress), and how to query a change request already made (GetChangeInfo). The fields of each method are in the tables below. All methods also receive the general fields Method, PartnerId and BusinessUnitId.

Which method to use

SituationMethodWhen to use
Correct or update registration dataChangePersonInfoOnly after a request from Fits, for example when the UpdatePersonCondition webhook indicates divergent data.
Add the first addressRegisterAddressOnly for an account that has no address. Do not use it to change an address that already exists.
Query a change requestGetChangeInfoAfter sending a change with ChangePersonInfo, to check the status of the request by its USN.

To convert a limited account into a full account, see Upgrading a Limited Account.

How the registration correction works

When the analysis of an opening finds incorrect data, Fits notifies the BU through the UpdatePersonCondition webhook, with classification 0 (Divergent Information) and the list of fields that need correction. The BU queries the data it sent, corrects the indicated fields with ChangePersonInfo and waits for the result.

flowchart TD
  A["UpdatePersonCondition webhook with classification 0"] --> B["The BU queries the data it sent"]
  B --> C["The BU calls ChangePersonInfo with the indicated fields"]
  C --> D["Fits runs KYC and AML analysis within 48 business hours"]
  D --> E{"Result in the UpdatePersonInfo webhook"}
  E -- Approved --> F["Data updated"]
  E -- "Approved, with Rejected items" --> G["Only the approved fields were updated"]
  E -- Rejected --> H["Data not updated and the account remains blocked"]

A successful API response only confirms that the request was received. Track the progress by the USN, the identifier that comes in the response and also in the webhook.

ChangePersonInfo

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.

FieldRequirementDescription
TaxNumberMandatoryCPF or CNPJ of the person whose data will be changed.
HolderTaxNumberConditionalCompany CNPJ, sent when the TaxNumber belongs to a person who is part of that company's corporate structure. It must be a CNPJ and cannot be the same person as the TaxNumber.
PersonInfosMandatoryList of the data to change, one item for each data. To change the address, send together the items AddressLine, AddressLine2, ZipCode, CityName, State and CountryOfResidence.
PersonInfos.PersonInfoTypeMandatoryNumber of the data to change, from 0 to 28. Values in Code Mapping, section Registration data changed.
PersonInfos.PersonInfoValueMandatoryNew value of the data, as text.
WasSignedMandatoryInforms whether the end customer accepted the terms.
SignatureDateMandatoryDate the terms were signed.

Response fields

FieldDescription
Success"true" or "false".
MessageReturn message, described in the Success Catalogue.
USNIdIdentifier (USN) of the request. Use it to track the result and to query the request with GetChangeInfo.

ChangePersonInfo rules

  • Use the method only when there is a request from Fits.
  • The analysis time is up to 48 business hours, and pending items or divergences may increase it.
  • For sensitive data, the limit is 3 accepted requests per TaxNumber, counted separately by BU and Partner. The counter is valid for 30 days and restarts at each request counted, and the fourth request is refused. The refusal message gives the time left for a new attempt: in days, when 1 day or more is left (EXE0153), or in hours, when less than 1 day is left (EXE0154). Changes only to phone, email or address do not count. The sensitive data are:
    • Individual: the full name, the mother's name and the date of birth.
    • Company: the trade name, the legal name, the constitution date and the company type.
  • To change the address, send all the address fields together (the items listed in the request fields table). Sending only one of them returns an error.
  • ChangePersonInfo only changes an address that already exists: for a person with no registered address, the return is EXE0160 ("There is no address for this person"). To add the first address, use RegisterAddress.
  • Informing whether the end customer accepted the terms and the signature date is required (see the request fields table). By requesting the change, the customer accepts the latest version of the terms.
  • The request may be granted in part: only the approved fields are updated.
  • In changes to critical data, such as a change of CPF or CNPJ, Fits may query BC Protege+. An active restriction may deny the update, and in that case the customer must check and regularize the protection on gov.br before a new request.

The data that can be changed, with the number of each one (PersonInfoType), are in Code Mapping.

Monthly income is not required in the registration data change (ChangePersonInfo).

The diagram below shows the limit of 3 requests in 30 days for sensitive data.

flowchart TD
  A["The BU sends ChangePersonInfo"] --> B{"What does the request change?"}
  B -->|"Only phone, email or address"| C["Does not count toward the limit"]
  B -->|"Sensitive data"| D{"Are there already 3 accepted requests in the last 30 days?"}
  D -->|No| E["Request accepted: counts as one of the 3 and restarts the 30-day count"]
  D -->|Yes| F["Fourth request refused with the time left"]
  F --> G{"How much time is left?"}
  G -->|"1 day or more"| H["Time left given in days"]
  G -->|"Less than 1 day"| I["Time left given in hours"]

Result of the request

The result arrives through the UpdatePersonInfo webhook, which carries the USN of the request and has three messages: created, approved and rejected. When the message is Approved, update the data in the BU system only with the approved fields, because the request may be granted in part. When it is Rejected, keep the current data, evaluate the reason and guide the end customer. The description of the webhook is in Webhooks.

Adding the first address

RegisterAddress adds the first address to an account that has none, for example for card delivery and for compliance with BACEN rules. All the address fields are required.

Request fields

FieldRequirementDescription
TaxNumberMandatoryCPF or CNPJ of the person who will receive the address.
AddressLine2MandatoryHouse number.
ComplementMandatoryComplement of the address.
Other address fieldsMandatoryAll the address fields are required.

The response only brings Success (text "true" or "false") and Message, with the success message described in the Success Catalogue.

The errors returned by these methods are listed in the Error Catalogue, in the sections "UpdatePersonData and ChangePersonInfo", "RegisterAddress" and "GetChangeInfo".

Querying the request (GetChangeInfo)

GetChangeInfo queries a change request by its USN. The response returns the PersonInfoSolicitation object, described in the tables below.

Request fields

FieldRequirementDescription
USNMandatoryIdentifier of the request, in GUID format, returned by ChangePersonInfo in the USNId field.

Response fields

FieldDescription
Success"true" or "false".
PersonInfoSolicitationData of the request.
PersonInfoSolicitation.TaxNumberCPF or CNPJ of the person.
PersonInfoSolicitation.StatusStatus of the request, as text.
PersonInfoSolicitation.PersonInfosData changed in the request.
PersonInfoSolicitation.PersonInfos.PersonInfoTypeNumber of the data changed. Values in Code Mapping, section Registration data changed.
PersonInfoSolicitation.PersonInfos.PersonInfoValueNew value requested for the data.
PersonInfoSolicitation.PersonInfos.StatusStatus of the data, as text.

The Status of the request and of each field come as text: Created, Approved, Rejected, ApprovedJD, DisapprovedJD or AwaitingValidation. Use the query to check the result of a request, including the status of each field. The success return of the method is in the Success Catalogue and the errors are in the Error Catalogue.

How to handle changes

  1. Do not call ChangePersonInfo without a request from Fits.
  2. Query the data that was sent before correcting it.
  3. 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.
  4. Update the BU system only with the final result.
  5. Do not treat the successful API response as approval of the registration.
  6. For an address, send all the fields together.

Did this page help you?