viaBanking
Schedule a demo

Bank Account Verification API

Bank account verification API: one API, every bank

Use the bank account verification API to access consented account data, verify ownership, read balances, and support onboarding or risk workflows. One verification API endpoint covers every bank, every account number, every name match API check, every account validation, through one API integration.

Talk to Sales Explore API

Free sandbox · Run a verification API call in any market in under a day.

  • 1One verification API
  • ∞Aggregated providers
  • 2.5k+Banks & EMIs
  • AIS+ PIS coverage
  • SCASecure consent
  • SDKDeveloper-ready API

Definition

What is a bank account verification API?

In business terms, a bank account verification API confirms a customer truly owns a bank account before you pay out, accept a payment, or onboard them. The API returns a clean verification result your code can branch on, with no manual upload of statements, no card-based fallback and no friction.

The verification API answers the four questions every risk team asks:

  1. 01 Is this account real?

    Direct check against the bank, not a third-party list.

  2. 02 Does the name match?

    Account holder name vs. application name, with a confidence score.

  3. 03 Are there enough funds?

    Live balance read, scoped to the consent the customer granted.

  4. 04 Is the account in good standing?

    Status flags, recent activity and any bank-reported issues.

Technically, a bank account verification API is an open banking AIS API wrapped with a verification layer. It consumes the bank's account data and emits a normalised response with account name, account number, IBAN, balance and status. viaBanking ships a single verification API that covers every bank in the open banking network, so one API call is enough to verify any bank account in any market.

The verification is carried out in a secure manner, in compliance with the financial, security and data privacy laws. See industry maps on the solutions overview.

The problem

Stitching a verification API per bank does not scale

Every bank publishes its own open banking API. Most are technically compliant, operationally different, and any team trying to run a verification API check across borders feels it on the first API integration. These are the technical challenges viaBanking is built to absorb.

  • Integration fatigue

    Any API integration looks easy in isolation. Twenty bank API integrations do not. Each verification API has its own quirks; your team owns the patchwork.

  • Provider fragmentation

    Use one verification API provider for Germany, another for France, a third for EMIs. Different API contracts. Different verification API rules per API.

  • Inconsistent bank APIs

    One bank API returns the holder name flat; the next nests it. One verification API gives an account number, the next only an IBAN. Your code branches per API.

  • Compliance & maintenance

    PSD2 licences, SCA exemptions, audit logs. Any verification API change costs engineering time. Maintenance scales with every bank, every API, every market.

One verification API
Universal verification API

Providers, banks and EMIs behind a single bank account verification API contract.

Auth flows

1 API

Account schema

1 API

EU banks

2,500+

Markets

30+

API uptime

99.99%

The viaBanking solution

One verification API, every bank, every check

viaBanking is the universal bank account verification API aggregator. We integrate providers, banks and EMIs, normalise the account verification API model, and expose one verification API your team writes code against. The API routes any verification API check (account number, IBAN, name match, balance API check) to the right bank API in the right market, through one verification API endpoint.

The result is one verification API contract, one auth flow, one set of webhooks, one upgrade path. Your engineers ship features. Your risk team uses the verification API for every account API check: onboarding, payment validation, ad-hoc account verification. Your finance team uses the API for reconciliation. The verification API becomes a single bank account service across every bank API you need.

Core capabilities

Everything the verification API exposes

Each capability is one verification API endpoint. One API contract. One bank account verification API integration.

  • AIS

    Account data access

    The verification API pulls consented account data (account name, account number, IBAN, balance) from any bank API, on one API call.

  • PIS

    Payment verification

    Use the same verification API to confirm a payment API landed on the named bank account. One API endpoint for every payment API check.

  • VFY

    Ownership verification

    The verification API verifies the account holder name and account number against your application data. The API returns a deterministic match score.

  • NM

    Name match check

    Submit a name and the verification API returns a name match decision per bank: exact, fuzzy, mismatch. One API, one normalised name check format.

  • IBAN

    Account number & IBAN validation

    The verification API runs IBAN checksum validation, account number format validation and bank routing validation in one API call.

  • TX

    Transaction retrieval

    Pull transaction data within bank-permitted windows. The verification API hands your code statement data for a deeper check.

  • FSM

    Status handling

    One unified verification API state machine (Pending, Verified, Mismatch, Failed) on every bank account API check, across every API.

  • EVT

    Webhooks

    The verification API emits signed webhook callbacks on any account verification, consent change or balance API check refresh.

  • CARD

    Card vs bank account API check

    Skip card-based verification with its card fee and card chargeback risk. The bank account verification API replaces card check fallbacks.

  • SBX

    Sandbox & testing

    A free, no-card sandbox simulates any verification API call on any bank account, including name match and account number check fixtures.

  • DOCS

    API documentation

    Code-first verification API reference with sample bank account verification API calls in five languages. Read the API reference.

  • BULK

    Bulk & async verification

    The verification API accepts bulk account verification API jobs. Use the async API pattern: submit a list, get a webhook per account API check on every bank.

API endpoints

The full verification API catalogue

Every verification API endpoint shares one API contract, one auth flow and one normalised response. Pick the API you need and call it directly.

  • POST /v1/api/verify/account

    Master verification API endpoint. The API confirms the account number, the IBAN number, the routing number and the account holder name on any bank API. The API returns a verification number you can store for audit.

  • POST /v1/api/verify/account-number

    Account number check API. Runs account number format validation, account number checksum validation and account number-bank routing match. The API returns a confidence number per account number.

  • POST /v1/api/verify/iban

    IBAN API validation. The API parses the IBAN number, runs the IBAN checksum number check and confirms the IBAN-bank number match on any bank API.

  • POST /v1/api/verify/name

    Name match API endpoint. The verification API returns a similarity number per name component and a single name match decision the API treats as authoritative.

  • POST /v1/api/verify/balance

    Balance check API. The API returns the balance number, the available number, the currency and the bank API timestamp for every balance API check call.

  • POST /v1/api/verify/owner

    Ownership verification API. The API confirms the account holder, returns the account number, the IBAN number and a match number across every bank API in the network.

  • GET /v1/api/banks

    List the bank API coverage. The API returns the number of supported bank APIs per market, the number of supported account types and the verification API capabilities per bank.

  • GET /v1/api/verify/{verification_number}

    Read a verification API result by verification number. The API returns the full audit record for any account verification API you have run on any bank API.

  • POST /v1/api/verify/bulk

    Bulk verification API. Submit a batch of account verifications, get a job number; the API streams a verification number per account through one webhook API.

  • POST /v1/api/verify/async

    Async verification API pattern. The API returns a queue number and a callback url; the verification API emits a webhook with the final API result.

  • POST /v1/api/webhooks

    Webhook subscription API. Register an endpoint by url and the verification API will post signed webhook events with the verification number, the account number and the bank API source.

  • GET /v1/api/health

    Status API. The API returns the live bank API count, the number of degraded API integrations and the verification API uptime number for the last 24 hours.

Service tiers

Pick the right verification API service

Every tier is the same verification API. The service level, support service and SLA scale with the number of verifications you run.

Sandbox service

Free API keys, full verification API access, every bank API fixture. A self-serve developer service for prototyping verification API before you commit to a paid service.

Production service

Pay-as-you-go verification API service. The number of API calls scales with traffic; the service-level target stays the same on every bank API.

Enterprise service

A managed verification API service with dedicated SLAs, a named support service team, custom routing controls and a high call number ceiling per second on every bank API.

Use cases

Where teams put the verification API to work

  1. 01

    Onboarding

    Use the verification API at sign-up. The API confirms the account number, runs a name match API check and verifies ownership in seconds. No statement upload, no card check fallback.

  2. 02

    Lending & underwriting

    The verification API reads 12 months of account data. Use the same API for balance API check, income check, name match and account number validation in one workflow.

  3. 03

    Merchant payments

    Use the verification API to confirm a payment really landed on the merchant bank account. One API endpoint, every bank, every payment API check.

  4. 04

    Reconciliation

    The verification API matches incoming bank credits to invoices. Use the API to confirm the account number and account name on every reconciled payment.

  5. 05

    Risk checks & expansion

    Use the verification API for ad-hoc account API check, batch name match and live balance API check. Open new markets by switching bank APIs on the same API. See coverage on the pricing page.

Integration flow

From API access to live verification API monitoring

  1. 01

    Request API access

    Sign the developer terms and get sandbox API keys the same day. Any team can start a verification API integration without a procurement gate.

  2. 02

    Consent & SCA

    Your application redirects the account holder to their bank. The bank handles SCA, releases the account data and grants the verification API the scope it needs.

  3. 03

    Verification API request

    Call /v1/verify/account with the account number, name and bank routing. One API contract for any verification API check on any bank.

  4. 04

    Response & webhooks

    The verification API returns a unified verification API response. Listen for webhook events on any async verification API check. Render the API result to the customer.

  5. 05

    Production monitoring

    Promote your code, point at live bank APIs and watch every API call from one dashboard. Runbooks in the developer docs.

Security & compliance

Explicit consent. SCA on the bank. Data minimisation by default.

Any verification API call requires explicit, revocable consent from the account holder. Strong Customer Authentication (SCA) runs on the bank side, so the verification API never sees credentials. Data minimisation means the API only stores the account fields in scope, only for the period your application needs them.

The bank account verification API operates within the PSD2 framework and tracks emerging PSD3 guidance. Specific licence and authorisation details vary by market; review the current regulatory scope on our about page before going live with the verification API.

  • Explicit verification API consent capture & revocation per account, audit-logged
  • SCA orchestration: account holder credentials stay on the bank, never on the API
  • Data minimisation per verification API scope, per application, per account
  • TLS in transit, encryption at rest across every verification API call
  • Secure API access via signed bank account verification API keys

FAQ

Common questions before you ship the verification API

How fast can I integrate the bank account verification API?

Any team can run their first verification API call from sandbox in under a day. A production verification API rollout for every bank API you need usually takes two to four weeks of API integration work.

Which banks and account types does the verification API cover?

The verification API covers over 2,500 EU bank API connections plus major EMIs. Any open banking account that exposes data on the bank API can run a verification API check via the bank account verification API: account number, IBAN, name match and balance API check, on one API.

Does the API do both account data access and payment verification?

Yes. The same verification API serves AIS for account data and PIS for payment verification. One verification API contract, one set of webhooks, one auth flow for any verification API check on any account or any payment.

Who handles consent and SCA when the verification API runs?

The bank does. The account holder authenticates with their bank, approves the verification API scope, and the bank releases the account data the API needs. viaBanking never sees credentials; the verification API only sees the consented scope.

When can my application start running verification API calls in production?

As soon as you finish sandbox testing the verification API, request production API keys and enable the bank APIs you need. The verification API goes live with no procurement gate, on the same bank account verification API contract you used in sandbox.

Is the bank account verification API suitable for high-volume risk checks?

Yes. The verification API supports bulk verification, async verification, webhook verification and per-account rate controls. Any risk team can use the same verification API for batch onboarding, ad-hoc account API check, recurring name match validation and live balance API check across every bank API.

Free sandbox · No card needed

Ready to verify any bank account? Ship the verification API today.

Get sandbox API access, browse the bank account verification API documentation and run your first verification API call in a day. Use one verification API for every bank, every account API check, every name match, every account number validation, across every market.

Talk to Sales Explore API