On this page

Bank Statement Ownership Verification

Vector checks the account holder's name on uploaded bank statements before using the statements for underwriting. The check uses the applicant information already available in the application.

Personal applications#

The account holder's name must match at least two full names from the applicant's BVN-verified identity.

  • Names may appear in a different order.

  • Capitalization, punctuation and spacing differences are ignored.

  • Initials do not count as full-name matches.

For example, a statement belonging to Chukwu Yusuf Adeyemi can match an applicant verified as Yusuf Adeyemi.

Business applications#

A business application can include statements from a business account or a personal account.

Business account: The account holder's name must match the official business name supplied in business.businessName. Common legal suffix variations, such as Ltd and Limited, are accepted. Trading names alone do not satisfy the check.

Personal account: The account holder's name must match at least two full names from the BVN-verified applicant.

Vector uses the information provided in the application. This check does not include a separate CAC or director-status lookup.

Multiple bank statements#

Vector checks every uploaded statement independently, including separate PDFs and statements containing multiple accounts.

If any uploaded statement fails ownership verification, the application fails before financial scoring.

Error codes#

CodeDescriptionRequired action
STATEMENT_NAME_MISMATCHThe account holder does not match the applicable applicant or business name.Submit a statement with a matching account holder.
STATEMENT_NAME_UNAVAILABLEThe statement does not contain an identifiable account holder name.Upload a statement showing the account holder's name.
BUSINESS_NAME_REQUIREDThe official business name is needed to match a business account statement.Supply business.businessName.

These errors are non-retryable. A corrected application can be submitted.

Failed application response#

GET /api/v1/applications/{application_id}

json
{
  "application_id": "APPLICATION_ID",
  "status": "failed",
  "error": {
    "code": "STATEMENT_NAME_MISMATCH",
    "message": "The statement account holder does not match the verified applicant or registered business name.",
    "retryable": false
  },
  "created_at": "2026-11-17T10:00:00Z",
  "failed_at": "2026-11-17T10:00:15Z"
}

The initial POST /api/v1/applications request can return received because statement parsing happens during application processing. Retrieve the application status or consume the decision.ready webhook to obtain the final result.

Standalone statement uploads#

For POST /api/v1/bank-statements, ownership verification runs during the asynchronous parsing job. The upload can initially return 202 Accepted.

Check GET /api/v1/bank-statements/{id} for the final statement status. A mismatch appears as status: "failed" with a failureReason beginning with [STATEMENT_NAME_MISMATCH].

Sandbox testing#

Use a test-environment API key and a synthetic BVN outside the reserved scenario range 00000000001–00000000012.

The sandbox BVN provider returns a synthetic verified applicant name. Prepare a sample statement with a matching account holder for the successful case, then change the account holder's name to test rejection.

Recommended test cases:

  1. Personal account with two matching names.

  2. Personal account with fewer than two matching names.

  3. Business account matching `business.businessName`.

  4. Business account showing a different trading name.

  5. Personal account submitted with a business application, matching the BVN applicant.

  6. Statement with no identifiable account holder.

  7. Multiple statements where one account holder does not match.

The reserved scenario BVNs use fixed underwriting outcomes and bypass normal statement parsing. They cannot be used to test ownership verification.

Supported input paths#

Ownership verification applies to uploaded PDF, CSV and TXT statements where Vector can extract an account holder name, as well as uploaded statements containing multiple accounts.

Pre-structured transaction arrays and JSON ledgers do not carry extracted bank-statement ownership evidence through this check. They retain their existing handling.

A CSV or TXT statement without an extractable account holder name fails with STATEMENT_NAME_UNAVAILABLE.