A workflow engine for in-person ceremonies.

Witness is not a single product. It is a workflow engine that executes configurable ceremonies — the password-recovery flow, the new-account flow, the high-value-transaction flow — each composed of steps you can mix, match, and reorder. The ceremony is the workflow.

What we operate is the part you do not want to: the trusted-location network, the document transit, the QR-bound liveness and biometrics check, the scan-back ingestion, the bundle of artifacts your relying-party system reads. You declare what a ceremony looks like for your customers; Witness runs it.

The canonical ceremony, end to end

This is the same flow the trial on this site runs. In a B2B2C deployment, the relying party integrates with Witness; their flow walks the end user through the configured ceremony, and they receive the signed evidence bundle at the end. The steps in the middle are identical.

1. 1
   The end user is asked to verify in person.A high-stakes flow on the relying party's site (forgot password, new account, large transfer) routes the user to Witness. A nearby trusted location is picked.
2. 2
   A document is generated and emailed to the location.The document carries everything the ceremony needs: subject identity, instructions, a payment instrument, and a QR pointing back at the running ceremony.
3. 3
   The user walks into the trusted location.They pick up the printed document at the counter. No app to install, no new account.
4. 4
   The user scans the QR with their phone.The scan is recorded as a ceremony event. The phone opens the next step on the same Witness domain the QR previewed.
5. 5
   A liveness + biometric check runs on the phone.A colored-flash challenge proves a real human is in front of the camera, defeating deepfake replay. A face template extracts on-device — the image stays on the phone; the template rides with the ceremony bundle.
6. 6
   The notary signs and seals the document.The trusted-location clerk witnesses the user signing, then signs and seals as notary. The seal is the trusted-third-party fingerprint on the artifact.
7. 7
   The completed document scans back to Witness.The clerk scans-and-emails the finished page. Witness reads the QR off the returned image to bind the scan-back to the original ceremony, and records a final event.
8. 8
   The relying party reads the bundle.An ordered timeline of every event in the ceremony, plus the artifacts each step produced. The relying party's decision system makes the call.

Want to see this happen for real? Open the trial flow — you can complete the ceremony at a trusted location of your choice and watch the status page on your phone update event by event.

What this gives you

• A strong custody chain

  The ceremony is closed-loop — opened and closed at the same trusted location, in one bounded session. The artifacts in the bundle were produced together, in one place, not assembled remotely from spoofed inputs.

• Strong facts

  Liveness, biometric template, QR scan, scan-back — each is recorded as an event in the bundle. The scanned-back page itself carries the wet signature and notary impression. Your decision system reads the event log and makes the call with real evidence behind it.

• Low friction

  The end user picks a nearby trusted location, walks in, completes the ceremony, walks out. No app install, no new account, no biometric enrollment ahead of time.