Decide what a visit has to capture
A template is the contract three people read: the agent standing at a door, the reviewer signing it off, and the developer parsing the result. Build it once — text answers, multiple choice, documents, signatures, Aadhaar or PAN checks, and photographs that can only be taken with the camera there and then. Write the instruction that appears under each one, because an agent in front of a stranger needs to know exactly what to frame.
- Text, multiple choice, upload, camera, signature, KYC
- Camera fields open the camera — never a file picker
- Require a location fix, and a minimum accuracy, per field
- Guidance text on every capture, shown where it is needed
- A template is frozen onto each visit, so edits never rewrite work already dispatched
Raise it from your own system
One POST with the address and your own reference. You get back a link to hand to whoever is going — single-use, time-limited, scoped to that one visit, and useless for anything else. Or assign the work to a colleague and it lands in their app. Retrying with the same idempotency key returns the same verification instead of sending a second person.
- POST /physical-verification/requests
- A hosted page for agents with no login, like a payment gateway
- Or assign it to your own staff, who work it from the SubhX app
- Retries are safe — one key, one visit, one charge
- Your reference travels through every response and callback
Consent first, then evidence
Nothing is captured until the person at the address has been shown, in your own words, what the visit is for and has agreed. That sentence is stored verbatim as they read it, with the time and place — not as a pointer to whatever the template says next month. It is the difference between evidence and a photograph of somebody's home.
- Your purpose text, shown and recorded word for word
- Consent is mandatory — a visit cannot be filed without it
- Camera permission asked for at the moment it is needed, with a reason
- Location read at the instant of capture, never tracked
- Every photograph stored privately, scanned, and never given a public link
Review it, and be told the moment anything changes
Submitted work waits for a reviewer, who accepts it or sends it back with a reason. Every step — created, assigned, started, submitted, completed, rejected — arrives at your webhook signed, retried and deduplicated, so your system never has to poll and never has to guess.
- Accept, or send back with a reason the agent can act on
- Eight signed callbacks covering the whole lifecycle
- At-least-once delivery with a stable delivery id to key on
- The person who does a visit can never sign off their own work
- Full audit trail, including who read what
Why teams pick it
Physical Verification, in a nutshell
Send a real person to a real address and get back proof — geo-tagged photographs, answers and documents, with a signed callback at every step.
Proof, not paperwork
A photograph with the place and the moment attached, taken by a person who was there.
Consent on the record
Shown in your words, agreed on the doorstep, and stored exactly as it was read.
Works like a gateway
Raise, redirect, and receive a signed callback. Nothing to poll.
Pay per verification
Charged once, when the work is submitted. Cancelled and expired visits cost nothing.
Separated duties
Dispatching, doing and approving are three permissions, so nobody marks their own homework.
Nothing to install
Agents work in a browser on any phone, or in the SubhX app if they are your own staff.
Questions
The things people ask about Physical Verification
Whoever you choose. Assign it to your own staff and it appears in their SubhX app, or send the hosted link to a contractor or agency — they need no account with us. Either way the same rules apply: consent first, camera-only photographs, and a reviewer who is not the person who did the visit.
Once, at the moment the agent submits their work. Not when you raise the request, not when you assign it, and not again when you accept it. A verification you cancel, or that expires, is never charged. If a reviewer sends work back and the agent goes again, the second submission is free.
Nothing happens twice. Every request carries an idempotency key; retrying with the same one returns the verification you already have rather than dispatching a second person, and the charge is tied to the verification, not the call.
Not for a camera field. Those open the camera directly and the picture is taken there and then, with the location read at that instant. If you also want to accept existing files — a bill, a letter, a scan — that is a separate upload field, and the result records which of the two it was.
Your webhook is told. Act on that rather than on the redirect: the redirect exists to move a person along after they finish, carries no signature, and a browser can be closed before it lands. The callback is signed, retried and deduplicated, and the API read confirms it.
In private storage, virus-scanned on the way in, with no public or shareable link anywhere in the product. They come back only through an authenticated request from somebody in your organisation who holds the permission to see them, and every read is audited.
Turn a doorstep into an API call
Switch on Physical Verification from the marketplace, build your first template in a few minutes, and raise a verification the same day.