Approvals that cannot be faked or replayed
Approvers review the exact amount, destination and checks, and confirm with a passkey bound to that transfer. Notifications reach them by email and on their phone the moment something waits.
9:41
Tuesday 7 October
CChainvara · now
Approval needed
48,000 USDC to Northwind Ltd
Face ID
Controls you can prove
Separation of duties
Requesters cannot approve their own transfers unless your policy allows it.
Passkeys bound to the intent
The passkey signature covers the transfer's intent hash: it cannot be reused for anything else.
Two-factor everywhere
Require TOTP for every sensitive action; sign-in and code guessing are throttled.
Phone notifications
Web Push and email to every person who can approve, as soon as approval is needed.
Admin quorum
Policy, team and execution changes need a second owner or admin.
Integrity checked
Before execution, the intent hash is recomputed: any change after approval stops the transfer.
How it works
- 1
Add approvers
Invite your team with roles; approvers add a passkey in Settings → Security.
- 2
Get notified
Approvers turn on phone notifications.
- 3
Approve with a touch
Review the transfer and confirm with Face ID, Touch ID or a security key.
Works best with
Ready to see Chainvara in action?
Start free on test networks. Move to production when your controls are in place.