Verify destination bank account data through Brick's supported bank network before saving beneficiary details or initiating payouts.
Verify whether a destination bank account can be validated through Brick's supported bank network. When available, the validation response returns the account holder name provided by the bank network.
Use BAV before saving beneficiary details or initiating payouts to reduce failed transfers caused by an unsupported bank code, invalid account number, or mismatched recipient data.
What BAV Validates
BAV can help confirm:
- The bank short code is supported by Brick.
- The account number can be checked through the relevant bank network.
- The account holder name is returned by the bank network, when available.
BAV does not confirm legal ownership of the account, complete regulatory identity verification, or fraud risk by itself. Treat BAV as one validation layer within your broader onboarding, compliance, and risk process.
Implementation
Integrate BAV through the Account Verification API.
Required inputs:
bankShortCodebankAccountNo
Typical response data:
- Validation status
- Account holder name, when returned by the bank network
Usage and monitoring are available from the Usage History page in the Brick Dashboard.
Bank Coverage
Bank coverage depends on Brick's supported destination network and may vary by bank infrastructure or partner availability.
Review the List of Bank Coverage before enabling BAV in production.
Coverage is reviewed periodically and may be adjusted as Brick's bank network changes.
Important Notes
Name Masking
The account holder name is returned as provided by the bank network. Some banks may partially mask names or apply different formatting rules. Your system should avoid strict exact-string matching and use reasonable comparison tolerance where appropriate.
Validation Scope
BAV validates account data through the available bank network. If your workflow also requires identity ownership assurance or regulatory identity verification, combine BAV with your own KYC/KYB, compliance, or IDV process. Contact your Brick representative if you need guidance on the right verification setup.
Virtual Account Considerations
Virtual Account behavior may vary by issuing bank and VA type. Closed-loop VAs may only be recognized within the host bank's ecosystem, while open-loop VAs may be reachable from external banks. Validate your intended use case before relying on VA validation in production.