> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Lerian SRC?

> Lerian SRC sends your institution's restriction consultations to BACEN's BC Protege+ and records BACEN's verdict for each protection type.

**Lerian SRC** is the Lerian service for **BC Protege+**, a BACEN system. Your institution consults BC Protege+ before it opens an account, and before it changes the ownership of an existing relationship. BC Protege+ answers whether the person or the company has an active restriction.

Lerian SRC exchanges messages with BACEN over the RSFN, through IBM MQ. It sends each consultation as an SRC0001 message. BACEN answers with an SRC0001R1 message, or rejects the consultation with an SRC0001E message.

The API is asynchronous. Lerian SRC accepts a consultation with `202` and the status `pending`. `pending` is a normal state. You read the outcome later, from the API or from an event.

## What Lerian SRC does and does not do

***

**Lerian SRC does:**

* Checks each request before it sends anything to BACEN. It checks the CPF or CNPJ check digits, the document type, the protection types, and the motivation.
* Stores each accepted consultation before it sends the consultation to BACEN.
* Sends the consultation again, within a budget of attempts, when a send fails or BACEN gives a transient rejection.
* Matches each answer and each rejection from BACEN to its consultation, and stores BACEN's verdict for each protection type.
* Keeps BACEN's rejection code as BACEN sent it.
* Records the institution record that your institution files after a consultation with an active restriction.
* Keeps an evidence trail for each consultation.
* Opens an operator case for each situation that your back office must see, such as a message that Lerian SRC refused to send.
* Publishes an event when it accepts a consultation, and when the consultation completes or fails.

**Lerian SRC does not:**

* **Decide on the account.** Lerian SRC records BACEN's verdict and the record that your institution files. It does not approve, block, or score a contract.
* **File an institution record on its own.** Your institution files each record through the API.
* **Connect to Midaz.** Your systems call Lerian SRC and act on the outcome.
* **Serve several institutions from one deployment.** One deployment serves one institution. A client with several institutions runs one deployment for each.

## Who it serves

***

Lerian SRC serves supervised institutions that consult BC Protege+ before they open an account or change the ownership of an existing relationship.

Your onboarding and KYC systems create consultations and read their outcomes. Your back office reads consultations and the evidence trail, files institution records, and works the operator cases.

## Glossary

***

| Term | Meaning |
| - | - |
| **BC Protege+** | The BACEN system that answers restriction consultations. |
| **Consultation** | One request to BC Protege+ about one CPF or CNPJ. |
| **Protection type** | What the consultation asks about: `account_opening`, `ownership_change`, or both. |
| **Verdict** | BACEN's answer for one protection type. `permitted` is `true` when BACEN reports no active restriction for that protection type, and `false` when BACEN reports an active restriction. |
| **Subject role** | The role of the consulted person or company: `individual`, `company`, `holder`, or `representative`. A `holder` or a `representative` consultation links to the consultation of its company. |
| **Motivation** | The reason for a consultation. `motivation.reference` names the event in your system that caused it, such as an account-opening request. |
| **BACEN control code** | The code that BACEN assigns to a consultation that it answers. The API returns it as `bcbControlCode`. |
| **Operation number** | The number your institution assigns to a consultation for BACEN. It starts with your CNPJ base, followed by a date and a sequence number. The API returns it as `regulatoryOperationNumber`. |
| **Institution record** | The record that your institution files after a consultation with an active restriction: an exceptional proceed or a refusal explanation. |
| **Evidence trail** | The records that Lerian SRC keeps about each consultation. |
| **Operator case** | An item in the back-office queue, such as a message that Lerian SRC refused to send. |
| **SRC and SCR** | Lerian SRC is not [Lerian SCR](/en/rails/scr/what-is-lerian-scr), a separate service for a different BACEN system. |

See also [Native messaging and partner interfaces](/en/rails/native-messaging).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.