Built for lending platforms

Bank Statement Analysis API for Lending Platforms

Send a bank statement PDF and receive structured cash-flow metrics, NSF and overdraft counts, MCA indicators, and risk signals—ready for your LOS, CRM, or underwriting workflow.

Request API Key →Book Integration Demo
✓ REST API✓ JSON responses✓ Server-side authentication
POST /api/v1/analyze
curl -X POST \
  https://statementscrub.com/api/v1/analyze \
  -H "X-API-Key: ss_your_key" \
  -F "[email protected]"

HTTP/1.1 200 OK
{
  "analysis_id": 1842,
  "status": "complete",
  "result": { ... }
}
Use cases

Put statement intelligence inside your workflow

Application pre-screening

Analyze cash flow when statements enter your application funnel and route files by risk.

Automated underwriting

Pre-populate deposit, balance, NSF, overdraft, and MCA fields for underwriter review.

Broker and lender portals

Return consistent analysis inside the experience your partners already use.

Quality control

Apply the same first-pass review and metric definitions across every file.

Portfolio review

Retrieve completed analyses and support standardized monitoring workflows.

Decision orchestration

Use structured results as inputs to your rules, scorecards, and human review queues.

One request. Structured results.

01

Authenticate

Pass your account-specific key in the X-API-Key request header.

02

Upload

Send a standard bank statement PDF as multipart form data.

03

Analyze

StatementScrub extracts transactions and evaluates cash flow and risk signals.

04

Consume

Receive JSON immediately and retrieve prior analyses by ID when needed.

Example JSON

Data your platform can act on

Map normalized values into an LOS, show exceptions in a reviewer queue, or combine the response with your own policy engine. Field availability reflects the uploaded document and analysis.

application/json
{
  "analysis_id": 1842,
  "status": "complete",
  "result": {
    "bank_name": "Example Bank",
    "statement_period": {
      "from": "2026-01-01",
      "to": "2026-03-31"
    },
    "summary": {
      "avg_monthly_deposits": 86420.00,
      "avg_daily_balance": 9180.00
    },
    "red_flags": {
      "nsf_count": 2,
      "overdraft_count": 1,
      "mca_loans_detected": true
    }
  }
}
Security

Designed for server-to-server use

API-key authentication

Each request is tied to an active StatementScrub account and key.

Encrypted transport

Use HTTPS for document upload and response delivery.

Key hygiene

Keep keys in a secret manager or server environment—never client-side code.

Controlled retention

Uploaded files follow StatementScrub document-retention and deletion policies.

Performance

Fast enough for active application flows

<30s
Typical processing target

Most standard PDFs complete in under 30 seconds. Longer or complex documents may take more time.

Integration patterns

Connect from an LOS, CRM, broker portal, lender portal, document intake service, workflow automation layer, or your own backend.

API access

Request your API key

Create an account, open Settings, and generate or manage your API key. For team volume, platform rollout, or integration planning, book a demo and tell us about your expected statement volume.

Create AccountOpen API SettingsBook Demo

API questions

What does the API return?

Structured JSON containing statement details, cash-flow metrics, monthly summaries, NSF and overdraft counts, MCA indicators, risk signals, and status.

How do I request an API key?

Create an account and use Settings to request or generate API access, or book a demo for team deployment.

How long does processing take?

Most standard statements complete in under 30 seconds; document length and complexity can affect timing.

How should I store the key?

Store it in a server-side secret manager or environment variable and pass it through the X-API-Key header. Never expose it in frontend code.

Bring statement analysis into your platform.

Start with an account or map your integration with our team.

Request API KeyBook Integration Demo