{"title":"Bank account verification with open banking","category":"default","creationDate":1776961628,"content":"

Adyen's verification through bank report service uses Adyen's open banking gateway to retrieve bank account verification reports from third-party banks.<\/p>\n

For example, you consider hiring an unregistered third-party individual on a contract-basis for services, such as food-delivery or as a courier. You want to make sure the person is who they say they are before<\/em> you enter into an agreement with them for their services.<\/p>\n

You can verify them through Account Information Service Providers (AISPs) such as Plaid or Tink. The third-party individual can authorize their bank to share a bank account verification report with you, which provides bank account ownership verification and Know Your Customer (KYC) verification quickly and securely.<\/p>\n

Requirements<\/h2>\n

Before you begin, take into account the following requirements and preparations.<\/p>\n\n \n \n \n \n \n \n
Requirement<\/th>\n Description<\/th>\n <\/tr>\n <\/thead>\n
Integration type<\/strong><\/td>\n This feature is supported with an Adyen for Platforms<\/a>, Marketplaces<\/a>, or a Classic integration<\/a>.<\/td>\n <\/tr>\n
API credentials<\/strong><\/td>\n You must have an API key<\/a> (recommended) or basic authentication username and password<\/a> to access this API.

Ensure that you have asked your Adyen contact to assign the following role to your API credential:
  • Role for OpenBanking account verification use case: EXTERNAL<\/strong><\/li><\/ul><\/td>\n <\/tr>\n
Setup steps<\/strong><\/td>\n \n Before you begin, you have the option to customize the open banking widget. If you choose to, provide Adyen the necessary information to customize and display your company name and logo within the widget when the flow transitions to the Adyen's open banking gateway:\n \n \n \n \n \n \n \n \n
Information<\/th>\n Required?<\/th>\n Shown to third-party individual<\/th>\n <\/tr>\n
Company name<\/td>\n Yes<\/td>\n No<\/td>\n <\/tr>\n
Logo<\/td>\n No, but recommended<\/td>\n Yes<\/td>\n <\/tr>\n
Application name<\/td>\n Yes<\/td>\n Yes<\/td>\n <\/tr>\n
Legal entity name<\/td>\n Yes<\/td>\n No<\/td>\n <\/tr>\n
Website<\/td>\n Yes<\/td>\n No<\/td>\n <\/tr>\n
Address<\/td>\n Yes<\/td>\n No<\/td>\n <\/tr>\n <\/table>\n <\/td>\n <\/tr>\n <\/tbody>\n<\/table>\n

How it works<\/h2>\n

When you want to verify a third-party individual's bank account ownership through a redirect, use the following flow.<\/p>\n

    \n
  1. \n

    Make a request to the \/routes<\/a> generation endpoint to get a list of available account verification routes. Each route represents a possible connection path between the third-party individual and their bank. When the third-party individual successfully connects through one of these routes, you will receive a report code<\/a>. Use the code<\/a> to:<\/p>\n