FedNowSM Service

®
ISO 20022 Message Flows
Version 1.3, 8 December 2022
NONCONFIDENTIAL // EXTERNAL

Introduction
The FedNow Service will be governed by the terms of an operating circular issued by each of the Reserve Banks. Other Reserve Bank operating circulars are also applicable to
the Reserve Banks provision of financial services, including operating circulars that govern the account relationships and electronic connection with the participants. This
FedNow Service Release 1 ISO 20022 Message Flows document is provided solely to provide FedNow participants with guidance on how to comply with the message format
requirements of the FedNow Service. It does not create new obligations on the Reserve Banks. To the extent of any inconsistency between this document and an applicable
Reserve Bank operating circular, the terms of the operating circular govern.

The messaging flows outlined in this document do not confer or connote legal status or responsibilities of any party to a funds transfer through the service under applicable
law.

Moreover, nothing in this document otherwise modifies or supersedes requirements imposed on FedNow participants under applicable law. This includes any statutory,
regulatory, or supervisory requirements or guidance applicable to participants that require the participants to obtain, retain, populate, or send information in connection with
handling payments messages.

The Reserve Banks and FedNow participants will use electronic connections and message queues in sending and receiving messages in connection with the service. This
infrastructure that will support processing FedNow messages will not contain the features of the FedNow Service application, which will be used by the Reserve Banks to
perform the messaging functions of the FedNow Service. To the extent that a description in this document outlines a response from the FedNow Service, that description is
based on an assumption that the related messages successfully traversed related infrastructure and was ingested into the FedNow application in a manner that allows the
FedNow Service application to interrogate the message and initiate a response. Messages sent to or received from the FedNow Service will be sent to or received from one or
more Reserve Banks in operating the service.

This document is provided free of charge. The information in the document may not be sold, relicensed, or otherwise used for commercial gain. You may link to the document,
but you may not charge a fee for providing a link to it. The Federal Reserve Banks grant to FedNow participants a nonexclusive, royalty-free, perpetual, revocable license to use
or embed or implement the document as a component of or in combination with the FedNow Service. The Federal Reserve Banks may revoke this license at any time. The
Federal Reserve Banks reserve the right, in their sole discretion, to amend, supplement, or otherwise modify this document at any time. If you would like to make additional
uses of the document, you must contact us for permission. The Federal Reserve Banks do not sponsor, endorse, or recommend (or provide any warranties, express or implied,
regarding) any third party or any third-party products or services referenced in this document.

The Financial Services logo, “FedNow” and “FRBservices.org” are service marks of the Federal Reserve Banks. A list of marks related to financial services products that are offered to financial institutions by the
Federal Reserve Banks is available at FRBservices.org®. “ISO” is a registered service mark of the International Organization for Standardization.

2
NONCONFIDENTIAL // EXTERNAL

Customer Credit Transfer

* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does
not match.
1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send an 3
admi.002.
NONCONFIDENTIAL // EXTERNAL

Payment Status Request

1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature orit does not match, then it should send back an admi.002.
2 The FedNow Service determines based on message content whether the request is directed to itself or to a FedNow participant. If directed to the FedNow Service, it sends a FedNow payment status (pacs.002),
if directed to a FedNow participant, it sends a receipt acknowledgement (admi.007) to the sender of the payment status request and forwards the request to the FedNow participant.
3 The FedNow participant receiving the request sends a receipt acknowledgement (admi.007) across the FedNow Service to the sender of request, prior to sending the requested status.
* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.

4
NONCONFIDENTIAL // EXTERNAL

Return Request & Return Request Response

1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002.
2 If the message passes both syntax and business validation, then the FedNow Service sends a receipt acknowledgement (admi.007) to the sender of the return request and forwards the request to the FedNow participant.
3 The FedNow participant receiving the request sends a receipt acknowledgement (admi.007) across the FedNow Service to the sender of request, prior to sending the return request response.
4 If the message passes both syntax and business validation, then the FedNow Service sends a receipt acknowledgement (admi.007) to the sender of the return request response (camt.029). The FedNow participant receiving the return request
response sends a receipt acknowledgement (admi.007) to the sender of the return request response (camt.029).
* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.

5
NONCONFIDENTIAL // EXTERNAL

Payment Return

* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.
1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002. 6
NONCONFIDENTIAL // EXTERNAL

Financial Institution Credit Transfer

* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.
1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002. 7
NONCONFIDENTIAL // EXTERNAL

Request for Payment & Request for Payment Response

1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002.
2 If the message passes both syntax and business validation, then the FedNow Service sends a receipt acknowledgement (admi.007) to the sender of the RFP (pain.013) and forwards the RFP to the FedNow participant.
3 The FedNow participant receiving the RFP sends a receipt acknowledgement (admi.007) across the FedNow Service to the sender of the RFP, prior to sending the RFP response (pain.014).
4 If the message passes both syntax and business validation, then the FedNow Service sends a receipt acknowledgement (admi.007) to the sender of the RFP response (pain.014). The FedNow participant receiving the RFP response sends a receipt acknowledgement
(admi.007) to the sender of the RFP response (pain.014).
* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.
** Depending on the use case. Not all responses may be sent.

8
NONCONFIDENTIAL // EXTERNAL

Request for Payment Cancellation Request & Response

1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002.
2 If the message passes both syntax and business validation, then the FedNow Service sends a receipt acknowledgement (admi.007) to the sender of the RFP Cancellation Request (camt.055) and forwards the RFP Cancellation Request to the FedNow participant.
3 The FedNow participant receiving the RFP Cancellation Request sends a receipt acknowledgement (admi.007) across the FedNow Service to the sender of the request, prior to sending the RFP Cancellation Request Response (camt.029).
4 If the message passes both syntax and business validation, then the FedNow Service sends a receipt acknowledgement (admi.007) to the sender of the RFP Cancellation Request Response (camt.029). The FedNow participant receiving the RFP Cancellation Requ est
Response sends a receipt acknowledgement (admi.007) to the sender of the RFP Cancellation Request Response (camt.029).
* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.

9
NONCONFIDENTIAL // EXTERNAL

Information Request & Information Request Response

1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002.
2 If the message passes both syntax and business validation, then the FedNow Service sends a receipt acknowledgement (admi.007) to the sender of the Information Request (camt.026) and forwards the Information Request to the FedNow participant.
3 The FedNow participant receiving the Information Request sends a receipt acknowledgement (admi.007) across the FedNow Service to the sender of the request, prior to sending the Information Request Response (camt.029).
4 If the message passes both syntax and business validation, then the FedNow Service sends a receipt acknowledgement (admi.007) to the sender of the Information Request Response (camt.029). The FedNow participant receiving the Information Request Response (camt.029) sends a receipt acknowledgement (admi.007) to the sender of the
Information Request Response (camt.029). Depending on the use case an Additional Payment Information (camt.028) message may be sent that follows the same flow.
* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.
** Participant may send a message (camt.056) to request a return of the payment instruction, or to request cancellation of a request for payment
***With the IPAY code, debtor agent may indicate that they will be sending a corrective payment

10
NONCONFIDENTIAL // EXTERNAL

FedNow Broadcast

1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002.
* If a FedNow participant is suspended or reactivated, an online/offline status will be sent to all FedNow participants. 11
NONCONFIDENTIAL // EXTERNAL

Participant Broadcast (Sign On/Off/Connect/Disconnect, Ping)

Sign On/Off/Connect/Disconnect

Ping

* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.
1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002. 12
NONCONFIDENTIAL // EXTERNAL

Retrieval Request

* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.
1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002. 13
NONCONFIDENTIAL // EXTERNAL

Account Reporting Request & Account Reports

* Syntax validation fails if the FedNow Service cannot parse an incoming message based on the xsd specification or if the digital signature cannot be verified or does not match.
1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002. 14
NONCONFIDENTIAL // EXTERNAL

Account Debit/Credit Notification

1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002.
* Applicable only for Correspondents that opt in to receive the Account Debit/Credit Notification
15
NONCONFIDENTIAL // EXTERNAL

End of Day Reports

1 If a FedNow participant cannot parse a message received from the FedNow Service or cannot verify the digital signature or it does not match, then it should send back an admi.002.
16
NONCONFIDENTIAL // EXTERNAL

Document Change History

Section Description of Change Version Release Date

All First release FedNow Service ISO 20022 Message Flows 1.0 31 March 2021
Reorganized message flows to align with FedNow Service ISO 20022
All 1.1 8 March 2022
Implementation and Readiness Portal Guides.
Return Request & Response,
Information Request & Response, Change: updates to reflect the introduction of a new FedNow Acknowledgment
(admi.007) message that will be sent by the FedNow Service to acknowledge the
Request for Payment & Response, 1.1 8 March 2022
successful processing of nonvalue messages exchanged between FedNow
RFP Cancellation Request & Response participants.
Payment Status Request
Return Request & Response,
Change: updates to footnotes to reflect the enhanced admi.007 message flow
Information Request & Response,
(renamed Receipt Acknowledgment) that will be sent by the FedNow Service to
Request for Payment & Response, acknowledge the successful processing of end-to-end nonvalue messages 1.2 29 June 2022
exchanged between FedNow participants, and by FedNow participants to
RFP Cancellation Request & Response
acknowledge successful receipt of those messages.
Payment Status Request
Return Request & Response,
Information Request & Response,
Correction: updates to footnotes to reflect renamed admi.007 implementation
Request for Payment & Response, guideline from Receipt Acknowledgment into Receipt Acknowledgement to align 1.3 08 December 2022
with name in FedNow Service technical header.
RFP Cancellation Request & Response
Payment Status Request
For the latest version, the reader should always refer to the FedNow Service ISO 20022 message specifications as published onthe Federal Reserve Financial Service’s MyStandards web portal * that take
precedence over the content of this document. The document is subject to change without notice, including based on feedback the Reserve Banks receive. Where terminology, definitions, rules or guidelines
differ from the official ISO 20022 Message Definition Reports (MDRs), the FedNow Service ISO 20022 message implementation guidelines and flows take precedence.
* www2.swift.com/mystandards/#/group/Federal_Reserve_Financial_Services/FedNow_Service

17