Request and response codes
The payment status is reflected in the status field of Instant Payment responses. Below is a breakdown of the possible statuses for instant payments:
Status | Description |
---|---|
Created | Initial status for both inbound and outbound payments. |
Pending | Outbound – Payment is under validation before submission to the RTP network. Inbound – Payment has been received and is awaiting authorization. |
Processing | Outbound – Payment has been submitted to the Instant Payments network. Inbound – Payment is authorized and awaiting confirmation of successful processing by the network. |
Completed* | Outbound – Payment accepted and received by the receiving institution. Inbound – Payment has been received and accepted. For credit transfers, this also indicates the payment has successfully posted. |
Rejected* | Outbound – Payment was rejected by the receiving institution or RTP network. Inbound – Payment was manually or automatically rejected. Rejection reasons are found in the Result.Code field. |
Canceled* | Outbound payment canceled by an internal user while in Hold or ResearchRequired status. Payments can only be canceled in these statuses. |
Hold | Payment is under review by the Operations Team. |
TimedOut* | Payment was not acknowledged within the SLA window with The Clearing House. |
Failed* | Payment failed due to technical issues. |
Finalizing | Payment is in the process of posting to an account. |
ResearchRequired | No response was received for an outbound payment. Manual review is required to determine if the payment should be canceled or completed. |
* Indicates a final status for a payment.
The paymentType field in Instant Payments responses specifies the nature of the transaction. This value provides details about the type of payment or request being processed, indicating whether it involves monetary movement or serves as a non-monetary notification or request.
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. |
SystemTimeout | Notification to the Creditor FI that a Credit Transfer has timed out. This is a non-monetary transaction. |
RemittanceAdvice* | Allows the Debtor to send stand-alone remittance information to the Creditor or 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* | Acknowledges that 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 (accepted without posting) have posted to the Creditor’s account. This is a non-monetary transaction. |
RequestForInformationResponse* | Provides requested additional information as 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® network via The Clearing House (TCH). |
FedNow | The pacs.008 credit transfer is routed through the FedNow® network. |
CRNow | The pacs.008 credit transfer is routed internally through Cross River’s CRNow network for partner payments. |
<blank> | The credit transfer is routed according to Cross River criteria and logic. |
The resultCode in Instant Payments responses explains why a payment didn’t complete. If successful, the resultCode will show OK.
Code | Description |
---|---|
650 | Cannot parse the message |
690 | Signature mismatch or verification error |
OK | Ok |
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 forbidden on this type of account |
AG03 | Transaction type not supported/authorized on this account |
AGNT | Incorrect Agent |
AM02 | Transaction amount exceeds allowed maximum |
AM04 | Insufficient funds to cover message amount |
AM09 | Amount received is not as agreed or expected |
AM11 | Transaction currency is invalid or missing |
AM12 | Amount is invalid or missing |
AM13 | Transaction amount exceeds clearing system limits |
AM14 | Transaction amount exceeds limits set by bank and client |
BE04 | Creditor's address missing or incorrect |
BE06 | End customer not known or no longer exists |
BE07 | Debtor's address missing or incorrect |
BE10 | Debtor country code is missing or invalid |
BE11 | Creditor country code is missing or invalid |
BE13 | Debtor’s residence country code missing or invalid |
BE14 | Creditor’s residence country code 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 not supported |
DUPL | Duplicate payment detected |
DS0H | Signer not authorized for this account |
FF02 | Syntax error in narrative information |
FF03 | Invalid Payment Type Information |
FF08 | End to End Id missing or invalid |
MD07 | End customer is deceased |
NARR | Narrative information provided for reason |
RC01 | Bank identifier code format is incorrect |
RC02 | Bank identifier is invalid or missing |
RC03 | Debtor FI identifier is invalid or missing |
RC04 | Creditor FI identifier is invalid or missing |
TM01 | Invalid Cut Off Time |
TK01 | Invalid Token |
TK02 | Sender Token Not Found |
TK03 | Receiver Token Not Found |
TK04 | Token Expired |
TK05 | Token Counterparty Mismatch |
TK06 | Token Value Limit Rule Violation |
TK07 | Single Use Token Already Used |
TK08 | Token Suspended |
INSF | Insufficient funds for outbound message |
NOAT | Customer account does not support this message type |
1100 | Reason provided in additional information |
9909 | Central Switch (RTP) system malfunction |
9910 | Instructed Agent signed-off |
9912 | Recipient connection unavailable |
9934 | Instructing Agent signed-off |
9946 | Instructing Agent suspended |
9947 | Instructed Agent suspended |
9948 | Central Switch (RTP) service suspended |
The returnResponseRejectCodes attribute specifies the reason for rejecting a return response. This applies only to RTP via TCH.
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 |
The returnRequestStatuses attribute indicates the status of a return request. This applies only to RTP via TCH.
Code | Description |
---|---|
IPAY | Payment will be refunded |
RJCR | Cancellation request has been rejected |
PECR | Payment will be partially refunded |
The returnRequestCodes attribute defines the reason for initiating a return request. This applies only to RTP via TCH.
Code | Description |
---|---|
AC03 | Invalid Creditor Account Number - Requested by the customer due to mistake or error |
AM09 | Wrong Amount - Amount of the Credit Transfer or Request for Payment is incorrect |
CUST | Requested By Customer - Cancellation requested by the Debtor due to mistake or error |
DUPL | Duplicate Payment - Identical to another transaction |
FRAD | Fraudulent Origin - Debtor claims the payment was unauthorized or fraudulently induced |
FRTR | Final Response - Repeat attempt due to prior non-response |
TECH | Technical Problem - Cancellation requested due to technical issues |
UPAY | Undue Payment - Payment was made through another channel (for Request for Payment expiry) |
WIAM | Wrong Amount with Indemnity |
WICT | Requested By Customer with Indemnity |
WIDP | Duplicate Payment with Indemnity |
WIFD | Fraudulent Origin with Indemnity |
WIFT | Final Response with Indemnity |
WITH | Technical Problem with Indemnity |
The fedNowReturnRequestCodes attribute defines return request reasons for FedNow transactions.
Code | Description |
---|---|
AC03 | Invalid Creditor Account Number - Requested by the customer due to mistake or error |
AM09 | Wrong Amount - Amount of the Credit Transfer or Request for Payment is incorrect |
AGNT | Requested By Agent |
CUST | Requested By Customer - Cancellation requested by the Debtor due to mistake or error |
CUTA | Return Request Upon Information Request |
DUPL | Duplicate Payment |
FRAD | Fraudulent Origin - Debtor claims the payment was unauthorized or fraudulently induced |
NARR | Narrative |
SVNR | Service Not Rendered |
TECH | Technical Problem - Cancellation requested due to technical issues |
UPAY | Undue Payment - Payment was made through another channel (for Request for Payment expiry) |
The returnClearingChannels attribute defines the clearing channel used for processing returns.
Code | Description |
---|---|
MPNS | ACH Payment |
RTGS | FedWire |
RTNS | CHIPS |
The paymentAckTypes attribute defines the types of acknowledgments in response to a payment transaction.
Code | Description |
---|---|
ACK | Acknowledgment from Creditor (end-user) to the sender of the Credit Transfer |
ACWP | Acknowledgment from Creditor FI that funds have been posted to the Creditor Account following an ACWP transaction status |
The requestForPaymentResponseCodes attribute defines the possible responses to a request for payment. This applies only to RTP via TCH.
Code | Description |
---|---|
AC06 | Account specified is blocked, prohibiting transactions |
AG01 | Transaction forbidden on this type of account |
AG03 | Transaction type not supported or authorized on this account |
AM09 | Amount received is incorrect |
AM14 | Transaction amount exceeds limits agreed between bank and client |
BE04 | Missing or incorrect creditor address required for payment |
BE07 | Missing or incorrect debtor address required for payment |
CH11 | Creditor Identifier Incorrect - Customer indicates creditor is unknown |
CUST | Requested By Customer - Customer declines payment |
DS04 | Order Rejected - The bank rejected the order due to content issues |
MD07 | End customer is deceased |
NARR | Narrative reason provided in additional information |
1100 | Other Reasons - Not covered by specific codes |
SL12 | Debtor does not wish to receive RFPs from this Creditor |
The requestForPaymentCancellationCodes attribute defines the reasons for canceling a request for payment. This applies only to RTP via TCH.
Code | Description |
---|---|
AC03 | Invalid Creditor Account Number |
AM09 | Incorrect Amount |
CUST | Requested By Customer - Cancellation requested |
DUPL | Duplicate Payment |
FRAD | Fraudulent Payment - Unauthorized or fraudulently induced |
TECH | Technical Problem - Cancellation due to system issues |
UPAY | Undue Payment - Payment was made through another channel |
AC14 | Invalid or Missing Creditor Account Type |
AM06 | Amount Too Low |
BE05 | Unrecognized Initiating Party |
FOCR | Following Refund Request |
MS02 | No Specified Reason - Customer |
MS03 | No Specified Reason - Agent |
NARR | Narrative reason provided in additional information |
RR04 | Regulatory Reason |
RUTA | Return Upon Unable To Apply |
The fedNowRequestForPaymentResponseCodes attribute defines responses for a FedNow request for payment.
Code | Description |
---|---|
AC02 | Invalid Debtor Account |
AC05 | Closed Debtor Account |
AC06 | Blocked Account |
AG01 | Transaction Forbidden |
AG03 | Transaction Not Supported or Authorized on This Account |
AM04 | Insufficient Funds |
AM09 | Amount Received is Incorrect |
AM14 | Transaction Amount Exceeds Limits |
BE01 | Inconsistent End Customer |
BE05 | Unknown Initiating Party |
CUST | Requested By Customer |
DS02 | Order Canceled |
DT01 | Incorrect Date |
DUPL | Duplicate Request for Payment |
NARR | Narrative reason provided in additional information |
- TransactionAccountContext is an internal CR code that provides extra details about a payment’s state within its current status.
- To understand the overall status of a payment in relation to the Instant Payments network, refer to PaymentStatus.
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 determined by the receiving institution, this status applies to Credit Transfers and Requests for Payment.
Status | Description | Network platform |
---|---|---|
ACTC | Payment has been accepted. | TCH, FedNow, CRNow |
RJCT | Payment or payment-related message has been rejected. | TCH, FedNow, CRNow |
RCVD | Payment-related message has been received by the receiving institution. | TCH |
ACWP | Payment instruction within the credit transfer is accepted but not yet posted to the creditor’s account. | TCH, FedNow |
ACCC | Payment has been posted to the creditor customer’s account. | FedNow |
ACSC | Accepted settlement is completed. | FedNow |
BLCK | A payment previously in ACWP status is now blocked. Funds will not be posted to the creditor’s account or returned to the debtor’s account. (FedNow specific) | FedNow |
PDNG | Payment in ACWP status has not yet posted to the creditor’s account. (FedNow specific) | FedNow |
SDVA is the only accepted code for RTP via TCH, indicating that payments must be executed with same-day value to the creditor (processed in seconds for RTP via TCH).
For RTP via TCH, this identifies the origination condition of the instruction, allowing the instructed agent to correctly process the transaction.
Code | Description |
---|---|
INTERMEDIARY | Payment sent through a domestic Payment Service Provider – either “Ultimate Debtor” or “Ultimate Creditor” must be present. |
STANDARD | Standard RTP payment. |
Identifies the Debtor/Sender as a business or consumer customer of the Debtor FI.
RTP via TCH Category Purpose Codes
Code | Description |
---|---|
BUSINESS | Business initiated. |
CONSUMER | Consumer initiated. |
FedNow Category Purpose Codes
Code | Description |
---|---|
BIZZ | Business initiated. |
CONS | Consumer initiated. |
GOVT | Government initiated. |