Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Dashboard ↗ JA
Home / Critical Brief / No. 185
No. 185 Critical Brief · Regulatory Attribute Proof

Studco: Payments went to an account named by a party posing as its supplier, and the receiving bank was held not liable (US Fourth Circuit ruling)

$559K
Total of four ACH payments sent to what Studco believed was its supplier's account (court's account: $558,868.71). Not recovered
10-01→11-21
From the first email announcing the bank change to the receiving bank learning of the scam (2018, per the opinion)
03-26→10-06
From the Fourth Circuit rejecting the receiving bank's liability to the Supreme Court denying review (2025)
CountryUS
Incident date2025-03-26
Published2026-11-05
AuthorsLemma Critical Team
Contents
  1. 01Summary
  2. 02What got through
  3. 03Pre-execution check
  4. 04What Lemma does
  5. 05Facts and timeline
  6. 06Sources

Summary

  1. 01What happened

    Each payment was deposited into the account number written on the payment order. The account belonged not to the supplier but to an individual customer of the receiving credit union.

  2. 02What was found

    Per the opinion, the credit union’s system generated a name-mismatch warning for every deposit, but such warnings ran to hundreds or thousands a day and no one read them. The Fourth Circuit held that under the Uniform Commercial Code (UCC) a beneficiary’s bank may rely on the account number and is not liable unless it actually knew that the name and number did not match. The Supreme Court declined review, so that holding stands.

  3. 03Why it got through

    A receiving bank may deposit by account number alone and will not necessarily stop a deposit when the name differs. Whether the name and account belong to the real vendor is for the paying side to check before sending.

Exhibit 1Detection vs pre-execution check

A pre-execution check means checking a change to a vendor's bank account through a registered contact other than the email that delivered it before using it for payment. Detection means noticing the scheme after the transfer. The ruling dealt with the receiving bank's liability. Dates are in 2018, per the majority and concurring opinions.

Pre-execution check · on the paying sideCheck the account change with the vendor through a contact other than the email, then pay
What was confirmedEmails posing as the supplier changed the account
$559K in four payments went to someone else
Detection · worked after the transfersMismatch warnings were generated but unread; the scam surfaced when the sender reported it
10-01
Emails posing as the supplier announce a bank change
10-04
A deposit report shows a name-mismatch warning
11-13
Last deposit (per the concurrence)
11-21
The receiving bank learns of the scam from Studco's president

What got through

What got through
Four ACH transfers that Studco ordered as payment of invoices from its supplier, Olympic Steel. The beneficiary was named as “Olympic Steel Inc”, and the account was one at 1st Advantage Federal Credit Union given in emails posing as the supplier. The total was $558,868.71 (per the opinion).
What reached the receiving side
Per the opinion, the beneficiary’s bank deposits ACH orders automatically by account number, without anyone reading the order. When the name differs from the account holder, its system generates a warning, but it notified no one, and the reports were not reviewed as a matter of course. On the paying side, per the opinion, emails in the name of the supplier’s account manager announced a bank change and supplied new account details.
Not disclosed
How Studco’s email system was intruded upon. The date and amount of each of the four transfers (the opinion says payments began a few days after the first email). How the account change was registered and approved internally. What happened after remand, and whether Studco sought recovery from its own bank or others.

Pre-execution check

Whatever the route, the condition for telling them apart is that the paying side checks, before transferring, that a changed account is the vendor’s, through the vendor’s registered contact and not the email that arrived. It cannot rely on the receiving bank to match the name.

Pre-execution gate
Before transferring to a changed account, check that account with the vendor's registered contact, not the email that delivered it.
Who approves
The vendor. It approves the account change through its registered contact. That contact is one registered beforehand, such as a registered phone number or a signature with the vendor’s key, not the email that delivered the change or a number written in it.
Where it is checked
The step that changes a payee account, and the approval before the first transfer to a changed account. Accounts that cannot be matched to the vendor’s approval are held and not used for payment.
What is recorded
Which account change was used for payment, who checked it, and how, so you can show what was checked before sending for recovery, investigation, insurance or litigation.

The name mismatch was recorded by the receiving bank’s system with each deposit, but it was not tied to any step that would stop a transfer. A similar case where a lookalike domain led to a payment is the City of Liberty (an invoice arrived from a domain made to look like a vendor’s). Cases where email exchanges with a counterparty were taken over are Modalis and Ovid Therapeutics (a payment went to a party posing as a development partner).

What Lemma does

Lemma builds the pre-execution check into the step that changes a vendor’s bank account and the approval before a transfer is carried out. It does not look for intrusions or impersonating emails; it confirms on the paying side, before the transfer, that a changed account is one that could be matched to the vendor’s approval.

Industries and operations to watch

IndustryManufacturing
Companies that pay long-standing suppliers by ACH or transfer for each invoice. Per the opinion, the two companies had done business for over nine years.
IndustryFinance
Banks and credit unions that, as the beneficiary’s bank, deposit automatically by account number. Decide who looks at name-mismatch warnings, and when.
OperationBank account changes
Registering and changing vendors’ payee accounts.
OperationApproval
Approving the first transfer to a changed account.

Current controls vs Lemma

The route in this case ran through column 1 (an account change delivered by emails posing as the supplier) and column 2 (transfers to the changed account), and ended in column 3 (deposit at the receiving bank) into an account in another name. Column 4 is the intrusion into the sender’s email system that the court described.

Control Account change request Transfer to the changed account Deposit at the receiving bank Intrusion into the sender’s email
Checking the sender (domain, signature) Partial Not applicable Not applicable Not effective
Transfer approval (checking the contents) Not applicable Partial Not applicable Not effective
Receiving bank’s name matching (automatic warnings) Not applicable Not applicable Partial Not applicable
Lemma (pre-execution check) Effective Effective Not applicable Not effective

Checking the sender is hard when a domain is made to resemble the real one. Transfer approval cannot tell a request apart by its contents when the beneficiary name and amount match a real transaction. As for the receiving bank’s name matching, per the opinion the warnings were generated but no one was notified, and under the UCC the bank had no duty to check. Lemma does not work on the receiving bank’s side and does not deal with the intrusion into the sender’s email; it confirms on the paying side, before the transfer, that a changed account could be matched to the vendor’s approval.

Note: Lemma’s check works only when it is built into the step that changes accounts and the approval before transfer, with the vendor’s approval received through a registered contact or key other than the email that delivered the change. It can be passed if the registered contact itself has been altered, or if the check uses a contact given in the change email. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions.

CheckChecklist

Three things to confirm about payments to vendors

  • Do you have a step that holds the first payment to a newly changed account before it is carried out?
  • Do you have a step that confirms a vendor’s account change through a contact registered beforehand, not one given in the email that delivered it?
  • If a scheme is found after a transfer, is there a set procedure to contact your bank, the receiving bank and law enforcement immediately?

Facts and timeline

Parties
Studco Building Systems US, LLC, a metal fabricator in Webster, New York, and 1st Advantage Federal Credit Union in Newport News, Virginia. The supplier was Olympic Steel, Inc., in northern Ohio.
What happened
Per the opinion, someone who had intruded into Studco’s email system sent emails in the name of an Olympic account manager announcing a bank change and naming an account at 1st Advantage as the new payee. The emails came from olysteel.net, not Olympic’s actual domain, olysteel.com. Studco sent its next four invoice payments to that account.
Receiving account
The account belonged not to Olympic but to a longtime individual customer of 1st Advantage. Per the opinion, that customer had also been drawn into the scam through a job advertisement and believed the deposits and withdrawals were legitimate business.
The bank’s system
1st Advantage’s DataSafe system automatically generated a report with a warning for each ACH deposit whose beneficiary name differed from the account holder. Per the opinion, such warnings ran to hundreds or thousands a day, notified no one, and were not reviewed as a matter of course. The warnings for the four deposits were not read before the scam came to light.
Impact
The FBI investigated and concluded the scam originated in the Near East or North Africa. The scammers were never identified and none of the money was recovered. Studco paid Olympic again for the four invoices and bore the loss (per the opinion).
Trial court
The US District Court for the Eastern District of Virginia found for Studco on its misdescription (§ 8.4A-207) and bailment claims and awarded $558,868.71 plus attorneys’ fees and costs. It denied punitive damages.
Court of appeals
The majority held that a beneficiary’s bank may rely on the account number and is not liable unless it had actual knowledge that the name and number did not match. It held that the trial court erred in treating what could have been known with due diligence as actual knowledge, rejected the bailment claim, and remanded with instructions to enter judgment for 1st Advantage.
Concurrence
Judge Wynn agreed with the result but said a factfinder could infer that a bank employee gained actual knowledge of the mismatch, through an October investigation, before the two November deposits. He would instead rest on privity: Studco must seek recovery from its own bank and cannot recover directly from 1st Advantage.

Glossary
ACH — The US system through which banks process debits and credits electronically and automatically in bulk. Per the opinion, it handles over 33 billion transfers and over $86 trillion a year.
UCC Article 4A, § 4A-207 — The part of the Uniform Commercial Code governing funds transfers. Section 4A-207 covers payment orders whose beneficiary name and account number refer to different persons (misdescription of beneficiary). Virginia adopted it as § 8.4A-207.
Certiorari denied — The US Supreme Court declining to review a lower court's decision, which then stands.

Timeline

  • An email in the name of an Olympic account manager announces a bank change. In response to a Studco employee’s reply, the new account details arrive (per the opinion).
  • 1st Advantage’s system automatically shows a name-mismatch warning on a deposit report (record cited in the concurrence).
  • Two overseas wire attempts from the receiving account trigger a US sanctions (OFAC) alert, and 1st Advantage cancels them (concurrence).
  • A further deposit reaches the receiving account (concurrence; the two November deposits exceeded $150,000).
  • The last deposit reaches the receiving account (concurrence).
  • 1st Advantage first learns of the scam from Studco’s president (per the opinion).
  • The district court enters judgment for Studco.
  • The Fourth Circuit reverses (opinion amended on 2 April).
  • The Fourth Circuit denies rehearing (per the Supreme Court docket).
  • The Supreme Court denies Studco’s petition for certiorari (No. 25-80).

The facts rely on the US Court of Appeals for the Fourth Circuit’s opinion (primary) and the US Supreme Court docket (primary). The events of 4 and 25 October and 5 and 13 November rely on the record cited in Judge Wynn’s concurrence. The majority does not give these dates. How the email system was intruded upon and how the account change was handled internally have not been disclosed. The ruling’s conclusion concerns the receiving bank’s liability. What has not been disclosed does not mean there were no controls.

After disclosure

  • Fourth Circuit: Reversed the district court and remanded with instructions to enter judgment for 1st Advantage, and affirmed the denial of punitive damages. Banking industry groups (The Clearing House, Nacha and credit union associations) had filed amicus briefs supporting 1st Advantage.
  • 1st Advantage: Per the opinion, in July 2019 it replaced the vendor of the system that monitored account activity and issued alerts with one offering broader coverage.
  • Studco: Petitioned the Supreme Court, which denied review on 6 October 2025.

Sources

  1. Primary, opinionUS Court of Appeals for the Fourth Circuit “Studco Building Systems US, LLC v. 1st Advantage Federal Credit Union, Nos. 23-1148, 23-1766”2025-03-26, amended 2025-04-02 · ca4.uscourts.gov/opinions/231148.P.pdf
  2. Primary, docketSupreme Court of the United States “Docket No. 25-80, Studco Building Systems US, LLC v. 1st Advantage Federal Credit Union”2025-10-06 · supremecourt.gov/docket/docketfiles/html/public/25-80

References: “The last layer left in AI-era cyber defense”

The same method elsewhereSee all 16 "Payee & bank-account changes" cases

This Brief sets out, from disclosed facts, what organisations in a similar position can check. It is not guidance on individual losses or procedures.

This material is a structured analysis of public information; it is not an audit, diagnosis, or recommendation for any specific organization.

Cite this Brief

Lemma Critical Team. (2026).
"Studco: Payments went to an account named by a party posing as its supplier, and the receiving bank was held not liable (US Fourth Circuit ruling)".
Lemma Critical Brief No.185. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/185-studco-fourth-circuit-ach-name-mismatch/
Read nextNext
All Briefs →
Lemma

If it can't be verified,
it doesn't enter your operation.

Lemma is a pre-execution check: logins, payments, records and publishing that look genuine are checked before they run, with cryptographic proofs the receiving side verifies without asking the issuer. Detection stays; the check sits in front of it.