Bank Account Verification

Perform fast bank account checks for users in Europe.

Sumsub’s Bank Account Verification enables a real-time connection between businesses and customer financial data on a pan-European level, including account ownership, credit limit, balance details, and complete transaction history.
We offer a secure and effortless method for organizations to obtain key customer financial data, prevent identity and financial fraud, optimize the due diligence procedures, and stay compliant with PSD2 and AML/CTF mandates.

Sumsub’s Bank Account Verification ensures effective and reliable access to payment account data in banks, credit institutions, and electronic money institutions by leveraging the EU Open Banking framework that has been adopted and regulated in 30 countries of the European Economic Area (EEA) under the Revised Payment Services Directive (PSD2).

📘

Note

The Open Banking infrastructure under the Directive (EU) 2015/2366, officially referred to as the Revised Payment Services Directive (PSD2), is a technological and legal framework which mandates Account Servicing Payment Service Providers (ASPSPs) in the European Economic Area (EEA), including banks, credit institutions, and electronic money institutions, to allow authorized Third Party Providers (TPPs) access to financial customer data via application programming interfaces (APIs) on the basis of explicit customer consent. TPPs consist of Payment Initiation Service Providers (PISPs), Account Information Service Providers (AISPs), and Card-Based Payment Instrument Issuers (CBPIIs).

The Account Information Service (AIS) is an online service regulated under the PSD2 that allows authorized or registered AISPs, to access and consolidate financial customer information from ASPSPs on behalf of the customer.

Use cases

Bank Account Verification satisfies three primary use cases for Sumsub clients.


Case 1: Verification of payee

Real time verification of the individual's identity and bank account ownership before processing and confirming the payment transactions that the end-user has initiated, especially large-amount transactions when Enhanced Due Diligence (EDD) should be applied:

  • Payment service providers
  • Trading platforms
  • E-Commerce platforms
  • Social Media Platforms

Case 2: Payment Method Verification

Payment Method Verification helps authorize customer transaction legitimacy and prevents different types of identity fraud, including account takeovers, that could cause chargeback losses:

  • iGaming operators
  • Trading platforms
  • BNPL platforms
  • E-Commerce platforms

Case 3: Financial vulnerability checks

Financial Vulnerability and Creditworthiness Checks help evaluate the customer’s exposure to immediate financial issues as well as existing indebtedness to execute responsible financial practices:

  • iGaming operators
  • Trading platforms
  • BNPL platforms
  • Banking institutions

Case 4: Age verification

Age Verification helps determine that customers meet the requirements for age-restricted services and activities to prevent the risk of legal liabilities and negative public exposure:

  • iGaming operators
  • Dating platforms
  • Social media platforms

Solution benefits

Key benefits of the Sumsub Bank Account Verification solution include the following:

  • Fraud Prevention. Verifies that the payment method is valid and belongs to the customer, minimizing the risk of identity fraud, such as account takeover or illicit use of payment credentials.
  • Regulatory Compliance. Helps businesses meet CDD and EDD requirements under AML/CTF regulations, and seamlessly integrates with broader PSD2 obligations in EEA as well as upcoming mandates in Europe, such as the Instant Payments Regulation.
  • Customer Conversion. Simplifies the end-user journey and prevents potential drop-offs by leveraging a simple, online banking authentication process that is both secure and familiar to the customer.
  • Operational Efficiency. Automates customer data verification through a direct connection to major European banking institutions, eliminating the need for manual document inspection and authenticity checks.
  • Risk Management. Enables businesses to assess customer risk levels by gaining insights into their financial behavior over an extended period of time, which helps detect signs of financial vulnerability.
    CDD Optimization. Implements early-stage customer segmentation, allowing low-risk users through a simplified onboarding flow, while assigning additional due diligence measures for high-risk users.

How Bank Account Verification works

The verification process is enabled through a seamless user bank account login that leverages Strong Customer Authentication (SCA) tools, implemented by financial institutions as part of the PSD2 requirements.

Step-by-step product journey:

  1. The user selects their country from a dropdown menu on the onboarding page.
  2. The user chooses a banking institution from a list of supported banks.
  3. The user reviews and provides consent for data sharing, as required for verification purposes.
  4. The user enters their online banking credentials to establish a secure connection.
  5. The user verifies their account ownership and confirms their real-time presence via secure authentication methods.
  6. Relevant bank account details are retrieved automatically and securely by Sumsub.
  7. Retrieved data is instantly matched against the user's personal information for validation.
  8. The user’s bank account data is verified, and the process is successfully completed, with data delivered to the client via API or SDK.

Supported jurisdictions

The Bank Account Verification solution is supported by the banks of the following jurisdictions:



Compliance overview

The Sumsub Bank Account Verification solution aligns with critical European regulatory frameworks, ensuring businesses meet compliance requirements while enhancing the security of financial transactions:

  • Payment Method Verification. Under the 4th Anti-Money Laundering Directive (Directive (EU) 2015/849), all regulated institutions whose operations involve payment transaction processing are advised to perform payment method ownership verification in order to combat both money laundering and the financing of terrorist activities. The Bank Account Verification solution helps businesses ensure the legitimacy of both the payer’s and payee’s account legitimacy and ownership, providing accurate identification and traceability for all parties involved in a transaction. This verification process plays a pivotal role in safeguarding the financial ecosystem against fraud and illicit activities.
  • Verification of Payee (VoP). The Verification of Payee (VoP) requirement, introduced under Regulation (EU) 2024/886, is essential for payment service providers (PSPs) to ensure secure and accurate credit transfers within the SEPA zone. This regulation aims to enhance payment security by requiring PSPs to verify payee information in real-time before processing transactions, reducing the risk of misdirected or fraudulent payments. The regulation becomes mandatory for Eurozone PSPs from October 2025 and non-Eurozone PSPs from July 2027. The Bank Account Verification solutions play a critical role by cross-checking the payer's provided details against the payee's banking records, ensuring compliance with VoP requirements, and safeguarding the integrity of transactions across the payment ecosystem.
  • Financial Vulnerability and Creditworthiness Checks:
    • Financial Institutions. Verifying Financial Vulnerability and Creditworthiness is a crucial compliance measure across regulated industries, including under the 4th Anti-Money Laundering Directive (Directive (EU) 2015/849), European Banking Authority (EBA) Guidelines on loan origination and monitoring (EBA/GL/2020/06), and Markets in Financial Instruments Directive II (MiFID II) (2014/65/EU). These checks aim to ensure that individuals have the financial capacity to engage in transactions or commitments, reducing risks associated with over-indebtedness, fraud, and financial abuse. Bank account verification solutions support this process by confirming account ownership, monitoring transaction history, and validating financial stability, enabling institutions to assess creditworthiness and comply with regulatory standards effectively.
    • Gambling Operators. Gambling Operators under most national regulatory frameworks are required to implement Financial Vulnerability and Affordability Checks to assess whether customers can afford their gambling activity, including analyzing their income, spending patterns, and other financial data, which indicates both the necessary deposit as well as spending limits within the platform. That includes, but is not limited to, the UK Gambling Commission License Conditions and Codes of Practice (LCCP), Ontario Alcohol and Gaming Commission of Ontario (AGCO) Standards, British Columbia Lottery Corporation (BCLC), Australian Communications and Media Authority (ACMA) Interactive Gambling Act 2001, and USA State Gambling Regulations, including the New Jersey Division of Gaming Enforcement (NJDGE) Regulations, and Nevada Gaming Control Board (NGCB) Regulations.
  • Strong Customer Authentication. To validate the financial account ownership the solution leverages Strong Customer Authentication (SCA) methods that have been adopted by all regulated banking institutions in line with the 5th Anti-Money Laundering Directive (Directive (EU) 2018/843) and PSD2 (Directive (EU) 2015/2366). This ensures a protected identity, account, and transaction data sharing access for the end user and regulatory compliance with the directive’s requirements for businesses concerning ownership verification.

Setup and configuration

The provided Bank Account Verification solution scheme demonstrates the following:

  • Overall solution functionality
  • Required steps of the end-user journey
  • Integration architecture between Sumsub and the Open Banking Infrastructure

Get started with Bank Account Verification

The Bank Account Verification solution is currently supported via the Sumsub's WebSDK framework.

Refer to the complete technical integration guide to get started with the implementation process of Bank Account Verification.

Bank Account Verification FAQ

Find the most frequently asked questions about Bank Account Verification.

What is the Account Information Service (AIS) and how is it different from the Payment Initiation Service (PIS)?

The AIS enables access to complete customer bank account details and is primarily applied for various data verification purposes, including personal data cross-checks, payment method verification, financial vulnerability and creditworthiness checks.

The PIS facilitates payment transaction initiation from the customer’s bank account and is commonly applied for real-time identification presence validation, basic personal data cross-matching, and payment method checks.

Which account types are supported for verification?

Bank Account Verification currently supports the following account types:

  • CACC — Current account. Account used to post debits and credits when no specific account has been nominated.
  • CARD — Card account. Account used for credit card payments.
  • CASH — Cash payment. Account used for the payment of cash.
  • LOAN — Loan. Account used for loans.
  • SVGS — Savings. Account used for savings.
  • OTHR — Other. Account not otherwise specified.
If the end-user decides to share multiple accounts for verification, how is Sumsub going to handle the data output?

Sumsub has implemented internal data weighing logic based on the remaining account balance as well as the volume of executed transactions to filter out the accounts shared by the end user and ensure that only relevant details are returned.

Is the end-user charged any bank transfer fees for completing the verification?

No, the end-user is not charged any fees for the process, as they are not required to conduct a payment transaction.

What is the current coverage of the age verification indicator within the solution?

The current coverage of the age verification indicator is around 35-40% and depends on the disclosure of the customer’s date of birth information by each individual ASPSP.

What are the possible reasons why the customer verification could be rejected?

The Bank Account Verification session could be rejected if:

  • The user denies the data sharing consent.
  • The user does not complete the banking authentication.
  • The users bank account ownership details do not match with their previously provided personal data.
Is the Bank Account Verification solution enabled via secure and legally recognized methods?

Yes, Sumsub’s Bank Account Verification solution is built on the EU/EEA open banking infrastructure, which requires most regulated financial institutions to publicly release the API connections to those services that facilitate customer data verification based on their consent.

How can Sumsub's clients request an addition to the list of covered jurisdictions or ASPSPs?

Clients can submit a request to Sumsub via their dedicated Customer Success Manager to check if the desired country is available within the EU/EEA or other open banking ecosystems and is capable of facilitating reliable customer bank account data verification via both secure and nationally-recognized methods.

What is the maximum time period for which we can retrieve the customer transaction history details?

In the upcoming solution releases, Sumsub will is able to retrieve detailed customer transaction data for the last 12 months.