Accuracy starts with proper verification.
Overview
Bank Account Validation (BAV) is an API-based validation module that enables businesses to verify conventional bank, e-wallet, and digital bank accounts, ensuring the account number is valid and recognized by the respective financial network.
BAV is designed to be easy to integrate, simple to use, and adaptable across industries. It provides an additional verification layer to strengthen financial data accuracy and reduce operational risk.
1. Usage
Bank Account Validation is used to confirm whether a bank account number exists and retrieve the associated account holder name as provided by the bank network.
Because BAV is available via API, it can be embedded directly into onboarding flows, compliance checks, account registration systems, risk engines, or background validation processes. It does not require complex setup and can function independently as a validation utility.
BAV serves as an additional verification checkpoint to ensure that submitted banking information is accurate before being stored, processed, or used in financial workflows.
2. Use Cases
The core purpose of BAV across industries is to validate bank account information and provide an extra layer of account verification.
In multifinance and lending, BAV enhances borrower profiling by validating submitted bank account information during onboarding.
In NPL and risk operations, BAV helps maintain accurate banking records and reduces inefficiencies caused by invalid or outdated account information.
In digital platforms, payroll systems, and enterprise onboarding workflows, BAV strengthens financial data integrity at the point of entry.
In background checking and compliance processes, BAV supports financial data verification by confirming that an account exists within the bank network.
The bottom line across all industries is consistent: BAV exists to validate bank account data and provide an additional verification layer that improves data accuracy and operational trust.
3. Implementation
BAV can be implemented by integrating the Account Verification API into your system.
The integration requires:
• Bank code
• Bank account number
The API response returns:
• Validation status
• Account holder name (as provided by the bank network)
Because BAV is API-based, it can be deployed as a modular validation service without dependency on other payment modules. It is designed for quick integration and minimal operational overhead.
Usage and monitoring can be managed through the Usage History dashboard for tracking validation activity.
4. Bank Coverage
Bank Account Validation coverage depends on supported banks within the Brick network. Availability may vary depending on bank infrastructure and network support.
Before enabling BAV in production, businesses should review the supported bank list to ensure alignment with operational needs.
List of Bank Coverage
View the full list of supported Bank Account Validation: Disbursement Destination List
Notes: Bank coverage is reviewed and updated periodically to align with network and partner bank developments. Please note that adjustments may be implemented from time to time as part of ongoing service improvements.
5. Constraints & Important Notes
Virtual Account (VA) Considerations
Some Virtual Account (VA) channels are sensitive to expiry settings and the looping mechanism used by the issuing bank:
Close-loop VAs: These can only be recognized within the host bank’s own ecosystem (e.g., via internal transfers or channels, billing, etc).
Open-loop VAs: These are accessible from external banks and can receive funds via interbank transfers.
In many cases—especially with e-commerce platforms—VAs are issued as close-loop, which limits their interoperability and often results in lower success rates, especially when validation are made from outside the issuing bank.
⸻
Name Masking & Bank Network Response
The account holder name returned in the BAV response is provided directly by the bank network and is returned exactly as received.
Banks may partially mask names (for example, “JOHN D****”) in accordance with internal policies and regulatory requirements. Brick does not modify, normalize, or expand the returned name.
As formatting and masking standards may vary across banks, systems should avoid strict exact-string matching logic and instead implement reasonable comparison tolerance where appropriate.
⸻
Validation Scope Limitation
BAV confirms:
• The bank account number exists
• The associated account name is returned by the bank network
However, BAV does not guarantee:
• Legal ownership of the account
• Regulatory identity verification compliance
• Complete fraud prevention
BAV should therefore be positioned as an additional validation layer within a broader compliance and risk management framework.
Recommended Approach
For a more comprehensive verification framework, businesses may consider integrating Identity Verification (IDV) service.to reinforce identity and account ownership validation.
Combining BAV with IDV services provides a more comprehensive validation approach by verifying both banking information and identity data, helping strengthen fraud mitigation and regulatory compliance processes.