Opening Modes
This page explains how to open an account for your end customer: which opening modes exist, which data to send in each one, how limited (simplified) accounts work and the Locker account. Before you start, confirm that the customer is eligible in Eligibility.
Choose the opening mode
| Mode | Method | When to use |
|---|---|---|
| Full account, individual or company | NewAccount | Standard opening, with all required data and documents. |
| Limited (simplified) account, individual | LimitedAccount | Simplified opening, with less registration data and usage limits. |
| Limited (simplified) account, company | CompanyLimitedAccount | Simplified opening for a company, with minimum data, to issue charges and make withdrawals. |
| Locker account | CreateLockerAccount | Account linked to an existing regular account, used to separate funds. |
The diagram shows which method to use and what a successful return means.
flowchart TD
A{"Which mode to use?"}
A -->|"Individual or company, full account"| B["NewAccount"]
A -->|"Individual, limited account"| C["LimitedAccount"]
A -->|"Company, limited account"| D["CompanyLimitedAccount"]
A -->|"Account linked to an existing regular account"| E["CreateLockerAccount"]
B --> F["Response with Success true"]
C --> F
D --> F
F --> G["Request received, not approved"]
G --> H["Analysis result by webhook"]
How to read the Requirement column
Each data item has its requirement. Mandatory is the data that must be sent. Optional is the data that can be left out. Conditional is the data whose requirement depends on another data item, as described in the text.
Full account, individual (NewAccount)
Request fields
| Data | API field | Requirement |
|---|---|---|
| Full name | PersonName | Mandatory |
| CPF | TaxNumber | Mandatory |
| Nationality | Nationality | Mandatory |
| PEP declaration | PubliclyExposedPerson | Mandatory |
| Monthly income | MonthlyIncome | Mandatory |
| Addresses | Addresses | Mandatory |
| Street | Addresses[].AddressLine | Mandatory |
| Neighborhood | Addresses[].Neighborhood | Mandatory |
| City | Addresses[].CityName | Mandatory |
| State | Addresses[].State | Mandatory |
| ZIP code | Addresses[].ZipCode | Mandatory |
| City code | Addresses[].CityCode | Mandatory |
| Country | Addresses[].Country | Mandatory |
| Address type | Addresses[].AddressType | Mandatory |
| Number | Addresses[].AddressLine2 | Optional |
| Complement | Addresses[].Complement | Optional |
| Reference | Addresses[].Reference | Optional |
| Terms acceptance | WasSigned | Mandatory |
| Signature date | SignatureDate | Mandatory |
| Date of birth | BirthDate | Mandatory |
| Mandatory | ||
| Phone | PhoneNumber | Mandatory |
| Bank data | Bank, branch, account and digit fields | Optional |
The address fields marked as Mandatory must be sent in every request. Number, Complement and Reference are always optional. The monthly income (MonthlyIncome) is mandatory and must be greater than zero, otherwise the request is refused. If the income is not sent, the response is error EXE0056.
The documents for individuals are listed in Required Documents.
With NewAccount, Fits identifies whether the customer is an individual or a company by the length of the TaxNumber (11 digits for a CPF, 14 for a CNPJ). Do not send the IsCompany field: it is not an input field and, if sent, it is ignored.
Full account, company (NewAccount)
Request fields
| Data | API field | Requirement |
|---|---|---|
| Legal name | PersonName | Mandatory |
| CNPJ | TaxNumber | Mandatory |
| Legal nature | CompanyType | Mandatory |
| Economic activity (up to 200 characters, no special characters) | CompanyActivity | Mandatory |
| Constitution date | ConstitutionDate | Mandatory |
| Monthly revenue | MonthlyIncome | Mandatory |
| Monthly revenue justification (company only) | MonthlyIncomeJustification | Conditional |
| Addresses | Addresses | Mandatory |
| Street | Addresses[].AddressLine | Mandatory |
| Neighborhood | Addresses[].Neighborhood | Mandatory |
| City | Addresses[].CityName | Mandatory |
| State | Addresses[].State | Mandatory |
| ZIP code | Addresses[].ZipCode | Mandatory |
| City code | Addresses[].CityCode | Mandatory |
| Country | Addresses[].Country | Mandatory |
| Address type | Addresses[].AddressType | Mandatory |
| Number | Addresses[].AddressLine2 | Optional |
| Complement | Addresses[].Complement | Optional |
| Reference | Addresses[].Reference | Optional |
| People of the company (partners and representatives) | Persons | Mandatory |
| Terms acceptance | WasSigned | Mandatory |
| Signature date | SignatureDate | Mandatory |
| Company email | Mandatory | |
| Company phone | PhoneNumber | Mandatory |
| Digital contract (see Digital contract) | Contract and Signatories | Conditional |
| Bank data | Bank, branch, account and digit fields | Optional |
The address fields marked as Mandatory must be sent in every request. Number, Complement and Reference are always optional. The monthly revenue (MonthlyIncome) is mandatory and may be zero, provided the justification (MonthlyIncomeJustification) is filled in; without it, the request is refused. The justification is therefore mandatory when the revenue is zero, and it is used only when opening a company account. If the revenue is not sent, the response is error EXE0056.
Response fields
The NewAccount response is the same for individuals and companies.
| Field | Description |
|---|---|
| Success | "true" or "false", as text. |
| Message | Success message. Comes when the opening is registered as a request. |
| AccountKey | Key of the account created. Comes in the normal opening flow. |
| Code | Currently always empty. |
| CardResult | "True" or "False", as text. Comes only when the BU requests a card at opening. |
The success messages are listed in the Success Catalogue.
People of the company
Inform in the list of persons (Persons) all partners and representatives of the company. Partners must be individuals, as explained in Eligibility. The table below lists the main fields of each person. All other fields follow those of an individual, with the same requirements.
| Data | API field | Requirement |
|---|---|---|
| Full name | PersonName | Mandatory |
| CPF | TaxNumber | Mandatory |
| Role in the company (1 Attorney, 2 Cardholder, 3 Associate, 4 Manager) | PersonRoleType | Mandatory |
| Nationality | Nationality | Mandatory |
| PEP declaration | PubliclyExposedPerson | Mandatory |
| Date of birth | BirthDate | Mandatory |
| Mandatory | ||
| Phone | PhoneNumber | Mandatory |
| Monthly income (greater than zero) | MonthlyIncome | Mandatory |
Digital contract (company account)
In the full account of a company, NewAccount accepts the digital contract. The data below is Conditional: it applies only when the digital contract is used.
| Data | API field | Requirement |
|---|---|---|
| Contract model (0 AcceptanceTerm, 1 DigitalSignature) | Contract.ContractModel | Conditional |
| Signatories of the contract | Signatories | Conditional |
| Signatory CPF | Signatories[].TaxNumber | Conditional |
| Signatory role (0 Buyer, 1 Seller) | Signatories[].SignatoryRole | Conditional |
With ContractModel 1 (DigitalSignature), the buyer (SignatoryRole 0) receives the contract by email to sign it, and the progress arrives through the UpdatePersonContract webhook, described in Webhooks. The values of the webhook are in the Code Mapping.
The Signatories list follows these rules. Each rule that is not met returns the error shown, which is in the Error Catalogue:
| Error | When it occurs |
|---|---|
| EXE0096 | The Signatories list is empty |
| EXE0097 | A signatory is not among the persons of the request (Persons) |
| EXE0098 | There is no signatory with the buyer role |
| EXE0099 | There is more than one buyer |
| EXE0100 | The same person is buyer and seller |
| EXE0101 | The same role was informed more than once for the same signatory |
Bank data
The opening methods accept the bank data of the account: bank, branch, account and digit. They are optional, but required when your end customer needs to have more than one account, to tell one from the other. Note: these are only internal bank data and are not SPB data (Brazilian Payments System).
Limited (simplified) account
A limited account is a simplified account: it requires less registration data than a full account and has usage limits. The remaining data is filled in at the upgrade to a full account, with UpdatePersonData, subject to the BU rules, as explained in Upgrading a Limited Account.
Individual (LimitedAccount)
Request fields
| Data | API field | Requirement |
|---|---|---|
| CPF | TaxNumber | Mandatory |
| PEP declaration | PubliclyExposedPerson | Mandatory |
| Name | Name | Mandatory |
| Phone | Phone | Mandatory |
| Mandatory | ||
| Nickname | Nickname | Optional |
| Date of birth | BirthDate | Mandatory |
| Monthly income | MonthlyIncome | Mandatory |
| Addresses | Addresses | Mandatory |
| Validation type (send 0: validation done by Fits) | ValidationType | Mandatory |
| Terms acceptance | WasSigned | Mandatory |
| Signature date | SignatureDate | Mandatory |
| Bank data | Bank, branch, account and digit fields | Optional |
The LimitedAccount does not receive nationality. The Addresses list is mandatory and has the same fields as the Addresses list of NewAccount for individuals, all mandatory except Number, Complement and Reference, which remain optional. Without the list, nothing is saved and the response is error EXE0056; with a mandatory field missing, the request is refused. An invalid ZIP code returns error EXE0109. The monthly income (MonthlyIncome) is mandatory and must be greater than zero; if it is not sent, the response is error EXE0056.
Response fields
| Field | Description |
|---|---|
| Success | "true" or "false", as text. |
| Message | Success message. |
| AccountKey | Key of the account created. |
| RequestIdentifier | Identifier of the request. Comes only when it exists. |
The success messages are listed in the Success Catalogue.
Usage restrictions:
- the maximum amount transacted is defined by the compliance and risk area of the Business Unit (BU);
- transactions outside the ecosystem are not allowed, except between accounts with the same ownership.
Company (CompanyLimitedAccount)
Request fields
| Data | API field | Requirement |
|---|---|---|
| Name | PersonName | Mandatory |
| Phone | Phone | Mandatory |
| CNPJ | TaxNumber | Mandatory |
| Mandatory | ||
| Constitution date | ConstitutionDate | Mandatory |
| Validation type (send 0: validation done by Fits) | ValidationType | Mandatory |
| Legal nature | CompanyType | Mandatory |
| Terms acceptance | WasSigned | Mandatory |
| Signature date | SignatureDate | Mandatory |
| People of the company, including the signer | Persons | Mandatory |
| Addresses | Addresses | Mandatory |
| Bank data | Bank, branch, account and digit fields | Optional |
The CompanyLimitedAccount does not receive economic activity or revenue. The Addresses list is mandatory and has the same fields as the Addresses list of NewAccount for individuals, all mandatory except Number, Complement and Reference, which remain optional. Without the list, nothing is saved and the response is error EXE0056; with a mandatory field missing, the request is refused. An invalid ZIP code returns error EXE0109.
Response fields
| Field | Description |
|---|---|
| Success | "true" or "false", as text. |
| Message | Success message. |
| AccountKey | Key of the account created. |
| RequestIdentifier | Identifier of the request. Comes only when it exists. |
The success messages are listed in the Success Catalogue.
Allowed inflows: boleto, collection order (CollectionOrder), incoming TED (TEDIn) and incoming PIX (PIXIn).
Outbound transfers only to accounts of the same ownership.
Limited account rules
Limited accounts, for individuals and companies, are opened without all the information and documents of a full account. For this reason this rule applies: outgoing transactions are allowed only to accounts with the same ownership.
The opening of a limited account is atomic from the BU's point of view: the account remains created only if the whole opening process finishes successfully. Before saving any data, Fits checks the KYC configuration of the BU; if it does not allow the opening, the request is refused with error EXE0047.
At the time of opening, tell your end customer that the account has an operational restriction. Do not present the account as Verified while any document is pending. The tracking rules are in Pending Documents.
Locker account
The Locker account (CreateLockerAccount) is linked to a single regular account of the customer. A regular account can have several Locker accounts.
The request and response fields of CreateLockerAccount are in Locker Account.
After the request
A successful API response confirms that the request was received, not that the account was approved. The result of the analysis arrives through webhooks, as described in Tracking Account Processing. Opening times are in SLAs.
The errors returned by these methods are listed in the Error Catalogue, in the sections "NewAccount, CreateAccount, LimitedAccount and CompanyLimitedAccount" and "CreateLockerAccount".
Updated 11 days ago

