New features and improvements to StatementIQ. Building something with us? Follow along here.
Each transaction in the report JSON and XML now includes fiskil_category — the CDR feed's enrichment label — alongside StatementIQ's own category, so you can reconcile against the bank's view or drive your own rules from it.
Requests created with an ongoing consent can now be refreshed from the API. Once the customer has shared their report, POST /v1/requests/{id}/refresh re-pulls their live bank feed and re-runs the analysis — no new consent journey, no second share step.
The “Monthly avg” figure on each stream was overstated. It divided a stream's total by the time between its first and last transaction, which is one payment period short — so the total was spread over fewer months than it actually covered.
If your client started their journey inside your application, they can now be returned to it as soon as they've shared their report.
Your clients' consent journey now carries your brand colour and button label colour, alongside your logo — on every screen, not just the first.
Decide whether a client's bank connection ends after the assessment or stays available for repeat pulls — set it under Settings → Consent retention, or per request.
Report delivery now lets you pick which file formats you receive and whether they come zipped or as separate attachments.
Choose how each finished report is split into documents — a combined summary, one per bank, one per account, or any combination.
When an assessment needs the complete picture, a request can now ask your client to connect every bank they use — not just one.
The request list now fits the screen at every width, and you can select requests to act on several at once.
The request list now presents each status as a clear next step, with meaningful icons and four distinct progress segments instead of an abstract continuous bar.
Buttons now show a spinner and clear in-progress wording as soon as an action starts, so creating, saving, sending, sharing, switching or downloading never feels like an empty click.
Client connection links now show a purpose-built preview when shared by message or email. The preview identifies the requesting firm and explains the secure open banking step without exposing the client's name or financial details.
Requests now show four clear gates from invitation to delivery, so bank access and customer sharing are never confused. The request list stays compact, while each request page shows the full progression.
Sandbox consent links are now explicitly restricted to Fiskil's test bank, even after your company is approved to connect live institutions. Test and production requests remain isolated from creation through consent and reporting.
Reports now go to your client first. When their report is ready, they review it on their secure link and share it with you in one tap — then it lands in your portal, API and webhook as before. This reflects how the Consumer Data Right works: the report is derived from their data, so sharing it is their call. It also doubles as a built-in accuracy check.
We no longer store your API keys — only a one-way fingerprint, the same model Stripe uses. A key is shown exactly once when generated, so copy it somewhere safe; if it's ever lost, rotate to get a new one instantly.
Settings → Billing & usage now shows how many reports you've generated this month and in previous months, split by production and sandbox — so an invoice never surprises you. Your plan and payment details live alongside it.
Full guides for building on StatementIQ are now live, alongside an interactive API reference you can call straight from the browser.
Every company now has two API keys, so you can build and test safely before touching real customer data — the same model as Stripe's test and live keys.
Invite your colleagues and give each the right level of access — Admin, Developer, Billing or User — with permissions enforced across the portal and API.
New companies start in a safe sandbox with mock data, then apply for production access through a short due-diligence checklist. Email and SMS delivery of consent links turns on once approved.
If a bank's consent notification is ever delayed, a background reconciler now completes the report automatically — so a request never gets stuck waiting.