> ## Documentation Index
> Fetch the complete documentation index at: https://docs.veriox.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How Verifications Are Counted

> Exactly what increments your verification count.

Understanding what counts as a billable verification helps you predict costs and avoid surprises.

## What counts

A verification is counted when **all of the following are true**:

1. A visitor completes the Concordium proof flow in the popup
2. The proof is cryptographically valid and accepted by the verifier
3. A signed session cookie is issued to the visitor

## What does NOT count

| Event                                         | Counted?                                                      |
| --------------------------------------------- | ------------------------------------------------------------- |
| Visitor opens popup but closes it             | No                                                            |
| Visitor starts proof flow but abandons it     | No                                                            |
| Proof rejected (invalid or malformed proof)   | No                                                            |
| Returning visitor with a valid session cookie | No — the session is validated locally, no verification occurs |

## Session reuse

When a verified visitor returns within their session TTL, their cookie is validated locally by the worker. This does not trigger a new verification and does not count toward your usage. A single verification can cover many return visits.

## Counting across workers

Each worker (domain) counts separately. If you have two workers, a visitor who verifies on both sites is counted twice — once per worker.

## Billing cycle

Usage is tallied at the end of each calendar month and charged to your payment method on file. See [billing and invoices](/dashboard-billing/billing-invoices) for more.