Free demo hits. Pay when you go live. Request access
Banking & Credit

Bank Statement Analysis API

Upload bank statements, or fetch them with consent, and receive parsed transactions, categorised inflows and outflows, salary detection, EMI obligations, bounces and balance trends. Underwrite on real cash flow instead of declared income.

Response
Async, by webhook
Inputs
1 required · 1 optional
Consent
Recorded per request
Billing
Per successful call
POST /v1/bank-statement-analysis
Sandbox · Production
  1. Your application sends

    • Statement PDFs (with password if protected)*
    • Consent reference for account-aggregator fetch
  2. emver API

    Issues a hosted consent link, tracks the person's authorisation and assembles the result.

  3. Completed via

    Statement upload or account aggregator consent

  4. You receive by webhook

    • Parsed transactions
    • Categorised inflows and outflows
    • Detected salary credits and employer
    • EMI and loan obligations
    • Bounces and penalties
    • Average and minimum balances
    • Tamper check result
bank-statement-analysis Full reference
Overview

What the Bank Statement Analysis API does

Bank statements are the richest financial document a lender or employer can hold, and the hardest to read at scale. The Bank Statement Analysis API parses statements from every major bank, detects tampering, categorises transactions and computes the indicators credit and HR teams rely on.

It supports uploaded PDFs, including password-protected ones with the password supplied, and consented fetch through the account aggregator ecosystem where enabled.

Consent is part of the contract

Financial data is sensitive personal data. Capture the person's consent before analysis; the consent record is stored with the request.

Benefits

Why teams use the Bank Statement Analysis API

Turn PDF statements into categorised transactions, income and risk indicators.

Cash-flow underwriting

Decide on observed income and obligations.

Tamper detection

Edited PDFs are flagged before they mislead a decision.

Every major bank

Formats normalised into one structure.

Minutes, not hours

Replaces manual statement review.

Use cases

Where it's called

Where the Bank Statement Analysis API is typically called, and what it settles there.

Personal and business lending

Income, obligations and bounces at a glance.

Salary verification

Confirm declared salary and employer from credits.

Tenant screening

Affordability evidence for rentals.

Insurance underwriting

Financial stability signals for large policies.

How it works

Four steps, one response envelope

Request and response details, environments and a ready-to-import collection are in the developer console.

  1. 01

    Authenticate

    Call with your organisation API key. Sandbox and production use the same contract.

  2. 02

    Create the consent link

    Send the person's details and the documents you need. You receive a hosted link to share on any channel.

  3. 03

    The person authorises

    They sign in and choose what to share. Nothing moves without their approval.

  4. 04

    Receive the result

    Verified documents and details arrive by webhook or on the status endpoint.

Privacy and security built in

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

FAQ

Bank Statement Analysis API: frequently asked questions

What teams ask before adding the Bank Statement Analysis API to their integration.

With the person's consent through the account aggregator ecosystem, yes, where your organisation is enabled for it. Uploaded PDFs are supported for everyone.

They are purged under your retention policy. The structured output is returned to you.

Related

APIs that run alongside it

Usually called with the Bank Statement Analysis API, on the same key.

All APIs
Access usually set up within one working day

Start verifying with emver today.

Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.