SignedBySign in

Verified Badge for Real Estate

Wire fraud costs real-estate buyers real money. Prove your closing documents are genuinely from you.

A scammer who intercepts a closing email thread can send fake wire instructions that look completely legitimate — costing a buyer their down payment. Seal your real documents first: a hash and identity-verified proof your client can check before they wire anything.

Now built right into your dashboard — seal your first document free today.
Generate Your Proof →

Free to start, no card required — takes about a minute to set up.

A Verified Badge stamped in the corner of a real-estate closing statement — the SignedBy mark, a scannable QR code, and a verification link

How it works

1. Verify once

A one-time government-ID check (about a minute, hosted by Stripe). Reused across every future seal — no re-scanning your ID each time.

2. Seal the document

Upload your finished wire instructions or closing document PDF from your dashboard — SignedBy hashes it, timestamps it, and generates your badge.

3. Embed the badge

Drop the badge on the document before you send it. A client scans it and lands on a public ledger page — no account needed.

What this actually proves

A Verified Badge is a provenance and integrity proof, not a fraud-detection tool. It confirms this exact file existed, unaltered, as of a cryptographically verified timestamp, sealed by an identity-verified person — a real, useful, different claim from “this looks legitimate.” Honest framing, on purpose: overclaiming here would undercut the one thing that actually holds up under scrutiny.

Generate Your Proof

Free to start — 3 seals a month included, no card required. Need more? Pro plan or higher gets unlimited sealing, no per-seal charge.

Generate Your Proof →

Frequently asked questions

Does this stop wire fraud?

No — and it doesn't claim to. A Verified Badge proves your real wire instructions or closing document existed, unaltered, as of a cryptographically verified timestamp, sealed by an identity-verified person. That gives your client an actual way to check before they wire money, instead of just trusting that an email looks right — it isn't a guarantee nothing bad can ever happen.

What does the client actually see?

A badge on your document — a QR code, the SignedBy mark, and a short verification link as plain text, so it reads as legitimate even printed or screenshotted. Scanning or visiting it lands on a public ledger page: your name, when the file was sealed, and confirmation it hasn't been altered since. No account or login needed to check it.

What if my identity check is old?

Your first seal verifies your identity via a government-ID check (about a minute, hosted by Stripe). Later seals reuse that same verified check rather than re-scanning your ID every time — cheaper and faster. The ledger page always shows "identity verified on [date]" alongside "sealed on [date]" as two separate facts, so it's clear if the identity check itself is from earlier than this specific seal.

Does this work for non-PDF files?

PDFs only for now. If your closing documents or wire instructions come from another system as something else, export or print them to a PDF first, then seal that.

What plan do I need?

Any plan, including Free, no card required. Free includes 3 Verified Badge seals a month. Pro plan or higher gets unlimited sealing, no per-seal charge. Seal a file right from your dashboard's New Document menu — developers can also do this from Console chat or the API, see the developer docs.

What actually makes the timestamp "cryptographically verified"?

Every seal is submitted to a real Time Stamping Authority (Sectigo's public RFC 3161 service, with FreeTSA as an automatic fallback if Sectigo can't be reached) that signs the file's hash together with the time. That's independently verifiable by anyone, trusting only the TSA — not just a date in SignedBy's own database. The ledger page at signedby.ai/verify shows which TSA backed a given seal.

Also on SignedBy: Console · Magic Quote · Verify a document · API & MCP docs