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.
- 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
See also Native messaging and partner interfaces.