Most platforms slap one "verified" badge on a profile and treat the entire concept of identity verification as binary — either you're verified or you're not. That's useless, because verification is plural. There are several independent things a verification can prove, and each one means something different to the person evaluating you.
Realr keeps the badges separate on purpose. Here's what each one actually proves — and what it doesn't.
Phone verified
What it proves: the person has access to a working phone number. Specifically: when we sent a 6-digit code to that number, the same person entered the code into the verify field within 5 minutes.
What it doesn't prove: that the phone number is registered in their real name, that they own the SIM long- term, or that this is their primary number. Disposable virtual numbers (Google Voice, Skype, Burner) pass phone verification just fine.
Useful for: baseline trust — a contactable person on the other end. Combined with one or two other verifications, it becomes much stronger.
Email verified
What it proves: the person controls the email address. We sent a one-time link or code; they returned with the right token in under 24 hours.
What it doesn't prove: that they own the domain, that the email is their real personal address, or that they haven't created the address minutes before signing up. Throwaway email services pass this check trivially.
Useful for: a contact channel that survives device changes. Stronger when the email uses a domain the person owns (you@yourbusiness.com vs you1234@protonmail.com).
Government ID verified
What it proves: the person uploaded a document issued by a government (passport, driver's license, Aadhaar, PAN, etc.) and a human reviewer (or automated KYC check) confirmed the document is genuine and the photo on it matches a selfie they took during the same session.
What it doesn't prove: that the document is currently valid, that the person hasn't changed their legal name since issue, or that the issuing government's data is accurate. It also doesn't tell anyone looking at your Realr what's on the document — the document stays on Realr, only the badge shows.
Useful for:the strongest single identity signal Realr offers. A government-ID-verified user is meaningfully harder to fake than every other badge combined. This is what raises the accountability cost of a scam from "create a new account" to "commit document fraud."
Selfie verified
What it proves: the person passed a liveness check — they're a real human, alive at the moment of the check, holding the device. Includes a face match against the government ID photo if both are submitted.
What it doesn't prove: that the selfie matches any other photo on the internet, that the person is the original owner of the gov ID (in deepfake / stolen-ID scenarios). Deepfake bypasses do exist but are still expensive to produce at scale.
Useful for:proves there's a real human attached to the account, not a bot or AI persona. Combined with government ID, it's the "this is genuinely the person on the ID" signal.
Payment method verified
What it proves: the person has a working payment instrument (card, UPI, bank account) that passed a small authorization test. The instrument is in their name (or a name they have legitimate access to).
What it doesn't prove: their financial standing, creditworthiness, or that the payment method is their primary one.
Useful for: proves there's recourse if a transaction goes wrong. A user with a verified payment method is one a buyer can request a refund from with realistic recovery odds — that itself raises trust.
Couple verified
What it proves: two independent Realr accounts have mutually confirmed they're in a relationship. Both accounts had to actively accept the link. Either party can revoke at any time.
What it doesn't prove: the legal status of the relationship (marriage, civil union), how long they've been together, anything about their financial or living arrangements. It's a social claim, not a legal one.
Useful for: couples who want shared trust when they're doing things together — joint accounts, co-hosting, joint creator businesses, long-distance relationships sharing one trust profile. The privacy guard means neither person's private data leaks to the other.
How they combine
Each badge is independent evidence. A profile with three or four of them is meaningfully stronger than a profile with one, not in a linear way — in a multiplicative way. The reason: the cost of forging multiple independent verifications climbs much faster than the cost of forging one. That's the whole point of layered identity.
Rule of thumb for someone reading a profile:
- Email + phone: baseline contactability. Acceptable for low-stakes interactions.
- + Selfie: proves a real human is behind the account. Suitable for most buyer-seller transactions.
- + Government ID: the strongest commonly- available identity claim. Appropriate for higher-value transactions, partnership-level trust, dating-app second- sourcing.
- + Payment method: closes the recourse loop. You know a payment came from a real instrument that can accept a refund.
What Realr never shows publicly
The badges show what was verified — never the raw data. Government-ID-verified users get a green check; the document itself is encrypted, never displayed, and only used for the verification + the audit trail. Same for phone, email, payment instrument. Nothing sensitive is on your public profile by design.
This is the privacy guard that lets Realr be both public and safe. Buyers see "verified", not the document.
The longer arc
Identity verification has been treated as a single binary for a decade because the platforms that handle it (Twitter, Instagram, dating apps) had no incentive to expose the underlying complexity. The unfortunate result: a market that treats "verified" as synonymous with "safe to transact with", when the two have very different thresholds.
Layered verification — six independent badges, each meaning something specific — is the honest version. Adopting it across the open internet is how trust starts to actually compound instead of getting compressed into a confusing single flag.
See /identity-verification for the product surface. Or, if you'd just like one of these badges yourself, claim your handle and start with email + phone — both are free.