Skip to main content
Skip table of contents

Introduction to Account Holder Type Check

Checks an account, and what kind of account holder it is (e.g. joint account holder).

This report is appropriate for B2C use cases.

What it solves

During account checks, it must be possible to distinguish whether an account is a private account or a company account.
It is also relevant for credit applications, for example, whether the account is a joint account.

Account Holder Type Check

This check uses account information such as the account holder to check what type of account holder is on file with the Bank for the account.

As a result, you get a statement whether it is one of the following types:

  • Private person

  • Joint account holder

  • Company account

  • Self employer

Used data fields

No Case is required for checks. Only one data source must have been synchronized successfully.

The account holder is mainly used for this check as input data.

Result

This gives you a quick overview of the transactions used in the report through aggregated values that can serve as a summary.

A full API schema can be seen here: https://docs.finapi.io/?product=di#post-/checks/accountHolderType

Field

Description

Mandatory

checkData

List of the check result, organized by accounts.

yes

checkData[].accountHolderType

Represents what type of account holder it is. Can contain the following values: PRIVATE, JOINT, COMPANY, SELF_EMPLOYER UNKNOWN.

yes

checkData[].accountId

UUID of the bank account belonging to the imported bank connection.

yes

checkData[].accountIban

IBAN of the bank account.

checkData[].transactionsStartDate

Date when user's first transaction has been detected for the imported data of the account. This field takes into consideration all the transactions of the user for the account, irrespectively of the assigned to them label.

checkData[].accountType

Type of the account. Can be:

  • CHECKING

  • SAVINGS

  • CREDITCARD

  • SECURITY

  • LOAN

  • POCKET

  • MEMBERSHIP

  • BUILDING_SAVINGS

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.