Integrations · Stripe Identity

Know who you are treating.

Patients verify their identity before care begins - a photo ID and a selfie, on their own device, inside the booking flow. The outcome is recorded against the patient, so the check is part of the record rather than a note in someone’s inbox.

document + selfieinside the booking flowrecorded against the patient
ehr.usejump.co.uk · Appointments · Today
One appointment, end to endEverything on the record
booked online · seen · prescribed · billed · GP informed · follow-up armed
09:12Booked online, paid in full before the slot confirmed · pre-booking questionnaire returned codedPaid
14:00Consultation coded as written · Dysuria · SCT 49650001 · new episodeCoded
14:09Prescription checked against the record, sent to pharmacy · dm+d matched · allergy check passedDispensing
14:11Invoice raised from the appointment · INV-2026-0412 · Xero-syncedSettled
14:24Letter to her NHS GP over the NHS message exchange · sent as your practice · delivery trackedDelivered
14:25Follow-up armed · recall fulfils itself when she attendsWatching
The record afterwards
Problem list
Dysuria · SCT 49650001 · active
Medication record
Nitrofurantoin 100mg MR · dm+d · 3 days
Correspondence
NHS GP letter · delivered 14:24
Audit trail
every entry · who, what, when

How it works

Verified before the slot is confirmed.

Identity sits inside the booking flow: after the patient books, before they pay.

  1. 01Patient books onlinepatient
  2. 02Identity check requestedautomatic
  3. 03Photo ID and selfie on their own devicepatient
  4. 04Outcome recorded against the patientautomatic
  5. 05Reviewed where it matterspractice

In-person checks are recorded too, so a practice that verifies at the desk keeps the same trail.

What the connection does

A check that stays with the record.

Identity verification powered by Stripe Identity, recorded in Jump.

  1. 01Document and selfieThe patient uploads a photo ID and takes a selfie to match against it.
  2. 02On the patient’s own deviceNo app to install and nothing for the practice to handle.
  3. 03Inside the booking flowRuns after booking and before payment, so you know before you confirm.
  4. 04Recorded against the patientThe outcome sits on the record, not in an inbox.
  5. 05Remote or in personRemote verification at registration; in-person checks recorded too.
  6. 06Useful for remote careParticularly where the patient will never be in the room.

Setup and security

Setup time

Connected from the App Store alongside Stripe

Security

  • Identity documents are handled by Stripe, not stored by the practice
  • The verification outcome is recorded against the patient with a timestamp

Requirements

  • A Stripe account with Identity enabled

Common questions

Questions, answered.

What practices ask about verifying patient identity. If yours is not here, ask us on a demo call.

Inside the booking flow - after the patient books and before they pay - so you have the answer before the appointment is confirmed. It can also be requested at registration.

See a patient verified before they arrive.

Thirty minutes through the booking flow: booked, verified, paid, confirmed - with the check on the record.