Account Verification

Cobre’s Account Verification API provides a standardized mechanism to validate bank account ownership and account holder information directly against financial institution records. This cross-feature service helps reduce payment rejections, operational errors, and fraud risks by ensuring recipient data is accurate before executing transactions.

Account Verification is typically used before creating counterparties or initiating money movements, acting as a preventive control layer within the Cobre platform.

Creating Account Verifications

Account verifications are created through the Create Account Verification API (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.

Each verification is performed using a verification model, which defines the required input fields and the validation logic applied.

Verification Models Catalog

The following catalog lists all supported verification models and their characteristics.

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.

Model	Geo	Account Type	Description
`mex_acc_ownership_1`	MEX	CLABE	Confirms ownership of a CLABE account by validating the account number and the account holder’s identification

Required Fields

Field	Description
`account_number`	CLABE account number (18 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

Only accounts from the MEX geography are supported, and they must be CLABE accounts.

Verification Results

Once the verification process is completed, the 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

The unresolved result may occur due to invalid formats, incorrect identifiers, or repeated verification attempts within a short period.

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	Depend on the receiving bank
Retries	Repeated validations in short intervals may result in failures; wait at least 12 hours before retrying

Verification responses are provided only within the established schedules.

Verification Status Object

In addition to the verification result, every account verification includes a status object that describes the operational state of the verification process.

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:

id (e.g., av_xxxxx)

model

geo

verification_request

verification_response

status

📘 Learn more: 🔗 Create an Account Verification

Account Verification Object

An Account Verification represents a single verification attempt performed by the client.

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.

To enable this functionality, please contact your KAM

Account Verification

Creating Account Verifications#

Verification Models Catalog#

Required Fields#

Verification Results#

Account Verification Considerations#

Verification Status Object#

Actions performed on Account Verifications#

Account Verification Object#

Key Attributes#

How to Get Started#

What to expect after using this API#

Creating Account Verifications

Verification Models Catalog

Required Fields

Verification Results

Account Verification Considerations

Verification Status Object

Actions performed on Account Verifications

Account Verification Object

Key Attributes

How to Get Started

What to expect after using this API