Pricing Reference

This page is the reference version of the explanatory text on the pricing page. Live plan allowances and prices are published on the pricing page; this page carries no price or quota figures.

Plans

PRICING

Plan from approved catalog facts.

Compare approved plan allowances, annual commitments, and month-to-month alternatives. Request a walkthrough for qualification and contract-specific terms.

Starter

planning fit: one defined workflow and its operating assumptions

Common starting point

Request a walkthrough for Starter

Growth

planning fit: a broader evaluated traffic and evidence scope

Request a walkthrough for Growth

Scale

planning fit: multiple workflows with larger published allowances

Request a walkthrough for Scale

Professional

planning fit: higher published capacity and retention needs

Request a walkthrough for Professional

Enterprise

planning fit: contract-defined limits, support, and service scope

• Contract-defined AI Assistant credit allowance
• Custom collector requests per month
• Custom ingestion requests per month
• Custom events per month
• Custom-day risk-evidence retention
• Custom domains

Discuss contract scope

AI Assistant credits

About AI Assistant credits

The catalog lists a monthly plan allowance. Additional whole packs are team-provisioned and are not a self-service charge.

Plan card allowance labels

• AI Assistant credits per month
• collector requests per month
• ingestion requests per month
• Score API calls per month
• KYC verifications included per month
• events per month
• domains

Billing

Public catalog amounts are fixed in USD and are informational list prices that may change. Taxes, payment method, renewal, cancellation, refunds, and proration are governed by the Noxtica Terms of Service (Fees, Billing and Payment section) and any applicable Order Form.

Billing period

• Annual
• Monthly

Billed month to month

Estimator

ILLUSTRATIVE ESTIMATE

Build a catalog-based estimate.

This planning aid separates the base commitment, team-provisioned capacity, and catalog-listed module usage. It is not a quote, checkout, or charge.

Base plan

• Starter
• Growth
• Scale
• Professional

Billing period

• Annual

• Monthly

• Expected collector requests per month

• Expected events per month

• Required risk-evidence retention (days)

• Domains

Optional capacity and module assumptions

• Advanced IP reputation requests per month

Public rules for cache hits, retries, failures, bot traffic, and duplicate submissions are not approved; estimates assume each attempt may count.

Calculate illustrative estimate

I need help estimating

Synthetic illustrative bill

Starter · annual base · one AI-credit pack · module usage

• Annual base commitment
• Base monthly equivalent
• Illustrative initial charge

Assumptions: every attempt may count; whole AI-credit packs round up; the plan’s share of the listed module allowance applies before the per-request rate.

Usage definitions and boundaries

• Collector request One collector /client/token issuance counted on the monthly collector-request axis.
• Event One event submission counted on the monthly event axis.
• Ingestion request
• Score API call
• Cache hits, retries, failures, bots, duplicates Public rules are not approved; estimates assume each attempt may count.
• Capacity block A whole team-provisioned pack. Partial needs round up; unused-capacity treatment is confirmed before activation.
• Module allowance and over-limit behavior

Definitions that state catalog figures are published on the pricing page.

Comparison

CATALOG COMPARISON

Allowances and commercial boundaries.

Catalog-derived comparison of Noxtica plans by included units, Score API calls, KYC verifications, free-allowance share, risk-evidence retention, domains, support scope, and service-level boundary.

Dimension

• Events per month
• Collector requests per month
• Ingestion requests per month
• Score API calls per month
• AI Assistant credits per month
• Included KYC verifications per month
• Share of listed module and KYC free allowances
• Domains
• Retention by data class

Enterprise column: Custom for events, collector requests, ingestion requests, AI Assistant credits, and domains; Contract-defined for retention by data class.

Retention unit: days (risk evidence).

Add-ons

TEAM-PROVISIONED CAPACITY

One approved whole-block add-on.

The approved projection currently lists one whole-block AI-credit add-on. Request it through the team; it is not a recurring usage charge or self-service purchase.

Additional AI credits

A stated-price whole pack, provisioned by the team. Unused-capacity treatment and contract timing are confirmed before activation.

Ask about this add-on →

A catalog price does not activate or charge the add-on. The team confirms eligibility, timing, and contract treatment first.

One approved whole-block add-on. — ask about team-provisioned capacity

Ask about capacity →

KYC rate card

KYC RATE CARD

KYC verification pricing

One rate card for every plan. Each KYC module has its own per-use price in USD, and the Full KYC bundle combines the four core checks into one price per verification.

Full KYC bundle

A verification that runs the full bundle is billed once, as the bundle, not again per module.

KYC module prices

• Module

• Price

• Free each month (Enterprise)

• ID Verification

• NFC Reading

• Proof of Address

• Document AI

• Passive Liveness

• Active Liveness

• AML Screening

• Ongoing AML Monitoring

• Device & IP Analysis

• Email Verification

• Company AML Screening

• Person AML (per UBO/officer)

• KYB Documents

Each plan includes its free-allowance share of every listed monthly module and KYC allowance, rounded down to a whole unit; Enterprise includes the full listed amount.

Prices are list rates in USD. The team activates modules after an eligibility review; there is no self-service checkout or automatic charge on this page.

Ask about KYC verification →

Metered modules

CATALOG-LISTED MODULES

Catalog-listed metered modules

The estimate can model Advanced IP reputation after its monthly allowance. Every catalog-listed module below is illustrative; team review and activation are still required before any of them can be enabled or charged.

Each plan includes its free-allowance share of every listed monthly module and KYC allowance, rounded down to a whole unit; Enterprise includes the full listed amount.

• Age Verify
• Bank Ownership Verify
• Calibrated Score
• Number Verify (CAMARA)
• SIM Swap Check (CAMARA)
• eID Verify
• Advanced IP reputation
• KPS Verify KPS/MERNIS is the Turkish national identity registry; this axis is only meaningful for Turkey-scoped identity checks.
• Verified Attested KYA Illustrative list rate applies to every verified attestation; there is no included monthly allowance, subject to eligibility and team activation.
• KYC Reverify
• Reputation Verify
• Speech STT (Platform)
• Speech STT (BYOK)
• Speech TTS (Platform)
• Speech TTS (BYOK)

Illustrative list rate applies to AI-credit-ledger usage, subject to eligibility and team activation.

Speech usage is metered through the AI-credit ledger, not the PAYG accrual path; this list rate is a published anchor, not a separate per-unit charge.

Coming soon

• Attestation Verify

Coming soon

List-rate output is illustrative. There is no automatic over-limit charge, checkout, or activation on this page.

Ask about module eligibility →

Why teams buy

BEFORE A COMMERCIAL DECISION

Separate known catalog facts from contract scope.

Use the projection for planning, then confirm unresolved counting rules, eligibility, support, and terms during a guided walkthrough.

Known base commitment

Annual totals and month-to-month alternatives are derived from integer-cent catalog inputs, not repeated in page copy.

Distinct charging layers

Base plan, team-provisioned capacity, and metered module usage remain separate in the estimate.

Unknowns stay visible

When a requirement exceeds an approved allowance without a public rate, the estimator requests review instead of inventing a precise bill.

FAQ

COMMERCIAL QUESTIONS

What this catalog does—and does not—settle.

The public projection supports planning. A walkthrough confirms workflow fit and contract-specific terms.

What does annual billing show?

The answer quotes catalog figures; see the pricing page.

Does the estimator produce a quote?

No. It is a read-only illustrative estimate using the versioned public projection. It does not persist inputs, run checkout, activate a module, or charge anything.

What happens above a plan allowance?

Score API calls above the included amount are billed as metered usage at the listed Calibrated score rate; ingestion requests are counted, not blocked. For other allowances there is no general automatic-overage promise: the estimator identifies requirements without an approved public rate and directs them to team review.

Are support response times or service levels included?

Human support is English-language. Response times, package scope, and any service-level commitment are confirmed during qualification or in the applicable contract.

How are retries, failures, bots, and duplicate submissions counted?

Those public counting rules are not yet approved. The estimator states the conservative assumption that each attempt may count and does not present the result as an exact invoice.

How is KYC verification priced?

Through the KYC rate card on this page: the Full KYC bundle has one price per verification with a monthly free allowance, and every other module has its own per-use price. A verification that runs the full bundle is billed once, as the bundle.

Need a workflow-specific estimate?

Request a walkthrough →

Every plan includes

COMMERCIAL BOUNDARIES

• Plan and allowance values come from the versioned public projection
• English-language human contact; response time is confirmed during qualification
• No self-service checkout, automatic module activation, or automatic over-limit charge
• Taxes, renewal, cancellation, refunds, proration, and service levels are governed by the Noxtica Terms of Service (Fees, Billing and Payment section) and any applicable Order Form; list prices are informational and may change

Customer value

SCOPE BEFORE SPEND

Buy capacity for a risk workflow you can define.

Published plans provide defined capacity. The commercial fit depends on the interactions you will protect, the traffic and history you will use, which eligible modules the evaluation requires, and the policy and review work your team will own.

Build the purchase case from scope, usage, and evidence

USE CASE

Scope the interaction and its owner.

Start with one budgeted problem—account takeover, signup abuse, checkout risk, unwanted automation, or a sensitive account change. Name the team that owns the final policy and the outcome source it trusts.

USAGE

Size what the workflow will actually consume.

Bring protected domains, API requests, event submissions, expected peaks, retention needs, and operator access. These inputs connect published capacity to your operating model more reliably than company size.

EVALUATION

Define the evidence and acceptance criteria.

Confirm module, browser, consent, tenant, and policy eligibility, then compare risk, confidence, reasons, unknown states, and proposed actions against labeled traffic before enforcement.

OPERATING COST

Count the work and friction the policy creates.

Track challenges, completion and abandonment, human-review volume, reason usefulness, support contacts, appeals, and rollback conditions alongside the unwanted activity you find.

Compare spend by job, not by category label

Identity, perimeter control, and analytics budgets may already solve part of the problem. Compare overlap at the exact route and decision you plan to evaluate before adding scope.

Identity-only lookup

Fund recognition or authentication there when that is the required outcome. Add interaction risk only when policy must evaluate the current action using more than a successful match.

Perimeter and bot controls

Keep the enforcement and traffic coverage that already work. Price Noxtica against the specific evidence or route-level decision gap it is expected to fill.

Analytics and replay tooling

Fund investigation and experience analysis there. Treat a live risk read, customer-owned policy, and explainable outcome record as separate requirements when your workflow needs them.

COMMERCIAL FIT

THE PURCHASE

Capacity, scope, and an operating fit.

Plans vary by published capacity and service dimensions. Additional capacity and separately eligible modules are distinct choices; use the comparison above for the current catalogue.

CONTACT FIRST

Every plan starts with a scope conversation.

There is no self-serve checkout. Bring your protected interaction, usage estimate, required evidence, and evaluation criteria so the team can confirm plan and module fit before provisioning.

A POOR FIT

A purchase with no owned policy or measurable outcome.

If nobody owns the decision, labels the evaluation, or measures customer friction and review cost, more signal volume alone will not establish value.

The closing next-steps block of the pricing page is the same as the one in Platform Overview.