Request and response codes

The initial status of inbound and outbound payments

Outbound - payment is being validated prior to submission to the RTP network

Inbound - payment has been received transaction is being authorized

Outbound - payment has been submitted to the Instant Payments network

Inbound - payment has been authorized and is waiting confirmation from the Instant Payments Network that transaction has processed successfully

Outbound- Payment was accepted and received by the receiving institution

Inbound- Payment has been accepted and received

For credit transfers, completed also means the payment has posted successfully

Inbound - payment was automatically or manually rejected
Outbound - the receiving institution or the RTP Network rejected the payment

Reason Code for the rejection can be found in Result.Code on the payment

An outbound payment initiated by an internal user and canceled while in a hold status. A payment may only be canceled while either in a Hold or ResearchRequired status.

The payment is currently on hold and being reviewed by the Operations Team

A payment was not acknowledged within the SLA with The Clearing House

The payment has failed due to technical reasons

Payment is in process of posting to an account

Payment sent by a Debtor FI to a Creditor FI

The originator of the original payment is requesting the funds be returned. This is a non-monetary transaction.

Response to a Return of Funds request. This is a non-monetary transaction. The actual money movement to return funds would be done in another payment as a credit transfer.

This is a non-monetary transaction

Notification to the Creditor FI that a Credit Transfer has timed-out

This is a non-monetary transaction

The ability for the Debtor to send stand-alone remittance information to the Creditor and
the ability for the Creditor to send detailed invoice information to the Debtor (B2B or B2C)

This is a non-monetary transaction

Used to request additional details related to a Credit Transfer that has been received

This is a non-monetary transaction

A Creditor may use a Payment Acknowledgement to acknowledge a Credit Transfer has been received and applied

A Creditor FI must use a Payment Acknowledgement to confirm the funds associated with a Credit Transfer previously accepted without posting (ACWP transaction status), has posted to the Creditor’s account

This is a non-monetary transaction

Used by the sender to provide the requested additional information in the form of an amendment to the original Credit Transfer

This is a non-monetary transaction

The pacs.008 credit transfer is routed through the RTP via TCH network

The pacs.008 credit transfer is routed through the FedNow network

Closed Account Number

Insufficient Funds

Already Returned

Customer Decision

Legal Decision

No Answer From Customer

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.

• Receiver FI is not signed onto the FedNow Service and therefore cannot receive instant payments.

• Sender FI and/or Receiver FI is not yet active on the FedNow Service.

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:

• Calendar date (CCYYMMDD) is the current date and aligned with the Business Application Header (BAH) date.

• Connection Party ID (nine alphanumerical characters).

• Reference sequence assigned by sender (up to 18 characters).

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:

• Greater than $0

• Maximum of two decimal places

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:

• Greater than $0

• Maximum of two decimal places

Invalid compensation amount. This amount must be:

• Greater than $0

• Maximum of two decimal places

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:

• Greater than $0

• Maximum of two decimal places

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

• IPAY

• RJCR

• PDCR

• PECR

Cancellation Status Reason Information component is incorrect:

• Reason code is required if status confirmation code is ‘RJCR.’

• Only one instance of the Cancellation Status Reason Information component is allowed

Proprietary under Reason cannot be populated.

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

• IPAY

• IDUP

• INFO

• NINF

• PDNG

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:

• ACTC

• PRES

• RJCT

• RCVD

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:

• CNCL

• RJCR

• PDCR

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

Cannot parse the message

Signature mismatch or verification error

Payment has been blocked

Debtor account Is Invalid

Creditor account Is Invalid

Account closed

Account is blocked

Creditor account closed

Debtor account currency is invalid or missing

Creditor account currency is invalid or missing

Debtor account type missing or invalid

Creditor account type missing or invalid

Transaction is forbidden on this type of account

Transaction type is not supported/authorized on this account

Incorrect Agent

Specific transaction/message amount is greater than allowed maximum

Amount of funds available to cover specified message amount is insufficient

Amount received is not the amount agreed or expected

Transaction currency is invalid or missing

Amount is invalid or missing

Transaction amount exceeds limits set by clearing system

Transaction Amount exceeds limits agreed between bank and client

Inconsistent end customer (FedNow specific)

Specification of creditor's address, which is required for payment, is missing/not correct

End customer specified is not known at associated Sort/National Bank Code or no longer exist in the books

Specification of debtor's address, which is required for payment, is missing/not correct

Debtor country code is missing or invalid

Creditor country code is missing or invalid

Country code of debtor’s residence is missing or Invalid

Country code of creditor's residence is missing or Invalid

Debtor identification code missing or invalid

Creditor identification code missing or invalid

Waiting time expired due to incomplete order

Future date is not supported

Payment is a duplicate of another payment

Signer is not allowed to sign for this account

Syntax error reason is provided as narrative information in the additional reason information

Invalid Payment Type Information

End to End Id is missing or invalid

End customer is deceased

Reason is provided as narrative information in the additional reason information

Bank identifier code specified in the message has an incorrect format

Bank Identified is invalid or missing

Debtor FI identifier is invalid or missing

Creditor FI identifier is invalid or missing

Regulatory reason (FedNow-specific)

Invalid Cut Off Time

Invalid Token

Sender Token Not Found

Receiver Token Not Found

Token Expired

Token Found with Counterparty Mismatch

Token Found with Value Limit Rule Violation

Single Use Token Already Used

Token Suspended

Receiving Customer Account does not support/accept this message type

Completed

Any Other Reasons Reason is provided as narrative in the additional information

Central Switch (RTP) system malfunction

Instructed Agent signed-off

Recipient connection is not available

Instructing Agent signed-off

Instructing Agent suspended

Instructed Agent suspended

Payment has not been been sent to the RTP Network

Payment is in a pending state

Payment is processing

Payment has completed

Transaction is being reversed

Attempting to set a Memo Post

Action has timed-out

Action has been canceled

Payment has been rejected

Authorizing a transaction

TCH, FedNow

TCH, FedNow

TCH

TCH, FedNow

FedNow

FedNow

FedNow

Payment sent through a Payment Service Provider (domestic) – one of “Ultimate Debtor” or “Ultimate Creditor” must be present

Business initiated

Business initiated

Consumer initiated