The bank statement parsing API

Documents that come back 200, at $0.49 each. A 422 for a PDF that is not a statement, a 500 on our side, a 402 or a 401 are all free, and none of them count against your monthly ceiling either. Every response says which it was in the X-Billable-Documents header, so you can reconcile against your own count rather than trusting ours. A multi-account PDF is one document. Six months of statements in one PDF is one document. We charge per file you send, and usage is invoiced monthly.

The PDF is parsed in memory and never written to disk. No transactions are stored and no account is created for the person whose statement it is. We keep a usage log — timestamp, size, duration, issuer, row count — because invoices are settled from it. If you send an Idempotency-Key the response body is held for 24 hours so the replay can be honoured, then deleted automatically. That body is the only place we hold anybody's transactions at rest, which is why it expires on a timer rather than at our discretion.

Open Banking needs the account holder present, consenting, and banking with a covered institution. Mortgage files, SME lending, tenant screening, immigration and legal disclosure all still run on PDFs handed over by the applicant, often for accounts no aggregator covers. This is for those. Plenty of our customers use both.

There is no supported list, because nothing here is configured per bank and there is no template to maintain. We read the statement as it is printed, so an issuer we have never seen works the same way as one we have. UK, US and European statements are all in regular use, and there is no queue to join before you can send us one.

Every response carries a verification object holding our own check of the extraction against the document. Where a statement prints opening and closing balances, the transactions have to account for the movement between them exactly. When that fails we tell you rather than looking confident, because a misread you cannot see is the failure that actually costs you money.

Not today. We read the text layer a bank's own PDF generator produces, which is why the figures are exact rather than best-effort OCR. A scan with no text layer comes back as 422 and is not charged.

Yes. A test key hits the same endpoint and returns a fixture document instead of parsing your file, so it is free, unlimited and safe to leave in CI. A header makes it return a multi-account statement, an unreconciled one, or any error code you need to handle. For how well we read your own statements, use the 25 free documents: neither needs a payment method.