Verified
The registered person approved this exact request on their trusted device. You can act on it.
Zastosowania
Payment fraud
Confirm the exact amount, beneficiary and destination account, bound together, before the money moves.
The problem
Confirming the supplier is not confirming the payment
Most payment fraud does not invent a fake company. It takes a real relationship and changes one field: the account number. Everything else — the letterhead, the invoice number, the contact — is genuine, which is exactly why it passes review.
What changes
Bind the approval to the values, not to the relationship
The approval covers this amount, to this beneficiary, at this account, for this reference. Change the destination and the previous approval is not merely stale — it is cryptographically invalid for the new instruction, and the system says so.
How this works
Approving a payment instruction
- The instruction is composed Amount, currency, beneficiary, destination account, reference, and an expiry.
- It is shown in full to the approver Not a summary and not a total — the actual destination account, on their own device.
- They approve those exact values The signature covers every field. There is no version of this approval that covers a different account.
- Any change invalidates it Alter one digit of the destination and the approval no longer matches. A fresh one has to be requested, and the change is visible.
Possible outcomes
Four answers, and one of them is silence
A verification request has more than two endings. Treating anything other than an explicit approval as approval is how verification systems fail people.
Rejected
The registered person saw this request and refused it. Treat it as fraudulent and report it.
Expired
The request was not answered in time and is no longer valid. Start again if it was genuine.
No response and Not verified are never shown as approval, and they never turn into approval by waiting.
Honest limits
What this does not fix
REAL AUTH verifies that a specific person approved specific values. It does not know whether those values are correct, whether the supplier is honest, or whether the approver was deceived into approving a genuine-looking instruction. It removes silent alteration as an attack; it does not remove the need for the approver to read what they are approving.
Related use cases
Invoice fraud
When a supplier's bank details change, check the change with the supplier — not with whoever sent the email an…
Dowiedz się więcej →Business impersonation
CEO fraud, fake suppliers, fake support desks. Check that the person is real and that they hold the authority…
Dowiedz się więcej →Crypto and wallet verification
Proving ownership of a wallet is not the same as proving a person intended this transaction. Confirm both.
Dowiedz się więcej →Try it against your own application
A free sandbox, real flows, and no card required.