From a standing report to a one-off question
The reports you run every month should be one click. The question you have never asked before should not require a ticket to engineering. Both live in the same place.
A library, not a blank page
33 report types ship with the platform and cover the questions a payments business actually asks every month: captured and declined volume, failure statistics, daily risk and status by merchant and by terminal, rolling reserve, settlement, monthly statements, chargebacks and disputes, stored cards, recurring series, account balances and web service call volumes. Each one is filtered rather than fixed, so the same report answers this month, this merchant or this terminal without anyone building a variant.
Transaction reporting in detailAsk for the report nobody built
Type the question the way you would say it to a colleague. The assistant turns it into a structured query plan - the metric, the grouping, the filters, the period - and shows you that plan before anything runs. It never writes free-form database queries, because every part of the plan has to resolve against a known reporting schema, which is what keeps a natural language feature from becoming a way to ask the database anything at all. You supply your own model key, so questions and results stay on terms you control.
Working with transactionsDashboards you configure yourself
Charts are configuration, not a development request. Build the views your operation watches, from approval and decline trends to wallet and balance monitoring, and give finance its own dashboard covering settled against unsettled volume by acquirer and currency. Views can be scoped so a group sees its own numbers and nobody else's, and the heavy aggregates are prepared in advance so opening a dashboard does not mean waiting on a query across every transaction you have ever taken.
Failure statisticsExports that survive real volume
Every report exports as a spreadsheet, a CSV, an HTML document or plain text, so whatever your accounting team or your data warehouse expects, it gets it. Large exports are queued and generated in the background rather than held open in a browser that gives up halfway through a million rows, and finished files are kept in an archive you can come back to. Reports can be delivered by email on a schedule, which is usually what people mean when they say they want a dashboard.
Exporting to accountingOperatorsAll merchants
MerchantAcme only
PartnerOwn book
Three audiences, one reporting engine
The reports your operators run, the ones your merchants pull from their own portal, and the ones your partners see for the merchants they introduced all come from the same engine with the same numbers. Scope is applied by permission rather than by building three versions of a report, so a merchant cannot see another merchant and a partner cannot see beyond their own book. It also means your support team and your merchant are looking at the same figure when they get on a call.
The partner control panel
