Manav.id
Get API key Book a demo
For title, escrow & closing platforms

The closing wire that can’t follow emailed instructions.

Your platform sits on the largest wire most people ever send. Manav gates disbursement on a passkey signature from the verified party — bound to the exact amount and destination account — so instructions that arrived by email can’t move money by themselves.

Talk about embedding this See where it sits

The receipt below was signed and checked in this tab, with zero network calls.

Never in your money pathNo biometric vaultVerify without us, forever
MANAV RECEIPT · v1 network: idle
…
Generating key & signing…
Ed25519 · WebCrypto · in this tab
actionclosing.disbursement amount USD fileescrow #E-20841 · payoff destinationCitibank ••••8830 (verified) signed bymanav:human:7f3a9c…e21b · escrow officer assurancepasskey + liveness challenge issued—
Cryptographic fields
nonce— kid— sig—
Edit the amount. Watch the signature fail.
The loss your customers are carrying
1 in 3

real-estate transactions saw wire-fraud attempts; full recovery in only 29% of loss cases.

ALTA survey (2021, latest)
$389,125

median loss when a mortgage-payoff wire goes to a fraudster.

CertifID, 2026
$275.1M

reported real-estate fraud losses in 2025 — with BEC at $3.04B across sectors, closings a prime target.

FBI IC3 2025
January 2026, one escrow account

Chicago Title is suing after $4,156,888.79 left escrow on January 21–22, 2026 — wired on emailed instructions from a compromised thread, unrecovered at recall. Account-verification tools score the destination; call-backs authenticate a voice deepfakes now fake. Neither binds a human signature to the exact disbursement. That’s the missing gate.

Chicago Title v. Earnspark, S.D.N.Y. 2026 · Complements account verification — they vet the destination once; we sign the disbursement every time.
What fails without it: the spoofed payoff letter, the last-minute “updated instructions,” the seller impersonator — none can produce the enrolled officer’s (or buyer’s) signature over the real amount and account.
What your platform gains: “signed disbursement” as the tier above account verification, a receipt underwriters can price, and 56%-of-customers-never-return risk (CertifID) converted into a trust feature.
Where it sits in your product

Three integration points. Your brand, our receipt.

Disbursement release

No wire leaves escrow without a signature over amount + destination. The 30-second ceremony replaces the callback queue at cutoff time.

Instruction changes

Any change to payoff or proceeds instructions requires the counterparty’s enrolled signature — the emailed “update” is inert.

Consumer-side signing

Buyers sign their cash-to-close from their own phone — enrolled at contract, verified at closing, no app install.

// Before the consequential action, from your backend:
const receipt = await manav.sign({
  action: 'closing.disbursement',
  payload: { fileId, amount, destAccount },
  approver: escrowOfficer.principal,
  assurance: 'passkey+liveness',
});
if (receipt.ceremony === 'completed') proceed(receipt.id);
// Anyone verifies the receipt offline against our published JWKS — forever.
Structurally neutral. The receipt format and verifier are Apache-2.0 open source, filed at the OpenID Foundation and IETF. You embed a standard, not a competitor.
Nothing of yours flows through us. Payloads never leave your systems — only hashes. A Manav outage can’t block your product: issuance pauses, every existing receipt still verifies.
Verification is free for everyone, forever. Your customers’ auditors, banks and counterparties check receipts with one public key — that’s what makes the receipt worth issuing.
We’re early and say so. No fake logos — the mechanism runs in this page. The wire-release playbook — statutes, cases and the auditor’s view →
Try it before you talk to us

Run the ceremony yourself. Then try to fake it.

A controlled sandbox of the exact flow above — your system asks, the enrolled human signs on their own device, a receipt is issued, and you attack it. Real Ed25519, in this tab, nothing sent anywhere.

Next step

A 30-minute integration conversation.

Bring the flow in your product where this belongs. We’ll run the ceremony on it and hand you a receipt you can verify yourself before the call ends — and a straight answer on what an embed looks like commercially.

Open the live demos no account · 2 min Run the security review everything inspectable Read the docs demo key works on localhost
Step 1 of 2

Talk to us about embedding

No biometrics, no tracking pixels. Your email goes to one inbox and nowhere else.
Step 2 of 2

Where would it sit?

Something went wrong. Email [email protected] and we’ll sort it.
✓

Request received.

You’ll get times from [email protected] within one business day — reply to lock one in.

We’re early, and we’d rather say so than fake logos: the receipt format and verifier are public, Apache-2.0 open source, and the mechanism above just ran in your browser. Judge it before you ever talk to us.