PRICING
Pay per fact verified.
FAEFACT charges for verification performed — per check, per operation, or as licensed infrastructure. Where a rate is not yet published, the card says so plainly.
Three ways to buy the same verification.
Every model runs the same verification, carries the same consent flow, and seals the same audit trail. The difference is how it is bought.
MODEL A
PER CHECK
Per Verification
For owners and small operators. Pay for what you check. No subscription, no minimum.
INCLUDED
- Identity, background, and financial standing checked against source
- Consent obtained from the person verified before anything proceeds
- A sealed report — findings in plain language, evidence attached
- An audit-trail entry held on record after the decision
MODEL B
VOLUME
Operator Plans
For managers, societies, hotels, and coliving operators. Volume pricing, dashboard, team seats, configurable workflows.
INCLUDED
- Bulk verification workflows across a portfolio
- Configurable risk thresholds and workflows
- A dashboard showing the compliance state of every unit
- Team seats with access controls, one audit trail across the operation
MODEL C
LICENCE
Platform / API
For rental platforms, PMS providers, and enterprises. White-label licensing, SLA-backed, sandbox included.
INCLUDED
- REST API, webhooks, and sandbox access
- PMS, lease-management, and CRM integrations
- White-label mode — your brand in front, our infrastructure underneath
- A shared audit trail, every report verifiable by its ID
A rate appears on this card when it is exact. Until then, the honest answer is a conversation.
What people ask before they buy.
Brief answers. The full record lives in the Trust Centre.
Visit the Trust Centre →How does consent work for the person being verified?
Consent comes first. The subject grants it before any check proceeds — recorded, revocable, and DPDP-aligned. Every report carries its consent reference, and a verification without consent does not exist in our system, by design.
How long does a verification take?
It depends on what is being checked. Identity verification resolves in seconds — at booking or check-in. Staff background verification completes in hours — at offer stage, before day one. Vendor entity checks take days — at empanelment, renewable on schedule. Exact turnarounds per check type are stated when we quote your case.
What happens when a verification fails?
A failed check is a finding, not a judgment. The verdict is recorded — confirmed, flagged, or failed — with the evidence attached: which claim could not be confirmed, against which source. You see what we saw. The decision stays yours, and the finding enters the audit trail like any other.
What data is retained, and for how long?
Retention follows the purpose of the check, under the DPDP Act — what is collected, why, for how long, and the subject’s rights are set out in plain language in the Trust Centre. The specifics live there, not in a pricing FAQ.
Read the data-protection record →Can a finding be disputed or corrected?
Yes. The person verified can raise a correction. The disputed claim is re-checked against source like any other, and the audit trail records both the original finding and the correction — the record is amended in full view, never erased.
Start with a single fact.
Run one verification on your own workflow and read what comes back, together with the rate for doing it again.