Sending Documents

This page explains how to send documents after the account was opened: how to resend a document that was requested at opening (ResendDocuments) and how to send an extra document, without changing the registration (SendDocument). 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
A document requested at opening must be sent againResendDocumentsThe document was considered invalid, illegible or incorrect, or Fits asked for it again. The BU is notified by the documents webhook.
Send an extra document, without changing the registrationSendDocumentOnly when the method is enabled for the BU. It stores the document, but does not run KYC or document analysis.

Flow to choose the method:

flowchart TD
  A["The BU needs to send a document"] --> B{"Did Fits request this document at opening, or request it again?"}
  B -- Yes --> C["Use ResendDocuments"]
  B -- No, it is an extra document --> D{"Is SendDocument enabled for the BU?"}
  D -- Yes --> E["Use SendDocument"]
  D -- No --> F["Talk to Fits before sending"]
  C --> G["Track the result through the documents webhook"]
  E --> G

ResendDocuments

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 who owns the documents.
HolderTaxNumberOptionalCPF or CNPJ of the account holder.
DocumentsMandatoryList of the documents to resend. Each item has the fields below.
Documents.DocumentFileMandatoryContent of the file, in base64.
Documents.DocumentFormatMandatoryFormat of the file, as a number, which must match the file sent. Values in Code Mapping, section Document format.
Documents.DocumentNameMandatoryName of the document.
Documents.DocumentTypeMandatoryType of the document, as a number. Values in Code Mapping, section Document type.
Documents.DescriptionMandatoryDescription of the document.
Documents.DocumentKeyOptionalKey of the document. Do not repeat a DocumentKey that was already sent.

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

SendDocument

Request fields

FieldRequirementDescription
RequestIdentifierMandatoryIdentifier of the request the document belongs to.
DocumentIdMandatoryIdentifier of the document.
DocumentTypeMandatoryType of the document, as a number. Values in Code Mapping, section Document type.

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

Before sending

A file that does not meet the requirement comes back as a pending item and delays the analysis. Check these points before calling the method:

  • The document is complete, without cuts, and all the information is visible.
  • The image is legible, without glare, shadows or low resolution.
  • Front and back were sent, when the document has both sides.
  • The document is valid, intact and matches the type informed.
  • The data in the document matches the registration data.
  • The file is not corrupted or empty.

Do not reuse documents that are expired, cropped or that do not match the DocumentType informed. When the registration is made by someone who is not a partner, administrator, building manager or direct legal representative, send the power of attorney with specific powers, issued at most 90 days ago, together with the identity document of the attorney and the signed attorney form.

Document type

The DocumentType field says which document is being sent. The numbers and the documents required for each account type are in Required Documents. Send the type that matches the document, and check in the API Reference the types that each method accepts.

How to track the result

The API response only confirms that the submission was received, not that the document was approved. The result of the analysis arrives through the documents webhook, with the status of each document. The meaning of each status and what to do in each one are in Pending Documents.

ResendDocuments does not limit the number of resubmissions. Each call is evaluated by the state of the process and by the rules of the document, such as a duplicated DocumentKey, an invalid type or format, and a missing front or back. Resend the document as soon as the pending item arrives.

The errors returned by these methods are listed in the Error Catalogue, in the section "SendDocument and ResendDocuments".

How to handle submissions

  1. Validate the format, legibility and type of the document before calling the method.
  2. Keep the original document, the pending item and the resubmission, linked to the TaxNumber, the USN and the account.
  3. When the webhook brings the rejection reason, fix that point before resending.
  4. Do not treat the successful API response as approval of the document.
  5. Protect the personal data that appear in the documents, according to the security and privacy policy.

Did this page help you?