Account Verification
Creating Account Verifications
POST /v1/account_verifications).This endpoint allows clients to submit account and account holder details, which are then compared against the records held by the corresponding financial institution.
Verification Models Catalog
Mexico
Colombia
Mexico – Account Ownership Verification
Mexico – Account Details Verification
This model verifies whether the provided account and account holder information match the official records of the financial institution.
Only accounts from the MEX geography are supported, and they must be CLABE accounts or SPEI cards numbers. Once the verification process is completed, the
The When requesting an Account Verification for an invalid CLABE or SPEI Card (invalid length or no numeric format), or to one that doesn't exist, our endpoint will provide a response with the corresponding errors in real-time.
Verification responses are provided only within the established schedules.
| Model | Geo | Account Type | Description |
|---|---|---|---|
mex_acc_ownership_1 | MEX | CLABE or SPEI Card | Confirms ownership of a CLABE account or SPEI Card by validating the account number and the account holder’s identification |
Required Fields
| Field | Description |
|---|---|
account_number | CLABE account number (18 digits) or SPEI card (15-16 digits) |
account_type | Must be clabe |
account_holder_id_type | Identification type (rfc or curp) |
account_holder_id_number | Identification number of the account holder |
Verification Results
verification_response field will return one of the following values:| Verification Result | Description |
|---|---|
matched | The account holder information matches the financial institution records |
unmatched | The account holder information does not match the records |
unresolved | The verification could not conclusively validate one or more fields |
unresolved result may occur due to invalid formats, incorrect identifiers, or repeated verification attempts within a short period.When verification Results can be expected in real-time
Account Verification Considerations
| Condition | Description |
|---|---|
| Response schedule | 7:00 a.m. – 6:30 p.m. on business days, 7:00 a.m. – 4:00 p.m. on non-business days |
| Response times | P50 within 10 minutes and P90 within 24 minutes Note: These times depends on the receiving bank and can vary each month. They are provided as reference. |
| Retries | Repeated validations in short intervals may result in failures; wait at least 12 hours before retrying |
Verification Status Object
| State | Code | Description |
|---|---|---|
processing | NA | Verification is being processed |
completed | NA | Verification process completed |
failed | F006 | The account could not be validated |
Actions performed on Account Verifications
🔑 Create
🔍 Retrieval
Description: Create a new account verification request using a supported model.What to expect after the action:
An Account Verification object including: 📘 Learn more: 🔗 Create an Account Verification
An Account Verification object including:
id (e.g., av_xxxxx)modelgeoverification_requestverification_responsestatusAccount Verification Object
Key Attributes
| Field | Description |
|---|---|
id | Unique identifier of the verification |
creator_id | Identifier of the client who performed the verification |
model | Verification model used |
geo | Geography of the verified account |
verification_request | Submitted account and holder data |
verification_response | Result of the verification |
status | Operational state of the verification |
external_id | Client-provided external reference |
created_at | Creation timestamp |
updated_at | Last update timestamp |
How to Get Started
Identify the verification use case
Determine whether account verification is required before creating a counterparty or initiating a money movement.
Select the appropriate verification model
Use the supported verification model that matches the account geography and type.
Prepare verification data
Ensure that account numbers and identification fields are correctly formatted.
Create the account verification
Submit the verification request using the Account Verification API.
Handle the verification result
Use the verification response to decide whether to proceed with downstream operations.
What to expect after using this API
Reduced payment rejections
Validate recipient information before initiating money movements.
Improved data accuracy
Ensure counterparty and account data matches financial institution records.
Operational risk mitigation
Detect mismatches or unresolved verifications early in the workflow.
Cross-feature consistency
Reuse verification results across Counterparties and Money Movements flows.
Modified at 2026-05-29 23:52:37