System error codes
Instant Payments system error codes can be retrieved from the RTP module by making a call to GET /v1/meta/errors.
Code | Description |
|---|---|
2000 | General exception |
2001 | Payment not found |
2002 | Invalid payment status |
2003 | Original Payment Not Found |
2004 | Return Request must be inbound and in a pending state to be rejected |
2005 | Credit transfers must be outbound in a hold status to be rejected |
2006 | Payment type cannot be rejected |
2007 | Direction not inbound |
2008 | Direction not outbound |
2009 | Payment cannot be canceled |
2010 | Payment must be outbound |
2011 | Payment must be inbound |
2012 | Payment cannot be completed |
2013 | Routing number isn't a valid RTP Participant |
2014 | Payment does not meet criteria to be resent |
2015 | Payment had already been refunded |
2016 | Ultimate Debtor can only be used when account is a business account |
2017 | Payments of $3,000 or more require a complete debtor address |
2018 | Invalid Debtor |
2019 | Return cannot be requested for a Credit Transfer due to payment status |
2020 | Return cannot be requested for an inbound Credit Transfer |
2021 | Only Credit Transfers can be refunded |
2022 | Payment already has an existing return of funds in process |
2023 | Payment must be a Return Response |
2024 | Payment must be awaiting response |
2025 | Return Request was not found |
2026 | Credit Transfer was not found |
2027 | Cannot manually update payment; funds will be returned through RTP Network |
2028 | Simulator-Credit Transfer must be inbound |
2029 | Payment has already been accepted |
2030 | Credit Transfer status must be Completed |
2031 | Payment already has an existing Payment Ack in process |
2032 | Payment cannot be manually updated with funds from an alternate rail |
2033 | Payment Awaiting Response already set to submitted status |
2034 | Awaiting Response is not settable for this payment type |
2035 | Alternate Payment Detail is not settable for this payment type |
2036 | Response has already been sent for payment |
2037 | Invalid amount specified |
2038 | Payment has expired |
2039 | Reason Code is missing or invalid |
2040 | Additional Info cannot be used with specified Reason Code |
2041 | Payment must be a credit transfer |
2042 | Additional Info is required for specified Reason Code |
2043 | Invalid Creditor |
2044 | Expiry Date exceeds configured MaxRfpExpiryDays |
2045 | Receiver does not support Request For Payment |
2046 | Payment type must be Request For Payment |
2047 | Requested Execution Date cannot be after Expiry Date |
2048 | Requested Queued Payment Expiry Date has already passed |
2049 | Participant is not active |
2050 | Debtor does not support Return Payment |
2051 | Unsupported message type on specified network platform |
2052 | Cannot check status of payment never transmitted |
2053 | Reason Code not valid for network platform |
2054 | Debtor requires additional identifier |
2200 | Global profile change not pending |
2201 | Global profile not found or invalid |
2202 | Global Change not approved |
2203 | Global config change approval requires dual control |
2204 | Global config required |
2205 | Global config accounts must be unique |
2206 | Offset account not found |
2207 | Unposted account not found |
2209 | Account change not approved |
2210 | Account change not pending |
2211 | This action requires dual control |
2212 | Account not enabled to send credit transfers for TCH |
2213 | Account config change approval requires dual control |
2214 | Account configuration not found or invalid |
2215 | Product change not pending |
2216 | Product change not approved |
2217 | Operator Account not found |
2218 | Product config change approval requires dual control |
2219 | Account config required |
2220 | Product config required |
2221 | Custom originator data not allowed for account |
2222 | TCH max payment amount exceeded for product/account |
2224 | Daily Sent Dollar Amount Limit Exceeded |
2225 | Daily Received Dollar Amount Limit Exceeded |
2226 | Daily Sent Transfer Count Limit Exceeded |
2227 | Daily Received Transfer Count Limit Exceeded |
2228 | Birth Fields should not be defined on Business Products |
2229 | Legal Entity Id should not be defined on Personal Products |
2230 | Enabling Payment Request Receive requires Credit Transfer Send to be enabled |
2231 | Enabling Payment Request Send requires Credit Transfer Receive to be enabled |
2232 | Account has not been enabled to send Payment Requests |
2233 | Custom originator data not allowed for account |
2234 | Daily Sent Payment Request Count Limit Exceeded |
2235 | FedNow Operator Account not found |
2236 | FedNow Payment Request Receive requires FedNow Credit Transfer Send |
2237 | FedNow Payment Request Send requires FedNow Credit Transfer Receive |
2238 | Outbound FedNow payments are globally disabled |
2239 | FedNow integration globally disabled |
2240 | Global FedNow operator account is invalid |
2241 | Product/account not enabled to send FedNow credit transfers |
2242 | Product/account FedNow max payment amount exceeded |
2243 | Account has not been enabled to send CRNow credit transfers |
2244 | Creditor Account has not been enabled to receive CRNow credit transfers |
2245 | Product/account CRNow max payment amount exceeded |
2246 | CRNow sending account does not have receiving account whitelisted |
2300 | Hold is not active |
2301 | Hold is not evaluating |
2302 | Manual holds can only be placed when payment is in hold status |
2352 | Integration already in requested state |
2376 | Active/active integration is disabled |
2377 | Cannot disable last active server |
2378 | Site already in requested state |