Bank statement papers on a yellow desk

Nigerian statement data / Product preview

MontraParse.

Bank statements. Clean data. One API.

From statement files to structured transactions and reconciled balances. A clearer foundation for your next financial product.

Read the API docs

NO SIGN-UP · FICTIONAL SAMPLE · JSON & CSV

01/

PDF & CSV

Intended input formats

02/

Structured JSON

A consistent data contract

03/

Balance checks

Keep discrepancies visible

04/

One REST API

Proposed /v1 integration

01 / Try it for yourself

Less paperwork. More possibility.

See the shape of clean statement data before you write your first line of code.

Explore the full demo
Statement sandboxDEMO ONLY

sample_gtbank.pdf

September 2026 · NGN

Opening balance₦500,000.00
Sample rows5
FormatPDF example

Preloaded fictional data. No upload, account or API key needed. No real statement is processed.

Your sample output, right here.

Structured transactions. Original amounts. Clear balances.

02 / A thoughtful data pipeline

From a file to your workflow.

01

Extract & normalize

Turn intended PDF and CSV inputs into consistent dates, descriptions, debit and credit directions, and integer monetary amounts.

02

Reconcile & review

Compare opening, closing and running balances. Surface mismatches and warnings without quietly changing financial records.

03

Connect & build

Use a proposed versioned REST contract for lending, accounting and other authorized financial workflows.

03 / Built for your stack

Your language.
One data contract.

JavaScript, TypeScript, Python, PHP or Go — any server-side language with an HTTP client can target the proposed REST API. No proprietary SDK required.

  1. 01/Configure your API origin and server-side key
  2. 02/Submit an authorized PDF or CSV
  3. 03/Poll the job, review results, then import

Examples describe a proposed API, not deployed endpoints. Official SDKs and signed webhooks remain planned.

POST /v1/statements · PROPOSED
curl --request POST "$MONTRAPARSE_API_ORIGIN/v1/statements" \
  --header "Authorization: Bearer $MONTRAPARSE_API_KEY" \
  --header "Idempotency-Key: $REQUEST_ID" \
  --form "file=@authorized-statement.pdf"

REST over HTTPS · JSON responses · No live endpoint yet

04 / Nigerian bank coverage

Different banks. A common format.

The current registry, with honest validation statuses.

Explore bank coverage

Guaranty Trust Bank

PDF / CSV · v0.3.1

In Validation

Access Bank

PDF / CSV · v0.2.4

In Validation

Zenith Bank

PDF · v0.2.0

In Validation

First Bank

PDF / CSV · v0.1.3

Registered / Experimental

United Bank for Africa

PDF · v0.1.2

Registered / Experimental

Kuda

PDF / CSV · v0.3.0

In Validation

OPay

CSV · v0.1.0

Registered / Experimental

Stanbic IBTC

PDF · v0.1.1

Temporarily Unavailable

Sample registry · 27 parser modules in the foundation, not 27 verified banks. Production validation is incomplete; no institution is claimed as production-ready.

05 / Pricing

A plan for what you’re building.

Explore proposed plans. Final pricing will be shared once approved.

Proposed plan / 01

Developer

For exploring an integration

Pricing to be confirmed

Rates and quotas are not yet approved.

  • Statement workflow preview
  • Sample JSON & CSV exports
  • API reference & code examples
Explore the demo

Proposed plan / 02

Business

For growing financial workflows

Pricing to be confirmed

Rates and quotas are not yet approved.

  • Proposed API processing
  • Reconciliation & review
  • Proposed signed webhooks
Discuss your workflow

Proposed plan / 03

Enterprise

For organization-wide integrations

Pricing to be confirmed

Rates and quotas are not yet approved.

  • Custom integration planning
  • Coverage & volume discussions
  • Security & retention requirements
Talk to us

Proposed plans only. No payment, subscription or live API access is activated.

Start with the data

Meet your next statement workflow.

Explore the sample. Read the contract. Build with clarity.