Report request failed. Review request, update and resubmit as needed.

ISO message does not exist, can resend with same message ID (or new message ID).

Sender of the payment status request is not authorized to receive transaction status.

Original ISO message referenced was not processed; resend with new unique message ID.

Transaction is still processing; retry after timeout clock has elapsed.

Invalid dates included in the reporting from date and/or to date fields.

Internal processing error; contact FRB Service Support Center.

Balance inquiry is not allowed for this account or by this Participant.

Invalid response sender and receiver. Response sender and receiver must match original transfer request.

Pending transaction status is not valid for this message.

Finalized transaction status is not valid for this message.

Internal error. Contact FRB Services Support Center for details.

Invalid settlement relationship. Sender FI and Receiver FI must have a valid settlement relationship within the FedNow Service to indicate the appropriate Master Account to which transactions will be settled.

Internal processing error; contact FRB Service Support Center.

Invalid FedNow Service profile for the Sender FI RTN. As a result, the RTN is not eligible to send this message type.

Invalid FedNow Service profile for the Receiver FI RTN. As a result, the Receiver FI RTN is not eligible to receive this message type.

Sender FI or Receiver FI does not have a Participant Profile enabled to send and/or receive instant payments;

or Receiver FI does not have a Participant Profile enabled to receive Request for Payment (RfP) messages.

Liquidity Management Transfers (LMTs) were sent outside of supported hours. LMTs can be sent only during specified LMT operating hours.

Sender FI or Receiver FI does not have a Participant Profile enabled for the indicated RTN to send and/or receive LMTs.

Invalid transaction limit. Transaction exceeds the FedNow Service transaction limit, or a lower limit set by the Sender FI.

Reserved response timeout. Insufficient time remains on the payment timeout clock to accommodate Receiver FI reserved response time.

Timeout clock has expired. Processing of the transaction exceeded the payment timeout clock.

ISO message has a creation date or timestamp that is in the future from when it was received by the FedNow Service. This is not allowed.

ISO message exceeds the maximum allowable size of 25,000 characters.

Invalid clearing system member ID field. The ID in the “to” component should be the FedNow Service member ID (e.g., "021150706").

ISO message does not meet the FedNow Service ISO 20022 message specifications for one or multiple fields.

Invalid message definition identifier. This identifier should be associated with the underlying message and must be a version that FedNow Service supports.

Business processing date/time element is not allowed in the ISO message. This element is used only by the FedNow Service.

Copy duplicate element is not allowed in an ISO message sent by a Participant. This element is used only by the FedNow Service.

Related element is not allowed in an ISO message sent by a Participant. This element is used only by the FedNow Service.

Invalid message ID. A valid message ID must meet the following criteria:

Structured remittance information field exceeded the maximum length of 4,000 characters.

Message contains both structured and unstructured remittance elements. The FedNow Service only allows one or the other within a single message.

Invalid sending party or sending party information. A valid sending party is a Participant or a Service Provider that is authorized to send messages on behalf of the Participant.

ISO message ID is a duplicate. The message ID must be unique.

ISO message does not contain an original transaction ID or original UETR. The ISO message must contain one or both.

ISO message does not contain a phone number in the preferred contact Method (PHON) field. A phone number must be provided when phone is the preferred contact method.

ISO message does not contain a mobile number in the preferred contact method (CELL) field. A mobile number must be provided when cell is the preferred contact method.

ISO message does not contain an email address in the preferred contact method (MAIL) field. An email address must be provided when mail is the preferred contact method.

ISO message does not contain the required status reason code for the rejected transaction.

Invalid transaction status code. ISO messages must include one of the following eligible codes:

ACTC

ACWP

ACCC

BLCK

PDNG

RJCT

Invalid original message name identification. A valid ISO message name as permitted in the ISO 2022 message specification rules is required.

Invalid original interbank settlement amount format. This amount must be:

Insufficient information provided. When debtor of the return is a party, the debtor party, account and agent must be provided.

Invalid local instrument. The local instrument specifies the FedNow Service product code under which the message is sent. The code should be FDNA.

Invalid returned interbank settlement amount format. This amount must be:• Greater than $0.• Maximum of two decimal places.

Invalid message signature on ISO 20022 message. For the signature to be valid, it must be signed with the key owner’s private key that corresponds to an active public key that was previously created and validated by the FedNow Service.

Invalid country code. See the officially assigned code list on the ISO 20022 website (www.iso20022.org).

Invalid interbank settlement amount format. This amount must be:

Invalid compensation amount. This amount must be:

ISO message does not contain the required transaction identification or UETR.

Invalid category purpose field. This field must contain either CONS, BIZZ or GOVT.

Insufficient information. If the ISO 20022 message used reason code is NARR, additional information or additional incorrect information must be present, as applicable.

Key signature algorithm not supported.

Account balance request cannot include a reporting period because the balance is as of a particular date and time.

Account balance request must include the account type.

If an account balance report (ABAR), account activity totals report (AATR or IATR) or an account activity details report (AADR) is requested, then the member identification field must be the FedNow Service Connection Party identifier of the requestor of the report(s) and must match the "From" field in BAH.

Invalid Market Practice Identifier

Invalid original message date. Original message date must be the current date or previous calendar date.

Message referenced in admi.007 is not found

Reporting Period and Account Type are not allowed for an intraday account activity totals report (IATR) or a correspondent intraday account activity totals report (CITR).

Invalid Account ID for message type. A correspondent account activity totals report cannot be requested for a single RTN.

Invalid status code. The status code must be TS02.

Invalid charges amount format. This amount must be:

Invalid status confirmation code for the return request response message. Must contain one of the following codes:

Cancellation Status Reason Information component is incorrect:

Proprietary under Reason cannot be populated.

Invalid status code for the information request response message. Must be one of the following codes:

Incorrect format in fnclockstart field. Refer to the Technical Specification document for the correct format.

Invalid Correction Transaction component in information request response message. If the correction transaction component is present, the status must be “IPAY.”

If an (end-of-day) account activity totals report (AATR), an (end-of-day) account activity details report (AADR), a (end-of-day) correspondent account activity totals report (CATR), or a (end-of-day) correspondent account activity details report (CADR) is requested, then Reporting Period is mandatory, and Account Type is not allowed.

Invalid Requested Message Name Identification in the camt.060 message. A valid ISO message name as permitted in the ISO 20022 message specification rules is required.

Invalid Transaction Status Code. Must be one of the following codes:

The Status Reason Information component can only occur once

The Business Service element in the BAH must not be used by participants

Invalid Status Confirmation code. Must be one of the following codes:

If the Resolution Related Information is populated, the status must be IDUP

If the Resolution Related Information is populated, the status must be either IPAY or PECR

Invalid key encoding. The encoding algorithm must be one supported by the FedNow Service.

Invalid key algorithm. The key algorithm must be one supported by the FedNow Service.

Invalid encoded key. Unable to parse the key using the given encoding and key algorithms.

Invalid key length

Invalid key fingerprint

Invalid key expiration. Keys with an expiration date greater than one year are not accepted by the FedNow Service.

Duplicate key. All keys added must be unique.

Event Time future dated

Error in event code field. If Event Code-FPON/FPOF then Event Parameter must be 9-digit RTN. If Event Code-FPCD/FPCR then Event Parameter must be 7-digit Hexa decimal (connection point ID).

At least one connection point must be connected per Connection party.

Balance inquiry service not available at this time. Or balance inquiry not allowed for this account.

Entry pair matches the Receiver FI’s fraud controls