Product Overview
Verify who owns a Mexican bank account before you move funds. Mexican Account Validation looks up a CLABE, phone number, or debit card on SPEI and returns the name and identification found for that account.
Key Features & Benefits
- Recipient Verification: When the validation reaches
COMPLETED, you receive the account holder’s name. When the proof of payment (CEP) reports the identification as not available, that response still includes the name. The identification fields onverified_ownerare defined in the API Reference. A later validation returns the same identification the CEP reported. - Three account identifiers: Validate by CLABE, phone number, or debit card.
- Asynchronous results: Create returns immediately with
PROCESSING. The terminal state arrives by webhook or GET.PROCESSINGregularly takes a few minutes, and in a few cases it can take hours.
Supported Account Identifiers
| Identifier | account.type | What you send |
|---|---|---|
| CLABE | CLABE | The 18-digit standardized Mexican account number. |
| Phone | PHONE | A 10-digit Mexican number or E.164 number, plus the 5-digit bank code. |
| Debit card | DEBIT_CARD | The 16-digit card number (no separators), plus the 5-digit bank code. |
What to expect
Nvio Pagos México, the Bitso entity that operates SPEI in Mexico, sends a penny validation to the receiving bank. That bank publishes the CDA (comprobante digital de abono) to Banxico, the Central Bank of Mexico. Banxico publishes the CEP, and Nvio queries it there. That regularly takes a few minutes. In a few cases it can take hours, depending on the receiving bank. Busy days or other external factors at the receiving bank, such as maintenance or payroll, make a long wait more likely. If you need to respond quickly, handle that wait in your own flow. Keep your own timeout or pending state, and apply the webhook when it arrives.
Compare verified_owner with the person you intend to pay. expected_owner.name is required, and Bitso returns it as you sent it. The verified name may be abbreviated, and the name parts may appear in any order.
A FAILED validation carries one of these error.code values. The message for each code, and whether to create another validation, is in Account Validation Flow.
error.code | When Bitso returns it |
|---|---|
account_unreachable | The receiving bank did not accept the penny payment, or it refunded it. |
cep_unavailable | The proof of payment (CEP) was not published after a long wait. |
cep_empty | The CEP was retrieved and reported both the name and the identification as ND (No disponible). |
cep_mismatch | The CEP was retrieved, but the receiving bank reported in it a different account than the one the penny validation was sent to. |
spei_withdrawals_disabled | The penny validation could not be sent because SPEI withdrawals are temporarily disabled. |
account_validation_internal_error | A technical error prevented the validation from completing. Contact Bitso. |
Get Started
Ready to validate Mexican accounts?
- Enable the product: Contact your account manager or Business Customer Support at
[email protected]. - Set up credentials: Create or reuse Bitso API credentials and sign requests as described in Authentication.
- Register your webhook URL: Subscribe to
account_validationwith Create webhook subscriptions so you receive terminal-status updates. - Call the API: Create a validation with
type: MX_SPEI, then retrieve it by id or wait for the webhook.
For more details, check out our full documentation:
Updated 13 days ago