The small green Verified badge on a GoWith Activity Partner profile is the single most useful signal in the app. It is also the one most people assume is cosmetic. It is not — it represents four independent checks, every one of which has to pass before a profile can accept a single booking. Here is what each one actually does.
Check 1 — Government photo ID
PAN card as the primary document, with Aadhaar as the identity-match counterpart via DigiLocker. The partner uploads their PAN, our system reads the name, DOB, and card number via the government's own verification APIs, and matches the name on the PAN against the name they signed up with. Mismatch means the badge doesn't issue — the partner has to update their account name to match the legal document.
This is why some profiles show as "Rohan S." rather than a full name — the display name is derived from the PAN, not freeform. It is a small UX cost in exchange for a strong guarantee that the person you meet is the person on file.
Check 2 — Aadhaar via DigiLocker
The partner authenticates into DigiLocker from inside the app and shares their Aadhaar KYC packet. We never see the full Aadhaar number — the Aadhaar reference ID is what gets stored. We verify the Aadhaar name matches the PAN name, and the DOB matches too. If either mismatches, the KYC is paused and the partner is contacted.
Check 3 — Live selfie liveness match
The partner takes a live selfie in the app. The liveness check confirms it is a real person in front of the camera (not a photo of a photo); the face match confirms the selfie is the same person as the PAN card photo. Both pieces have to pass. We use a vendor liveness SDK that catches the common attack vectors — printed photos, screens, static deepfakes.
Check 4 — Bank account or UPI
A ₹1 name-match verification against the partner's declared payout account. The bank returns the name they have on file; it must match the PAN name. This step catches a specific attack — people who pass identity verification with a stolen or borrowed PAN but have no way to receive payouts under that name. It also guarantees we have a working, correctly-named bank or UPI handle to send earnings to.
The badge issues only when all four pass
A partner who has done three out of four cannot accept a booking. They can set up their profile, write their services, upload their intro video, and still sit on the Browse page with no verified badge — which means no booking button. This is enforced server-side, not just in the UI, so there is no way around it.
What verification does not promise
Verification is identity verification, not character verification. GoWith does not run criminal background checks and does not vouch for a partner's professional qualifications beyond what their profile claims. The verified badge means: this is a real, legally-identifiable person, with a real bank account in their real name, and the face in the selfie is theirs. It does not mean they are necessarily skilled, pleasant, or on time. For those signals, use the rating and meet count on the profile.
Why the pipeline is this strict
Most activity-booking marketplaces in India launched with light verification and tightened later after incidents. We built the opposite path — launched with four strict checks so the identity floor is high from day one. The cost is a slower onboarding (partners typically clear verification in 2-6 hours); the benefit is that every booking you make is to a real, bank-verified individual. See our longer piece on the full six layers of safety that make this work.