Initiate a FedNow Request for Payment using pain.013 and handle the debtor's pain.014 response
domain: fednow · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Build a pain.013 CreditorPaymentActivationRequest with CdtTrfTxInf including ReqdExctnDt, InstrAmt, Cdtr details, and a structured remittance reference (Ustrd or Strd/CdtrRefInf)
Send the pain.013 to the debtor's bank via the FedNow network; the creditor's participant bank routes it using the debtor's routing number in DbtrAgt
Await the pain.014 CreditorPaymentActivationRequestStatusReport from the debtor's bank indicating whether the debtor accepted (ACTC) or rejected (RJCT) the request
If accepted (ACTC), wait for the subsequent pacs.008 credit transfer from the debtor's bank which actually moves funds
Match the arriving pacs.008 to the originating pain.013 using the EndToEndId or the pain.013's PmtInfId carried in the pacs.008 PurpCd or RltdRmtInf
Expire unfulfilled pain.013 requests after the ReqdExctnDt and notify the creditor that no payment was received
Known gotchas
A pain.014 acceptance does not move money — it is only the debtor's intent; the pacs.008 is the settlement event and may still fail or be delayed
FedNow RfP has a network cap on the request amount; verify current limits with your participant bank as they may differ from the standard pacs.008 per-transaction cap
The debtor's bank must be a FedNow participant and have RfP receive capability enabled; not all FedNow members support RfP at launch
Give your agent this knowledge — and 15,600+ 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?