Implement a FedNow Request for Payment flow to initiate pull-based instant payments
domain: frbservices.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Connect to the FedNow Service through your participant bank's API or a certified FedNow service provider; ensure your participant is enabled for both credit-push and request-for-payment message types
Construct and send a pain.013 creditor payment activation request message targeting the debtor's FedNow-connected account; include the requested amount, due date, and payment purpose
The debtor's bank presents the RFP to the account holder; upon approval, the debtor's bank sends a pacs.008 credit transfer back to your account, crediting funds in real time
Handle declined RFPs: the debtor's bank may return a pain.014 message indicating rejection; implement timeout handling if no response is received within your defined SLA window
Reconcile received pacs.008 credit transfers against outstanding RFPs by matching the end-to-end identification field; mark fulfilled RFPs and cancel or resend expired ones per your business logic
Known gotchas
FedNow RFP is not a guaranteed collection mechanism; the debtor can ignore or decline the request — it is not equivalent to a direct debit mandate
FedNow transaction limit is $10M (effective November 2025); RFPs requesting amounts above this limit will be rejected at the network level
pain.013 and pain.014 are ISO 20022 message types; your implementation must produce and parse schema-valid XML — invalid messages are rejected without a business-level error code
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?