Answers for the moment trust matters.

Mojo Verify is an identity verification platform from Mojo Verify LLC. A business can request a configurable set of identity, liveness, contact, sanctions, and risk checks through one hosted flow.

The capture flow supports government-issued identity documents, including front-and-back cards and passport photo pages. The exact documents accepted can depend on the verification request and issuing country.

Auto-capture waits until the document is aligned, large enough in frame, well lit, sharp, and stable. It helps produce a usable image without requiring perfect timing.

Yes. When a mobile camera will create a better result, scan the QR code shown on the desktop flow. Your verification continues securely on the phone.

A liveness check is a short, guided camera experience designed to establish that a real person is present. When requested, the live face can also be compared with a reference portrait such as the one on an identity document.

The guided capture itself typically takes about five seconds after camera access and consent. Connection speed, device performance, and retries can affect the total time.

Check the camera permission for your browser and confirm another app is not using the camera. Reload after granting access. A current Safari, Chrome, or other modern mobile browser works best.

Ask the business that sent the request to issue a new verification link. Expired links cannot be reopened, which protects the verification session.

With your permission, a participating partner can receive your current verification tier and which checks were completed. Raw ID images, SSNs, and liveness media are not shared through the portable status, and access can be revoked.

Terminal webhooks carry the event type, request identifier, and timing—not personally identifiable information. Business systems verify the signature, then fetch protected results server-to-server.

Sandbox is for integration testing and uses keys beginning with mvs-. Production processes live verification requests and uses keys beginning with mvp-. Keep both kinds of key on the server.

A signing request can require a liveness check before the customer is allowed to sign. Combined with government ID verification and face matching, this connects the signature to a verified, live person instead of only to someone who opened a link.

The append-only trail can record request creation, document viewing, liveness attempts and results, signing start, signature capture, PDF generation, completion, downloads, and secure-sharing activity. Events can include actor, time, IP address, geolocation, browser information, and event-specific metadata.