Consent-first verification
No rental agreement check runs without explicit consent.
Fast review path where supportedStarts at ₹99DPDP-native consentSandbox demoAddress proof check
Verify Rental Agreements in India
PRAMAAN verifies registered or notarised rental agreements using document OCR, notary and date consistency checks, address extraction, and consent-first workflows designed for Indian verification teams.
- Price
- Starts at ₹99
- Result path
- Usually under 2 min
- Consent
- Required
- Sandbox
- Fixture data
OCR + document intelligence
Extracts parties, address, dates, rent, and tenure signals.
Notary/date validation
Checks notary, registration, and agreement date consistency signals.
Address extraction
Surfaces the residence address for reviewer comparison.
Audit trail
Links the result to purpose, consent reference, and timestamp.
Sandbox fixture data
Demo mode uses fixture data only. No real PII is processed.
Verification flow
Four steps from agreement upload to reviewable result.
The page now explains the complete journey: initiation, explicit consent, document intelligence, and a report that separates signals from reviewer decisions.
1
Upload or initiate the check
Requester starts a Rental Agreement verification from a clear purpose and uploads the agreement or sends a hosted flow.
2
Subject gives explicit consent
The data principal receives a consent request, reviews what will be checked, and approves before processing.
3
PRAMAAN extracts document signals
OCR and document checks extract parties, address, dates, rent, tenure, and notary or registration signals.
4
Report supports reviewer decisioning
The result includes confidence, risk indicators, consent reference, timestamp, and manual review notes where needed.
What PRAMAAN checks
Rental-agreement-specific signals, presented for operational review.
PRAMAAN should help teams understand what the document says, where confidence is strong, and where a reviewer needs to slow down.
Landlord name extraction
Extracts the landlord or lessor name and surfaces low-confidence text for review.
Tenant name extraction
Extracts the tenant or lessee name and helps compare it with the consented subject.
Registered / rented address
Parses the address block so reviewers can compare it with declared residence.
Agreement start and end date
Checks tenure, validity window, and date readability from the document.
Rent amount and tenure
Extracts monthly rent, deposit references where visible, and rental period signals.
Notary stamp signal
Highlights stamp presence, readability, and date consistency where applicable.
Registration or notary date consistency
Flags date mismatches or unusual sequencing for reviewer attention.
Backdated agreement risk
Surfaces signals that may indicate stale, inconsistent, or backdated paperwork.
Sub-let / possession chain signal
Highlights ownership, tenant, and sub-tenant chain clues where present in the document.
Document quality / OCR confidence
Marks blur, crop, glare, missing pages, or weak extraction as review required.
Consent reference and audit trail
Connects the result to consent purpose, timestamp, requester, and audit reference.
Why it matters
A practical address proof when government ID address data is stale.
Rental agreements are not a magic answer. They are useful because they can carry the current residence context that many onboarding teams actually need.
Rental agreements are commonly used as address proof across tenant, employee, vendor, and society workflows.
They can help when Aadhaar, PAN, or another ID carries an old address or no usable current residence signal.
Structured verification reduces ambiguity around parties, address, tenure, dates, and document quality.
Risk indicators help teams spot mismatch, stale paperwork, informal sub-let chains, or possible backdating signals.
Use cases
Built for individuals, operators, and enterprise risk teams.
Each buyer sees the same underlying verification evidence, but the decision context changes by workflow.
Landlords
Verify tenant-provided rental agreement signals before onboarding or handover.
Housing societies / RWAs
Validate resident or tenant address documents with a consent-first workflow.
Employers
Support employee address verification during onboarding or compliance review.
Staffing companies
Verify contractor residence proof before deployment to client locations.
Vendor onboarding
Check address proof for vendors, freelancers, and service providers.
Platforms / marketplaces
Support address verification workflows for high-trust users or sellers.
Consent and DPDP workflow
Verification starts with the person, not the document.
PRAMAAN positions rental agreement verification as a consent-first workflow: purpose shown, consent captured, consent logged, and the document check initiated only after approval.
No rental agreement check runs without explicit consent from the data principal.
The subject receives a consent request with the requester, purpose, and document type.
Consent is logged with a reference, timestamp, and purpose before verification starts.
The check runs only after consent is captured.
Sandbox demo mode uses fixture data only and does not process real PII.
Audit-ready consent evidence supports compliant verification workflows.
Report preview
A sample sandbox report with dummy rental agreement data.
The report preview shows the decision structure buyers expect: extracted fields, confidence, risk flags, consent reference, and reviewer notes.
Sample sandbox report — no real PII
Rental Agreement verification result
- Verification status
- Review required
- Document type
- Rental Agreement
- Agreement type
- Registered / Notarised
- Tenant name extracted
- Aarav Mehta
- Landlord name extracted
- R. Krishnan
- Address extracted
- Indiranagar, Bengaluru, Karnataka
- Agreement date
- 12 Apr 2026
- Tenure / rental period
- 11 months
- Rent amount
- ₹28,000 / month
- Notary / registration signal
- Stamp present; date readable
- OCR confidence
- 92%
- Consent reference ID
- CNS-RA-DEMO-2048
- Timestamp
- Sandbox timestamp
- Reviewer note
- Confirm address match with onboarding record.
Risk flags
Signals are evidence for review, not final legal conclusions.
Backdated agreementNo strong signal in sample
Unregistered documentNot applicable in sample
Sub-let chainReview if chain appears
Date mismatchNo mismatch in sample
Poor document qualityNo issue in sample
Risk signals
Clear outcomes without overstating legal certainty.
PRAMAAN should communicate verification signals in plain language so teams know when to proceed, review, or request a better document.
Green signal
Registered or notarised agreement, clear OCR, valid tenure, address extracted cleanly, and readable date signals.
Amber signal
Unregistered agreement, sub-let chain, weak OCR, old date, address mismatch, or missing supporting context.
Red signal
Date inconsistency, suspected tampering, missing parties, unreadable stamp, or document quality too poor to review confidently.
These are verification and review signals. They should not be presented as final legal conclusions or government certification.
Pricing and checkout
Start with one rental agreement verification. Scale when your workflow is ready.
Designed for self-serve buyers and evaluation teams: ₹99 entry price, UPI checkout path, sandbox demo, and report language suitable for review workflows.
Rental Agreement verification
₹99
- Rental Agreement verification starts at ₹99
- UPI checkout path for self-serve checks
- Fast review path for supported rental agreement checks
- Full PRAMAAN verification usually returns in under 2 minutes
- Sandbox demo available with fixture data only
- No real PII in sandbox mode
Developer and API evaluators
Built to fit API-led verification workflows.
Technical teams can evaluate the sandbox, API docs, webhook patterns, and consent-reference model before moving live verification into production workflows.
API-ready verification workflow
Evaluate consented verification creation and result retrieval in PRAMAAN developer docs.
Sandbox keys and fixtures
Test report shape, consent references, and fixture responses before live processing.
Webhook-ready integration path
Review webhook documentation for event delivery patterns and integration planning.
Audit logs and consent reference
Design integrations around purpose, consent reference, status, and evidence fields.
FAQ
Rental agreement verification questions.
Short, legally careful answers for buyers, operators, and compliance teams.
Can an unregistered under-11-month agreement be verified?
Yes. PRAMAAN can extract and evaluate document signals from an unregistered agreement, but the report should mark confidence and review needs carefully.
What if the person owns the property and has no rental agreement?
Use a more relevant address proof such as a property tax receipt, sale deed, utility bill, or another supported document where available.
How is a sub-let arrangement handled?
PRAMAAN can highlight chain-of-possession signals where the document shows owner, tenant, and sub-tenant context. Reviewers should confirm the relationship before relying on it.
Can PRAMAAN detect backdated agreements?
PRAMAAN flags date inconsistency, stale tenure, notary or registration date mismatch, and document quality signals. These are review signals, not legal conclusions.
Is consent required?
Yes. No rental agreement verification runs until the data principal gives explicit consent, and the consent event is logged.
Is sandbox using real PII?
No. Sandbox mode uses fixture data only, so buyers and developers can evaluate the workflow without real personal data.
How fast is rental agreement verification?
End-to-end PRAMAAN verification usually returns in under 2 minutes where the supported check can complete normally.
Can this be used for employee address verification?
Yes. Employers can use rental agreement verification as a consent-first address proof workflow during onboarding or review.
Can housing societies use this for tenant onboarding?
Yes. Housing societies and RWAs can use it to validate tenant or resident address documents with explicit consent.
What happens if OCR confidence is low?
The report should mark the extraction as low confidence and route the document for manual review or request a clearer upload.
Related document checks
View verification flowPair rental agreement verification with adjacent identity and address rails.
Aadhaar
Identity and address proof signal for Indian residents.
PAN
Tax identity signal for tenants, vendors, and paid workers.
Voter ID
Fallback identity and registered address signal.
Driving Licence
Identity, DOB, and address-bearing document signal.
Passport
Strong identity and travel document verification signal.
GSTIN
Business identity signal for vendor and marketplace onboarding.
Consent-first PRAMAAN
Verify a Rental Agreement with consent-first PRAMAAN
Start with a sandbox demo or run a ₹99 verification when the subject is ready to consent.