Payment & treasury change control.
When someone asks you to change where money goes, Foundry makes the real authorized signer prove it, cryptographically, before the change takes effect.
Book a demoThe scenario
A vendor, contractor, or counterparty requests new remittance bank details, by email, phone, or portal message. Your team updates the payee record. The next payment run sends public funds or corporate cash to an impersonator.
This is change control impersonation: the change looks legitimate; only the authorized signer can know if it is real.
The exposure
76%
of U.S. organizations experienced attempted or actual payments fraud in 2025.
AFP Payments Fraud and Control Survey, 202674%
were affected by business email compromise in 2025.
AFP Payments Fraud and Control Survey, 2026$3.05B
in losses to business email compromise were reported to the FBI in 2025.
FBI Internet Crime Report, 2025
Since 2026, Nacha’s rules require risk-based processes to identify ACH payments initiated due to fraud, including payments induced under false pretenses: someone misrepresenting their identity, their authority to act for another party, or the ownership of the account to be credited. Among the procedures Nacha names:
“change controls regarding payment information and instructions for vendor and payroll payments.”Nacha Operating Rules, Fraud Monitoring Phase 2, effective June 19, 2026
What goes wrong today
- Callback verification can be social-engineered.
- Email and ticket approvals are spoofable and not bound to the exact payee record.
- ERP and treasury systems record that someone clicked approve, not that the right signer authorized this change.
- After fraud, investigation relies on narratives, not independently verifiable proof.
What changes at execution
Before the payee change executes in your financial system, Foundry verifies a trustable bound to the exact change: tamper-evident content, authorized signers, and a trust report your consuming application uses to allow or block the update.
Fraud is blocked before the payment run, not investigated after money moves.
| Time | Change | Vendor | Signed | Status |
|---|---|---|---|---|
| 09:14 | Bank account | Helion Components | –0 of 22 of 2 | ReceivedChallenge sentSignedReleased |
| 08:52 | Payee update | Northwind Supply | 2 of 2 | Released |
| 08:05 | Bank account | Kestrel Freight | 0 of 2 | Rejected |
01A bank-detail change arrives. The payee record does not change yet.02Foundry challenges the vendor’s authorized signers.03Both sign on their own devices, bound to this exact change.04The trust report passes. The payee record updates, with proof.
Soft gate, hard gate
Soft gate (start here): An operator receives the change out-of-band, dispatches a verification challenge to known signers, and only proceeds when cryptographic approval settles, even if the ERP is not yet wired to Foundry.
Hard gate (production): Embed the Trustables API in treasury, ERP, or AP so the payee record cannot update unless verification passes.
See it in actionEvidence for compliance
Trust reports and exported verification bundles give audit and treasury oversight teams cryptographic evidence: who signed, whether the artifact was intact, and whether policy was satisfied.
Verifiable independently of your application logs.


