Request and response codes
See the payment status in the status field of Instant Payment responses. Status of an instant payment.
Status | Description |
Created | The initial status of inbound and outbound payments |
Pending | Outbound - payment is being validated prior to submission to the RTP network Inbound - payment has been received transaction is being authorized |
Processing | 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 |
Completed* | 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 |
Rejected* | 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 |
Canceled* | 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. |
Hold | The payment is currently on hold and being reviewed by the Operations Team |
TimedOut* | A payment was not acknowledged within the SLA with The Clearing House |
Failed* | The payment has failed due to technical reasons |
Finalizing | Payment is in process of posting to an account |
ResearchRequired | Response to an outbound payment was not received and manual review of the payment is required to determine if the payment should be canceled or completed |
*A final status for a payment
This value appears in the paymentType field in Instant Payments responses. The paymentType value tells you details about the transaction.
Type | Description |
CreditTransfer | Payment sent by a Debtor FI to a Creditor FI |
ReturnRequest | The originator of the original payment is requesting the funds be returned. This is a non-monetary transaction. |
ReturnResponse | 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 |
SystemTimeout | Notification to the Creditor FI that a Credit Transfer has timed-out This is a non-monetary transaction |
RemittanceAdvice* | 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 |
RequestForInformation* | Used to request additional details related to a Credit Transfer or a Request for Payment that has been received This is a non-monetary transaction |
PaymentAck* | 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 |
RequestForInformationResponse* | Used by the sender to provide the requested additional information in the form of an amendment to the original Request for Payment or Credit Transfer This is a non-monetary transaction |
Unknown | Payment type was not recognized |
*This payment type is not currently supported
Network Platform | Description |
TCH | The pacs.008 credit transfer is routed through the RTP via TCH network |
FedNow | The pacs.008 credit transfer is routed through the FedNow network |
<blank> | If no network platform is specified, CR uses implicit routing to try a network based on partner configuration and routing number availability |
RTP via TCH and FedNow return their own, specific error codes. See the error codes value in the result.code field of the response.
Code | Description |
AC04 | Closed Account Number |
AM04 | Insufficient Funds |
ARDT | Already Returned |
CUST | Customer Decision |
LEGL | Legal Decision |
NOAS | No Answer From Customer |
NOOR | No Original Transaction Received |
Refer to the ISO 20022 External Code Set on the ISO website for additional information on FedNow response reject codes.
Error Code | Error Description |
E301 | Report request failed. Review request, update and resubmit as needed. |
E400 | ISO message does not exist, can resend with same message ID (or new message ID). |
E401 | Sender of the payment status request is not authorized to receive transaction status. |
E402 | Original ISO message referenced was not processed; resend with new unique message ID. |
E411 | Transaction is still processing; retry after timeout clock has elapsed. |
E481 | Invalid dates included in the reporting from date and/or to date fields. |
E500 | Internal processing error; contact FRB Service Support Center. |
E600 | Balance inquiry is not allowed for this account or by this Participant. |
E760 | Invalid response sender and receiver. Response sender and receiver must match original transfer request. |
E890 | Pending transaction status is not valid for this message. |
E891 | Finalized transaction status is not valid for this message. |
E960 | Internal error. Contact FRB Services Support Center for details. |
E970 | 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. |
E974 | Internal processing error; contact FRB Service Support Center. |
E980 | Invalid FedNow Service profile for the Sender FI RTN. As a result, the RTN is not eligible to send this message type. |
E981 | Invalid FedNow Service profile for the Receiver FI RTN. As a result, the Receiver FI RTN is not eligible to receive this message type. |
E982 | 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. |
E983 | Liquidity Management Transfers (LMTs) were sent outside of supported hours. LMTs can be sent only during specified LMT operating hours. |
E984 | Sender FI or Receiver FI does not have a Participant Profile enabled for the indicated RTN to send and/or receive LMTs. |
E990 | Invalid transaction limit. Transaction exceeds the FedNow Service transaction limit, or a lower limit set by the Sender FI. |
E996 | Reserved response timeout. Insufficient time remains on the payment timeout clock to accommodate Receiver FI reserved response time. |
E997 | Timeout clock has expired. Processing of the transaction exceeded the payment timeout clock. |
E998 |
|
E999 | 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. |
T501 | ISO message exceeds the maximum allowable size of 25,000 characters. |
T504 | Invalid clearing system member ID field. The ID in the “to” component should be the FedNow Service member ID (e.g., "021150706"). |
T505 | ISO message does not meet the FedNow Service ISO 20022 message specifications for one or multiple fields. |
T506 | Invalid message definition identifier. This identifier should be associated with the underlying message and must be a version that FedNow Service supports. |
T508 | Business processing date/time element is not allowed in the ISO message. This element is used only by the FedNow Service. |
T509 | Copy duplicate element is not allowed in an ISO message sent by a Participant. This element is used only by the FedNow Service. |
T510 | Related element is not allowed in an ISO message sent by a Participant. This element is used only by the FedNow Service. |
T512 | Invalid message ID. A valid message ID must meet the following criteria:
|
T514 | Structured remittance information field exceeded the maximum length of 4,000 characters. |
T515 | Message contains both structured and unstructured remittance elements. The FedNow Service only allows one or the other within a single message. |
T516 | 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. |
T517 | ISO message ID is a duplicate. The message ID must be unique. |
T518 | ISO message does not contain an original transaction ID or original UETR. The ISO message must contain one or both. |
T519 | 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. |
T520 | 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. |
T521 | 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. |
T522 | ISO message does not contain the required status reason code for the rejected transaction. |
T523 | Invalid transaction status code. ISO messages must include one of the following eligible codes: ACTC ACWP ACCC BLCK PDNG RJCT |
T524 | Invalid original message name identification. A valid ISO message name as permitted in the ISO 2022 message specification rules is required. |
T525 | Invalid original interbank settlement amount format. This amount must be:
|
T526 | Insufficient information provided. When debtor of the return is a party, the debtor party, account and agent must be provided. |
T527 | Invalid local instrument. The local instrument specifies the FedNow Service product code under which the message is sent. The code should be FDNA. |
T528 | Invalid returned interbank settlement amount format. This amount must be:• Greater than $0.• Maximum of two decimal places. |
T529 | 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. |
T530 | Invalid country code. See the officially assigned code list on the ISO 20022 website (www.iso20022.org). |
T532 | Invalid interbank settlement amount format. This amount must be:
|
T533 | Invalid compensation amount. This amount must be:
|
T534 | ISO message does not contain the required transaction identification or UETR. |
T535 | Invalid category purpose field. This field must contain either CONS, BIZZ or GOVT. |
T536 | Insufficient information. If the ISO 20022 message used reason code is NARR, additional information or additional incorrect information must be present, as applicable. |
T537 | Key signature algorithm not supported. |
T538 | Account balance request cannot include a reporting period because the balance is as of a particular date and time. |
T539 | Account balance request must include the account type. |
T540 | 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. |
T542 | Invalid Market Practice Identifier |
T543 | Invalid original message date. Original message date must be the current date or previous calendar date. |
T544 | Message referenced in admi.007 is not found |
T545 | 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). |
T546 | Invalid Account ID for message type. A correspondent account activity totals report cannot be requested for a single RTN. |
T547 | Invalid status code. The status code must be TS02. |
T548 | Invalid charges amount format. This amount must be:
|
T550 | Invalid status confirmation code for the return request response message. Must contain one of the following codes:
|
T551 | Cancellation Status Reason Information component is incorrect:
|
T553 | Proprietary under Reason cannot be populated. |
T554 | Invalid status code for the information request response message. Must be one of the following codes:
|
T555 | Incorrect format in fnclockstart field. Refer to the Technical Specification document for the correct format. |
T556 | Invalid Correction Transaction component in information request response message. If the correction transaction component is present, the status must be “IPAY.” |
T557 | 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. |
T558 | 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. |
T560 | Invalid Transaction Status Code. Must be one of the following codes:
|
T561 | The Status Reason Information component can only occur once |
T562 | The Business Service element in the BAH must not be used by participants |
T563 | Invalid Status Confirmation code. Must be one of the following codes:
|
T565 | If the Resolution Related Information is populated, the status must be IDUP |
T566 | If the Resolution Related Information is populated, the status must be either IPAY or PECR |
T570 | Invalid key encoding. The encoding algorithm must be one supported by the FedNow Service. |
T571 | Invalid key algorithm. The key algorithm must be one supported by the FedNow Service. |
T572 | Invalid encoded key. Unable to parse the key using the given encoding and key algorithms. |
T573 | Invalid key length |
T574 | Invalid key fingerprint |
T575 | Invalid key expiration. Keys with an expiration date greater than one year are not accepted by the FedNow Service. |
T576 | Duplicate key. All keys added must be unique. |
T580 | Event Time future dated |
T581 | 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). |
T584 | At least one connection point must be connected per Connection party. |
T600 | Balance inquiry service not available at this time. Or balance inquiry not allowed for this account. |
F101 | Entry pair matches the Receiver FI’s fraud controls |
F002 | Entry pair matches an entry on the Sender FI’s Negative List with a send restriction |
The reasonCode attribute in an Instant Payments response provides the reason a message did not complete. The resultCode will be OK if the payment was successfully sent or received.These codes are specifically for RTP via TCH.
Refer to the ISO 20022 External Code Set on the ISO website for additional information on FedNow reason codes.
Code | Description |
650 | Cannot parse the message |
690 | Signature mismatch or verification error |
BLKD | Payment has been blocked |
AC02 | Debtor account Is Invalid |
AC03 | Creditor account Is Invalid |
AC04 | Account closed |
AC06 | Account is blocked |
AC07 | Creditor account closed |
AC10 | Debtor account currency is invalid or missing |
AC11 | Creditor account currency is invalid or missing |
AC13 | Debtor account type missing or invalid |
AC14 | Creditor account type missing or invalid |
AG01 | Transaction is forbidden on this type of account |
AG03 | Transaction type is not supported/authorized on this account |
AGNT | Incorrect Agent |
AM02 | Specific transaction/message amount is greater than allowed maximum |
AM04 | Amount of funds available to cover specified message amount is insufficient |
AM09 | Amount received is not the amount agreed or expected |
AM11 | Transaction currency is invalid or missing |
AM12 | Amount is invalid or missing |
AM13 | Transaction amount exceeds limits set by clearing system |
AM14 | Transaction Amount exceeds limits agreed between bank and client |
BE01 | Inconsistent end customer (FedNow specific) |
BE04 | Specification of creditor's address, which is required for payment, is missing/not correct |
BE06 | End customer specified is not known at associated Sort/National Bank Code or no longer exist in the books |
BE07 | Specification of debtor's address, which is required for payment, is missing/not correct |
BE10 | Debtor country code is missing or invalid |
BE11 | Creditor country code is missing or invalid |
BE13 | Country code of debtor’s residence is missing or Invalid |
BE14 | Country code of creditor's residence is missing or Invalid |
BE16 | Debtor identification code missing or invalid |
BE17 | Creditor identification code missing or invalid |
DS24 | Waiting time expired due to incomplete order |
DT04 | Future date is not supported |
DUPL | Payment is a duplicate of another payment |
DS0H | Signer is not allowed to sign for this account |
FF02 | Syntax error reason is provided as narrative information in the additional reason information |
FF03 | Invalid Payment Type Information |
FF08 | End to End Id is missing or invalid |
MD07 | End customer is deceased |
NARR | Reason is provided as narrative information in the additional reason information |
RC01 | Bank identifier code specified in the message has an incorrect format |
RC02 | Bank Identified is invalid or missing |
RC03 | Debtor FI identifier is invalid or missing |
RC04 | Creditor FI identifier is invalid or missing |
RR04 | Regulatory reason (FedNow-specific) |
TM01 | Invalid Cut Off Time |
TK01 | Invalid Token |
TK02 | Sender Token Not Found |
TK03 | Receiver Token Not Found |
TK04 | Token Expired |
TK05 | Token Found with Counterparty Mismatch |
TK06 | Token Found with Value Limit Rule Violation |
TK07 | Single Use Token Already Used |
TK08 | Token Suspended |
NOAT | Receiving Customer Account does not support/accept this message type |
OK | Completed |
1100 | Any Other Reasons Reason is provided as narrative in the additional information |
9909 | Central Switch (RTP) system malfunction |
9910 | Instructed Agent signed-off |
9912 | Recipient connection is not available |
9934 | Instructing Agent signed-off |
9946 | Instructing Agent suspended |
9947 | Instructed Agent suspended |
9948 | Central Switch (RTP) service is suspended |
TransactionAccountContext is a CR code used internally for additional details about the state of a payment, within a status. Use PaymentStatus to determine the status of a payment with regard to the Instant Payments network.
Context | Description |
NotSubmitted | Payment has not been been sent to the RTP Network |
Pending | Payment is in a pending state |
Processing | Payment is processing |
Complete | Payment has completed |
Reversal | Transaction is being reversed |
MemoPost | Attempting to set a Memo Post |
TimedOut | Action has timed-out |
Canceled | Action has been canceled |
Rejected | Payment has been rejected |
AuthOnly | Authorizing a transaction |
NotSet | Not Set |
Network status of the payment (rtpTransactionStatus), as set by the receiving institution. This applies to Credit Transfersand Requests for Payment.
Status | Description | Network platform |
ACTC | Payment has been accepted | TCH, FedNow |
RJCT | Payment or Payment-related message has been rejected | TCH, FedNow |
RCVD | Payment-related message has been received by the receiving institution | TCH |
ACWP | Payment instruction included in the credit transfer is Accepted but not yet posted to the Creditor’s account | TCH, FedNow |
ACCC | Payment has posted to the Creditor Customer's account | FedNow |
ACSC | Accepted settlement completed | FedNow |
BLCK | A payment instruction that previously had an ACWP status is blocked. Funds will neither be posted to the Creditor's account nor returned to the Debtor's account. (FedNow specific) | FedNow |
PDNG | A payment instruction that had an ACWP status still has not posted to the Creditor's account (FedNow specific) | FedNow |
SDVA is the only code accepted by RTP via TCH, which means payment must be executed with same day value to the creditor (for RTP via TCH this will be done in seconds).
For RTP via TCH, identifies the origination condition of the instruction to allow the instructed agent to properly process the transaction.
Code | Description |
INTERMEDIARY | Payment sent through a Payment Service Provider (domestic) – one of “Ultimate Debtor” or “Ultimate Creditor” must be present |
STANDARD | Standard RTP payment |
Identifies the Debtor/Sender as either a business or consumer customer of the Debtor FI.
Code | Description |
BUSINESS | Business initiated |
CONSUMER | Consumer initiated |
Code | Description |
BIZZ | Business initiated |
CONS | Consumer initiated |
GOVT | Government initiated |