Wires, payouts & refunds
Bind approval to the exact amount and beneficiary. A changed invoice or swapped account number invalidates the approval automatically.
Development preview · verification infrastructure for product teams
Trust, but verify.
Every time.
Wire transfers, password resets, payout changes, admin actions — the requests that hurt most when they're faked. This local preview demonstrates how EasyAuths can bind an authenticated approval to exact request details. Production identity, delivery, managed keys, infrastructure, and independent review remain on the roadmap.
Not generally available yet. Tell us what you need to verify and we will get in touch — demand shapes what we build next.
Local demo workflow Prototype signed receipts Tested single-use state
Concept interface
9:41● ● ●
Planned native flow
Approve wire transfer
Requested by Jordan Lee · Northstar
$24,750
FromBusiness checking ••4821
ToFirst National ••9077
RecipientApex Hosting LLC
Wire instructions arrived by email. Verify before the money moves.
receipt: ES256 ✓
Designed for approval workflows in
FintechHealthcareSaaSMarketplacesInternal tools
Where sessions fall short
Every product has actions that deserve their own proof.
A logged-in session proves someone signed in — once, on some device, maybe hours ago. These are the moments your product should demand more, and where EasyAuths drops in.
Resets & profile changes
Password resets, email and phone changes, new payees, new devices — the exact steps attackers chain. Challenge them out-of-band before they stick.
Destructive & privileged ops
Deleting a workspace, exporting customer data, granting admin, changing billing. One compromised admin session shouldn't be enough.
Consent & release
Releasing records, e-prescriptions, changing a care plan. Capture a context-bound, auditable approval from the right person, every time.
Withdrawals to new destinations
Crypto withdrawals to fresh addresses, seller bank-account changes, first payouts. The highest-fraud moments in any platform that moves value.
Break-glass & deploys
Production access, support impersonation, config pushes. Give internal tools the same approval rigor you give customers — with receipts for the audit.
The platform
One narrow, versioned integration surface.
Keep your frontend, your login, your user model. EasyAuths handles only the narrow ceremony between “someone asked” and “the action may execute” — challenges, device signing, policy, receipts, and audit.
const txn = await easyauths.transactions.create({
actionType: "MONEY_MOVEMENT",
title: "Approve vendor wire",
protectedResource: "Operating ••4821 → Vendor ••9077",
amount: 24750, currency: "USD",
recipientLabel: "Finance approvers"
});
// The approver confirms on an enrolled device …
const result = await easyauths.transactions.consume(txn.id, {
applicationId: "app_ledger"
});
// ES256-signed receipt — verify, then execute.1
Create the exact request
Your backend posts the action, amount, resource, and intended approver. Protected fields are canonicalized into the receipt digest — change one and the approval dies.
2
We challenge the right person
The current prototype demonstrates web approval. The production roadmap adds embedded web/native SDKs and independent push through the standalone EasyAuths apps.
3
Consume once, then execute
Your backend atomically consumes the approval and verifies an ES256-signed receipt against your tenant JWKS. Single use, audience-bound, fully audited.
Also for people, not just platforms
No engineers? It works out of the box.
The local Request Authentication preview lets a team create a request in the workspace and complete a WebAuthn-backed web review. Reliable managed email, production identity, native approval, and customer-ready records are not yet available.
Confirm the wire is real
An emailed payment instruction gets a code your finance team verifies before a dollar moves — even if the email account was compromised.
Know your caller is genuine
Help desks and IT verify the person — not the voice — before resetting a password or changing account details.
Approve sensitive changes
Direct-deposit updates, contact-info changes, benefits elections — approved by the actual employee on an enrolled device.
Honest assurance
We show what was proven—no more, no less.
Sender context recorded
The prototype records the requesting actor and assurance label. Production identity verification and revocable sessions are still required before those labels are customer-safe.
Out-of-band verified
In production, this label will require a separately enrolled device to display the exact context and return verifiable local-user evidence. The prototype simulates that ceremony.
Action authorized
The required approvers satisfied policy and produced an audience-bound, single-use receipt.