NACHA Native
NACHA's faster-payments mandates and FedNow rollout broke the only thing keeping ACH fraud manageable: latency. NACHA Native is the structured compliance layer that lets faster-payment volumes run without becoming a $50B fraud pipeline.
01 · The problem
Faster payments removed the latency safety valve
Traditional ACH gave fraud teams a 24-hour reversal window. Same-day ACH cut that to hours. FedNow cuts it to seconds. The fraud-detection systems banks and ERPs use today were architected when latency was the primary control. Now it is gone, and the structural fraud rate has tracked the speed-up exactly.
02 · The thesis
Real-time rails need a real-time control plane
Banks have invested in real-time fraud at the rail level. ERPs have not. The gap between submit and clear is now seconds. Fraud, sanctions, and compliance all have to run inside it.
NACHA Native is the structured overlay that runs those checks in the gap. Sanctions, beneficial-ownership, anomaly detection, and NACHA-mandated controls. All on the same primitive, at the same latency the rail demands.
03 · The product
What it does
Real-time anomaly detection
Statistical and graph-based models that score every outbound payment in under 100ms.
Sanctions + ownership screening
OFAC, FinCEN, and beneficial-ownership lookups in line with the payment, not after the fact.
NACHA rule enforcement
Native enforcement of return windows, originator obligations, and authorization handling. No bolt-on workflow, no consultant tax.
Audit-grade ledger
Every decision and supporting evidence captured for examiners on demand.
04 · Why now
The timing case
- 1
FedNow is now in general availability and onboarding mid-market originators every quarter. The control plane is six months behind the rail capacity.
- 2
NACHA's 2026 Risk Management and Fraud Monitoring rule changes formalize obligations that mid-market ERPs cannot meet with their current stack.
- 3
Real-time inference on tabular and graph data is now production-grade at sub-100ms latency. The infrastructure cost has cleared the threshold.
05 · Why I see it
The view from inside the work
Federal Reserve faster-payments and NACHA working-group contributor since 2011. The blind spot in the mandate is the integration layer between ERP and rail. That is the layer I have built on, twice.
06 · Comparable references
What's already in the market, and where the gap is
An honest read on the adjacent landscape. Not every comparable is a competitor. Some are partners. Some are the market the venture displaces.
07 · Key risks
What could break the thesis
Operator-grade pre-mortem. Surfaced because the buyers and partners worth talking to will surface them anyway.
Banks may push their own real-time control plane down to the ERP.
Banks chronically struggle to ship horizontal SaaS to mid-market ERPs. The distribution gap is the moat.
False-positive rates on real-time models could block legitimate payments.
Confidence-scored decisioning with explicit thresholds for block, review, and pass. ERPs control the policy. NACHA Native provides the signal.
Regulatory landscape on faster-payments fraud liability is still settling.
Operator's NACHA working-group access keeps the product calibrated to where the rules are heading, not just where they are.
08 · Proof of motion
What I've already shipped on this thesis
The artifacts that turn this from an essay into something with traction. Published work, working-group seats, operator scars.
09 · Questions partners ask
The next three follow-ups
Pre-empted because the buyers and partners worth talking to will surface them anyway.
Featurespace and Verafin already do this. Why now?
Both are bank-side platforms. They run inside the bank's perimeter and score outbound payments after they've already left the ERP. NACHA Native sits inside the ERP, where the mid-market gap actually is. The architectural seat is different, the buyer is different, and the integration story is different. Banks aren't the market. ERP-side mid-market is.
What about false positives blocking legitimate payments?
Confidence-scored decisioning with explicit thresholds for block, review, and pass. ERPs control the policy. NACHA Native provides the signal. Most fraud platforms fail because they assert a single binary verdict. We don't.
Status
NACHA Native is a published essay, not a stealth company. I am running Finexio. The thesis is here so the right operator or investor can find it and we can talk.
Of the eight ventures I've published, two are in discovery and I expect to operate one of them after Finexio. The rest, including this one, are pattern recognition I want in the open. If you read this and want to start it yourself, that is the outcome I'm hoping for.
Other concepts
Healthcare Adjudication
Apex Adjudication
AI claims-resolution engine for healthcare payers. Resolves manual denials at API speed.
Clearinghouse Automation
Clearing AI
Automated translation between legacy clearinghouse formats and modern APIs.
Healthcare Settlement
Ledger Health
Cryptographic settlement and audit trails for multi-party healthcare reimbursement.