Skip to main content

Request TED Transaction Scheduling with Two-Factor Authentication

Request

ENDPOINT
/account/ACCOUNT_KEY/ted_schedule
METHOD
POST

Authentication via Email and SMS

Request Body: Scheduling with TFA via SMS or Email
{
"request_control_key": "0c3d2a3e-c121-464e-b5a4-8e69e0c17bbd",
"target_account": {
"account_branch": "0001",
"account_number": "92796",
"account_digit": "1",
"owner_document_number": "23599885000192",
"owner_name": "Titular da Conta",
"ispb": "12345678",
"account_type": "checking_account"
},
"transaction_amount": 8.86,
"schedule_date": "2024-12-01",
"tfa_info": {
"approver_document_number": "98765432100",
"contact_type": "email"
}
}

Authentication via Device

In addition to the existing authentication methods via sms and email, it is possible to authenticate the transaction using a previously registered device. In this case, the session_id must be obtained in the Device Scan and sent in tfa_info.

Request Body: Scheduling with TFA via Device
{
"request_control_key": "0c3d2a3e-c121-464e-b5a4-8e69e0c17bbd",
"target_account": {
"account_branch": "0001",
"account_number": "92796",
"account_digit": "1",
"owner_document_number": "23599885000192",
"owner_name": "Titular da Conta",
"ispb": "12345678",
"account_type": "checking_account"
},
"transaction_amount": 8.86,
"schedule_date": "2024-12-01",
"tfa_info": {
"approver_document_number": "98765432100",
"session_id": "b2f18d3a-67c2-4a7f-98e5-1d3f5c6b8a72",
"contact_type": "device"
}
}

Body Params

FieldTypeDescriptionCharacters
request_control_key *stringUnique request identification key used by the client in uuid v4 format.36
target_account *objectTarget accounttarget_account Object
transaction_amount *floatTransfer amount10
schedule_date*stringDate when the transaction will be executed.10
tfa_info*ObjectObject containing the account approver's document and contact method.tfa_info Object

tfa_info Object

FieldTypeDescriptionCharacters
approver_document_number *stringAccount approver's document number.11
session_idstringUnique device session identification key in UUID v4 format (required for device TFA).36
contact_type *stringContact method for the account approver, can be sms, email or device

target_account Object

FieldTypeDescriptionCharacters
account_branch *stringBranch.4
account_digit *stringAccount digit1
account_number *stringAccount number.20
owner_document_number *stringCPF or CNPJ (numbers only) of the account holder.14
owner_name *stringAccount holder's name.50
account_type*stringAccount type.account_type Enumerator
ispb *stringBased on the financial institution's CNPJ (8 digits).8

account_type Enumerator

EnumeratorTranslation
checking_accountchecking account
deposit_accountdeposit account
guaranteed_accountguaranteed account
investment_accountinvestment account
payment_accountpayment account
saving_accountsavings account

Response

STATUS
202
Response Body: Schedule Created
{
"request_control_key": "b6804f32-101e-4702-8fbc-c2dbc4c2caec",
"schedule_key": "f64b3fa7-d09d-4927-ad4f-b966df9fb153",
"schedule_status": "pending_2fa_approval",
"schedule_date": "2024-12-31"
}
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 error descriptionSchema Inválido
404TED000006Target account Not FoundTarget account was not found for given parametersConta destino não encontrada para os parâmetros informados
404TED000009Not FoundAccount not found for the given key: {account_key}Conta não encontrada para a chave fornecida: {account_key}
403TED000014Invalid target accountInvalid target accountConta destino inválida
400TED000015Bad RequestAccount blocked or closed can not perform this actionA conta bloqueada ou fechada não pode executar esta ação
400TED000016Bad RequestHub account can not perform this actionA conta hub não pode executar esta ação
403TED000018UnauthorizedProvided account not owned by SELECTED_AGENTConta fornecida não pertencente ao SELECTED_AGENT
400TED000031Bad RequestISPB number {ispb} does not exist or is inactiveISPB {ispb} não existe ou está inativo
400TED000044Invalid Timestamp Format sentGiven parameter is not in the correct format {timestamp_format}Parametro enviado não está no formato correto {timestamp_format}
400TED000046Invalid uuid v4 string sent{key} was not accepted for not being a valid uuid v4 string{key} não foi aceito por não ser uma palavra uuid v4 válida
400TED000054Invalid Transaction AmountTransaction Amount {transaction_amount} is invalidValor de transação {transaction_amount} é inválido
400TED000057Invalid Document NumberGiven {document_number} document number is invalidCPF/CNPJ {document_number} fornecido não é valido
409TED000064Bad Requestrequest_control_key {request_control_key} already in userequest_control_key {request_control_key} já utilizada
400TED000065Bad RequestIt has been identified by request_control_key that this request is already being processedFoi identificado por request_control_key que está requisição está sendo processada
403TED000079No approver permissionGiven document number does not belong to an approver for this accountNúmero de documento enviado não pertence a um aprovador da conta
400TED000080tfa_info is requiredClient must send object tfa_infoCliente deve enviar objeto tfa_info
400TED000081Error occurred while sending tokenAn unexpected error occurred while sending tokenUm erro inexperado ocorreu ao tentar enviar token
400TED000089Invalid Schedule DateSchedule date must be after current date for UTC-3Data de agendamento deve ser após a data atual em UTC-3
400TED000090Invalid Schedule DateSchedule date must be a workdayData de agendamento deve ser um dia útil
400TED000091Target Account and Source Account must be differentTarget Account must not be the same as Source AccountA conta de destino não pode ser a mesma da conta de origem