Consent-first verification
No Ration Card check runs before explicit consent.
Fast result pathStarts at ₹99DPDP-native consentSandbox demoAddress proof checkSensitive-data aware
Verify Ration Cards in India
PRAMAAN verifies PDS Ration Card signals including card validity, family head, listed members, address, state, and sensitive category handling through consent-first verification workflows.
- Live check
- INR 99
- Result
- Usually under 2 min
- Consent
- Required
- Sandbox
- Fixture data
Purpose-limited use
The requester sees verification-relevant signals only.
PDS document signal
Designed around state-issued Ration Card and PDS signals.
Family-unit address proof
Useful when household-level address context matters.
Sensitive category handling
BPL, APL, and Antyodaya context is minimized carefully.
Audit-ready trail
Purpose, consent, timestamp, and report reference are captured.
Sandbox fixture data
Demo mode does not process real personal information.
India-region workflow
Designed for Indian verification and DPDP-aware workflows.
Verification flow
Four steps from consent request to family-unit address evidence.
PRAMAAN separates request, consent, PDS document verification, and report review so the workflow is easier for individuals and accountable for teams.
1
Initiate Ration Card verification
The requester starts a Ration Card check with a clear purpose, price, and document type before any verification work begins.
2
Subject gives explicit consent
The data principal receives a consent request, reviews the purpose, and accepts before the check is initiated.
3
PRAMAAN verifies PDS document signals
The workflow checks card validity, issuing state, family head, listed members, address, and available PDS signals.
4
Result/report is generated
The requester receives a reviewable report with address and family-unit indicators, consent reference, and limitation notes.
What PRAMAAN checks
PDS Ration Card signals, presented with context and limits.
The check is strongest as consented address and family-unit evidence. Sensitive category context is handled carefully and should not be used for discriminatory decisions.
Ration card number validity
Checks whether the submitted Ration Card reference resolves as a valid document signal.
Issuing state / PDS signal
Returns the state or PDS source signal available for the record, where supported.
Family head name
Surfaces the family head name as a household identity and address context signal.
Family head photo if available
Shows whether a photo signal is available for review without overclaiming match certainty.
Listed family members
Returns family-unit member indicators where available, useful for household address context.
Address extraction / confirmation
Provides the address signal available from the Ration Card record for declared-address comparison.
State and district signal
Surfaces state and district context when returned by the relevant PDS source.
Sensitive category handling
BPL, APL, and Antyodaya context is treated as sensitive and minimized unless a documented purpose requires it.
ONORC portability caveat
One Nation One Ration Card portability can require issuing-state interpretation rather than blanket pan-India assumptions.
Consent reference and audit trail
Links the result to the consent event, purpose, requester, timestamp, and report reference.
Data freshness caveat
Recent family, address, or state PDS updates may lag and should be treated as review context when mismatched.
Why it matters
Ration Card can be practical address proof, especially when other documents lag real life.
Use the document as a consented verification signal for address and family-unit context, while keeping the human context dignified and purpose-limited.
Practical address proof
For many Indian workers and families, a Ration Card can be a practical household-level address proof when other documents are stale or unavailable.
Family-unit context
The document can support family and household address context, which is useful for worker, resident, contractor, and program workflows.
Dignity-first handling
Because the document can include socio-economic context, the workflow must stay consented, purpose-limited, and non-discriminatory.
Sensitive data handling
Sensitive by design: verify address, not economic status
Ration Card data can include socio-economic category context. PRAMAAN treats such fields carefully, keeps the workflow consent-first, and frames category information as sensitive context rather than a decisioning tool.
No discrimination use
BPL, APL, or Antyodaya context should not be used to reject, rank, or economically profile a person.
Purpose limitation
Only verification-relevant signals should be shown to the verifier for the stated purpose.
Field minimization
Sensitive fields should be masked, minimized, or omitted unless the documented purpose requires them.
Accountability trail
Consent, purpose, timestamp, and report reference support review and accountability.
Use cases
Talk to salesBuilt for individuals, operations teams, and compliance buyers.
The best workflows use Ration Card verification for consented address evidence, not broad social or economic profiling.
Household worker verification
Verify address proof for domestic workers, drivers, cooks, helpers, and caregivers with consent.
Housing societies / RWAs
Support resident, tenant, and worker entry verification workflows with logged consent evidence.
Staffing companies
Verify address proof for blue-collar and contract workforce deployment.
Employers
Support employee or field staff address verification during onboarding.
Facility management
Verify housekeeping, security, maintenance, and service staff documents.
NGOs / social-sector programs
Validate household and family-unit address proof responsibly and with purpose limitation.
Platforms and marketplaces
Support high-trust onboarding where Ration Card is used as address evidence.
Consent and DPDP
No Ration Card check runs without explicit consent.
The data principal sees the request purpose before processing. The verifier receives purpose-relevant information after consent is captured and logged.
- 1
No Ration Card check runs without explicit consent from the data principal.
- 2
The consent request states the requester, document type, and purpose before verification.
- 3
Consent is logged with timestamp, purpose, and reference for audit review.
- 4
The check runs only after consent is captured.
- 5
The requester receives purpose-relevant information rather than unrestricted document data.
- 6
Sandbox demos use fixture data only and do not process real personal information.
Report preview
Sample sandbox report — no real PII.
The preview shows how a Ration Card result can summarize address and family-unit signals while minimizing sensitive category context.
Risk and limitations
Verification signals are evidence, not final legal conclusions.
Ration Card records can be stale, partial, or shaped by state PDS update cycles. PRAMAAN should help teams decide the right next review step.
Green
Clear verification signals
- Card number valid
- Issuing state matched
- Address signal available
- Family-unit information consistent
Amber
Review recommended
- New family member not yet reflected
- State PDS update lag
- Address partially matched
- ONORC portability requires issuing-state check
- Manual review recommended
Red
Verification cannot proceed cleanly
- Invalid card number
- State mismatch
- Address unavailable
- Family head mismatch
- Consent missing or expired
Pricing
Start with one consented Ration Card verification.
Use sandbox first, then run a live INR 99 verification when the purpose and consent flow are ready.
Ration Card verification
₹99
- Single Ration Card verification
- Starts at INR 99
- UPI checkout path
- Fast review path where supported
- Full PRAMAAN verification usually under 2 minutes
- Sandbox demo with fixture data only
Developers and API evaluators
Designed to support API-led verification workflows.
Technical teams can review sandbox behavior, consent references, audit logs, and purpose-limited response design before production use.
API-ready verification workflow
Evaluate consent-led verification creation, status retrieval, and report review through PRAMAAN developer routes.
Sandbox keys and fixture flows
Test the workflow safely with fixture data before live checks. No real PII is required for sandbox review.
Consent reference in responses
Design responses around purpose, consent reference, timestamp, and audit evidence.
Webhook-ready workflows
Use existing developer webhook documentation for event delivery patterns where your integration needs asynchronous status.
Related document checks
View all servicesCombine Ration Card with adjacent verification rails.
Use the right document mix for identity, address, work role, and business context.
Aadhaar
Household help, driver, tutor — the default identity rail in India.
PAN
Tenant, vendor, employee — anyone receiving payment in India.
Voter ID
Fallback identity and address verification for workers, tenants, vendors, staffing candidates, and platform users.
Driving Licence
Drivers, delivery workers, fleet operators — DL is the implicit job-credential.
Passport
Most senior hires, mid-management vendors, NRIs returning.
GSTIN
Vendor onboarding, B2B contractor vetting, marketplace seller verification.
FAQ
Ration Card verification questions.
Short answers for buyers, societies, households, NGOs, and developer evaluators.
BPL, APL, or Antyodaya category: is this used to discriminate?
No. Category context is treated as sensitive and should not be used to reject, rank, or economically profile a person. PRAMAAN frames it for purpose-limited handling and minimization.
What if a new family member is not reflected?
State PDS records can lag family changes. Treat missing or stale family information as an amber review signal, not a final adverse conclusion.
How does multi-state PDS or One Nation One Ration Card work?
ONORC portability may affect how a card is used across states. PRAMAAN interprets verification signals against the issuing-state context where applicable.
What if the physical ration card is lost?
A check can be initiated from the document reference where the workflow supports it. The requester should still collect explicit consent before running verification.
Is consent required?
Yes. No Ration Card 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 inspect the flow without processing real personal information.
How fast is Ration Card verification?
A full PRAMAAN verification is usually available in under 2 minutes where the supported check can complete normally.
Can this be used for worker address verification?
Yes, when the worker gives explicit consent and the requester uses the result as an address verification signal rather than a socio-economic decisioning tool.
Can housing societies use this?
Yes. Societies and RWAs can use it for consented resident, tenant, worker, or vendor address workflows with clear purpose and audit trails.
What happens if state PDS data is outdated?
Outdated source data should be treated as an amber signal. Use manual review and avoid adverse action from one stale signal.
Are sensitive fields shown to the verifier?
Sensitive fields should be minimized or masked unless the documented verification purpose requires disclosure. The default design should avoid unnecessary category exposure.
Consent-first address verification
Verify Ration Cards with consent-first PRAMAAN
Run a live check for INR 99, inspect the sandbox, or evaluate API-led workflows for higher-volume teams.