Skip to Content
FeaturesIdentity Verification

Identity Verification (IDV)

Identity Verification lets you confirm that the people behind a company — roles, shareholders, and beneficial owners — are who they say they are, without leaving Strise. You send a person a secure link, they verify themselves through Strise’s identity partner Signicat, and the result lands back on the entity page with a clear status and an audit trail.

You can also record verifications that were completed elsewhere, so the entity page reflects every check your team has done — inside or outside Strise.

This article covers the IDV section on the entity page. For the team-wide view of every verification in progress, see Data Collection. For the underlying partner, certifications, and bring-your-own-provider options, see the IDV Module overview.

Where to find it

The Identity verification card appears on both company and private person entity pages.

  • On a company, the card lists verifications for the company’s roles, shareholders, and beneficial owners together.
  • On a private person, it lists verifications for that individual.

Each row shows the person’s name (a link to their profile), the verification method and date once completed, and a status badge. A row menu (⋯) exposes the actions available for that status.

If your team has the Identity Verification module enabled, the card is shown automatically. Contact your account manager or support@strise.ai to enable it.

Requesting a verification

Click Request IDV to open the Request identity verification dialog:

Select who to verify and add an email for each. They get a secure link.

  1. Choose a verification workflow. If your team has more than one workflow configured, pick the one to use (for example a passport-and-selfie flow versus a bank-ID flow). With a single workflow this step is skipped.
  2. Select who to verify. Search roles, shareholders, and owners by name or relationship. People who already have a verification in progress can’t be selected again.
  3. Add a recipient email. Each selected person gets a Send link to field — enter the address where their secure link should be sent.
  4. Send. The button reads Send request for one person, or Send N requests for several.

Each recipient receives an email with a secure link and completes the verification on their own device. The request appears in the card with a Pending status straight away, and updates automatically as the person progresses.

Recording a verification manually

If a check was completed outside Strise — an in-person passport check, a verification in another system, or a corporate record — record it with Add verified identity:

Record a verification done outside Strise. No request is sent.

FieldRequiredNotes
PersonYesPre-selected on a private person page; chosen from roles/shareholders/owners on a company page.
Full legal nameYesAs it appears on the ID document.
Date of birthNo
NationalityNo
Verified onYesDefaults to today.
Verification methodYesSee the methods below. Choose Other to type a custom method (e.g. “In-person passport check”).
DocumentsNoAttach ID documents, reports, or screenshots (PDF, PNG, JPG, JPEG, WebP).

No request or email is sent. The record appears immediately with a Verified status, marked as a manual entry.

Statuses

StatusWhat it meansWhat you can do
PendingThe person has been sent a link and hasn’t finished yet. You’ll be notified when it’s answered.Copy the verification link, or withdraw the request.
Pending approvalThe verification came back but needs a human decision — for example the name or date of birth didn’t match, or it couldn’t be verified automatically.Open the row to review, then Approve or Decline.
Request expiredThe secure link expired before it was used.Regenerate and copy a new link, or withdraw.
FailedThe automated verification failed (for example a document was rejected).Request a new verification, or withdraw.
DeclinedA team member reviewed the result and rejected it.Request a new verification, or withdraw.
VerifiedThe identity was confirmed — automatically or by manual entry.Open the row to view the full details.

Reviewing and approving

Click a Verified, Pending approval, or Declined row to open the details drawer. It shows:

  • Source — Signicat for an automated verification, or Manual entry.
  • Method — the verification method used.
  • Verified / Notified — when the verification was completed and when the result arrived.
  • Full legal name, date of birth, and nationality captured during verification.
  • Documents — the ID images or reports collected, available to download.

When a result is flagged for approval, an Identity comparison section shows the value Strise holds next to the value from the verification — so you can see exactly what didn’t match before deciding. Use Approve to confirm the identity or Decline to reject it.

To clear a completed verification, use Withdraw. You’ll be asked to confirm:

This clears the current identity verification and its status. This can’t be undone.

Managing requests in flight

From a row’s ⋯ menu you can:

  • Copy verification link — share the secure link with a pending recipient directly.
  • Regenerate & copy link — issue a fresh link when the original has expired.
  • Request new verification — restart the process for a failed or declined person.
  • Withdraw request — cancel a request that’s no longer needed.

Verification methods and partner

Automated verifications are powered by Signicat, Strise’s identity verification partner. The methods available for manual records — and configurable in your workflows — are:

  • Norwegian BankID
  • Swedish BankID
  • SMS OTP
  • Email OTP
  • Onfido
  • Signicat Video ID
  • Other (a custom method you specify)

Notifications

Your team can choose to notify assigned users when identity verifications complete — sending an email when a verification is approved, declined, or fails. This is configured in your team’s settings.

See also

  • Data Collection — every IDV and form across your whole team in one place.
  • IDV Module — the partner, certifications, and bring-your-own-provider option.
  • Customer Facing Forms — collect and verify entity information with secure forms.
Last updated on