The release your product triggers deserves a signature your customer’s CFO can’t disown.
Your platform moves your customers’ money. Manav adds one call before release: a passkey signature from the named approver, bound to the exact amount, beneficiary and account — and an Ed25519 receipt their bank, auditor and insurer verify offline. The deepfake on the call can’t produce it.
The receipt below was signed and checked in this tab, with zero network calls.
Cryptographic fields
The last line of defense on a large payment is a phone call — a channel NIST SP 800-63B-4 now classifies as restricted
and not phishing-resistant, carrying a voice that deepfake attempts rose 1,300% against. FS-ISAC, the ABA and BPI concede the callback assumes threat actors won’t have compromised the callback channel itself
— and recommend FIDO2 passkeys instead. Your customers are running that control inside your product today.
Three integration points. Your brand, our receipt.
// Before the consequential action, from your backend: const receipt = await manav.sign({ action: 'wire.release', payload: { amount, currency, beneficiary, account }, approver: payment.authorizedApprover, assurance: 'passkey+liveness', }); if (receipt.ceremony === 'completed') proceed(receipt.id); // Anyone verifies the receipt offline against our published JWKS — forever.
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.
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.