PayProof

An invoice payment agent · Agents You Can Audit

Check the change before paying the invoice.

A supplier email asks a Canadian construction business to use a new bank account. PayProof holds the payment until a separate person checks the saved supplier contact and approves the exact details.

Real language model and MongoDB Atlas.
Synthetic business data. Simulated payments.

PayProof holds a CAD 4,800 invoice because the saved account ends in 0042 and the requested account ends in 7719.
0042 7719A changed destination pauses the payment.

The Canadian Anti-Fraud Centre · May 13, 2026

CAD 3.5 million
recovered in one
payment-redirection case.

Read the CAFC news release

The CAFC reported helping recover approximately CAD 3.5 million for a Quebec business after criminals impersonated legitimate contacts and supplied false payment instructions.

The same release identifies construction and contracting businesses among common targets. It recommends checking payment instructions independently and confirming bank changes through trusted contact information.

Incoming emailNew account: 7719
Saved supplier recordAccount: 0042
HoldCheck the saved contact

The email can propose.
Your team gives permission.

For the Agents You Can Audit track, permission comes before action. MongoDB Atlas holds the identities, supplier and policy revisions, verification, and approval used by the server to decide whether a payment may run.

Read the request

The model extracts the invoice and looks up the saved supplier. Email text can't change the trusted contact or grant approval.

Check and approve

A separately signed-in person checks the trusted contact, then approves the exact invoice revision, amount, and destination. The server binds that permission to the current supplier and policy revisions.

Execute and check

A separate HTTP service records the simulated payment. PayProof matches its receipt to the approved details and saves the result.

The model reads.
The server checks.
Atlas remembers.

PayProof connects an untrusted email to a controlled payment workflow. The server enforces the rules using current records in Atlas. A separate person gives permission for a specific payment; the model cannot grant that permission itself.

Finance operatorSupplies the invoice email
Language modelExtracts supplier, amount, and account
PayProof serverCompare → hold → check authority → dispatch
Separate approverVerifies through the saved contact;
approves exact payment details
MongoDBAtlasPeople · suppliers · approvals
Current state · decision history
HTTP payment simulatorRecords one operation;
returns a matching receipt
The server reads trusted records and saves decisions in Atlas. Only a checked dispatch reaches the simulator; its result returns through the server to Atlas. MongoDB® is a registered trademark of MongoDB, Inc. Used here to identify the database; no endorsement is implied.

What each part is responsible for

Language model
Turns email text into a proposed invoice using limited server tools. Email instructions cannot replace a saved contact or approve a payment.
PayProof server
Applies policy. Before dispatch, it checks the current user, approver, supplier, invoice revision, and exact approved details.
MongoDB Atlas
Stores the trusted supplier and identity records, invoice, verification, approval, state, and audit events. Atlas supplies the data for the server's checks.
ElevenLabs · read-only voice Q&A
STT sends the spoken question to the server. The server reads only the signed-in user's authorized Atlas evidence; TTS reads the answer. This path cannot approve, change an account, or pay. It is separate from the overview video's narrator.
Payment simulator
A separate HTTP service records the approved operation. It has no bank connection and moves no money.

Check authority before dispatch.

The server uses a transaction to check the role, tenant, invoice and supplier revisions, policy, and exact approval against current Atlas records. Account 0042 differs from 7719, so a separate person must first verify the change through the saved contact.

Approval binds the exact payment.

Changes require new approval. An approval covers a specific revision, amount, currency, destination, supplier revision, and policy revision. Changing the amount clears the old verification and approval. The server rejects a dispatch using the old revision.

One operation. One entry.

Concurrent dispatch requests converge on the same operation ID. The simulator uses a unique tenant-and-operation key, so retrying that operation produces one ledger entry. The server checks its receipt before marking the invoice paid.

Follow one invoice
from email to evidence.

These are actual screens from a synthetic demo for Maple Ridge Construction and Cedar Supply Co. Open any screenshot to read it at full size.

Invoice email requesting CAD 4,800 and a new bank account, with the Process invoice button.

1 · Finance operator

Start with the supplier email.

Sign in as the operator, paste the invoice email, and choose Process invoice. The model looks up the supplier and proposes the payment.

This example asks for CAD 4,800, a new account ending in 7719, and an urgent payment. The saved account ends in 0042, so the server puts it on hold.

When repeating a demo, change the invoice number. Duplicate supplier invoice numbers are intentionally rejected.

The payment approver records verification using the saved supplier contact Alex Chen and reviews the exact payment details.

2 · Separate payment approver

Use the contact you already trust.

Sign in separately as the approver. Check the change through the saved supplier contact, then choose Record verification and Approve this payment.

The agent can't approve its own request. The email's replacement phone number doesn't become the trusted contact.

The contact and confirmation shown here are a synthetic role-play. No phone call was made.

The invoice amount is CAD 4,900 at revision 2 and the bank-change hold returns after the old approval is invalidated.

3 · Change the payment details

An approval has a precise target.

$4,800$4,900

Use Amend payment details and save an amendment. Changing the amount or destination clears the previous verification and approval.

The old revision can't be dispatched, even with a direct API request. The actual server response in this demo was Payment revision changed.

The revised invoice is approved and its CAD 4,800 simulated payment is confirmed.
Fresh approval, then a matching receipt.
The decision trail shows approval invalidation, the denied old revision, independent verification, fresh approval, dispatch authorization, and payment confirmation.
The people, revisions, and decisions stay together.

4 · Execute and inspect

Approve again.
Pay once.
Read the trail.

Return to the correct amount, record a fresh check, and approve. As the operator, choose Run payment agent.

The demo produced 1 simulated ledger entry and 13 recorded actions. The receipt matched the approved payment details.

Ask about a payment.
See the evidence behind the answer.

Open an invoice and use Ask about this invoice. Choose Record question, ask your question, then choose Stop and ask. You can also type a question. The answer includes readable Atlas records and an audio player.

Ask why a payment was held, who approved it, what changed after an amendment, or whether the simulated payment completed. The server uses only this invoice's evidence and checks your current identity and tenant before answering.

Question audioElevenLabs turns your question into text.
Answer + supporting recordsThe model explains the authorized Atlas snapshot. The screen shows the records it cites.
Spoken answerElevenLabs reads the explanation. The existing controls handle verification, approval, and payment.

Voice questions read evidence. They cannot approve, send money, or change an account. The recorded 60-second demo shows the payment workflow; this voice panel was added afterward.

Atlas keeps permission
and evidence in reach.

Invoice documents hold verification, approval, operation IDs, and the action timeline. Separate collections store suppliers, identities, and denied security events.

State and history update atomically. The same invoice update saves the new state and appends its audit event. The dispatch transaction checks current authority and revisions before the HTTP payment call. The simulator uses one unique ledger key per tenant and operation to prevent duplicate entries.

Read the code and run locally

What you're looking at

Real
Tool-calling LLM, MongoDB Atlas, ElevenLabs speech recognition and synthesis, server-side permission checks, HTTP requests, and receipt matching.
Synthetic
Companies, invoices, contacts, and human confirmation records.
Simulated
Payments recorded in a separate service. No bank connection, funds moved, or emails sent.

This is an application-level audit trail. Database administrators can change stored data; the demo doesn't claim tamper-proof records or complete fraud detection.

See it as a six-slide pitch.

Embedded demo clips play without API calls. Right goes forward, left goes back, and down restarts the current slide. Each clip holds its last frame, then loops.

Open pitch slides