Skip to content

Main content

Biometric Presentation Record Caller Code Tool

Check an explicit presentation-record code without classifying spoofing or authenticity.

Loading tool…

Description

Check a presentation code against a supplied vocabulary.

Biometric research records separate subject IDs, template dimensions, image geometry, enrollment support and attempt budgets. Local counts and comparisons can reveal inconsistencies without reading biometric templates, detecting a physical trait or authenticating a person’s identity.

Check a presentation code against a supplied vocabulary.

When to use this tool

Use Biometric Presentation Record Caller Code when checking the stated biometric record, count, support, geometry or budget convention.

How to use the tool and how it works

  1. Enter code, permittedCodes, source, version. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read known, sourceKey. Inspect known before interpreting the associated values.

Check a presentation code against a supplied vocabulary. Require nonempty source/version; known is literal code membership, sourceKey serializes source, version and code.1

Input fieldMeaning and unitsAccepted input
codeCodeRequired. Text; maximum UTF-16 length 8192.
permittedCodesPermitted CodesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
sourceSourceRequired. Text; maximum UTF-16 length 8192.
versionVersionRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
knownSupplied knowledge or lexical-recognition flag under the stated convention, without independent authentication.Required. Boolean.
sourceKeySource KeyRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "code": "A",
    "permittedCodes": [
      "A",
      "B"
    ],
    "source": "protocol",
    "version": "v1"
  },
  "output": {
    "known": true,
    "sourceKey": "[\"protocol\",\"v1\",\"A\"]"
  }
}

Limitations and assumptions

  • The vocabulary is caller-defined; no presentation attack, sensor quality or identity authenticity is detected.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use verified acquisition/enrollment records and the complete appropriate format and evaluation process for actual identity, quality, capacity or privacy decisions.

References

  1. Calculation and input contract: biometrics/biometric-presentation-record-caller-code — tool.io

Similar or alternative tools