Nacha
Nacha (formerly the National Automated Clearing House Association) is the nonprofit, member-governed steward of the ACH Network, the batch-based account-to-account payment rail that moves consumer and business direct deposits, direct payments, bill pay, and B2B transfers across the United States — more than 30 billion payments and over $80 trillion in value annually. Nacha writes and enforces the Nacha Operating Rules that bind the network's participating depository financial institutions, but it is not itself an ACH Operator (the Federal Reserve and The Clearing House clear and settle the files). Nacha is documentation- and rulebook-first rather than a self-serve PSP: it does not operate a public production payments API of its own. Its API posture is delivered through Afinis Interoperability Standards, the Nacha-stewarded group that publishes royalty-free, standardized financial-services API specifications (payment initiation, account validation, transaction status, returns reporting, and directory services) as Swagger/OpenAPI documents on SwaggerHub, and through Phixius, its payment-information exchange platform. Its home market is the United States.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Nacha the way a machine reads it — 28 machine-readable artifacts across 24 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Nacha scores 37.9/100 (thin), with a separate agent-readiness read of 65/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Nacha
Each block below is one kind of artifact we hold for Nacha. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 24
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Afinis Initiate ACH Payment API
Afinis Interoperability Standards API for initiating an ACH credit or debit payment instruction from an originator through their financial institution. Part of the Afinis standa...
Afinis International ACH Remittance (IAR) API
Afinis International ACH Remittance (IAR) API for sending remittance information tied to incoming IAT (International ACH Transaction) credits.
Afinis IAR Plus API
Afinis IAR Plus API, an extended International ACH Remittance message for incoming IAT credits carrying additional remittance detail.
Afinis Transaction Status API
Afinis Transaction Status API for querying the status of an ACH credit or debit payment by instruction ID or transaction ID.
Afinis Initiate Wire Payment API
Afinis Initiate Wire Payment API enabling a business to originate a wire transfer through its financial institution via a standardized API call.
Afinis Get Wire Status API
Afinis Get Wire Status API enabling the originator of a wire to retrieve the status of the wire payment.
Afinis Initiate Instant Payment API (IIP)
Afinis Initiate Instant Payment (IIP) API enabling a business to make an instant payment through its financial institution, mapping to US real-time rails (RTP and FedNow).
Afinis Instant Payment Transfer API (IPT)
Afinis Instant Payment Transfer (IPT) API enabling a financial institution to send another financial institution an instant payment via an API.
Afinis Initiate Payment API
Afinis Initiate Payment API used to request movement of funds from a debtor account to a creditor account across supported payment rails.
Afinis Reporting ACH Return (RET) API
Afinis Reporting ACH Return (RET) API allowing originators and payment providers to share ACH return payment data in support of fraud and risk mitigation.
Afinis Authorize to Pay (Debit Authorizations) API
Afinis Authorize to Pay API letting a buyer business provide bank account or virtual card details, purpose of payment, and authorization for a seller to debit the account.
Afinis Pay Me API
Afinis Pay Me API for requesting a payment (request-for-payment) from a payer through standardized messaging.
Afinis Account Validation API
Afinis Account Validation API for validating that a bank account is open and able to accept ACH credits or debits, reducing returns and fraud.
Afinis Account Validation Plus Ownership (Name) API
Afinis Account Validation Plus Ownership API validating account status together with account-owner name/ownership for confirmation-of-payee style checks.
Afinis Account Validation Plus Name Plus Return API
Afinis Account Validation combined with name verification and ACH return-history signals in a single standardized message.
Afinis Real-Time Billing Account Validation API
Afinis Real-Time Billing Account Validation API for validating a consumer bank account at the point of billing enrollment.
Afinis Get Corporate Account Balances API
Afinis Get Corporate Account Balances API letting a corporate/business customer retrieve balance information for their accounts for a date or date range.
Afinis Get Corporate Transaction History API
Afinis Get Corporate Transaction History API letting a corporate bank customer retrieve financial transaction history for review or integration.
Afinis Get Transaction Detail API
Afinis Get Transaction Detail API letting a corporate financial professional request detailed information for a specific transaction in their account.
Afinis Payee Profile API
Afinis Payee Profile API for exchanging standardized payee onboarding and directory profile information between participants.
Afinis Written Statement of Unauthorized Debit (WSUD) API
Afinis WSUD API letting an ODFI send an automated electronic request to an RDFI for a copy of a consumer's Written Statement of Unauthorized Debit.
Afinis Proof of Authorization API
Afinis Proof of Authorization API providing a real-time alternative message for a request for an ACH proof of authorization to increase automation and reduce manual handling.
Afinis Bank Contacts API
Afinis Bank Contacts API for retrieving standardized operational contact information for financial institutions.
Afinis Bank Contact V2 API
Afinis Bank Contact V2 API, a two-step input/retrieve interface for exchanging standardized financial-institution contact information.
Scroll within the panel for all 24 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
nacha-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Nacha — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/nacha · machine-readable index on apis.io