Integrating · For a brand's operations team and a developer
Getting your data out
Everything in the first table is yours and available from the console without asking us. There is no export fee, no notice period and no ticket to raise. The second table is what you can see on a screen but cannot yet take as a file — listed, not hidden.
Files the console produces today #
| Export | Where | Audited | Masked |
|---|---|---|---|
Print files — codes.csv, the SVG ZIP, the Excel bundle | A batch's page | Yes, after activation | No — they are the codes; see the download rule |
Warranty registrations (warranties.csv) | Rewards → Warranties | Yes | Phone numbers masked |
TDS statement, per financial year (tds.csv) | Rewards → Payouts → Exports | Yes — it decrypts PANs | Phone numbers masked |
Payout statement, per month (statement.csv) | Rewards → Payouts → Exports | Yes | Phone numbers masked |
| Batch-upload template (Excel) | A product's page → Bulk upload | No | — |
| Certificate template, pre-filled with codes | A certificate batch's page | No | — |
On a screen, not yet in a file #
| Data | Today |
|---|---|
| Scan history | On the dashboard. An export needs to be a background job like the print files; it is not built. |
| The credit ledger | On the Wallet page, row by row. |
| Members, claims and wallet balances | On the Rewards pages. |
| Fake reports | On the dashboard, with their status. |
| Batch states | On each batch's page. |
If you need one of these as a file today, ask at connect@avrascan.com and we will produce it.
The download rule for print files #
A partner downloads freely until the batch is activated. After that the file is a list of live codes: platform-admin only, every download audited, purged 30 days after activation.
Last reviewed 18 Sep 2026 · Something wrong? connect@avrascan.com