Introduction to Account Verification

Overview

The bank of your end-user already performed a thorough identification of the account ownership when opening the bank account. Our Account Verification allows you to make use of this valuable information the banks have on your users. By connecting and sharing the account information within your application, your end-user can immediately get to your core service offering without time-consuming identification processes like micro-deposits or manual provision of bank statements. Qwist has developed a comprehensive name-matching algorithm that compares the provided name of your end-user with the account holder name fetched from the end-user's account information.

Optionally, you can also combine the Account Verification with fetching the account transactions of your users.

How it works

You can find a Step-by-Step description in the next section.

Prerequisites

API Access & Authentication

In order to get started to test our Account Verification product, you need access to our API with some test credentials. The finX API requires a ClientID and Client Secret to authenticate with Basic Auth. Also, you need a host URL to reach our finX API platform.

If you want to get started with your credentials, please reach out to us!

Widget Integration

The Account Verification can be accessed via the finX API, which is providing a Widget User Interface to guide the user through the account connection flow.

Some important information on how to handle our widget:

  • The widget UI supports internationalization. Localization defaults to German de when a locale isn't specified or supported. It does not attempt to read user's machine language preference i.e. Accept-Language header. You have to explicitly instruct which language to display when initiating the flow by setting the language key in the request.
  • The Widget UI supports multiple browsers like Internet Explorer 11, Edge, Chrome, Firefox and Safari.
  • The Widget UI can be integrated as standard OAuth redirect flow or as iframe. Check out our technical documentation for the full Widget specification.

🚧

iframe limitations

When integrating the Widget inside a native app, it's highly recommended to integrate it by opening the link location you get on flow initiation service on top-level (browser or WebView) instead of in an iframe. If the Widget is integrated with an iframe in an environment where programmatically opening a new tab isn't possible i.e. WebView, it won't be able to complete redirect challenges.