Implement FedNow Request for Payment (pain.013) handling as the RFP Receiver FI, including payer presentment and pain.014 response codes
domain: frbservices.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable the FedNow 'Receive Request for Payment' capability for your institution — it is disabled by default, and only participants that are also eligible to send Customer Credit Transfers (pacs.008) can receive RFPs.
On receiving a pain.013 message, validate it and decide whether to present it to the payer (Debtor) or reject it outright without presentment.
Send a timely notification to the payer through their preferred channel and present the required RFP data elements: creditor name, amount due, due date, a reference ID (End-to-End Identification), and any description.
Let the payer accept or decline the RFP; if declined, capture a reason using ISO 20022 StatusReason1Code values such as AM09 (wrong amount), APAR (already paid), BE05 (unrecognized initiating party), DUPL (duplicate payment), NARR (free-text narrative), or MS02 (reason not specified).
Send the pain.014 Request for Payment Response back to the RFP Sender FI immediately with a Transaction Status of ACTC (accepted), PRES (presented), RJCT (rejected — reason required), or RCVD (received).
If the payer accepts, initiate the corresponding pacs.008 Customer Credit Transfer without delay, in addition to sending the pain.014 response.
Known gotchas
A participant limited to 'Receive'-only status (i.e., not eligible to send Customer Credit Transfers) cannot receive RFPs even though it can send them — eligibility to receive an RFP is tied to the ability to respond with a pacs.008.
A payer declining an RFP only means they are not paying through that RFP — it does not settle, waive, or acknowledge the underlying debt, so don't treat RJCT as extinguishing the obligation.
Both the pain.014 response and, if accepted, the follow-on pacs.008 credit transfer must be sent back immediately — delaying either undermines the real-time nature of the flow and can desynchronize the payee's records.
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?