Find a statement and its evidence in the console
An operator sees in the console what was accrued for each month, creates a statement from it and downloads the evidence behind a line or behind the whole statement. This guide walks through those screens. How to read the lines of a statement and to check the ledger, the seals and the approvals offline is in Read a statement and check its evidence.
Reference pages: Evidence and offline checking and Downloads, where tanba-verify is.
Before you start
- Billing is for an administrator of the operator organisation.
- Everything you see is an estimate: the screen says "Estimate only, not a payment invoice" and "Amounts exclude VAT".
Open a period
Open Billing. The list shows one row per month with the amount, the VAT and the state, Open or Closed. A closed period can no longer change. Choose a month to open its page.
The page shows the total and then the accrual lines. Each line has a type, a reference, a quantity, an amount and the VAT.
| Type | What it is |
|---|---|
| Impressions (per 1000) | Plays of one structure and approval, with the hours they cover in the reference |
| Approval, single / prepaid / priority | The fee for an approval |
| Data and delivery proof | A data fee |
| Laboratory test | A laboratory fee |
If plays were reported but are not part of the bill, a note above the lines says how many and through which channel: operator CMS rows, device certificate, device signature, signed operator CMS or player report. Plays you imported from your own CMS are in that note, and they are never billed.
Create a statement
Choose Create a statement (PDF) in the Statements card of the period. The row that appears has its number, date, amount and state. The state is Estimate, Issued or Void; a statement you create is an Estimate. Download PDF saves the statement. It is made in the language the console is set to when you create it.
Download the evidence
There are two downloads, and both are a zip file with the signed telemetry batches behind the figures:
- On an impressions line, the Evidence button gives the pack of that line.
- On a statement row, Evidence of the period gives the pack of the whole statement.
A pack holds a signed manifest (manifest.json and manifest.p7s), the batches exactly as the devices sent them, the signing keys, the approvals, the daily seals with their proofs, and a README.txt in Kazakh, Russian and English. Each download is recorded in the audit log.
Check the pack
You need the pack and root.pem, the platform root certificate. Do not unpack the zip:
tanba-verify evidence pack.zip --ca root.pemOK means that the manifest signature, the signature and hash of every batch, the Merkle paths to the daily seals and the hourly recount of the plays agree. Any other answer is a code and the batch where the fault was found, and the exit code tells a script which case it is.
| Exit | Code | Meaning |
|---|---|---|
| 0 | OK | Everything agrees |
| 2 | BAD_SIGNATURE | A signature of the manifest, a batch or a seal does not verify |
| 3 | HASH_MISMATCH | A file is not the one the manifest lists |
| 4 | ROOT_MISMATCH | The batches do not lead to the root of the manifest or of a seal, for example because one is missing |
| 5 | UNKNOWN_CREDENTIAL | A batch is signed with a key the pack does not hold, or a certificate does not chain to the root |
| 6 | PENDING_LEDGER | A seal is not yet in a ledger day; check again later |
| 7 | RECOUNT_MISMATCH | The recount of the plays differs from the figures |
| 8 | BAD_LEDGER_PROOF | The proof from a seal to the ledger does not verify |
| 9 | PARTIAL | Some batches could not be recounted in full; the contributions of those batches are taken as declared |
| 10 | UNKNOWN_FORMAT | The pack is in a newer format; use the current tanba-verify |
| 11 | BAD_MANIFEST | The file is not a pack or its manifest is damaged |
| 64 | Wrong command or no root given |
If you disagree with a figure
Next to each line the console offers Dispute, and Dispute the period once a statement exists. Dispute opens a dispute on that line or on the whole period.
What the evidence does not show
A pack proves what the platform received and that it was not changed afterwards. A play that was never reported is not in it.