Skip to main content
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

EventCounted?
Visitor opens popup but closes itNo
Visitor starts proof flow but abandons itNo
Proof rejected (invalid proof, wrong network)No
Returning visitor with a valid session cookieNo — the session is validated locally, no verification occurs
Testnet verificationsNo — testnet is free and not billed

​
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 for more.