How verification works
What we check, and what we don't.
This page is the long version of every badge in the product. If something here contradicts what the product says, this page is the one that's wrong, and we want to hear about it.
The five levels
- Self-reportedStated by the tenant only.
- DocumentedBacked by a document: a contract, a transfer receipt, a letter from the residence.
- Confirmed by landlord contactConfirmed by the landlord contact the tenant provided, after automated checks.
- Confirmed by verified landlordConfirmed by a landlord whose identity is verified and whose name matches the contract, or by a residence or agency from its verified corporate email domain.
- Bank-verifiedVerified through Open Banking. Not switched on yet.
A fact can rise a level later: your landlord can confirm every earlier payment in the same step, and if they verify their identity afterwards, everything they confirmed rises to level 4.
What a passport shows is how many facts sit at each level. It never adds them up into a score.
Making sure the landlord is the landlord
The honest risk is obvious: a tenant could send the confirmation link to a friend, or to a second email address of their own. No link can rule that out completely. So there are layers, and the badge says exactly which ones were passed.
Automated checks, every time
- The landlord's email or phone cannot match anything belonging to the tenant, or to anyone connected to them.
- Disposable email domains are blocked.
- A confirmation from the same device, browser session or network the tenant normally uses does not raise the level, and is flagged for review.
- Every confirmation needs a one-time code sent to the landlord's email, not just a click.
- A confirmation is never performed by opening a link. Email providers fetch links automatically to scan them, so opening the page does nothing — confirming needs a deliberate tap on a button.
Agreement between sources
- The name of whoever confirms has to match the landlord named on the contract, and the payee on the transfer receipts when the tenant provides them. A mismatch blocks the rise and is explained to the tenant.
- Residences and agencies can only confirm from their own corporate email domain.
- A tenant can add the RTB registration number of the tenancy. We record it; we do not validate it against an API that does not exist.
A landlord with verified identity
- If the landlord verifies their identity and their name matches the contract, their confirmations become level 4 — including the ones they already made.
- What they get for it is their own record as a landlord: tenancies confirmed, deposits returned on time.
Patterns, and consequences
- We watch for the shapes that fraud makes: one landlord confirming many unrelated tenants at different addresses, confirmations in bursts, crossed details between tenant and landlord.
- A false confirmation closes both accounts and removes the affected facts from the passport. The Terms say so plainly.
- Every confirmation leaves an audit entry: when, from where, and which layers it passed.
Bank verification, later
- The strongest proof does not need the landlord at all: the payment leaves the tenant's account towards a payee whose name matches the contract. The architecture is ready; the connection is not switched on.
We don't publish the exact thresholds the detection uses, for the obvious reason.
What identity verification is, and isn't
Identity is checked with a document, a liveness check and a face match. That confirms who a person is. It does not confirm their income, their payments, or how a tenancy ended. No badge in this product claims otherwise.
We keep the result and the minimum metadata. We do not keep the images of your document.