Avouch

Nothing irreversible without proof of who approved it

Avouch holds a risky payment until the person who should approve it signs the exact amount and payee with their passkey, and leaves a receipt anyone can check.

Request accessSee how it works

Follow one payment from held to proven

09:12:03Held.

New bank details and fourteen times the usual amount. The rest of the run goes; this one waits for Dana.

09:14:07Signed.

Dana reads the exact payment on her phone and approves it with her passkey. No password, no app.

09:14:07Proven.

Her signature covers the SHA-256 of the sentence. Anyone can check it, without an account.

09:14:08Recorded.

The receipt joins a log that can only grow, and the payment is released.

Two recent losses began with a convincing request.

In both cases, nobody could show afterwards who had said yes.

$25M

Hong Kong, 2024. An employee joined a video call with the CFO and four colleagues. None of them were real, and he released the money.1

About $100M

Las Vegas, 2023. Someone called the service desk and asked for a password reset. There was no deepfake and nothing to detect.2

  • 79%of finance teams hit by attempted or actual payment fraud.3
  • $122,000average business email compromise loss.4
  • $250,000typical social-engineering insurance sublimit.5

Most payments are never interrupted.

Measured over a year of accounts payable: 210 approvals, 204 cleared without interrupting anybody. The 6 that stopped were the 6 planted attacks.6

Each line is one approval. The six in blue were held for a signature; the rest went straight through.

  • 204of 210 approvals cleared with nobody interrupted.
  • 6 of 6planted attacks held for a signature.
  • 0legitimate payments held.

Run the same year against the live engine

One API call, made before the payment file is released.

Your ERP already makes HTTP requests. Avouch adds one.

Identity
5 minutesA standard OIDC app.
Each approver
SecondsA passkey your identity provider already issued.
Your ERP
An afternoonOne call before the payment file goes.
POST /v1/gate
{
  "type": "payment_approval",
  "principal": "dana@meridianfreight.com",
  "requester": "ops@meridianfreight.com",
  "context": {
    "id": "PAY-1041",
    "amount_usd": 2400000,
    "payee": "NORTHWIND LOGISTICS",
    "display": "Approve $2,400,000.00 to NORTHWIND LOGISTICS"
  }
}

Connects to Okta, Microsoft Entra ID, Google Workspace, Auth0 or any oidc provider, and to NetSuite, QuickBooks, Ramp, Bill.com and Slack.

Three pieces, each one you can check.

Assembled, not invented. The parts are standard; pointing them at your own irreversible act is not. How it is built

The gate

Sits before release, inside the payment run you already have. It decides what waits; it never moves money itself.

The passkey

Lives on the approver’s own phone or laptop. A passkey works only on the site it was made for, so there is no password to phish.

The log

Append-only and chained. Anyone holding a receipt can check it was in the log, and that nothing before it moved.

What Avouch does not do.

A deceived approver
We do not stop one.If they are not a required signer, the payment still goes. The receipt shows exactly who said yes, and to what.
The fake itself
We do not spot it.A passkey cannot tell a fingerprint from a PIN. What it proves is which person’s device signed which sentence.
Certifications
No customers, no SOC 2, no pen test.A readiness assessment, which is the better thing to hand over.
Independent witness
None runs yet.The monitor is built. Nobody outside this company holds a key.

The full security and policy page

Start with an export you already have.

Avouch runs read-only first. Nothing is blocked until you choose to enforce it.

Request access

Tell us what you approve.

We will come back with an exposure report from an export you already have. No connector, nothing blocked, nothing stored.