DevelopersSecurityHow we testPricing
Get started
Get started

Use cases / Logistics

Proof of delivery is a squiggle on a phone, until it's disputed.

Nib checks the driver's photo of the signature against the recipient's own references, so a disputed delivery comes with reasons.

What you send

  • The driver's photo of the signed delivery note or screen
  • The recipient's reference signatures
  • Your reference, such as the consignment 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 regular recipients

    Enrol reference signatures for the accounts you deliver to.

    API

  2. Send from the driver app

    Your app sends the photo when the driver closes the delivery.

    API

  3. Or batch at the end of the day

    Drop the day's photos and a manifest in your bucket instead.

    Bucket drop

  4. Answer a dispute

    Pull up the check by consignment number, with its verdict and reasons.

    API

Decisions that matter

  • UNREADABLE

    A blurred photo: ask for a retake. Free.

  • NO SIGNATURE

    Nobody signed. Catch it early. Free.

  • FLAG

    Someone looks before a claim is settled.

What it reads

  • Phone photos

Up to 50 MB and 200 pages.

Try it

Check your first signature today.

Get started Talk to us