Usage Reporting
The IDV Platform reports its usage to the Innovatrics Transaction Counting System (TCS), the service that produces the usage statements behind the commercial model. This page explains what is reported, so that a Company knows exactly which information leaves the platform, and which options a self-hosted deployment has.
Reporting is metering only — it does not enforce quotas or change how verifications run.
What is reported
Two kinds of events are sent:
| Event family | When | Content |
|---|---|---|
| Session operations | During every verification session, finished or abandoned. | One record per biometric or document operation the workflow performed — for example a document read, a liveness evaluation, a face comparison or a 1:N search — grouped under the session's identifier. Each record carries the operation type and technical metadata such as the liveness type. |
| Daily record count | Once a day, for tenants on the Stored data tier. | The number of active (non-anonymized) Customers and Digital Identities in the tenant's database. |
The session operations let the usage statement distinguish, for instance, an identity verification from a document-only check or an age check, and count abandoned sessions separately. The daily record count is the basis of per stored user billing.
What is not reported
- No personal data. Events contain identifiers of the session and of the operation, never names, document data, images or biometric templates.
- No verification results. Whether a session was accepted or rejected is not part of the report.
- No configuration. Trust Factor settings, workflow definitions and thresholds stay in the platform.
The tenant is identified by the signed credential the platform uses towards TCS, not by any field in the event.
Which steps produce records
| Workflow step | Reported operation |
|---|---|
| Session start / final outcome | Session start and end markers (a session without a final outcome counts as abandoned) |
document_capture | Document page read |
nfc_capture | Document chip read |
face_capture, smile_capture, multirange_capture | Liveness record and liveness evaluation (passive, smile or multi-range) |
tf_eval | Customer and document inspection |
dedup_face | 1:N watchlist search |
matching | 1:1 face comparison |
dedup_document, best_duplicate, decision, external_capture, mobile_redirect | No record |
A step produces at most one record of each type, even when a capture is retaken or an internal operation is retried — recaptures are never double-counted.
SaaS deployments
Reporting is always on and needs no configuration. The usage statement is available from your Innovatrics representative.
Self-hosted deployments
A self-hosted platform reports in the same way, authenticated with the licence credential issued to the deployment. Three options exist for constrained environments:
| Mode | Behaviour |
|---|---|
| Full reporting (default) | Session operations and the daily record count are sent as they occur. |
Count-only (db_size_only) | Session operations are not sent; only the daily record count is. The usage statement is then based on stored records alone and cannot break sessions down by type. Requires the Stored tier. |
| Offline export | For sites without outbound connectivity, events are stored locally and exported and imported in batches at a reduced frequency. Late delivery is acceptable — statements are produced monthly. |
The mode is a deployment setting agreed with Innovatrics during installation.
See also
- Deployment Models & Data Tiers
- Data Storage
- Transaction reporting in the IDV Toolkit — the same counting system as used by the Toolkit components