Access FedNow through your financial institution's FedNow participant connection or via a technology service provider (TSP) acting on behalf of a participant bank
Build the credit transfer request as an ISO 20022 pacs.008 message including CreditorAgent with the beneficiary bank's routing number, Creditor account details, IntrBkSttlmAmt, and a unique end-to-end identification
Submit the message to the FedNow Service; the service operates 24/7/365 and aims to provide final settlement in seconds
Receive and parse the pacs.002 response for the transaction status: ACSC (accepted and settled) is final and irrevocable; RJCT requires reading the StatusReasonCode to identify the rejection cause
Implement inbound FedNow message handling (pacs.008 received) to credit beneficiary accounts and return a pacs.002 acknowledgment within the required response window
Known gotchas
FedNow transaction limit is $10M per payment as of mid-2026; participating institutions may set lower per-transaction limits for their customers
FedNow and RTP are separate networks; a beneficiary bank may participate in one but not the other — always check participant directory before sending
Receiving institutions must respond to inbound credit transfers within a strict timeframe or the payment may be returned; implement a timeout handler in your inbound processing
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp