Skip to main content

Request Individual Account Opening

Account opening occurs in two mandatory stages. First, a POST request sends preliminary data to reserve the account. Then, a webhook of type account_request.status_change with status pending_additional_data is triggered. In the second stage, a PATCH request finalizes the opening, officializing the account with complementary information.

Request Account Reservation

Request

ENDPOINT
/account_request/checking
METHOD
POST
Request Body
{
"request_control_key": "5ef0f67a-7672-4d00-8a02-faf847157c4b",
"account_owner": {
"document_number": "99999999999",
"email": "email@teste.com",
"birthdate": "2017-09-16",
"name": "Titular da Conta",
"documents": {
"rg": {
"ocr_front_key": "2ef0f67a-7672-4d00-8a02-faf847157b4a",
"ocr_back_key": "1bd0e0a1-c1fa-4f9c-a230-f7a4163864be"
},
"cnh": {
"ocr_key": "7a73be1a-0b66-4c0a-932a-1d1d02efdc4c"
}
},
"face": "d38dd3c0-6f24-43b9-a37a-425d6700620f"
}
}
CPF/CNPJ Mock

To simulate approval, rejection, and manual analysis situations, you can use the first digit of the account owner's CPF/CNPJ:

0 to 7 -> Manual Analysis

8 -> Automatically rejected in KYC

9 -> Automatic Approval

Request Body Params

FieldTypeDescriptionCharacters
account_owner *objectObject containing the Account Holder informationaccount_owner Object
request_control_key *UUIDUnique identifier per partner request36

account_owner Object

FieldTypeDescriptionCharacters
document_number *stringAccount Holder CPF11
email *stringEmail11
birthdate *stringAccount Holder birthdate (YYYY-MM-DD format)10
name *stringAccount Holder Full Name50
documents*objectAccount holder document(s)documents Object
face*uuidv4Face recognition key from antifraud (face_recognition_key)36

documents Object

FieldTypeDescriptionCharacters
rgobjectOCR keys from front and back RG upload of the holderrg Object
cnhobjectOCR key from CNH upload of the holdercnh Object
cnh_digitalobjectOCR key from digital CNH upload of the holdercnh_digital Object
national_registry_of_foreignersobjectOCR keys from front and back RNE upload of the holdernational_registry_of_foreigners Object
national_migration_registryobjectOCR keys from front and back CRNM upload of the holdernational_migration_registry Object
passportobjectOCR key from passport upload of the holderpassport Object
cin_digitalobjectOCR key from digital National Identity Card upload of the holdercin_digital Object
Information

OCR keys (ocr_key or ocr_front_key and ocr_back_key) from document image uploads are provided as responses from image uploads in antifraud. The face_recognition_key is returned in the facial recognition response.

rg Object

FieldTypeDescriptionCharacters
ocr_front_key *uuidv4OCR key from RG front image upload36
ocr_back_key *uuidv4OCR key from RG back image upload36

OR

FieldTypeDescriptionCharacters
ocr_key *uuidv4OCR key from RG image upload36

cnh Object

FieldTypeDescriptionCharacters
ocr_front_key *uuidv4OCR key from CNH front image upload36
ocr_back_key *uuidv4OCR key from CNH back image upload36

OR

FieldTypeDescriptionCharacters
ocr_key *uuidv4OCR key from CNH image upload36

cnh_digital Object

FieldTypeDescriptionCharacters
ocr_key *uuidv4OCR key from digital CNH image upload36

national_registry_of_foreigners Object

FieldTypeDescriptionCharacters
ocr_front_key *uuidv4OCR key from RNE front image upload36
ocr_back_key *uuidv4OCR key from RNE back image upload36

OR

FieldTypeDescriptionCharacters
ocr_key *uuidv4OCR key from RNE image upload36

national_migration_registry Object

FieldTypeDescriptionCharacters
ocr_front_key *uuidv4OCR key from CRNM front image upload36
ocr_back_key *uuidv4OCR key from CRNM back image upload36

OR

FieldTypeDescriptionCharacters
ocr_key *uuidv4OCR key from CRNM image upload36

passport Object

FieldTypeDescriptionCharacters
ocr_key *uuidv4OCR key from passport image upload36

cin_digital Object

FieldTypeDescriptionCharacters
ocr_key *uuidv4OCR key from digital National Identity Card image upload36

Response

STATUS
201
Response Body
{
"account_info": {
"account_branch": "0001",
"account_digit": "0",
"account_number": "1693580"
},
"account_request_key": "f230f1b5-07af-4737-b0e3-8a472304f5e7",
"account_request_status": "pending_bacen_validation"
}
Bacen Protege+ Flow

The proposal starts with status pending_bacen_validation. The system performs a preliminary validation with Bacen Protege+ before proceeding with KYC analysis. After Bacen approval, the status will be automatically updated to pending_kyc_analysis.

Warning

The account_request_key field must be stored and will be used for account opening confirmation.

Response Body Params

FieldTypeDescriptionCharacters
account_info *objectObject containing Account Holder informationaccount_info Object
account_request_key *stringCreation request identification key-
account_request_status *stringKYC Status-

account_info Object

FieldTypeDescriptionCharacters
account_branch *stringBranch Number4
account_digit *stringAccount Digit11
account_number *stringAccount Number50
STATUS
4xx
Response Body: Error
{
"title": "titulo",
"description": "description in English",
"translation": "descrição em portugues",
"code": "codigo",
"extra_fields": {}
}
HTTP Code
status
QI Code
code
Title
title
Description (eng)
description
Description(ptbr)
translation
400QIT000001Bad RequestSchema ErrorErro de Schema
404QIT000404Not FoundResource could not be foundRecurso não encontrado