A payments dashboard from your transactions export.
Export your transactions as CSV or Excel. Daized reads amounts, fees, status, chargebacks and fraud flags, and builds the dashboard around them.
What Daized builds from a fintech file
From the sample file, these were the key metrics it put first.
- Payment Volume
- Payment Success Rate
- Take Rate
- Chargeback Rate
- Processing Fees
- Average Transaction Value
Below them: a trend you can switch between lines and bars, a written “What changed” that names the biggest driver, and “Looking ahead”, which appears only when the forecast passes a test on your own history and shows its score. Every other column worth charting gets a chart of its own, and clicking a bar filters the whole page.
“Processing Fees rose 18.2% from the first half of the period to the second, most of it in Payment Method: EMI.”
How it reads your file
It tells you how it read each column before you rely on the dashboard, and you can correct it.
On the sample file it wrote: “Read as fintech. Each row is one transaction. Country as region and Chargeback as chargeback flag. Is that right?”
- Transaction Datea date, so every metric can be followed over time
- Merchant, Payment Method, Countryways to split the numbers and find where a change came from
- Transaction Amountthe value of each payment, used for volume and average value
- Processing Feeused for fees and for take rate
- Statusread as the payment outcome, used for success rate
- Chargeback, Fraud Flagread as yes or no flags, used for chargeback and fraud rates
Questions
- What does my file need to look like?
- A CSV or Excel file with a header row and one row per transaction, up to 100 MB. Column names do not have to match the ones above: Daized reads the values as well as the names, and tells you how it read each one.
- Do I have to set anything up?
- No. There is no data model to build, no formulas to write and nothing to prompt. You upload the file and the dashboard is built from it.
- Are the numbers calculated, or written by an AI?
- Calculated, in code, from your file. A written explanation only describes numbers the code already produced, and each one is labelled as written or computed.
- How long is my file kept?
- The table from your upload is kept for 30 days after you last open it, and you can delete a dataset yourself at any time. Read exactly what is stored.
- What does it cost?
- It is free to try. See the plans.