Patient Identity Verification

Last updated: 3 June 2026

Overview

Jump now has a dedicated Identity tab on the patient sidebar which shows a patient's current verification status, the actions available to verify their identity, and the full audit trail of previous verification events.

When a patient has been successfully verified, an ID Verified pill appears next to their name on the patient card and header, alongside the existing Active badge, so the status is visible at a glance across the app.

Verifying a patient's identity

  1. Open the patient in the sidebar and switch to the Identity tab.
  2. Click Verify identity to start a check.
  3. Choose the verification method that applies — available methods depend on which integrations are enabled for your organisation (for example, Stripe Identity).
  4. Follow the prompts to complete the check.

The Identity tab remains available even before any verification has been run, with a clear empty state explaining what the tab is for.

Stripe Identity

Organisations connected to Stripe Identity can launch a Stripe-hosted identity check directly from the patient sidebar. The Stripe Identity panel only appears when the integration is enabled for your organisation.

Audit trail

Every verification attempt — successful or otherwise — is recorded in the Identity tab's audit trail. Each row is clickable and opens the detail view for that event so you can review exactly what happened, when, and by whom.

Tips

  • Patient emails are now treated case-insensitively, so verifications and identity links no longer miss matches on casing differences.
  • If the Stripe Identity tab is hidden, check that the Stripe Identity integration is enabled in your organisation's settings.

Patient form links now follow your practice-wide identity-verification setting automatically — patients get the same verification step whether they reach you through a booking link or a form link, with no separate configuration.

To keep bookings and forms protected, at least one verification method is always kept active. If you try to switch both off, the platform will keep one enabled.