Pay-per-verification, privacy-first. Volume discounts and optional fallback for borderline cases.
No user accounts. No image storage. Token-based proof.
€0.080 / verification
Monthly volume: 0 - 100,000
What’s included
Tier profile: standard throughput, email support.
€0.045 / verification
Monthly volume: 100,001 - 1,000,000
What’s included
Tier profile: higher throughput allocation, priority email support.
€0.025 / verification
Monthly volume: 1,000,001 - 5,000,000
What’s included
Tier profile: burst handling, higher limits, onboarding support.
€0.015 / verification
Monthly volume: 5,000,001 - 35,000,000
What’s included
Tier profile: priority queues, escalation path, success contact.
from €0.010 / verification
Monthly volume: 35,000,001+
Minimum monthly commit may apply.
What’s included
Tier profile: dedicated capacity options, custom SLA and governance.
Add-ons are listed below from verification depth to enterprise governance.
Routes only BORDERLINE or INCONCLUSIVE outcomes to a document step, leaving the primary flow unchanged.
Defines response targets, escalation channels, and service windows for production operations.
Detects abnormal retry bursts and suspicious usage patterns before cost or risk drifts.
Aggregates monthly outcome, retry, and conversion data to tune policy decisions.
Applies approved product copy, legal messaging, and visual identity to the verification flow.
Centralizes governance across multiple brands, domains, and onboarding teams.
Reserves infrastructure lanes for high-throughput environments and strict control requirements.
Insert your monthly verification volume. The estimator applies tier unit rates and optional fallback rates.
Use the last complete month or a conservative launch forecast.
Use a sales setup when your launch has platform-level constraints or commercial governance needs.
A verification is billable when the flow returns a final outcome and issues a token-proof response. Sessions abandoned before a final outcome are not billed as completed verifications.
Standard retries are covered by policy thresholds. Repeated abnormal retries can be constrained by abuse controls and may require policy tuning.
Default behavior is deny. If Document Fallback is enabled, only those outcomes are routed to the additional document step.
Yes. Fallback routing can be configured by outcome class and deployment policy so it does not affect your full traffic.
No image storage in the core flow. The system is designed to return a short-lived proof token with minimized data handling.
Billing is based on monthly usage by tier and enabled add-ons. Tier E agreements may include minimum monthly commit and sales-led invoicing terms.
Estimates are indicative. Signed commercial terms prevail.