Saltar al contenido principal
POST
Create an account verification
v2 · Base URL https://api.fintoc.com/v2

Autorizaciones

Authorization
string
header
requerido

Encabezados

Fintoc-JWS-Signature
string
requerido

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.

Cuerpo

application/json
account_number
string
requerido

Account number of the counterparty to verify. The 18-digit standardized Mexican bank account number (CLABE).

Ejemplo:

"132969000000000190"

Respuesta

The created account verification.

id
string
requerido

Unique identifier of the account verification.

Ejemplo:

"accv_2daFu0zqqDtZGJaSi2TGI2Mm1nN"

object
any
requerido

Type of the object. Always account_verification.

counterparty
object
requerido

Details of the verified counterparty account.

mode
enum<string>
requerido

Whether the verification is live or test data.

Opciones disponibles:
live,
test
Ejemplo:

"test"

reason
enum<string> | null
requerido

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. 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.

Opciones disponibles:
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,
unknown,
null
Ejemplo:

null

receipt_url
string | null
requerido

URL of the verification receipt, or null.

Ejemplo:

null

status
enum<string>
requerido

Status of the verification. One of pending (in progress), succeeded (ownership confirmed), or failed (could not be completed).

Opciones disponibles:
pending,
succeeded,
failed
Ejemplo:

"pending"

transaction_date
string<date-time> | null
requerido

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

Ejemplo:

null

transfer_id
string | null
requerido

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

Ejemplo:

"tr_2daFu0zqqDtZGJaSi2TGI2Mm1nN"