Dark
Request a walkthrough
On this page
Developer overview

Integration Flow

The developer overview is the short evaluator path and current support matrix. This guide expands the ownership checkpoints without creating a second set of snippets.

Key points

  1. Your policy decidesYour application combines the lookup with context it already owns. Noxtica does not autonomously make the final customer decision.
  2. An absent score is not low riskA completed browser result can expose less than the authenticated server record. Do not infer low risk from an absent browser score.
  3. Keep the journey usableJavaScript disabled, blocked collection, reduced capability, tenant policy, and consent state can change what evidence you get. The customer journey must remain usable.
  4. Measure before you enforceObserve proposed actions, label outcomes, review false-positive cost, and then promote a bounded policy with an owner and a rollback path.
  1. 1. Customer client
  2. 2. Noxtica processing
  3. 3. Customer server
  4. 4. Customer policy
  5. 5. Investigation and measurement
  6. Evaluation checkpoints
How this page is organisedBar length shows each section’s share of the text. Select a section to jump to it.

  1. You own

    Customer client

    Load the browser collector. Pass just the returned identifier to your backend.

  2. Noxtica

    Noxtica processing

    Processes the evidence the browser and tenant settings admit.

  3. You own

    Customer server

    Keep the credential secret. Read the record with a deadline.

  4. You own

    Customer policy

    Continue, observe, verify, review or deny. Noxtica does not decide.

  5. You own

    Investigation and measurement

    Start in observation mode, label outcomes, then promote a bounded policy.

A Noxtica evaluation from collection to measurement, and who owns each step

1. Customer client

Load the verified public browser collector for the provisioned origin, using the snippet from Backoffice → Integrations & API → Script & Consent and the install walkthrough. The client reports either a collection result or an unavailable state. When a result contains a device identifier, pass only that identifier to your backend with the customer action it will inform.

JavaScript disabled, blocked collection, reduced capability, tenant policy, and consent state can change what evidence is available. The customer journey must remain usable.

2. Noxtica processing

Noxtica processes evidence admitted by the evaluated browser and tenant configuration. A completed browser result can expose less than the authenticated server record. Do not infer low risk from an absent browser score.

3. Customer server

Keep the credential secret and perform the authenticated v1 device lookup. Preserve received, missing, invalid, rate-limited, and unavailable states. Apply a deadline rather than waiting indefinitely on a customer-facing operation.

4. Customer policy

Your application combines the lookup with context it already owns. It chooses whether to continue, observe, request additional verification, review, or deny. Noxtica does not autonomously make that final customer decision.

5. Investigation and measurement

Confirm collection and lookup behavior, calculate proposed actions in observation mode, label outcomes from your own systems, review false-positive cost, and only then promote a bounded policy. Keep an owner and rollback path.

  • Your page

    Browser collector

  • Noxtica

    Processing

  • Your server

    Authenticated lookup

  • Your policy

    Decision and measurement

  1. Client

    The client reports a collection result or an unavailable state. Pass just the device identifier to your backend with the customer action it will inform.

  2. Processing

    Noxtica processes the evidence the browser and tenant configuration admit. Do not infer low risk from an absent browser score.

  3. Server

    Keep the credential secret and perform the authenticated lookup. Preserve received, missing, invalid, rate-limited, and unavailable states, and apply a deadline.

  4. Policy

    Combine the lookup with context you own, then continue, observe, request additional verification, review, or deny.

  5. Measure

    Calculate proposed actions in observation mode, label outcomes from your own systems, and review false-positive cost before promoting a bounded policy.

One request across the browser, Noxtica, your server and your policy

Evaluation checkpoints

  1. Provision the exact origin and public Site Key.
  2. Observe collection and unavailable behavior.
  3. Pass the returned identifier to the customer backend.
  4. Perform an authenticated read with a server-held credential.
  5. Exercise every result state in the maintained fixture.
  6. Evaluate policy in observation mode before enforcement.

Continue with Install & Browser Runtime or Backend Integration.