Skip to main content
POST
Create an account verification

Authorizations

Authorization
string
header
required

Headers

Fintoc-JWS-Signature
string
required

JSON Web Signature (JWS) of the request body. The signature authorizes the verification transfer. See the account verification guide for generating the JWS: https://docs.fintoc.com/docs/account-verification.

Body

application/json
account_number
string
required

Counterparty account identifier to verify. In Mexico, use an 18-digit standardized bank account number (CLABE), 16-digit debit card number, or 10-digit mobile phone number. In Chile, use the bank account number, digits only. Chilean account numbers cannot consist only of zeros.

Example:

"132969000000000190"

institution_id
string

Required if verifying an account in Chile, or a debit card or phone number in Mexico. Identifier of the counterparty bank. Only a CLABE encodes the bank. Ignored when account_number is a CLABE.

Example:

"40012"

account_type
enum<string>

Required if verifying an account in Chile. Type of the bank account. One of checking_account, sight_account, or savings_account. Only sight_account is supported for cl_fintoc. Ignored in Mexico.

Available options:
checking_account,
sight_account,
savings_account
Example:

"checking_account"

holder_id
string

Required if verifying an account in Chile. Chilean tax ID (RUT) of the expected account holder, with or without dots and hyphen. Cannot consist only of zeros. Ignored in Mexico.

Example:

"11.111.111-1"

Response

The created account verification.

id
string
required

Unique identifier of the account verification.

Example:

"accv_2daFu0zqqDtZGJaSi2TGI2Mm1nN"

object
any
required

Type of the object. Always account_verification.

counterparty
object
required

Details of the verified counterparty account.

mode
enum<string>
required

Whether the verification is live or test data.

Available options:
live,
test
Example:

"test"

reason
enum<string> | null
required

Reason code explaining why the verification failed, or null when the verification succeeded. transfer_fail means Fintoc could not send the verification transfer. cep_unavailable means the Mexican central bank (Banxico) had not yet published the payment receipt (CEP) when the verification timed out, so Fintoc could not confirm the account; you can retry the verification later. unknown means the reason could not be determined. In Mexico, the remaining codes mirror the transfer return_reason and report why the counterparty institution returned the verification transfer: non_existing_account, blocked_account, canceled_account, wrong_currency, account_not_from_receiving_institution, missing_information, wrong_payment_type, wrong_operation_type, account_type_does_not_correspond, invalid_character, exceeds_account_limit, exceeds_account_monthly_payments_limit, non_registered_mobile_phone, does_not_accept_non_banxico_payments, invalid_additional_information, missing_payment_instruction_due_to_balance_limit_reached, sender_client_protection_agreement, optional_payment_not_accepted_by_recipient_institution, codi_payment_without_quick_credit_notification, duplicated_tracking_key, and expired_sender_institution_certificate. In Chile, the codes mirror the transfer error_reason and report why the receiving bank rejected the verification transfer: recipient_account_disabled_for_tef, recipient_institution_timeout, recipient_institution_unavailable, invalid_recipient_account, recipient_account_closed, invalid_recipient_holder_id, invalid_holder_id_account_relationship, account_type_not_enabled, recipient_account_not_found, product_account_not_enabled, recipient_account_credit_restricted, recipient_institution_amount_limit_exceeded, system_amount_limit_exceeded, and unknown. In Chile, recipient_institution_timeout also covers transfers reversed because Fintoc could not determine whether the receiving bank approved the verification transfer. You can retry the verification. A reversal caused by a late bank approval or a failure to deliver the approval still results in a succeeded verification.

Available options:
transfer_fail,
cep_unavailable,
non_existing_account,
blocked_account,
canceled_account,
wrong_currency,
account_not_from_receiving_institution,
missing_information,
wrong_payment_type,
wrong_operation_type,
account_type_does_not_correspond,
invalid_character,
exceeds_account_limit,
exceeds_account_monthly_payments_limit,
non_registered_mobile_phone,
does_not_accept_non_banxico_payments,
invalid_additional_information,
missing_payment_instruction_due_to_balance_limit_reached,
sender_client_protection_agreement,
optional_payment_not_accepted_by_recipient_institution,
codi_payment_without_quick_credit_notification,
duplicated_tracking_key,
expired_sender_institution_certificate,
recipient_account_disabled_for_tef,
recipient_institution_timeout,
recipient_institution_unavailable,
invalid_recipient_account,
recipient_account_closed,
invalid_recipient_holder_id,
invalid_holder_id_account_relationship,
account_type_not_enabled,
recipient_account_not_found,
product_account_not_enabled,
recipient_account_credit_restricted,
recipient_institution_amount_limit_exceeded,
system_amount_limit_exceeded,
unknown,
null
Example:

null

receipt_url
string | null
required

URL of the verification receipt, or null. Always null in Chile.

Example:

null

status
enum<string>
required

Status of the verification. One of pending (in progress), succeeded (verification completed), or failed (could not be completed). In Chile, succeeded means the receiving bank accepted the transfer with the Chilean tax ID (RUT) you provided. Some banks accept transfers without validating the RUT.

Available options:
pending,
succeeded,
failed
Example:

"pending"

transaction_date
string<date-time> | null
required

Date and time when the verification was performed, as an ISO 8601 datetime in UTC, or null.

Example:

null

transfer_id
string | null
required

Identifier of the transfer issued to verify the account, or null.

Example:

"tr_2daFu0zqqDtZGJaSi2TGI2Mm1nN"