FedNow Profile and Queue Setup Overview - Dec. 20 2022

INTERNAL FR/OFFICIAL USE // EXTERNAL
FedNow Profile and

Queue Setup Overview
© 2022 Federal Reserve Banks. Pilot Confidential/FedNow Confidential Information. Materials are not to be used without consent.
Objectives
• Overview of Profiles and Queues
• Profile Considerations for Various Customer Types
• Setting Up Profiles and Queues
© 2022 Federal Reserve Banks. Pilot Confidential/FedNow Confidential Information. Materials are not to be used without consent. 2
Overview of
FedNow Profiles
and Queues
FedNow Service Roles

• FedNow Participant:
• A financial institution authorized by a Reserve Bank to send, receive, or settle messages through the FedNow Service
• Each participant, identifiable by Routing Transit Number (RTN), has a FedNow Participant Profile
• Profile settings allow the participant to be send and/or receive messages (customer credit transfers, liquidity management
transfers - LMT, etc.)
• A participant has established accounting information for settlement of credit transfers
• Service Provider:
• An agent of a FedNow Participant that act on behalf of that Participant
• Provides connectivity or profile management services; has an Authorized Connection Profile
• FedNow Participant authorizes a Service Provider to do one or more of the following:
− Initiate, transmit or receive messages on behalf of the participant
− Operate or otherwise manage the Electronic Connection used to send or receive messages
− Select the security procedure, profile settings or processing options on behalf of the Participant
• Correspondent:
• A financial institution that maintains a Master Account with a Reserve Bank and has agreed to maintain a Settlement Account
for another FedNow Participant
• May or may not need to onboard to the FedNow Service
• May choose to become a FedNow Service participant and receive notification of Respondent payment activity via ISO
messaging
FedNow Participant and ACP Overview

The FedNow Service allows flexibility in the setup of profiles to properly allow for messages and interactions across
the network.
• FedNow Participant Profile: Each FedNow Service participant has a FedNow profile for each RTN enrolled in the Service.
• Participant Profile includes participation type (e.g., Receive Only, Send & Receive, LMT, RFP) and configuration settings, including
transaction limits and reporting setup.
• Participants manage their own configurations or delegate to a Service Provider to accommodate their business needs.
• Authorized Connection Profile (ACP): A profile associated with a participant or service provider that maintains an electronic connection to
the FedNow Service via FedLine® Solutions. Serves as a central connection profile for the processing and management of messages and
payments on behalf of one or multiple RTNs which utilize the FedNow Service
• Profile captures connectivity information including queue setup and is used to map connectivity for one or more participant profiles
(RTNs).
• Ability to update connectivity settings that are applied to all participant profiles mapped, at once.
(Connection Point A)
FedNow Participant Profile Payments
for Connecting DI Application
Authorized Connection Profile
(Connection Point B)
Authorized Connection
RTN: {111111111} Profile Id: 111111111 Payments
Application
Connection Points map
FedNow Participant Profile to queues for each Out Q1
for Connecting DI Connection Party (Connection Point N) message type
Connection party Id: Payments
Multiple RTNs map to a 111111111 A single Connection Party can Application Out Q2
single Connection Party control multiple data centers,
RTN: {222222222}
providing options for resiliency
Overview of FedNow and Institution Queues

There are two types of queues:
➢ “OUT” queues are used to send messages to the FedNow Service
➢ “IN” queues are used to receive messages from the FedNow Service
Category Queue ISO 20022 messages
Credit Transfer and Payment <conn point id>.OUT.CT • Credit Transfer (pacs.008)
Return • Payment Return (pacs.004)
“OUT” queues are: • Payment Status (pacs.002)
Liquidity Management <conn point id>.OUT.LMT • LMT (pacs.009)
• Predefined by the FedNow Service
Nonvalue Message <conn point id>.OUT.NV • Return Request (camt.056)
• Cannot be modified by Participants • Return Request Response (camt.029)
• Request for Payment (pain.013)
• Associated with specific ISO messages • Request for Payment Response (pain.014)
• Mapped to Participant-defined “IN” queues • Payment Status Request to Participant (pacs.028)
• Request for Payment Cancellation Request (camt.055)
where reply messages are sent • Request for Payment Cancellation Request Response (camt.029)
• Information Request (camt.026)
• Information Request Response (camt.029)
• Additional Payment Information (camt.028)
• Message Receipt (admi.007)
Administrative <conn point id>.OUT.ADM • Participant Broadcast (sign on/off) (admi.004)
Reject <conn point id>.OUT.RJCT • Message Reject (admi.002)
Ping <conn point id>.OUT.PING • Connectivity Ping (admi.004)
Inquiry <conn point id>.OUT.INQ • Payment Status Request to FedNow Service (pacs.028)
• Account Report Request (camt.060)
• Retrieval Request (admi.006)
Note: Refer to FedNow Service Operating Procedures for any updates to this listing
Overview of FedNow and Institution Queues

There are two types of queues:
➢ “OUT” queues are used to send messages to the FedNow Service
➢ “IN” queues are used to receive messages from the FedNow Service
“IN” queues are:

• Defined by each institution in a way that will best fit their technology and business objectives
• Used to receive messages from the FedNow Service.
• You will select the naming convention, message categories and specify RTN(s) per queue if desired
• Used in two ways:
1. For receiving replies to messages, where FedNow Service replies to messages sent on OUT queues by a Sender FI.
2. For receiving unsolicited messages.
See the Operating Procedures for tables related to messages sent to IN queues
Note: Refer to FedNow Service Operating Procedures for any updates to this listing
Illustration of FedNow Queues

• Each Participant Profile is linked to a Connection Party, which is associated with logical groupings called Connection Points where Queues are defined
• Connection Point ID and OUT queues are predefined by the FedNow Service, whereas IN and REPLY-TO Queue Names are defined by the Participant
• Queues may be configured by RTN in order to prioritize or separate message traffic
To FedNow From FedNow

• Predefined by the FedNow Service • Configurable by participant
• Each queue carries messages representing a single category • May be assigned one or more message categories
• Each queue must be assigned a reply-to queue • A queue can be assigned one or more participant RTNs
Queue name format: Queue name format:
<connection point id>.OUT.<msg category> <connection point id>.IN.<participant defined>
Examples: Examples:
SAMPLE01.OUT.CT (reply-to= SAMPLE01.IN.CTREPLY) SAMPLE01.IN.PING [Mandatory, defined by FedNow]
SAMPLE01.OUT.LMT (reply-to= SAMPLE01.IN.LMTREPLY) SAMPLE01.IN.LMT (msg category = LMT)
SAMPLE01.OUT.NV (reply-to= SAMPLE01.IN.OTHERREPLY) SAMPLE01.IN.CT (msg category = CT)
SAMPLE01.OUT.INQ (reply-to= SAMPLE01.IN.OTHERREPLY) SAMPLE01.IN.OTHER (msg category=NV, AR, CN, ADM)
SAMPLE01.OUT.ADM (reply-to= SAMPLE01.IN.OTHERREPLY) SAMPLE01.IN.092384394CT (msg category=CT, RTN=092384394)
SAMPLE01.OUT.PING (reply-to= SAMPLE01.IN.OTHERREPLY) SAMPLE01.IN.092384394LMT (msg category=LMT, RTN=092384394)
SAMPLE01.OUT.RJCT (No reply-to queue) SAMPLE01.IN.CTREPLY
SAMPLE01.IN.LMTREPLY
SAMPLE01.IN.OTHERREPLY
Values in Red are defined by FedNow. Values in Purple are defined by the participant.
Correspondents in the FedNow Service

Any Financial Institution that offers Correspondent services can participate in the FedNow Service
Non-Participant Correspondent
Common to all 3 • Settles FedNow transactions for Respondents in Master Account
Correspondent types: • Does not onboard to FedNow; no Participant Profile created
• Will not receive any ISO messages or reports
• Establish Correspondent • Will not access the FedNow interface
settlement relationship with
Respondent by executing OC1
Appendix 2 Settlement Only Participant
• Subject to Liquidity Transfer • Onboards to FedNow, either directly or via a Service Provider
Management Instructions by • Establishes Participant Profile with type = Settlement Only
Correspondent to manage • Will not send/receive Credit Transfer or LMT value messages or reports
Respondent LMT participation • May elect to receive camt.054 – Account Debit/Credit notifications
• May act as Service Provider for
either Profile Management or
Participant and Settlement
Connectivity, subject to
designation by Respondent • Onboards to the FedNow Service either directly or via a Service Provider
• Choose Participation Type that indicate credit transfer and LMT capabilities
• May receive camt.054 messages for Respondents either directly or via
Service Provider
Profile Considerations
for Various Customer Types
FI Connecting Directly via FedLine

This configuration represents an FI who connects one or more RTNs to FedNow via their FedLine connection
• FedNow Participant Profiles: Each RTN the FI chooses to onboard will have its own FedNow Profile with unique configurations (e.g., Receive Only,
Send & Receive, LMT, RFP, transaction limits and reporting setup).
• Authorized Connection Profile: A central connection profile set up using the RTN or Electronic Transaction Identifier (ETI) where the connectivity is
established. It will be mapped to a Connection Party, where all RTNs will be directed for connection to the FedNow Service.
• Access to FedNow interface: FI has the option to choose which of the 4 available roles should be applicable to users at their institution. The role
chosen will allow visibility into both the participant and authorized connection profile.
Connection Points may be in

multiple data centers, providing
All RTNs used as participants and connection profiles belong to the same institution options for resiliency
(Connection Point A)
FedNow Participant Profile
for Connecting DI Payments
Application
RTN: {111111111}
Profile Id: 111111111 Payments
FedNow Participant Profile Application
for Connecting DI
Connection Party (Connection Point n) Out Q1
Multiple RTNs map to a 111111111 A single Connection Party Application Connection Points map
RTN: {222222222}
single Connection Party can map to multiple data to queues for each Out Q2
centers, providing options message type
for resiliency
FI Leveraging a Service Provider

This Profile configuration is for FIs who are connecting one or more RTNs using the FedLine connection of a Service Provider.
• Customer’s FedNow Participant Profiles: Each participating institution may choose to manage their own Participant profile
(requires the institution to have FedLine Advantage connection) or delegate that to their Service Provider
• Service Provider’s Authorized Connection Profile: The Service Provider will have a central connection profile set up using
the RTN or ETI where its connectivity is established. It will be used to map to a Connection Party. All participant RTNs will be
mapped to that Connection Party ID.
• Access to FedNow interface: The Service Provider may be granted edit access if the FI does not have a FedLine connection.
• The role provided enables the Service Provider user to the actions of that role for the ACP and the FIs participant profile.
for Customer Bank A
Connection Points may be in

RTN: {222222222} multiple data centers, providing
options for resiliency
Service Provider will
manage ACP and (Connection Point A)
FedNow Participant Profile Payments
for Customer Bank B
connections
Application
RTN: {333333333} Profile Id: 111111111 Payments
Application
for Customer Bank B Connection Party (Connection Point n) Out Q1
111111111 A single Connection Party Application Connection Points map
Multiple RTNs map to a
RTN: {444444444} can map to multiple data to queues for each Out Q2
single Connection Party
for resiliency
FI as Participant and Service Provider

This Profile configuration is for an FI who is connecting one or more RTNs using their own FedLine connection and providing
services as a Service Provider for their FI customers.
• Connecting FI Participant Profiles: Each RTN the participant chooses to onboard will have its own FedNow Profile with unique
configurations (e.g., Receive Only, Send & Receive, LMT, RFP, transaction limits and reporting setup).
• Customer Participant Profiles: Each participating institution may choose to manage their own Participant profile (requires the
institution to have FedLine Advantage connection) or delegate that to their Service Provider.
• Authorized Connection Profile: The FI that will have a central connection profile set up using the RTN where its connectivity is
established. It will be used to map to a Connection Party ID. All RTNs from this FI and their Customer FIs will be mapped to this
Connection Party ID.
for Connecting FI
• Access to FedNow interface: The Service Provider may be granted edit access if the FI does not have a FedLine connection.
• The role provided enables the Service Provider user to the actions of that role for the ACP and the FI’s profile.
RTN: {111111111} Connection Points may be in

multiple data centers, providing
options for resiliency
Connecting FI will manage
FedNow Participant Profile ACP and connections (Connection Point A)
for Customer Bank A Payments
Application
RTN: {222222222} (Connection Point B)
Profile Id: 111111111 Payments
Application
for Customer Bank B Connection Party (Connection Point n) Out Q1
111111111 A single Connection Party Application Connection Points map
Multiple RTNs map to a
RTN: {333333333} can map to multiple data to queues for each Out Q2
single Connection Party
for resiliency
Setting Up Profiles
and Queues
Authorized Connection Profile Setup Worksheet
FedNow Participant Profile Worksheet
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. “MyStandards” is a
registered mark of SWIFT. Marks of any other third parties identified in this document are owned by their respective holders.
17

FedNow Profile and Queue Setup Overview - Dec. 20 2022

Uploaded by

Copyright:

Available Formats

You might also like

FedNow Profile and Queue Setup Overview - Dec. 20 2022

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FedNow Profile and Queue Setup Overview - Dec. 20 2022

Uploaded by

Copyright:

Available Formats

INTERNAL FR/OFFICIAL USE // EXTERNAL

FedNow Profile and

FedNow Service Roles

FedNow Participant and ACP Overview

Overview of FedNow and Institution Queues

Overview of FedNow and Institution Queues

“IN” queues are:

Illustration of FedNow Queues

To FedNow From FedNow

Correspondents in the FedNow Service

FI Connecting Directly via FedLine

Connection Points may be in

FI Leveraging a Service Provider

Connection Points may be in

FI as Participant and Service Provider

RTN: {111111111} Connection Points may be in

Authorized Connection Profile Setup Worksheet

FedNow Participant Profile Worksheet

You might also like