--- updatedAt: 2026-07-23T12:19:42.000Z agentTools: projectIndex: https://docs.sumsub.com/llms.txt --- # Bank Account Verification Perform instant bank account checks across Europe with a single integration. Bank Account Verification is Sumsub's document-free data verification solution designed specifically for regulated businesses to enable a real-time connection to customer banking information on a pan-European level, including account ownership, balance details, and transaction history. It is based on the Account Information Service (AIS) that allows authorized Third Party Providers (TPPs) to securely access consolidated information from a customer's payment account in 28 countries and over 2200 financial institutions by using the EU/EEA open banking technical infrastructure. As a result, the solution covers over 90% of the adult population in each supported jurisdiction, as it successfully represents all residents that have an active account in any one of the available banks. Bank Account Verification solution works by simply having the applicant authenticate themselves on their selected banking platform via a standard login process, which leverages Strong Customer Authentication (SCA) tools, ensuring protected personal and financial data sharing. The result delivers comprehensive customer information in compliance with a range of use cases under the AML/CTF and the Revised Payment Services Directive (PSD2), including Payment Method, Financial Vulnerability, Creditworthiness, and Source of Funds/Wealth Checks, as well as a confirmation of their real-time presence and data owners. Overall, Bank Account Verification offers one of the most well-recognized solutions to customer banking data verification that helps businesses achieve international AML/CTF and PSD2 compliance, prevent identity fraud, and optimize due diligence procedures, all through a seamless, document-free user experience. ### Note - The Open Banking infrastructure under the [Directive (EU) 2015/2366](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015L2366), 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. - The solution can be enabled both via the **Standard** level type used for customer onboarding, as well as the [Applicant actions](https://docs.sumsub.com/sumsub/docs/applicant-actions) level type, leveraging the **Payment methods** verification infrastructure, to trigger Bank Account Verification after a specific event or customer action. - The Bank Account Verification solution is **only supported via the** [WebSDK](https://docs.sumsub.com/sumsub/docs/about-web-sdk), which requires redirecting to an external browser (for example, Chrome, Safari) to function correctly. It is not compatible with application-embedded browser environments, including WebView components (Android WebView and iOS WKWebView) as well as browser presentation components (Android Chrome Custom Tabs and iOS SFSafariViewController). # Use cases Bank Account Verification satisfies three primary use cases for Sumsub clients. *** {`

Case 1: 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 2: 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 3: 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: * **Efficiency**. Automate customer data verification, eliminating the need for manual document inspection and authenticity checks. * **Coverage**. Reach verified records of over 90% of the national adult population in each of the 28 supported countries with the use of a single solution. * **Compliance**. Meet international CDD and EDD requirements under AML/CTF, PSD2, and upcoming European regulatory mandates. * **Conversion**. Simplify the end-user journey and eliminate drop-offs by leveraging a simple and familiar online banking authentication process. * **Fraud Prevention**. Verify customer data legitimacy, minimizing the risk of identity fraud, such as account takeover or illicit use of payment credentials. * **Onboarding Optimization**. Implement early-stage customer segmentation, allowing low-risk applicants through a simplified onboarding flow. * **Seamless integration**. Seamlessly integrate Sumsub's solution into your system via our lightweight SDK and API frameworks. # How Bank Account Verification works Sumsub's Bank Account Verification is an advanced customer banking data verification solution that enables a real-time API connection between businesses and financial institutions via the EU/EEA open banking infrastructure, in full compliance with international AML/CTF and PSD2 regulations. The solution can be implemented through 2 different steps within the verification flow: 1. [Non-Doc](https://docs.sumsub.com/sumsub/docs/bank-account-verification#bank-account-verification-via-non-doc-step) step. Include Bank Account Verification as part of the initial onboarding by using the **Non-Doc** step in a **Standard** level type. 2. [Payment methods](https://docs.sumsub.com/sumsub/docs/bank-account-verification#bank-account-verification-via-payment-methods-step) step. Configure Bank Account Verification as an action triggered by a specific event using the **Payment methods** verification step in the [Applicant actions](https://docs.sumsub.com/sumsub/docs/applicant-actions) level type. ## Bank Account Verification via Non-Doc step 1. Applicant selects their country and preferred banking platform for verification. 2. Applicant logs into their bank account and provides consent for data sharing. 3. The system automatically retrieves all relevant data stored on the account. 4. Sumsub cross-checks the applicant's information to ensure a complete identity match. ## Bank Account Verification via Payment methods step 1. Applicant selects the Bank account payment verification method. 2. Applicant selects Online banking as the option for bank account verification. 3. Applicant selects their country and preferred banking platform for verification. 4. Applicant logs into their bank account and provides consent for data sharing. 5. The system automatically retrieves all relevant data stored on the account. 6. Sumsub cross-checks the applicant's information to ensure a complete identity match. # Supported jurisdictions The Bank Account Verification solution is supported by the banks of the following jurisdictions: *** {`
Austria
Belgium
Bulgaria
Croatia
Cyprus
Denmark
Estonia
Finland
France
Germany
Greece
Hungary
Iceland
Ireland
Italy
Latvia
Lithuania
Luxembourg
Malta
Netherlands
Poland
Portugal
Romania
Slovakia
Slovenia
Spain
Sweden
Norway
`} *** Explore our [Coverage Sheet](https://docs.sumsub.com/sumsub/docs/supported-aspsps-in-eu-eea) for a full breakdown of ASPSPs enabled by our Bank Account Verification solution within each jurisdiction for individual and business account data enrichment. # 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](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015L0849)), 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 and ownership of the payer’s account, providing accurate identification and traceability of any executed transaction. This verification process plays a pivotal role in safeguarding the financial ecosystem against fraud and illicit activities. * **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](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015L0849)), European Banking Authority (EBA) Guidelines on loan origination and monitoring ([EBA/GL/2020/06](https://www.eba.europa.eu/sites/default/files/document_library/Publications/Guidelines/2020/Guidelines%20on%20loan%20origination%20and%20monitoring/884283/EBA%20GL%202020%2006%20Final%20Report%20on%20GL%20on%20loan%20origination%20and%20monitoring.pdf)), and Markets in Financial Instruments Directive II (MiFID II) ([2014/65/EU](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0065)). 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](https://www.gamblingcommission.gov.uk/licensees-and-businesses/lccp/print)), Ontario Alcohol and Gaming Commission of Ontario (AGCO) [Standards](https://www.agco.ca/en/book/export/html/245361), British Columbia Lottery Corporation (BCLC), Australian Communications and Media Authority (ACMA) [Interactive Gambling Act 2001](https://www.legislation.gov.au/Details/C2023C00273), and USA State Gambling Regulations, including the New Jersey Division of Gaming Enforcement (NJDGE) [Regulations](https://www.nj.gov/oag/ge/), and Nevada Gaming Control Board (NGCB) [Regulations](https://gaming.nv.gov/uploadedFiles/gamingnvgov/content/regs/AllRegulations.pdf). * **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](https://eur-lex.europa.eu/eli/dir/2018/843/oj)) and PSD2 ([Directive (EU) 2015/2366](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015L2366)). 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 ![](https://files.readme.io/6efe1dcb12099fb793a23d46f8d508da64af707ce45a48803492673f62b4565d-image.png) # Get started with Bank Account Verification The Bank Account Verification solution is currently supported via Sumsub's [WebSDK](https://docs.sumsub.com/sumsub/docs/web-sdk) framework. Refer to the complete [technical integration guide](https://docs.sumsub.com/sumsub/docs/get-started-with-bank-account-verification) 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.

`}