Use case · Address verification
Address verification
No field agent.No guesswork.A verified address.
Where streets have no numbers, an address typed into a form tells you little, and sending someone to knock on the door costs more than the account earns. Toden takes a pin on a map, checks it against a bill and the customer's records, and can confirm from their phone that they really are there.
The workflow
A pin, a document and presence at the address, graded by how strong the evidence is. This is a starting point: add, remove or reorder any step in the workflow builder.
Step 01
Proof of Address
Utility bill or bank statement
Step 02
Address Intelligence
A map pin, an entrance photo and directions
Step 03
Presence verification
Confirms over several days that they are at the pin
Then your rules decide
A starting rule set
- The phone was at the pin when it was droppedApprove
- A document or record names the same areaApprove
- Nothing supports the addressReview
- Many unrelated people share the pinReview
- Location evidence was tampered withDecline
Every rule is yours to change on a visual canvas, and each result records which rule decided it. Publishing a new version needs no release.
Try the workflow builderConnection map
When a face, a phone or an address turns up again, the console draws everyone gathered around it and says in plain words what the connection means and how much weight it deserves.
- ReassuringShared surnames over 412 days, on separate devicesRecords built up gradually and each person used their own phone. That fits a family home.
- Reassuring2 confirmed as actually living hereTheir phones were at the address over several days, which supports that they live there.
- An illustration with invented people. In the console each card opens the customer's record.
How it works
The customer shows you where
They search or drop a pin, add the house number and directions, and photograph the entrance.
The evidence is compared
The pin is checked against the address on a utility bill and on their government record, and against where the phone actually was.
Presence confirms it
With your mobile app, the phone confirms over several days that it is at the pin, and you receive a verdict and can issue a certificate.
What powers it
Each address reaches a tier: attested when the person stood at the pin, corroborated when a record agrees, or simply collected.
Integrate
Mount the SDK with the workflow you published, or send a hosted link and write no code. The result arrives by signed webhook, and changing the workflow never needs a release.
import { TodenVerification } from "@todenhq/sdk-react"; export function Verify({ userId }) { return ( <TodenVerification apiKey="pk_test_..." workflowId="wf_AbC123dEf456" userId={userId} onSubmit={(s) => save(s.verificationId)} /> );}{ "event": "verification.completed", "data": { "verificationId": "ver_8fk2...", "status": "verified", "assuranceLevel": "gov_db", "idType": "bvn", "country": "NG", "dataMatch": true, "facialMatch": true, "facialConfidence": 91 }}Products involved
This solution combines products you can use on their own too.
Related use cases
Frequently asked
The pin and the document work in a browser. Presence verification needs the React Native or Flutter SDK, because only an app can check location over several days.
Address verification,in one workflow.
The sandbox opens when you sign up. Usage-based pricing, no sales call.