BC Protege+
This page explains BC Protege+, the check that Fits makes against the Central Bank service before opening accounts, adding signers or unlocking accounts, and shows what the BU receives and what it must do in each case.
What BC Protege+ is
BC Protege+ is a free service provided by the Central Bank that allows individuals and companies to notify the financial system that they do not want to open new accounts or be included as representatives in third-party accounts.
- the citizen can activate or deactivate the protection at any time, with immediate effect, on the gov.br platform;
- financial institutions are required to check the system before opening accounts or adding representatives.
When BC Protege+ is checked
Fits checks BC Protege+ in the following situations:
- when opening accounts (individuals and companies);
- when adding new holders or representatives to existing accounts;
- in critical registration changes, such as a change of CPF or CNPJ (Coming soon);
- in the account registration, at final activation (Coming soon).
What the BU receives in each case
When the person has BC Protege+ active, the request is denied. The BU finds out through the webhook indicated in the table and, for the account, through the Blocked condition (see Account Status). The fields of each webhook are in Webhooks.
| Situation | Scenario | Where it appears | Message returned |
|---|---|---|---|
| Account opening | The individual or company has BC Protege+ active when requesting the account opening | UpdatePersonCondition webhook, with MessageClassification 1 (Disapproved) | Account creation blocked. "Negado por restrição no BC Protege+. Oriente o usuário a rever o(s) CPF/CNPJ {0} e somente envie uma nova solicitação após revisão" |
| Change of the person's data (Coming soon) | The person has BC Protege+ active and a data change is made | UpdatePersonCondition webhook | Change denied, because the CPF or CNPJ has active protection in BC Protege+. "Negado por restrição no BC Protege+. Oriente o usuário a rever o(s) CPF/CNPJ {0} e somente envie uma nova solicitação após revisão" |
| Adding a signer | The signer has BC Protege+ active | Signer webhook (Method FBWebhookWorkerUpdateSignerSolicitation), with SignerSolicitationStatus Reprovado (see Adding Signers) | Signer addition not allowed. "Negado por restrição no BC Protege+. Oriente o usuário a rever o(s) CPF/CNPJ {0} e somente envie uma nova solicitação após revisão" |
| Account unlock | A new or updated account was blocked because a person or a signer has BC Protege+ active | Blocked condition in the account webhook and the UnlockAccount method (see Blocking and Unlocking) | The unlock is denied while the restriction exists |
What the BU must do
- in the opening, the change and the addition of a signer: guide the end customer to review the CPF or CNPJ informed and to regularize the protection on gov.br, and only send a new request after that review;
- in the unlock: use the UnlockAccount method with the Protege+ justification (6). Fits checks BC Protege+ again, and the unlock only proceeds if there is no restriction. The attempt limit, the interval between attempts and the restriction time are parameters defined per BU and are in Blocking and Unlocking. The result is asynchronous: a denial generates a notice, but an approval must be tracked by querying the account;
- if the signer was added with the AddSigner method, after the restriction is regularized, call AddSigner again for the signer that caused the block, so that it is checked again and the account can be unlocked.
In the opening, the addition of a signer and the unlock, the BC Protege+ check follows this decision:
flowchart TD
A["Opening, signer addition or unlock"] --> B["Fits checks Protege+"]
B --> C{"Protege+ active?"}
C -->|No| D["Request proceeds"]
C -->|Yes| E["Request denied and the BU receives the notice in the table"]
E --> F["BU guides the customer to regularize"]
F --> G["BU resends only after the regularization"]
G --> A
In the unlock, the new attempt is requested by the BU with UnlockAccount and justification 6, and the result is asynchronous:
flowchart TD
A["Account blocked by a Protege+ restriction"] --> B["BU calls UnlockAccount with justification 6"]
B --> C["Fits checks Protege+ again"]
C --> D{"Protege+ active?"}
D -->|Yes| E["Unlock denied and the denial generates a notice"]
D -->|No| F["Unlock proceeds, asynchronous result"]
F --> G["BU tracks the result by querying"]
The errors returned by these methods are listed in the Error Catalogue, in the sections "BlockAccount and UnlockAccount" and "AddSigner".
Updated 11 days ago

