Reference
Directions
Direction | Description |
---|---|
Inbound | Payment received from another bank |
Outbound | Payment sent to another bank |
Payment Status
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 RTP Network. Inbound - payment has been authorized and is waiting confirmation from the RTP Network that transaction has processed successfully. |
Completed* | Outbound- Payment was accepted/received by the receiving institution Inbound- Payment has been accepted/received. For credit transfers, completed also means the payment has posted successfully. |
Rejected* | Inbound - payment was automatically or manually rejected in COS Outbound - the receiving institution or the RTP Network rejected the payment. Outbound - the RTP payment originates from an account with insufficient funds. 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 in COS. |
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. |
*Indicates the status is the final status for a payment
Payment Types
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. Sending a Return Request is not currently supported. |
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 (end-user) 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. |
RequestForPayment* | Requests the initiation of a Credit Transfer from the party receiving the request. This is a non-monetary transaction. |
RequestForPaymentResponse* | Used to provide a business response to a Request for Payment. 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 |
*Indicates the payment type is not currently supported
Return Response Reject Codes
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 |
Reason Codes
Reason Codes provide the reason a message did not complete and can be found on the payment Result.Code. The Result.Code will be OK if the payment was successfully sent/received.
Code | Description |
---|---|
650 | Cannot parse the message |
690 | Signature mismatch or verification error |
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 |
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 |
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 narrativein 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
TransactionAccountContext is used internally for additional detail for the state of a payment within a status. PaymentStatus should be used for determining the status of a payment.
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 |
RtpTransactionStatus
Status of the payment, as set by the receiving institution. This applies to Credit Transfers and Requests for Payment.
Status | Description |
---|---|
ACTC | Payment has been accepted |
RJCT | Payment or Payment Related Message has been rejected |
RCVD | Payment Related Message has been received by the receiving institution |
ACWP | Payment instruction included in the Credit Transfer is Accepted without being posted to the Creditor Customer’s account. |
ServiceLevelCode
SDVA - Only code accepted by RTP, means Payment must be executed with same day value to the creditor (for RTP this will be done in seconds)
LocalInstrumentProprietary
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 |
ZELLE | Instruction originated as a Zelle Payment (Not currently supported in COS) |
CategoryPurpose
Identifies the Debtor/Sender as either a business or consumer customer of the Debtor FI
Code | Description |
---|---|
BUSINESS | Business initiated |
CONSUMER | Consumer initiated |
Return Request Status Codes
Code specified on the Return Response indicating if the funds will be returned
Status | Description |
---|---|
IPAY | Payment will be refunded |
RJCR | Cancellation request has been rejected |
PECR | Payment will be partially refunded |
Return Request Codes
Reason Code specified when sending a Return Request
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 not correct |
CUST | Requested By Customer Cancellation requested by the Debtor due to Debtor’s mistake or error |
DUPL | Duplicate Payment - Payment is a duplicate of another payment |
FRAD | Fraudulent Origin Debtor claims payment was unauthorized or fraudulently induced |
FRTR | Final Response - Repeat attempt to prior non-response |
TECH | Technical Problem Cancellation requested following technical problems resulting in an erroneous transaction |
UPAY | Undue Payment - Payment has been made through another payment 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 |
Clearing Channels
Identifies the channel that will be used to return funds when the funds are not being returned via a Credit Transfer
Code | Description |
---|---|
MPNS | ACH Payment |
RTGS | FedWire |
RTNS | CHIPS |
Updated 5 months ago