Create Wallet
To register bolePix, it is necessary that an active random Pix key exists in the account where the boletos will be registered.
Boleto wallets have a unique identification code (requester_profile_code) and specific default configurations for payment, discharge, protest, etc. of the boleto. The same account can have multiple boleto wallets, which allows the user to create multiple wallets with different default configurations. This dynamic facilitates the generation of boletos, with different configurations, in a more agile and automatic manner.
For all accounts, a boleto wallet is created with the client's default configurations. This default configuration pattern can be changed by contacting our support (suporte.baas@qitech.com.br). After account creation, it is also possible to change the account fees using the fee configuration endpoint.
The creation of boleto wallets is an asynchronous flow. After approval/rejection of wallet creation by CIP/Nuclea, the requester will be notified via webhook about the result of such request.
Request
Path parameters
| Field | Type | Description | Characters |
|---|---|---|---|
account_key | uuidv4 | Unique account identification key, in uuid v4 format | 36 |
Request Body
{
"request_control_key": "0868a24b-4a69-4138-ac4d-ecaeddf0005f",
"configuration_data": {
"max_payment_days": 1,
"protest_settings": {
"days_to_protest": 0
},
"bankruptcy_protest_settings": {
"days_to_bankruptcy_protest": 0
},
"write_off_settings": {
"days_to_write_off": 0
},
"fine_settings": {
"fine_type": "absolute",
"fine_amount": 10,
"days_to_fine": 0
},
"interest_settings": {
"interest_type": "workdays_daily_amount",
"interest_amount": 10,
"days_to_interest": 0
},
"qr_code_settings": {
"pix_key": "5df7a433-bd61-4f98-9515-df9aedc2980c",
"qr_code_on_discharge_enabled": false
},
"cnab_settings": {
"default_bank": "qi_scd",
"preferred_layout": "400"
}
}
}
Request Body Params
| Field | Type | Description | Characters |
|---|---|---|---|
request_control_key * | uuidv4 | Unique request identification key used by the client in uuid v4 format | 36 |
configuration_data * | object | Wallet default configurations | configuration_data Object |
configuration_data Object
| Field | Type | Description | Characters |
|---|---|---|---|
max_payment_days * | integer | Maximum calendar days the boleto will remain available for payment after due date (can be at most 365) | - |
write_off_settings | object | Default discharge configuration | write_off_settings Object |
protest_settings | object | Default protest configuration | protest_settings Object |
bankruptcy_protest_settings | object | Default bankruptcy protest configuration | bankruptcy_protest_settings Object |
fine_settings | object | Default fine configuration | fine_settings Object |
interest_settings | object | Default interest configuration | interest_settings Object |
qr_code_settings | object | Default PIX QR Code configuration (for bolePix) | qr_code_settings Object |
cnab_settings | object | Default CNAB files configuration | cnab_settings Object |
write_off_settings Object
| Field | Type | Description | Characters |
|---|---|---|---|
days_to_write_off * | integer | Days after due date for the boleto to be automatically discharged | - |
protest_settings Object
| Field | Type | Description | Characters |
|---|---|---|---|
days_to_protest * | integer | Days after due date for the boleto to be automatically protested | - |
bankruptcy_protest_settings Object
| Field | Type | Description | Characters |
|---|---|---|---|
days_to_bankruptcy_protest * | integer | Days after due date for a bankruptcy protest process to be automatically initiated | - |
fine_settings Object
Option 1: absolute amount fine (fine_type=absolute)
| Field | Type | Description | Characters |
|---|---|---|---|
fine_type * | string | Type of fine | fine_type Enumerators |
fine_amount * | float | Absolute amount of the fine | - |
days_to_fine * | integer | Days after due date for the fine to be charged | - |
fine_type=percentage)
| Field | Type | Description | Characters |
|---|---|---|---|
fine_type * | string | Type of fine | fine_type Enumerators |
fine_percentage * | integer | Percentage amount of the fine, from 1 to 100 | - |
days_to_fine * | integer | Days after due date for the fine to be charged | - |
fine_type Enumerators
| Enumerator | Description |
|---|---|
| absolute | absolute amount |
| percentage | percentage amount |
interest_settings Object
Option 1: interest using absolute amounts (interest_type=calendar_days_daily_amount or interest_type=workdays_daily_amount)
| Field | Type | Description | Characters |
|---|---|---|---|
interest_type * | string | Type of interest | interest_type Enumerators |
interest_amount * | float | Amount to be charged per determined time unit (business days or calendar days) | - |
days_to_interest * | integer | Days after due date to start charging interest | - |
interest_type=calendar_days_monthly_percentage)
| Field | Type | Description | Characters |
|---|---|---|---|
interest_type * | string | Type of interest | interest_type Enumerators |
interest_percentage * | integer | Percentage to be charged per determined time unit (business days or calendar days) | - |
days_to_interest * | integer | Days after due date to start charging interest | - |
interest_type Enumerators
| Enumerator | Description |
|---|---|
| calendar_days_daily_amount | Daily amount over calendar days |
| workdays_daily_amount | Daily amount over business days |
| calendar_days_monthly_percentage | Interest percentage charged monthly, based on calendar days |
qr_code_settings Object
| Field | Type | Description | Characters |
|---|---|---|---|
pix_key * | uuidv4 | Random type Pix key | 36 |
qr_code_on_discharge_enabled * | boolean | Determines if QR Code information will appear in the return file (CNAB) | - |
The PIX copy and paste will be returned in the CNAB file at position 029 to 105.
If the qr_code_settings object is sent in the request, this wallet will have bolePix generation as its default configuration. BolePix are boletos whose payment is linked to a PIX QR Code. Therefore, the payer can make payment of the boletos either using their readable lines, or by reading the linked PIX QR Codes. If payment is made via QR Code, financial settlement happens instantly. Regarding notifications, two webhooks are sent: one upon PIX transfer (payment notice, boleto goes to payment_notice status); and another a few seconds or minutes later, after confirmation of discharge at CIP/Nuclea (paid, boleto goes to paid status).
cnab_settings Object
| Field | Type | Description | Characters |
|---|---|---|---|
default_bank | string | Default bank layout for CNAB file processing | default_bank Enumerators |
preferred_layout | string | Preferred layout for CNAB files | preferred_layout Enumerators |
default_bank Enumerators
| Enumerator | Description |
|---|---|
| santander | Santander Bank |
| itau | Itaú Bank |
| bradesco | Bradesco Bank |
| qi_scd | QI SCD |
preferred_layout Enumerators
| Enumerator | Description |
|---|---|
| 400 | CNAB 400 Layout |
| 240 | CNAB 240 Layout |
Response
Response Body
{
"requester_profile_key": "fd86d9b1-2a5e-4e03-9a59-a043c7632c97",
"requester_profile_code": "329-04-2338-2625918",
"request_control_key": "0868a24b-4a69-4138-ac4d-ecaeddf0005f",
"account_key": "0494902f-b21c-4ae6-b37e-854cfe883402",
"requester_profile_status": "pending",
"configuration_data": {
"max_payment_days": 1,
"protest_settings": {
"days_to_protest": 0
},
"bankruptcy_protest_settings": {
"days_to_bankruptcy_protest": 0
},
"write_off_settings": {
"days_to_write_off": 0
},
"fine_settings": {
"fine_type": "absolute",
"fine_amount": 10,
"days_to_fine": 0
},
"interest_settings": {
"interest_type": "workdays_daily_amount",
"interest_amount": 10,
"days_to_interest": 0
},
"qr_code_settings": {
"pix_key": "5df7a433-bd61-4f98-9515-df9aedc2980c",
"qr_code_on_discharge_enabled": false
},
"cnab_settings": {
"default_bank": "qi_scd",
"preferred_layout": "400"
}
}
}
Response Body Params
| Field | Type | Description | Characters |
|---|---|---|---|
requester_profile_key * | uuidv4 | Unique wallet identification key in uuid v4 format | 36 |
requester_profile_code * | string | Unique wallet identification code | 19 |
request_control_key * | uuidv4 | Unique request identification key used by the client in uuid v4 format | 36 |
account_key * | uuidv4 | Unique account identification key in uuid v4 format | 36 |
requester_profile_status * | string | Wallet status | requester_profile_status Enumerators |
configuration_data * | object | Wallet default configurations | configuration_data Object |
profile_status Enumerators
| Enumerator | Description |
|---|---|
| pending | Wallet accepted and pending confirmation |
Error Response
Response Body: Error
{
"title": "titulo",
"description": "description in English",
"translation": "descrição em portugues",
"code": "codigo",
"extra_fields": {}
}
HTTP Codestatus | QI Codecode | Titletitle | Description (eng)description | Description (pt-br)translation |
|---|---|---|---|---|
| 400 | QIT000001 | Bad Request | Schema Error | Schema Inválido |
| 404 | BKS000001 | Not Found | Person not found with key: person_key` | Pessoa não encontrada com a chave: person_key` |
| 404 | BKS000004 | Not Found | Pix key not found: {pix_key} | Chave pix não encontrada: {pix_key} |
| 403 | BKS000005 | Forbidden | User is not allowed to do this action | Usuário não tem autorização para fazer essa ação |
| 404 | BKS000006 | Not Found | The source account key was not found. | A chave da conta de origem não foi encontrada. |
| 400 | BKS000007 | Bad Request | It was not possible to consult the source account at this time. Please try again in a few minutes. | Não foi possível consultar a conta de origem neste momento. Por favor, tente novamente em alguns minutos. |
| 400 | BKS000008 | Bad Request | The source account is closed. | A conta de origem está fechada. |
| 400 | BKS000009 | Bad Request | The source account is blocked. | A conta de origem está bloqueada. |
| 403 | BKS000010 | Forbidden | The pix key owner does not match the account owner. | O proprietário da chave pix não corresponde ao proprietário da conta. |
| 409 | BKS000014 | Conflict | Request control key already sent or duplicated sent: {request_control_key} | Chave de controle da requisição já utilizada ou enviada duplicada: {request_control_key} |
| 400 | BKS000047 | Bad Request | It was not possible to consult the sent pix key at this time. Please try again in a few minutes. | Não foi possível consultar a chave pix enviada no momento. Por favor, tente novamente em alguns minutos. |