Adding Signers

A signer is a person authorized to operate the account of a company. This page explains how to add a signer after the account has already been opened, with the AddSigner method. The inclusion is its own flow, with validation of identity, documents, Compliance, Risk and BC Protege+, and it only takes effect after the final approval. The fields of the methods are in the tables below. All methods also receive the general fields Method, PartnerId and BusinessUnitId. To query signers and requests, see Signers.

Before requesting the inclusion

  • The account must be active and unlocked.
  • The account holder must be active and verified. Otherwise, the request is denied.
  • The signer must be an individual and of legal age. A CNPJ cannot be a signer, and a signer who is a minor is refused.

What to send (AddSigner)

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
HolderTaxNumberMandatoryCPF or CNPJ of the account holder.
AccountKeyMandatoryKey of the account the signer will be linked to.
JustificationMandatoryReason for adding the signer, as free text.
SignerMandatoryData of the signer. The fields are in the following rows.
Signer.NameMandatoryFull name of the signer.
Signer.TaxNumberMandatoryCPF of the signer.
Signer.MailMandatoryEmail of the signer.
Signer.PhoneNumberMandatoryPhone of the signer.
Signer.MotherFullNameMandatoryFull name of the mother.
Signer.NationalityMandatoryNationality of the signer.
Signer.BirthDateMandatoryDate of birth.
Signer.BirthStateMandatoryCode of the state of birth, as a number.
Signer.PubliclyExposedPersonMandatoryInforms whether the signer is a politically exposed person (PEP), with true or false.
Signer.PersonRoleTypeMandatoryRole of the signer, as a number. Values in Code Mapping, section Role of the person.
Signer.WasSignedMandatoryInforms whether the signer accepted the terms.
Signer.SignatureDateMandatoryDate the terms were signed.
Signer.DocumentsMandatoryDocuments of the signer, as in Required Documents.
Signer.OccupationOptionalOccupation of the signer.
Signer.FatherNameOptionalName of the father.
Signer.SpouseNameOptionalName of the spouse.
Signer.AddressesOptionalAddresses of the signer. In each address, AddSigner validates AddressLine and AddressType (errors in the Error Catalogue, section AddSigner).
Signer.MonthlyIncomeOptionalMonthly income of the signer.

The role of the signer (PersonRoleType) is required and accepts: 1 (Procurador), 2 (Portador), 3 (Associado) or 4 (Dirigente). Do not send 0 (Holder), which identifies the account holder itself: AddSigner returns EXE0054. The required documents are in Required Documents. The values of PersonRoleType are listed in the Code Mapping, in the section Role of the person.

Response fields

FieldDescription
Success"true" or "false".
MessageReturn message, described in the Success Catalogue.
USNIdentifier of the request. Use it in GetRequestSigner and to relate the webhook to the request.

How the analysis works

Fits evaluates the request within 48 hours. The inclusion only takes effect after the final approval.

flowchart TD
  A["The BU sends the signer data and documents"] --> B["Fits verifies the account holder"]
  B --> C["Signer KYC"]
  C --> D["BC Protege+ query"]
  D --> E["Compliance and Risk analysis of the link with the company"]
  E --> F{"Result in the signer webhook"}
  F -- Aprovado --> G["The BU updates the signer link"]
  F -- Reprovado --> H["The BU does not link the signer and evaluates the cause"]

How to track the result

A successful API response only confirms that the request was received. The result arrives through the signer webhook, with the status Gerada, Aprovado or Reprovado (Method FBWebhookWorkerUpdateSignerSolicitation). The Gerada notice is not sent in every case. To query the request at any time, use GetRequestSigner.

ResultWhat the BU must do
AprovadoUpdate the signer link in the BU system, only after receiving the final return.
ReprovadoDo not link the signer and evaluate the cause, checking the webhook and GetRequestSigner.

GetRequestSigner

GetRequestSigner queries the status of a signer inclusion request made with AddSigner.

Request fields

FieldRequirementDescription
USNMandatoryIdentifier of the request, returned by AddSigner.

Response fields

FieldDescription
Success"true" or "false".
RequestStatusStatus of the request, as text, such as Gerada, Sob análise interna, Aprovado, Reprovado or Pendente de Documentos. See the Code Mapping, section Signer request status.
USNIdentifier of the request.
HolderDataData of the account holder.
HolderData.TaxNumberCPF or CNPJ of the holder.
HolderData.TrandingNameTrade name of the holder.
HolderData.ConstitutionDateConstitution date of the holder.
SignatoryDataData of the requested signer.
SignatoryData.NameName of the signer.
SignatoryData.TaxNumberCPF of the signer.
SignatoryData.BirthDateDate of birth of the signer.
SignatoryData.PersonRoleTypeRole of the signer, as text, such as Procurador, Portador, Associado or Dirigente.
SignatoryData.JustificationReason given at the inclusion, as free text.

The errors of GetRequestSigner are listed in the Error Catalogue, in the section "GetSigners and GetRequestSigner".

BC Protege+

Fits queries BC Protege+ when a signer is added. If a single signer has an active restriction, the request may be disapproved, and this may affect the company account. In that case, the customer must check and regularize the protection on the gov.br environment before a new request. See more in BC Protege+.

The errors returned by this method are listed in the Error Catalogue, in the section AddSigner.

How to handle the inclusion

  1. Check the conditions of the account and of the holder before calling the method.
  2. Send all the required data and documents at once.
  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 signer link only with the final return of the webhook.
  5. If the webhook does not arrive, query the request with GetRequestSigner before asking again.

Did this page help you?