Skip to main content
Account verification confirms a Mexican destination account identified by a standardized Mexican bank account number (CLABE), a 16-digit debit card number, or a 10-digit mobile phone number. Fintoc sends a 0.01 MXN micro-deposit from your account balance to the destination. When the verification completes, Fintoc returns the account holder’s information.

Create an account verification

An account verification creates a 0.01 MXN Transfer from your root Account to retrieve the target account holder’s information. Because this call moves money from your account, you must sign the request with a JSON Web Signature (JWS). See setting up JWS keys.
When you request an account verification, the API returns an account_verification object with a pending status. The holder_id and holder_name fields are null in this initial response. Fintoc populates these fields once the verification succeeds. The response looks like this:

Verify a debit card or mobile phone number

A CLABE encodes its bank, but a debit card or mobile phone number does not. To verify one, add the bank’s five-digit institution_id from the Banco de México institution list. If you omit institution_id, the API returns a 400 Bad Request error.
The API returns the same account_verification object, with account_type set to debit_card or mobile. The response looks like this:
For card numbers, account verification supports debit cards only, not credit cards.

Monitor verification status

When Fintoc retrieves the transfer and account holder information, it sends an account_verification.succeeded webhook. This event includes the account holder’s information in an account_verification object with a succeeded status. The event looks like this:
If Fintoc cannot retrieve the information, you receive an account_verification.failed webhook with a reason field explaining why the verification failed. For more on receiving webhooks with Fintoc, see the webhooks guide.