Use cases / Back offices

Every mandate checked by eye, against a signature card in a drawer.

Nib reads the scanned form, finds the signature and compares it with the customer's own references, with reasons you can file.

What you send

  • The scanned mandate, consent form or contract
  • The customer's reference signatures
  • Your reference, such as a mandate or contract number

What you get back

  • A verdict: one of six, from AUTO APPROVE to NO SIGNATURE
  • A probability from 0 to 1, with a band
  • Plain-language reasons you can show an auditor
  • The policy and version that produced it

An example of how a day's checks might split:

Sample
  • AUTO APPROVE
  • APPROVE
  • FLAG
  • FAILED

How it fits your process

  1. Enrol what you hold

    Enrol reference signatures from the cards and forms you already keep.

    API

  2. Drop the day's scans

    Put the scans and a manifest in your bucket. No code on your side.

    Bucket drop

  3. Collect the results

    Results land back in your bucket, one line per document.

    Bucket drop

  4. Find any check again

    Look a check up by your own reference when someone asks.

    API

Decisions that matter

  • APPROVE

    File it, with the reasons on record for an audit.

  • FLAG

    A person checks it before the change goes through.

  • UNREADABLE

    Ask for a better scan. Free.

What it reads

  • Scans
  • Forms
  • PDFs

Up to 50 MB and 200 pages.

Try it

Check your first signature today.