Verified
The registered person approved this exact request on their trusted device. You can act on it.
Cazuri de utilizare
Not "is this a real employee", but "does this person hold this authority, right now, in this organisation".
The problem
Systems verify that someone works at a company and then infer what they may do from a job title in a signature. Roles change, people leave, and permissions granted for one project quietly outlive it.
What changes
Every approval names the organisation and the role being exercised. Authorisation is checked server-side against the current record at the moment of use — not against something cached when the session began.
How this works
Possible outcomes
A verification request has more than two endings. Treating anything other than an explicit approval as approval is how verification systems fail people.
Verified
The registered person approved this exact request on their trusted device. You can act on it.
Rejected
The registered person saw this request and refused it. Treat it as fraudulent and report it.
Not verified
Nothing was proven, either way. Do not act on the request until you confirm it independently.
No response and Not verified are never shown as approval, and they never turn into approval by waiting.
Honest limits
REAL AUTH reports the roles an organisation has recorded. It cannot know whether those records reflect reality, whether a departure was processed, or whether a role was granted appropriately. Authority verification is only as trustworthy as the administration behind it.
CEO fraud, fake suppliers, fake support desks. Check that the person is real and that they hold the authority…
Află mai multe →Changing a payout account, adding an administrator, issuing a production key — approve the exact change, not t…
Află mai multe →When a supplier's bank details change, check the change with the supplier — not with whoever sent the email an…
Află mai multe →A free sandbox, real flows, and no card required.