Razorpay export to dashboard
Your Razorpay payments, in rupees and in order.
Export payments from the Razorpay Dashboard and drop the CSV here. Two things make that file awkward: amount is in paise, and created_at is a Unix epoch integer rather than a date. Both are handled on load, so you get a rupee revenue trend, a method split across UPI, cards and netbanking, and fee plus GST separated from what settles.
Prefer the full explorer? Open the app, or start from the generic dashboard builder.
Paise and epochs, the two Razorpay conversions
Razorpay follows the same minor-unit convention as Stripe, so a 499 rupee subscription is the integer 49900 in the amount column. Sum it in a spreadsheet and your monthly revenue is suddenly in crores. The fee and tax columns are in paise too, which matters because the GST line is small enough that a hundredfold error looks almost plausible.
The timestamps are the second conversion. created_at is Unix epoch seconds, a ten-digit integer, and Excel will read it as a very large number rather than a date. Nobody has ever eyeballed 1775051216 and thought April. On top of that, Razorpay's dashboard shows IST while the API export is UTC, so the two disagree by five and a half hours, which is enough to move a late-evening payment onto the previous day. This page converts both and lets you pick the offset.
How to export from Razorpay
- Open the Razorpay Dashboard Sign in at dashboard.razorpay.com and choose Transactions, then Payments in the left menu. Make sure the Live and Test toggle at the top is on Live, or you will export your own test data.
- Filter the date range and status Use the filter panel to set the period. Leave status unfiltered on the first pass: failed and refunded payments are exactly what you want to see in the dashboard.
- Click Download and choose CSV Razorpay also offers Excel. Take the CSV, since the Excel version pre-formats some columns and can lose the leading plus on contact numbers.
- Collect the file from Reports Larger exports are queued and appear under Reports, then Downloads, with an email when they are ready. The link expires, so grab it the same day.
- Drop it here Paise become rupees, the epoch becomes a date, and method becomes the first group-by chip you see.
If you pull the same data from the Payments API rather than the dashboard, the field names are identical, so a flattened JSON response converts cleanly and lands on the same panels.
Try with sample Razorpay data (the same columns, 104 rows, no upload needed).
What the dashboard shows
Every panel below is built from a column that is actually in the export, named the way Razorpay names it.
- Captured revenue over time. created_at decoded to a date, amount converted to rupees, and failed payments excluded from the revenue line but kept in the funnel.
- Payment method split. method as a donut. For most Indian merchants UPI dominates by count and cards by value, and seeing both at once is the point.
- Success and failure rate. status as a share, with failed payments ranked by method so you can see whether one bank or wallet is dragging.
- Fee and GST against volume. fee plus tax as a percentage of captured amount, both converted from paise.
- Bank and network detail. bank for netbanking rows and card_network for card rows, which are populated only for their own method.
- International share. The international flag as a filter, since those payments carry a different fee and settle differently.
id,entity,created_at,amount,amount_refunded,currency,status,method,card_network,bank,wallet,vpa,international,fee,tax,email,contact,order_id,descriptionReading a Razorpay export without getting burned
- Everything monetary is paise. amount, amount_refunded, fee and tax. Divide all four by 100. The tax column is GST on the fee, not on the sale, which surprises people.
- created_at is epoch seconds. Not milliseconds, which trips up anyone used to JavaScript timestamps. Multiply by 1000 before feeding it to a date library, or let this page do it.
- IST against UTC. The dashboard displays IST, the export is UTC, and the difference is five and a half hours. Any daily total near midnight will disagree with the dashboard until you shift it.
- Method-specific columns are mostly empty. vpa is only filled for UPI, bank only for netbanking, card_network only for cards. Empty is correct here, not missing data, and a naive completeness check will flag all three.
- contact keeps its plus. Phone numbers arrive as +91 followed by ten digits. Excel strips the plus and may reformat the rest, so keep them as text.
- Refunds sit on the payment. amount_refunded on the original row, in paise, exactly like Stripe. There is no separate negative row, so net revenue is a subtraction.
Once paise and epochs are out of the way, this is one of the more pleasant payment exports to work with, because the method breakdown is genuinely informative in a market where UPI, cards and netbanking behave so differently.
Frequently asked questions
Why is my Razorpay revenue a hundred times too high?
The amount column is in paise, the hundredth part of a rupee, which is Razorpay's way of avoiding decimal rounding in money arithmetic. A 499 rupee payment is stored as 49900. Divide by 100 to get rupees, and remember to do the same for fee, tax and amount_refunded, which are all in paise as well. This page applies the conversion on load.
How do I convert the created_at timestamp?
It is Unix epoch time in seconds, so multiply by 1000 for anything expecting milliseconds, or in a spreadsheet divide by 86400 and add the 1970 date serial. The dashboard here decodes it automatically and offers an IST view, because Razorpay's own web interface shows IST while the export is UTC, and the five and a half hour gap moves evening payments to the previous day.
What does the tax column represent?
GST on Razorpay's processing fee, not tax on the sale itself. It is 18 percent of the fee, in paise. Your own GST liability on the underlying goods or services is not in this file at all, which catches people who assume the export is a complete tax record. Treat fee plus tax as your cost of collection.
Why are the vpa, bank and wallet columns mostly empty?
Because each one only applies to a single payment method. vpa carries the UPI handle, bank the netbanking institution code, wallet the wallet provider, and card_network the card scheme. A UPI payment legitimately has nothing in three of those four. A data-quality tool that flags them as incomplete is measuring the wrong thing; group by method first and the pattern makes sense.
Can I see UPI against cards by value rather than count?
Yes, and you should look at both. Click the method chip to switch the breakdown, then switch the metric between count and sum of amount. In most Indian merchant accounts UPI wins on transaction count by a wide margin while cards carry a higher average value, so the two views tell quite different stories about the same quarter.
Is the customer contact data safe?
It never leaves your browser. A Razorpay export carries email addresses and mobile numbers, which are personal data under the DPDP Act, so the only responsible design is one where the file is read locally. Parsing happens in the tab, charts are drawn from memory, and closing the tab ends it. There is no server component to this page.
Related tools
Open a Razorpay dashboard right now
104 payments in paise with epoch timestamps, a realistic UPI-heavy method mix, failures and refunds included. Converted the moment it loads.
Open the sample Razorpay dashboard