Two ingest paths, two output shapes, one consistent analysis
TransactIQ meets lenders where they already work. Branch agents upload through a simple web interface. Loan origination systems talk to a REST API. Either way, every run produces the same structured Excel workbook and the same JSON payload — consistent, traceable, and configurable per customer.
Ingest and output surfaces
Two ways statements come in, two ways results go out — both driven by the same underlying analysis so the Excel read and the JSON read never drift.
Web upload
An agent-friendly web interface accepts one or several bank statement PDFs per applicant together with basic customer metadata. The agent uploads, the report returns when processing completes, and the full workbook downloads in one click. Designed for relationship managers and branch agents who prefer not to wire an API for every branch.
REST API posture
The API accepts an upload, returns a reference identifier, and exposes status and download endpoints so TransactIQ can be wired into a loan origination system, CRM, or decisioning engine. The precise endpoint paths, authentication shape, and response schemas are part of the integration pack shared under NDA with evaluating lenders — they are not published on the public site.
Structured outputs, in sync
Every run produces both an Excel workbook for humans and a JSON representation for systems. Both come out of the same underlying analysis, so the two views are always consistent. A lender whose underwriters read Excel and whose decisioning engine reads JSON does not have to reconcile two different pipelines.
Configuration and delivery
Different lenders need different shapes and different storage postures. TransactIQ supports both without forking the pipeline.
Per-customer lean or full toggle
Different lenders need different shapes. A credit-underwriting desk wants a lean report with obligation tracking, income view, FOIR, and fraud flags. A forensic audit team wants the full extended report. TransactIQ supports section-level toggles so each customer gets the shape they actually use, without running two different pipelines behind the scenes.
Flexible storage
Output reports can be kept locally within the deployment or synced automatically to AWS S3, Google Cloud Storage, or Azure Blob, depending on the lender's data-handling policy and existing document-management posture. The choice does not affect the analysis — only where the finished file lands.
Charts and forecast surfaces
Every report carries the same chart set: monthly income and expense trends, balance trajectory across the statement window, cash-flow-by-month split into income and expense components, and a 15-day forward projection of balance and cash flow. These render inline in the workbook; the same underlying values are available in the JSON output for any lender that wants to drive internal dashboards from them.
A note on the API contract
The concrete API contract — endpoint paths, authentication, webhook shapes, versioning, idempotency posture, and the full JSON response schema — is shared as an integration pack with lenders who have signed an evaluation NDA. The pack covers the contract in the detail an integration engineer needs to wire the API into a production loan origination system.
What the public surface documents is the posture: upload-in, reference-out, status and download paths, structured outputs in two shapes, per-customer section toggles, and a choice of storage backends. The implementation details follow under NDA so the contract stays stable for customers without being reverse-engineered from the marketing site.
Request the integration pack
The full integration pack — API contract, sample payloads, webhook specification, and storage configuration — is available under NDA to lenders in active evaluation.
Request the integration pack