Locker Account

This page explains the Locker account: an account linked to a regular account, created by the CreateLockerAccount method, with its own rules for linking, creation and closing.

What it is for

The Locker account meets the need for an efficient, secure and practical solution to manage financial resources in different operations. It lets the end customer isolate and control their transactions without losing flexibility and without leaving the Fits compliance rules. Every Locker account is linked to a regular account, which ensures that operations follow the required regulatory standards and gives more control and security.

Benefits:

  • Isolate funds: set aside money for specific goals, such as a project, buying a property or an emergency fund, with better control over how the funds are used.
  • Increased security: by keeping funds isolated in a Locker linked to the regular account, the customer reduces the risk of confusion or misuse.
  • Ease of control: there is no need to create a new independent bank account. The Locker is linked to the regular account, and management stays centralized.
  • Transparency: all transactions made in the Locker are recorded and monitored, with full visibility of the funds and how they are used.

Examples of use:

  • Project fund: a customer who plans to buy a property creates a Locker named "Real estate purchase" to separate the money for that goal and make sure it is used for the intended purpose.
  • Savings and financial planning: the customer sets aside part of the funds for long-term goals and keeps the rest in the regular account for daily expenses.

Linking rules

  • Linking: each Locker account is linked to a single regular account, and that regular account must belong to the same BU and have the Verified or Limited condition, with the KYC completed or KYC partially performed reason. A Limited account can receive a Locker if it meets these requirements. If the regular account belongs to another BU or does not meet this condition and this reason, the request is refused.
  • Linking limit: a regular account can have several Locker accounts, but each Locker can only be linked to one regular account.

Creating a Locker account

Use the CreateLockerAccount method. Besides the credentials and the fields common to all requests, described in Getting Started, the request carries the fields below. Request examples are in the API Reference.

Request fields

In the Requirement column, Mandatory means the field must be sent; Optional, that it can be left out; Conditional, that it depends on another field, as described.

FieldRequirementDescription
RegularAccountMandatoryData of the regular account linked to the Locker. Send the AccountKey or the Banks object.
RegularAccount.AccountKeyConditionalKey of the regular account. Required if Banks is not sent.
RegularAccount.BanksConditionalBank data of the regular account. Required if the AccountKey is not sent.
RegularAccount.Banks.HolderTaxNumberConditionalCPF or CNPJ of the holder of the regular account. Required if Banks is sent.
RegularAccount.Banks.BankConditionalBank code of the regular account. Required if Banks is sent.
RegularAccount.Banks.BankBranchConditionalBranch code of the regular account. Required if Banks is sent.
RegularAccount.Banks.BankAccountConditionalNumber of the regular account. Required if Banks is sent.
RegularAccount.Banks.BankAccountDigitConditionalDigit of the regular account. Required if Banks is sent.
LockerAccountMandatoryData of the Locker account to be created.
LockerAccount.LockerNickNameMandatoryNickname that identifies the purpose of the account. There is no validated size limit.
LockerAccount.BankMandatoryBank code of the Locker account, digits only, up to 4 characters.
LockerAccount.BankBranchMandatoryBranch code of the Locker account, digits only, up to 10 characters.
LockerAccount.BankAccountMandatoryNumber of the Locker account, digits only, up to 20 characters.
LockerAccount.BankAccountDigitMandatoryDigit of the Locker account, up to 2 characters (letters are accepted).

The BU provides the bank, branch, account and digit of the Locker account. Fits validates and stores these details and generates only the AccountKey. The bank combination must be unique among all intermediary accounts in the system, not only within the BU. If it already exists, the request is refused.

The diagram summarizes the conditions to create the Locker account.

flowchart TD
  A["The BU calls CreateLockerAccount"] --> B{"Is the regular account from the same BU?"}
  B -->|"No"| X["Request refused"]
  B -->|"Yes"| C{"Verified or Limited condition, with KYC completed or partially performed?"}
  C -->|"No"| X
  C -->|"Yes"| D{"Is the Locker bank combination new in the system?"}
  D -->|"No"| X
  D -->|"Yes"| E["Locker account created, with the AccountKey in the response"]

Response fields

FieldDescription
Success"true" or "false", as text.
MessageSuccess message.
AccountKeyKey of the Locker account created.

The success messages are listed in the Success Catalogue. The method does not generate a webhook. The errors returned by these methods are listed in the Error Catalogue, in the sections CreateLockerAccount and CloseAccount.

Closing a Locker account

The CloseAccount method accepts Locker accounts, with these rules. The general method is described in Closing an Account.

The diagram shows what happens depending on the account informed.

flowchart TD
  A["The BU calls CloseAccount"] --> B{"Which account will be closed?"}
  B -->|"Locker account, informed by AccountKeys"| C{"Does the Locker have a balance?"}
  C -->|"Yes"| D["Refused due to remaining balance"]
  C -->|"No, and no other blocking condition"| E["Closes directly, without a formal request"]
  E --> F["The Locker is removed and unlinked from the regular account"]
  B -->|"Regular account"| G{"Does it have Locker accounts?"}
  G -->|"Yes"| H["Refused: close all the Lockers first"]
  G -->|"No"| I["Closing of the regular account continues"]
  1. Balance check: if the Locker account has a balance, the closing is not allowed, and the response returns the remaining balance error; the customer must clear the balance and request the closing again. With no balance and no other condition that prevents the closing, it is direct, without a formal request, and the Locker account is removed automatically.
  2. Unlinking: once closed, the Locker is automatically unlinked from the regular account it was associated with. No unlinking request is needed.
  3. Identification: in CloseAccount, the Locker is informed by its AccountKey (AccountKeys field).
  4. Regular account with Lockers: all Locker accounts must be closed before the regular account is closed (error EXC0083).
  5. Notice: closing a Locker does not generate the UpdateCloseAccount webhook.

Next step

To compare the Locker account with the full and the limited account, see Opening Modes.


Did this page help you?