Error codes: Instant payments

instant payment error codes rtp via tch and fednow return their own specific error codes see the error codes value in the result code field of the response rtp via tch 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 fednow response reject codes 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 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 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 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) 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 greater than $0 maximum of two decimal places 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 greater than $0 maximum of two decimal places t533 invalid compensation amount this amount must be greater than $0 maximum of two decimal places 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 greater than $0 maximum of two decimal places t550 invalid status confirmation code for the return request response message must contain one of the following codes ipay rjcr pdcr pecr t551 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 t553 proprietary under reason cannot be populated t554 invalid status code for the information request response message must be one of the following codes ipay idup info ninf pdng 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 actc pres rjct rcvd 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 cncl rjcr pdcr 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 reason codes 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 e rror codes 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 can not 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 competed 2013 routing number isn't a valid rtp participant 2014 payment does 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 can not be requested for a credit transfer due to payment status 2020 return can not be requested for an inbound credit transfer 2021 only credit transfers can be refunded 2022 payment already has an existing return request 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 can not manually be updated with funds received from an alternate rail 2033 payment awaitingresponse already set to submitted status 2034 awaitingresponse is not a settable property for this payment type 2035 alternatepaymentdetail is not a settable property for this payment type 2036 response has already been sent for payment 2037 invalid amount specified 2038 payment has expired 2039 reasoncode is missing or invalid 2040 additionalinfo cannot be used with specified reasoncode 2041 payment must be a credit transfer 2042 additionalinfo is required for specified reasoncode 2043 invalid creditor 2044 expirydate 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 expires at date has already passed 2049 participant is not active 2050 debtor does not support return payment 2051 unsupported message type on specified network platform 2200 global profile change not pending 2201 global profile not found or is 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 has not been enabled to send credit transfers 2213 account config change approval requires dual control 2214 account configuration not found or is 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 max payment amount exceeded 2224 daily total dollar amount sent limit exceeded 2225 daily total dollar amount received 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 also be enabled 2231 enabling payment request send requires credit transfer receive to also 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 enabling fednow payment request receive requires fednow credit transfer send to also be enabled 2237 enabling fednow payment request send requires fednow credit transfer receive to also be enabled 2300 hold is not active 2301 hold is not evaluating 2302 manual holds can only be placed when the payment already has a status of hold 2350 public key id already exists 2351 public key id does not exist