Sign in

v1

latestOpenAPI 3.1.02026-07-228956435.8 KB
Account verifications

Create an account verification

Verifies the ownership and details of a counterparty account by issuing a verification transfer from one of your accounts. The verification uses the live or test mode of the API key. Requires a JSON Web Signature (JWS).

post/account_verifications

Headers

Fintoc-JWS-Signaturestring 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.

Request body

account_numberstring required

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

Example request

{
  "account_number": "132969000000000190"
}

Response

The created account verification.

idstring required

Unique identifier of the account verification.

object'account_verification' required

Type of the object. Always account_verification.

mode'live' | 'test' required

Whether the verification is live or test data.

reason'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' nullable 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. 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.

receipt_urlstring nullable required

URL of the verification receipt, or null.

status'pending' | 'succeeded' | 'failed' required

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

transaction_datestring date-time nullable required

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

transfer_idstring nullable required

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

Example response

{
  "id": "accv_2daFu0zqqDtZGJaSi2TGI2Mm1nN",
  "counterparty": {
    "account_number": "132969000000000190",
    "account_type": "clabe",
    "holder_id": "000000000",
    "holder_name": "Test Customer 1",
    "institution": {
      "id": "40012",
      "name": "BBVA Mexico",
      "country": "mx"
    }
  },
  "mode": "test",
  "status": "pending",
  "transfer_id": "tr_2daFu0zqqDtZGJaSi2TGI2Mm1nN"
}