How to Verify a Bank Account: 5 Methods for Businesses (2026)

Every business that sends money — payroll, vendor payments, marketplace payouts, refunds, or customer disbursements — faces the same problem: how do you know the bank account details you have been given are correct before you send the payment?

An incorrect bank account number means a failed transfer (best case), a payment to the wrong person (worst case), or a fraud loss (really worst case). The cost of a failed payment is not just the transaction fee — it is the operational overhead of investigating the failure, contacting the recipient, collecting correct details, and resending the payment, plus the reputational hit of a delayed payment.

This guide covers five methods for verifying bank account details, from instant API validation to manual verification, with the trade-offs of each.

Why Bank Account Verification Matters

Failed Payments Are Expensive

Industry data shows that 3-5% of first-time payments fail due to incorrect account details. For a company processing 10,000 payments per month, that is 300-500 failed transactions — each requiring manual investigation, customer outreach, and reprocessing.

The direct cost per failed payment (including operational overhead) ranges from $25 to $50. At scale, failed payments due to unverified account details can cost businesses hundreds of thousands of dollars annually.

Fraud Prevention

Verifying that a bank account exists, is active, and belongs to the expected account holder is a critical layer of fraud prevention:

• Invoice fraud: Scammers impersonate suppliers and send invoices with their own bank details. Account verification catches cases where the account does not match the expected payee.
• Payee takeover: Fraudsters change the bank details on a legitimate payee's profile to redirect payments. Verification flags the change.
• Synthetic identity fraud: Fake identities paired with real or newly created bank accounts. Account verification adds a data point for detection.
• Refund fraud: Refunds requested to accounts that do not belong to the original payer.

Regulatory Requirements

Many regulations require some form of bank account verification as part of customer due diligence:

• KYC/AML regulations: Verifying bank account details is part of the customer identification and verification process
• Payment Services Directive (PSD2): Requires payment service providers to verify payee information for certain transactions
• Confirmation of Payee (UK): A mandatory name-checking service for all UK bank transfers since 2020
• SEPA regulations: Banks must validate IBANs before processing SEPA payments

Method 1: IBAN Validation (Instant, API-Based)

Best for: Businesses operating in IBAN countries (80+ countries in Europe, Middle East, Africa)

IBAN validation is the fastest and most cost-effective way to verify bank account details in countries that use the IBAN system. A valid IBAN confirms:

1. The account number format is correct — length, structure, and character positions match the country specification
2. The check digits are valid — the MOD-97 algorithm confirms no transcription errors
3. The bank code exists — the bank identified by the IBAN is a real, registered financial institution
4. Bank details — the bank name, BIC/SWIFT code, branch, and SEPA participation status

How It Works

Send the IBAN to a validation API. The API performs structural validation, MOD-97 check digit verification, and bank code lookup against national bank registries.

curl https://api.edge-api.com/v1/iban/validate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d "iban=DE89370400440532013000"

Edge's IBAN Validation API returns:

• Validation result (valid/invalid with specific error codes)
• Country and BBAN breakdown
• Bank name, BIC/SWIFT code, and branch details
• SEPA membership status
• Bank address (where available)

Pros

• Instant — validation happens in milliseconds
• No customer friction — the customer only needs to provide their IBAN
• Catches most errors — typos, wrong length, non-existent bank codes
• Enriches data — returns bank name, BIC, and branch details you can display for confirmation
• Low cost — typically pennies per validation

Cons

• Does not confirm account ownership — a valid IBAN means the format is correct and the bank exists, but it does not prove the account belongs to the person who provided it
• Does not confirm account status — the account could be closed, frozen, or restricted
• Only works in IBAN countries — not applicable for US, Canada, Australia, etc.

When to Use

Use IBAN validation as your first line of defense for any payment to an IBAN country. It catches the vast majority of data entry errors instantly and at minimal cost. Layer additional verification methods on top for higher-risk payments.

Method 2: Micro-Deposits

Best for: High-assurance account ownership verification, particularly in non-IBAN countries

Micro-deposits verify that the account exists AND that the person claiming ownership can see transactions on the account.

How It Works

1. Send two small deposits (typically $0.01–$0.99) to the account with unique reference codes
2. Ask the account holder to check their bank statement and report the exact amounts or reference codes
3. If they can tell you the correct amounts/references, you have confirmed they have access to the account

Pros

• Confirms account ownership — the person must have access to the account's transaction history
• Works in any country — no dependency on IBAN or any specific banking standard
• Regulatory acceptance — widely accepted as a verification method by regulators

Cons

• Slow — takes 1-3 business days for deposits to arrive and be verified
• Customer friction — requires the customer to check their bank statement and come back to your platform
• Drop-off — many customers never complete the verification step
• Cost — each verification attempt costs the deposit amounts plus transaction fees
• Not real-time — cannot be used for instant onboarding or real-time payment flows

When to Use

Use micro-deposits when you need to prove account ownership and speed is not critical — typically during onboarding for recurring payment setups (direct debits, payroll).

Method 3: Instant Account Verification (Open Banking)

Best for: Real-time account ownership verification with minimal friction, in countries with open banking infrastructure

Open banking allows customers to securely share their bank account data with third parties through bank APIs, typically using OAuth-based consent flows.

How It Works

1. The customer selects their bank from a list
2. They are redirected to their bank's secure login page
3. They authenticate and consent to share account information
4. The bank's API returns verified account details (account number, name, balance, transaction history) directly to your platform

Pros

• Instant — verification happens in real-time
• High assurance — data comes directly from the bank, not from user input
• Confirms ownership — the customer authenticates with their bank, proving they control the account
• Rich data — can include account balance, transaction history, and account holder name
• Low friction — familiar OAuth flow (similar to "Sign in with Google")

Cons

• Geographic limitation — requires open banking infrastructure (EU/PSD2, UK Open Banking, some other markets)
• Not all banks participate — coverage varies by country and provider
• Consent dependency — the customer must actively consent; some are reluctant to connect their bank
• Integration complexity — requires integration with open banking aggregators or direct bank APIs
• Regulatory overhead — you may need specific licenses (AISP under PSD2) to access account information

When to Use

Use instant account verification when you need real-time account ownership confirmation in markets with open banking support. Ideal for lending (income verification), subscription payments (direct debit setup), and high-value onboarding.

Method 4: Database Verification

Best for: Verifying that account details (routing numbers, bank codes) correspond to real financial institutions

Database verification checks the bank-level details (routing number, sort code, bank code) against official banking directories to confirm the institution exists.

How It Works

Cross-reference the bank code, routing number, or sort code provided by the customer against official directories:

• National bank registries
• SWIFT/BIC directory
• Central bank databases
• Industry directories (e.g., ABA routing number database in the US)

Edge's Bank Directory API provides this functionality — search for banks by name, country, or code and get verified institution details.

Pros

• Instant — database lookups are fast
• Confirms institution exists — catches fake or decommissioned bank codes
• Enriches data — returns bank name, address, and additional identifiers
• Low cost — simple database lookup

Cons

• Does not confirm account-level details — confirms the bank exists, not that the specific account number is valid
• Does not confirm ownership — no proof that the customer controls the account
• Data freshness — banking directories change as banks merge, rebrand, or close branches

When to Use

Use as a supplementary check alongside other methods. Database verification catches obviously fake bank details and enriches the data you display to the customer for confirmation.

Method 5: Manual Verification

Best for: High-value or high-risk transactions where other methods are insufficient

Manual verification involves collecting supporting documentation from the account holder to confirm their bank details.

How It Works

Request one or more of:

• A voided check (shows bank code, branch code, and account number)
• A bank statement (shows account holder name, account number, and institution)
• A bank letter or certificate (official confirmation from the bank)
• A screenshot of online banking (showing account details)

Review the documentation manually to confirm the account details match what was provided.

Pros

• Flexible — works in any country, with any bank
• Can confirm ownership — documents show the account holder's name
• Regulatory acceptance — widely accepted for KYC purposes
• No technical integration — no APIs or banking infrastructure required

Cons

• Slow — document collection and review takes time
• Fraud risk — documents can be forged or digitally altered
• Operationally heavy — requires human review, which does not scale
• Customer friction — asking customers to upload bank documents increases drop-off
• No real-time validation — cannot be used in instant payment flows

When to Use

Use manual verification as a fallback for high-value or high-risk scenarios where automated methods are insufficient — large vendor payments, initial setup of recurring high-value transfers, or cases where automated verification returns inconclusive results.

Choosing the Right Method

The best approach depends on your use case, geography, and risk tolerance:

Scenario	Recommended Methods
Customer onboarding (IBAN country)	IBAN validation (instant) + sanctions screening
Customer onboarding (non-IBAN country)	Database verification + micro-deposits or open banking
Recurring payment setup	IBAN validation + micro-deposits or open banking
High-value vendor payment	IBAN validation + manual verification (bank letter)
Real-time marketplace payout	IBAN validation + database verification
Lending / income verification	Open banking (with transaction history)

Layered Verification

For most businesses, the right approach is layered verification:

1. First layer (instant, every transaction): IBAN validation or database verification — catches formatting errors and fake bank codes immediately
2. Second layer (onboarding): Micro-deposits or open banking — confirms account ownership
3. Third layer (high-risk): Manual document verification or enhanced due diligence — for high-value or suspicious cases

This layered approach gives you speed for the majority of cases (where IBAN validation is sufficient) while providing deeper assurance where the risk warrants it.

Implementing Bank Account Verification

For developers building payment systems, here is a practical implementation flow:

Step 1: Validate the IBAN at Input

Add real-time IBAN validation to your forms. As the user types or pastes their IBAN, call the validation API and display the result immediately — show the bank name and country so the user can confirm the details are correct.

const response = await fetch('https://api.edge-api.com/v1/iban/validate', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({ iban: userInput })
});

const result = await response.json();

if (result.data.is_valid) {
  // Show bank name and country for user confirmation
  showBankDetails(result.data.bank_name, result.data.country);
} else {
  // Show validation error
  showError(result.data.error_message);
}

Step 2: Screen Against Sanctions

For compliance, screen the account holder against sanctions lists before processing any payment.

Step 3: Store Verified Details

Store the verified IBAN along with the enriched bank details (bank name, BIC, country) returned by the validation API. This data is useful for payment reconciliation and future reference.

Step 4: Monitor for Changes

If a customer updates their bank details, re-validate the new IBAN and flag the change for review. Account detail changes can be a sign of fraud (payee account takeover).

Frequently Asked Questions

Can I verify a bank account number without sending money?

Yes. IBAN validation verifies the account number format, check digits, and bank code without sending any money. Open banking verification connects directly to the bank's API. Only micro-deposit verification requires sending actual funds.

How long does bank account verification take?

It depends on the method. IBAN validation and database verification are instant (milliseconds). Open banking verification takes 1-2 minutes (the time for the customer to authenticate with their bank). Micro-deposits take 1-3 business days.

Does IBAN validation confirm the account holder's name?

No. IBAN validation confirms the account number format and bank details, but does not verify who owns the account. For name confirmation, you need either open banking (which returns the account holder name from the bank) or Confirmation of Payee services (available in the UK and some EU countries).

What is Confirmation of Payee (CoP)?

Confirmation of Payee is a name-checking service that verifies whether the account holder's name matches the name provided by the payer. It was introduced in the UK in 2020 and is expanding to other markets. CoP reduces authorized push payment fraud by alerting payers when the name does not match.

How do I verify a US bank account without an IBAN?

US accounts use ABA routing numbers + account numbers instead of IBANs. Verification options include: micro-deposits, Plaid or similar open banking aggregators, ACH prenote (zero-dollar test transaction), or manual verification with a voided check.