Account Verification

Validate bank account and key ownership to reduce payment rejections and fraud

Account Verification is a Cobre capability that allows businesses to confirm whether an account identifier (such as a CLABE in Mexico or a Bre-B key in Colombia) and the declared account holder information match official records. It is designed to reduce payment failures, operational errors, and fraud by ensuring recipient data is accurate before a company creates counterparties or executes money movements. This feature supports both ownership verification (confirming a match) and details retrieval (returning holder information), depending on the model used.

1. What Cobre Enables with Account Verification

With Account Verification, businesses can:

Confirm whether recipient/account holder information matches official records

Validate ownership of bank account identifiers (e.g., CLABE in Mexico)

Validate ownership of key-based identifiers (e.g., Bre-B keys in Colombia)

Retrieve account holder details where supported (name and ID)

Reduce payment rejections caused by incorrect or mismatched information

Prevent operational errors such as paying to the wrong recipient

Strengthen fraud controls by confirming account/key ownership

2. Where It Fits in the Cobre Model

Account Verification is designed to operate as a pre-execution validation step in common payment flows:

Before creating a counterparty (beneficiary or payer representation)

Before initiating a money movement (payout or collection)

As a preventive check during onboarding (e.g., sellers, workers, suppliers)

It does not move funds — it verifies that the data used to move funds is trustworthy.

3. Key Capabilities / Options

Cobre supports multiple verification models depending on geography and identifier type. Each model defines what input is required and what output is returned.

Mexico

Colombia

4. Core Concepts and Terminology

Account Verification: A validation request that checks recipient identifiers and/or holder information against official sources.

Verification Model: A predefined ruleset that determines required inputs and verification logic for a specific geo and identifier type.

Account Ownership Verification: A model that answers “Does this identifier belong to this person/company?”

Account/Key Details Verification: A model that returns holder details when a valid identifier is provided.

Verification Result (matched, unmatched, unresolved): The outcome of an ownership verification model.

Verification Status (processing, completed, failed): The operational state of the verification process.

DICE (Colombia): Centralized directory used to validate Bre-B key ownership and key owner details in Colombia’s immediate payment system.

CLABE (Mexico): Standard 18-digit Mexican bank account identifier used for SPEI transfers.

Bre-B Key (Colombia): Key-based identifier used in Colombia’s immediate payment ecosystem.

5. Speed, Settlement & Reliability (if applicable)

Account Verification is a data validation capability, not a settlement mechanism—no funds move as a result of verification.

That said, reliability and timeliness depend on external sources:

Mexico models return responses only within defined schedules and response times depend on the receiving bank.

Retries should be managed carefully: repeated validations in short intervals can fail and it is recommended to wait at least 12 hours before retrying.

Colombia key verification relies on directory records and can return unresolved outcomes due to formatting issues, incorrect identifiers, or repeated attempts.

Account Verification outcomes are designed to be used as decision signals, improving predictability and success rates for downstream money movement execution.

6. Typical Business Use Cases

Common use cases include:

Beneficiary onboarding for payouts (marketplaces, payroll, vendors)

Validating recipient details before running payouts

Fraud prevention (preventing payouts to mismatched owner identifiers)

Reducing payment rejection rates in high-volume payout operations

Enriching recipient information (where details retrieval is supported)

Verifying Bre-B key ownership for Colombia payouts and collections flows

Account Verification is especially valuable in businesses where recipient data quality directly impacts operational cost, such as lenders, marketplaces, gig platforms, payroll processors, and treasury teams operating at scale.

7. Transactions, Reporting & Reconciliation

Account Verification itself does not create transactions because it does not move money. However, it improves downstream operational outcomes by:

Increasing the success rate of money movements by validating recipient data early

Reducing the number of failed payments that require manual remediation

Producing structured verification records that can be stored alongside:

counterparty profiles

payout decisions

reconciliation references

For finance and operations teams, the benefit is indirect but important: fewer failures, fewer reversals, and cleaner reconciliation due to accurate recipient data.

8. Governance, Controls & Auditability

Account Verification supports governance by providing:

A consistent record of each verification attempt (including who created it and when)

Clear operational states (processing, completed, failed)

Clear decision outcomes (matched, unmatched, unresolved) or verified holder details

This enables businesses to implement controls such as:

Only paying verified recipients

Flagging mismatches for manual review

Auditing verification evidence when investigating failures or fraud attempts

9. Summary — What Cobre Delivers with Account Verification

Cobre enables businesses to:

Verify ownership of Mexico CLABE accounts
Verify ownership of Colombia Bre-B keys using official directory records
Retrieve recipient details where supported (holder name and ID)
Reduce payment rejections and operational errors
Strengthen fraud controls and onboarding integrity
Use structured verification outcomes to support scalable workflows

Account Verification helps companies operate more confidently by validating recipient data before execution—improving reliability, reducing rework, and supporting stronger financial controls across payment operations.

Account Verification

Validate bank account and key ownership to reduce payment rejections and fraud#

1. What Cobre Enables with Account Verification#

2. Where It Fits in the Cobre Model#

3. Key Capabilities / Options#

4. Core Concepts and Terminology#

5. Speed, Settlement & Reliability (if applicable)#

6. Typical Business Use Cases#

7. Transactions, Reporting & Reconciliation#

8. Governance, Controls & Auditability#

9. Summary — What Cobre Delivers with Account Verification#