Error codes: Instant payments

comprehensive reference for all error codes encountered across our instant payment rails (fednow and tch rtp) most common error codes top rejection reasons the table below summarizes the most frequently occurring rejection codes across both payment rails, based on actual production data use this table as a quick reference to understand which errors your integration is most likely to encounter and to prioritize your error handling logic accordingly code description tm01 cut off time payment received after cut off time ac03 invalid creditor account number ds24 order rejected by the receiving party am04 insufficient funds ac06 blocked account ac04 closed account number 1100 any other reasons i e not covered by iso reason codes ag01 transaction forbidden not allowed for this account type 9909 ips switch system malfunction narr narrative reason provided as free text e997 fednow timeout clock has expired processing of the transaction exceeded the payment timeout clock ag03 transaction type not supported tk08 token service unavailable ac01 incorrect account number ac07 closed creditor account number ab05 timeout transaction not completed in time ab09 requested by psu cancelled by user e996 fednow reserved response timeout insufficient time remains on the payment timeout clock to accommodate receiver fi reserved response time ab08 invalid end to end id e999 fednow iso message has a creation date or time stamp that is in the future from when it was received by the fednow service this is not allowed tk03 invalid or expired token ac14 invalid agent country code rc04 invalid creditor bic ab06 offline process transaction stopped due to offline process dupl duplicate payment ac02 invalid debtor account number ms02 not specified reason customer generated sl03 specific service offered by creditor agent be01 inconsistent with end customer customer identification mismatch iso 20022 standard error codes iso 20022 messaging standard powers both fednow and tch rtp, which defines a universal set of reason codes for payment rejections and status reporting the global financial industry uses these codes and provide a standardized way to communicate why the system rejected, returned, or could not process a transaction the table below lists all iso 20022 reason codes that either rail returns code name definition ab01 abortedclearingtimeout clearing process aborted due to timeout ab02 abortedclearingfatalerror clearing process aborted due to a fatal error ab03 abortedsettlementtimeout settlement aborted due to timeout ab04 abortedsettlementfatalerror settlement process aborted due to a fatal error ab05 timeoutcreditoragent transaction stopped due to timeout at the creditor agent ab06 timeoutinstructedagent transaction stopped due to timeout at the instructed agent ab07 offlineagent agent of message is not online generic usage if it cannot be determined who exactly is not online ab08 offlinecreditoragent creditor agent is not online ab09 errorcreditoragent transaction stopped due to error at the creditor agent ab10 errorinstructedagent transaction stopped due to error at the instructed agent ab11 timeoutdebtoragent transaction stopped due to timeout at the debtor agent ac01 incorrectaccountnumber account number is invalid or missing ac02 invaliddebtoraccountnumber debtor account number invalid or missing ac03 invalidcreditoraccountnumber creditor account number invalid or missing ac04 closedaccountnumber account number specified has been closed on the bank of account's books ac05 closeddebtoraccountnumber debtor account number closed ac06 blockedaccount account specified is blocked, prohibiting posting of transactions against it ac07 closedcreditoraccountnumber creditor account number closed ac08 invalidbranchcode branch code is invalid or missing ac09 invalidaccountcurrency account currency is invalid or missing ac10 invaliddebtoraccountcurrency debtor account currency is invalid or missing ac11 invalidcreditoraccountcurrency creditor account currency is invalid or missing ac12 invalidaccounttype account type missing or invalid generic usage if cannot specify between group and payment information levels ac13 invaliddebtoraccounttype debtor account type missing or invalid ac14 invalidcreditoraccounttype creditor account type missing or invalid ac15 accountdetailschanged the account details for the counterparty have changed ac16 cardnumberinvalid credit or debit card number is invalid ag01 transactionforbidden transaction forbidden on this type of account (formerly noagreement) ag02 invalidbankoperationcode bank operation code specified in the message is not valid for receiver ag03 transactionnotsupported transaction type not supported/authorized on this account ag04 invalidagentcountry agent country code is missing or invalid generic usage if cannot specify between group and payment information levels ag05 invaliddebtoragentcountry debtor agent country code is missing or invalid ag06 invalidcreditoragentcountry creditor agent country code is missing or invalid ag07 unsuccesfuldirectdebit debtor account cannot be debited for a generic reason code value may be used in general purposes and as a replacement for am04 if debtor bank does not reveal its customer's insufficient funds for ag08 invalidaccessrights transaction failed due to invalid or missing user or access right ag09 paymentnotreceived original payment never received ag10 agentsuspended agent of message is suspended from the real time payment system generic usage if it cannot be determined who exactly is suspended ag11 creditoragentsuspended creditor agent of message is suspended from the real time payment system ag12 notallowedbooktransfer payment orders made by transferring funds from one account to another at the same financial institution (bank or payment institution) are not allowed ag13 forbiddenreturnpayment returned payments derived from previously returned transactions are not allowed agnt incorrectagent agent in the payment workflow is incorrect am01 zeroamount specified message amount is equal to zero am02 notallowedamount specific transaction/message amount is greater than allowed maximum am03 notallowedcurrency specified message amount is an non processable currency outside of existing agreement am04 insufficientfunds amount of funds available to cover specified message amount is insufficient am05 duplication duplication am06 toolowamount specified transaction amount is less than agreed minimum am07 blockedamount amount specified in message has been blocked by regulatory authorities am09 wrongamount amount received is not the amount agreed or expected am10 invalidcontrolsum sum of instructed amounts does not equal the control sum am11 invalidtransactioncurrency transaction currency is invalid or missing am12 invalidamount amount is invalid or missing am13 amountexceedsclearingsystemlimit transaction amount exceeds limits set by clearing system am14 amountexceedsagreedlimit transaction amount exceeds limits agreed between bank and client am15 amountbelowclearingsystemminimum transaction amount below minimum set by clearing system am16 invalidgroupcontrolsum control sum at the group level is invalid am17 invalidpaymentinfocontrolsum control sum at the payment information level is invalid am18 invalidnumberoftransactions number of transactions is invalid or missing generic usage if cannot specify between group and payment information levels am19 invalidgroupnumberoftransactions number of transactions at the group level is invalid or missing am20 invalidpaymentinfonumberoftransactions number of transactions at the payment information level is invalid am21 limitexceeded transaction amount exceeds limits agreed between bank and client am22 zeroamountnotapplied unable to apply zero amount to designated account for example, where the rules of a service allow the use of zero amount payments, however the back office system is unable to apply the funds to th am23 amountexceedssettlementlimit transaction amount exceeds settlement limit be01 inconsistenwithendcustomer identification of end customer is not consistent with associated account number (formerly creditorconsistency) be04 missingcreditoraddress specification of creditor's address, which is required for payment, is missing/not correct (formerly incorrectcreditoraddress) be05 unrecognisedinitiatingparty party who initiated the message is not recognised by the end customer be06 unknownendcustomer end customer specified is not known at associated sort/national bank code or does no longer exist in the books be07 missingdebtoraddress specification of debtor's address, which is required for payment, is missing/not correct be08 missingdebtorname debtor name is missing be09 invalidcountry country code is missing or invalid generic usage if cannot specifically identify debtor or creditor be10 invaliddebtorcountry debtor country code is missing or invalid be11 invalidcreditorcountry creditor country code is missing or invalid be12 invalidcountryofresidence country code of residence is missing or invalid generic usage if cannot specifically identify debtor or creditor be13 invaliddebtorcountryofresidence country code of debtor's residence is missing or invalid be14 invalidcreditorcountryofresidence country code of creditor's residence is missing or invalid be15 invalididentificationcode identification code missing or invalid generic usage if cannot specifically identify debtor or creditor be16 invaliddebtoridentificationcode debtor or ultimate debtor identification code missing or invalid be17 invalidcreditoridentificationcode creditor or ultimate creditor identification code missing or invalid be18 invalidcontactdetails contact details missing or invalid be19 invalidchargebearercode charge bearer code for transaction type is invalid be20 invalidnamelength name length exceeds local rules for payment type be21 missingname name missing or invalid generic usage if cannot specifically identify debtor or creditor be22 missingcreditorname creditor name is missing be23 accountproxyinvalid phone number or email address, or any other proxy, used as the account proxy is unknown or invalid ceri checkeri credit transfer is not tagged as an extended remittance information (eri) transaction but contains eri ch03 requestedexecutiondateorrequestedcollectiondatetoofarinfuture value in requested execution date or requested collection date is too far in the future ch04 requestedexecutiondateorrequestedcollectiondatetoofarinpast value in requested execution date or requested collection date is too far in the past ch07 elementisnottobeusedatb andc level element is not to be used at b and c level ch09 mandatechangesnotallowed mandate changes are not allowed ch10 informationonmandatechangesmissing information on mandate changes are missing ch11 creditoridentifierincorrect value in creditor identifier is incorrect ch12 creditoridentifiernotunambiguouslyattransaction level creditor identifier is ambiguous at transaction level ch13 originaldebtoraccountisnottobeused original debtor account is not to be used ch14 originaldebtoragentisnottobeused original debtor agent is not to be used ch15 elementcontentincludesmorethan140characters content remittance information/structured includes more than 140 characters ch16 elementcontentformallyincorrect content is incorrect ch17 elementnotadmitted element is not allowed ch19 valueswillbesettonexttargetday values in interbank settlement date or requested collection date will be set to the next target day ch20 decimalpointsnotcompatiblewithcurrency number of decimal points not compatible with the currency ch21 requiredcompulsoryelementmissing mandatory element is missing ch22 coreandb2bwithinonemessage sdd core and b2b not permitted within one message chqc chequesettledoncreditoraccount cheque has been presented in cheque clearing and settled on the creditor’s account cnor creditorbankisnotregistered creditor bank is not registered under this bic in the csm curr incorrectcurrency currency of the payment is incorrect cust requestedbycustomer cancellation requested by the debtor dnor debtorbankisnotregistered debtor bank is not registered under this bic in the csm ds01 electronicsignaturescorrect the electronic signature(s) is/are correct ds02 ordercancelled an authorized user has cancelled the order ds03 ordernotcancelled the user’s attempt to cancel the order was not successful ds04 orderrejected the order was rejected by the bank side (for reasons concerning content) ds05 orderforwardedforpostprocessing the order was correct and could be forwarded for postprocessing ds06 transferorder the order was transferred to veu ds07 processingok all actions concerning the order could be done by the ebics bank server ds08 decompressionerror the decompression of the file was not successful ds09 decryptionerror the decryption of the file was not successful ds0a datasignrequested data signature is required ds0b unknowndatasignformat data signature for the format is not available or invalid ds0c signercertificaterevoked the signer certificate is revoked ds0d signercertificatenotvalid the signer certificate is not valid (revoked or not active) ds0e incorrectsignercertificate the signer certificate is not present ds0f signercertificationauthoritysignernotvalid the authority of the signer certification sending the certificate is unknown ds0g notallowedpayment signer is not allowed to sign this operation type ds0h notallowedaccount signer is not allowed to sign for this account ds0k notallowednumberoftransaction the number of transaction is over the number allowed for this signer ds10 signer1certificaterevoked the certificate is revoked for the first signer ds11 signer1certificatenotvalid the certificate is not valid (revoked or not active) for the first signer ds12 incorrectsigner1certificate the certificate is not present for the first signer ds13 signercertificationauthoritysigner1notvalid the authority of signer certification sending the certificate is unknown for the first signer ds14 userdoesnotexist the user is unknown on the server ds15 identicalsignaturefound the same signature has already been sent to the bank ds16 publickeyversionincorrect the public key version is not correct this code is returned when a customer sends signature files to the financial institution after conversion from an older program version (old es format) to a n ds17 differentorderdatainsignatures order data and signatures don’t match ds18 repeatorder file cannot be tested, the complete order has to be repeated this code is returned in the event of a malfunction during the signature check, e g not enough storage space ds19 electronicsignaturerightsinsufficient the user’s rights (concerning his signature) are insufficient to execute the order ds20 signer2certificaterevoked the certificate is revoked for the second signer ds21 signer2certificatenotvalid the certificate is not valid (revoked or not active) for the second signer ds22 incorrectsigner2certificate the certificate is not present for the second signer ds23 signercertificationauthoritysigner2notvalid the authority of signer certification sending the certificate is unknown for the second signer ds24 waitingtimeexpired waiting time expired due to incomplete order ds25 orderfiledeleted the order file was deleted by the bank server (for multiple reasons) ds26 usersignedmultipletimes the same user has signed multiple times ds27 usernotyetactivated the user is not yet activated (technically) dt01 invaliddate invalid date (eg, wrong or missing settlement date) dt02 invalidcreationdate invalid creation date and time in group header (eg, historic date) dt03 invalidnonprocessingdate invalid non bank processing date (eg, weekend or local public holiday) dt04 futuredatenotsupported future date not supported dt05 invalidcutoffdate associated message, payment information block or transaction was received after agreed processing cut off date, i e , date in the past dt06 executiondatechanged execution date has been modified in order for transaction to be processed du01 duplicatemessageid message identification is not unique du02 duplicatepaymentinformationid payment information block is not unique du03 duplicatetransaction transaction is not unique du04 duplicateendtoendid end to end id is not unique du05 duplicateinstructionid instruction id is not unique dupl duplicatepaymentorcharge payment or charge is a duplicate of another payment or charge ed01 correspondentbanknotpossible correspondent bank not possible ed03 balanceinforequest balance of payments complementary info is requested ed05 settlementfailed settlement of the transaction has failed ed06 settlementsystemnotavailable interbank settlement system not available erin erioptionnotsupported extended remittance information (eri) option is not supported ff01 invalidfileformat file format incomplete or invalid ff02 syntaxerror syntax error reason is provided as narrative information in the additional reason information ff03 invalidpaymenttypeinformation payment type information is missing or invalid generic usage if cannot specify service level or local instrument code ff04 invalidservicelevelcode service level code is missing or invalid ff05 invalidlocalinstrumentcode local instrument code is missing or invalid ff06 invalidcategorypurposecode category purpose code is missing or invalid ff07 invalidpurpose purpose is missing or invalid ff08 invalidendtoendid end to end id missing or invalid ff09 invalidchequenumber cheque number missing or invalid ff10 banksystemprocessingerror file or transaction cannot be processed due to technical issues at the bank side ff11 clearingrequestaborted clearing request rejected due it being subject to an abort operation g000 paymenttransferredandtracked in an fi to fi customer credit transfer the status originator transferred the payment to the next agent or to a market infrastructure the payment transfer is tracked no further updates will foll g001 paymenttransferredandnottracked in an fi to fi customer credit transfer the status originator transferred the payment to the next agent or to a market infrastructure the payment transfer is not tracked no further updates will g002 creditdebitnotconfirmed in a fitofi customer credit transfer credit to the creditor’s account may not be confirmed same day update will follow from the status originator in a financial institution credit transfer with g003 creditpendingdocuments in a fitofi customer credit transfer credit to creditor’s account is pending receipt of required documents the status originator has requested creditor to provide additional documentation update g004 creditpendingfunds in a fitofi customer credit transfer credit to the creditor’s account is pending, status originator is waiting for funds provided via a cover update will follow from the status originator g005 deliveredwithservicelevel payment has been delivered to creditor agent with service level g006 deliveredwithoutservicelevel payment has been delivered to creditor agent without service level id01 correspondingoriginalfilestillnotsent signature file was sent to the bank but the corresponding original file has not been sent yet md01 nomandate no mandate md02 missingmandatoryinformationinmandate mandate related information data required by the scheme is missing md05 collectionnotdue creditor or creditor's agent should not have collected the direct debit md06 refundrequestbyendcustomer return of funds requested by end customer md07 endcustomerdeceased end customer is deceased ms02 notspecifiedreasoncustomergenerated reason has not been specified by end customer ms03 notspecifiedreasonagentgenerated reason has not been specified by agent narr narrative reason is provided as narrative information in the additional reason information neri noeri credit transfer is tagged as an extended remittance information (eri) transaction but does not contain eri rc01 bankidentifierincorrect bank identifier code specified in the message has an incorrect format (formerly incorrectformatforroutingcode) rc02 invalidbankidentifier bank identifier is invalid or missing generic usage if cannot specify between debit or credit account rc03 invaliddebtorbankidentifier debtor bank identifier is invalid or missing rc04 invalidcreditorbankidentifier creditor bank identifier is invalid or missing rc05 invalidbicidentifier bic identifier is invalid or missing generic usage if cannot specify between debit or credit account rc06 invaliddebtorbicidentifier debtor bic identifier is invalid or missing rc07 invalidcreditorbicidentifier creditor bic identifier is invalid or missing rc08 invalidclearingsystemmemberidentifier clearingsystemmemberidentifier is invalid or missing generic usage if cannot specify between debit or credit account rc09 invaliddebtorclearingsystemmemberidentifier debtor clearingsystemmember identifier is invalid or missing rc10 invalidcreditorclearingsystemmemberidentifier creditor clearingsystemmember identifier is invalid or missing rc11 invalidintermediaryagent intermediary agent is invalid or missing rc12 missingcreditorschemeid creditor scheme id is invalid or missing rcon rmessageconflict conflict with r message reci receivercustomerinformation further information regarding the intended recipient rf01 notuniquetransactionreference transaction reference is not unique within the message rr01 missingdebtoraccountoridentification specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing rr02 missingdebtornameoraddress specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing rr03 missingcreditornameoraddress specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing rr04 regulatoryreason regulatory reason rr05 regulatoryinformationinvalid regulatory or central bank reporting information missing, incomplete or invalid rr06 taxinformationinvalid tax information missing, incomplete or invalid rr07 remittanceinformationinvalid remittance information structure does not comply with rules for payment type rr08 remittanceinformationtruncated remittance information truncated to comply with rules for payment type rr09 invalidstructuredcreditorreference structured creditor reference invalid or missing rr10 invalidcharacterset character set supplied not valid for the country and payment type rr11 invaliddebtoragentserviceid invalid or missing identification of a bank proprietary service rr12 invalidpartyid invalid or missing identification required within a particular country or payment type s000 validrequestforcancellationacknowledged request for cancellation is acknowledged following validation s001 uetrflaggedforcancellation unique end to end transaction reference (uetr) relating to a payment has been identified as being associated with a request for cancellation s002 networkstopofuetr unique end to end transaction reference (uetr) relating to a payment has been prevent from traveling across a messaging network s003 requestforcancellationforwarded request for cancellation has been forwarded to the payment processing/last payment processing agent s004 requestforcancellationdeliveryacknowledgement request for cancellation has been acknowledged as delivered to payment processing/last payment processing agent sl01 specificserviceofferedbydebtoragent due to specific service offered by the debtor agent sl02 specificserviceofferedbycreditoragent due to specific service offered by the creditor agent sl03 serviceofclearingsystem due to a specific service offered by the clearing system sl11 creditornotonwhitelistofdebtor whitelisting service offered by the debtor agent; debtor has not included the creditor on its “whitelist” (yet) in the whitelist the debtor may list all allowed creditors to debit debtor bank acco sl12 creditoronblacklistofdebtor blacklisting service offered by the debtor agent; debtor included the creditor on his “blacklist” in the blacklist the debtor may list all creditors not allowed to debit debtor bank account sl13 maximumnumberofdirectdebittransactionsexceeded due to maximum allowed direct debit transactions per period service offered by the debtor agent sl14 maximumdirectdebittransactionamountexceeded due to maximum allowed direct debit transaction amount service offered by the debtor agent ta01 transmissonaborted the transmission of the file was not successful – it had to be aborted (for technical reasons) td01 nodataavailable there is no data available (for download) td02 filenonreadable the file cannot be read (e g unknown format) td03 incorrectfilestructure the file format is incomplete or invalid tk01 tokeninvalid token is invalid tk02 sendertokennotfound token used for the sender does not exist tk03 receivertokennotfound token used for the receiver does not exist tk09 tokenmissing token required for request is missing tkcm tokencounterpartymismatch token found with counterparty mismatch tksg tokensingleuse single use token already used tksp tokensuspended token found with suspended status tkve tokenvaluelimitexceeded token found with value limit rule violation tkxp tokenexpired token expired tm01 invalidcutofftime associated message, payment information block, or transaction was received after agreed processing cut off time ts01 transmissionsuccessful the (technical) transmission of the file was successful ts04 transfertosignbyhand the order was transferred to pass by accompanying note signed by hand cn01 authorisationcancelled authorisation is cancelled focr followingcancellationrequest return following a cancellation request fr01 fraud returned as a result of fraud noas noanswerfromcustomer no response from beneficiary nocm notcompliantgeneric customer account is not compliant with regulatory requirements, for example fica (in south africa) or any other regulatory requirements which render an account inactive for certain processing ruta returnuponunabletoapply return following investigation request and no remediation possible upay unduepayment payment is not justified aexr alreadyexpiredrtp request to pay expiry date and time has already passed alac alreadyacceptedrtp request to pay has already been accepted by the debtor arfr alreadyrefusedrtp request to pay has already been refused by the debtor arjr alreadyrejectedrtp request to pay has already been rejected atns attachementsnotsupported attachments to the request to pay are not supported edtl expirydatetoolong expiry date time of the request to pay is too far in the future edtr expirydatetimereached expiry date time of the request to pay is already reached frad fraudulentorigin cancellation requested following a transaction that was originated fraudulently the use of the fraudulentorigin code should be governed by jurisdictions iedt incorrectexpirydatetime expiry date time of the request to pay is incorrect irnr initialrtpneverreceived no initial request to pay has been received noar nonagreedrtp no existing agreement for receiving request to pay messages nopg nopaymentguarantee requested payment guarantee (by creditor) related to a request to pay cannot be provided nrch payerorpayerrtpspnotreachable recipient side of the request to pay (payer or its request to pay service provider) is not reachable pins typeofpaymentinstrumentnotsupported type of payment requested in the request to pay is not supported by the payer repr rtpreceivedcanbeprocessed request to pay has been received and can be processed further rtns rtpnotsupportedfordebtor debtor does not support request to pay transactions spii rtpserviceprovideridentifierincorrect identifier of the request to pay service provider is incorrect ucrd unknowncreditor unknown creditor ff12 originaltransactionnoteligibleforrequestedreturn original payment is not eligible to be returned given its current status ff13 requestforcancellationnotfound no record of request for cancellation found dc02 settlementnotreceived rejection of a payment due to covering fi settlement not being received apar alreadypaidrtp request to pay has already been paid by the debtor ab26 invalidbatchsettlementinstruction settlement instruction does not exist ab12 invalidconcurrentbatch duplicate concurrent batch sequence number– for settlement instructions ab13 invalidroutingcodeutilised wrong message routing type for return of funds ab15 invalidaccountnumberforsettlementtype instruction may not be placed on the continuous processing line settlement processor ab21 invalidsettlementagreementnumberspecified agreement number not valid (beneficiary) bday notbusinessday settlement cycle day and calendar day should be the same ds28 returnfortechnicalreason message routed to the wrong environment indt invaliddetails details not valid for this field isws invalidsettlementwindow cannot schedule instruction for night window minf missinginformation information missing for the field or cannot be empty nofr outstandingfundingforsettlement continuous processing line on hold instruction rc13 participantnotanactivememberofrtgs originator not active any more rc15 participantnotactivemembersettlementtype settlement agreement required rc16 participantnotactivememberofsadcrtgs participant blocked from sadc rtgs sbrn settlementbatchremovalnotification remove concurrent batch processing line on hold instruction rqnr requestnotrecognized payer did not recognize the request from payee participant, snrd servicenotrendered services are not yet rendered by the payee participant (creditor) osns optionalservicenotsupported requested optional service (for example instalment payments) is not supported amse attachmentmaximumsize size of the attachment exceeds the allowed maximum inar invalidactivationreference payer’s activation reference is invalid edna executiondatenotaccepted requested execution date of the payment is not accepted sl15 maximumnumberofcredittransactionsexceeded maximum number of credit transactions allowed by the account servicer per service period exceeded sl16 maximumcredittransactionsamountexceeded maximum total credit amount allowed by the account servicer per service period exceeded sl17 debtornotonwhitelistofcreditorside whitelisting service offered by payment system operator or financial institution debtor is not included on the creditor side whitelist sl18 debtoronblacklistofcreditorside blacklisting service offered by payment system operator or financial institution debtor included on the creditor side blacklist chrg underlyingchargebearerwasnotdebt related to a charge message to convey that the charge bearer code used in the corresponding payment message was not debt chco unacceptedchargecodetype related to a charge message to convey that the code in charge breakdown / type / code is not accepted by the receiving party ipns instalmentpaymentsnotsupported payments in instalments are not supported cnns creditnotesnotsupported credit notes are not supported eol1 endoflife expiration of the payment authorisation due to no use for too long pnrt paymentnotalignedwithrtprequest error code used for rtp initiated ctr when the pacs 008 details are not aligned with the pain 013 request tch rtp specific error codes besides the standard iso 20022 reason codes, the clearing house (tch) real time payments (rtp) network defines its own set of proprietary error codes these codes are specific to the rtp infrastructure and are not part of the iso 20022 standard you encounter these codes when a transaction is rejected or fails at the network level due to system issues, participant status changes, or rtp specific validation rules code description 1100 any other reasons i e not covered by iso reason codes 9909 ips switch system malfunction 9910 ips switch processing error 9912 rvc participant not available 9914 element mandatory if local instrument = zelle 9934 instructing agent signed off 9946 instructing agent suspended 9947 instructed agent suspended 9948 service suspended 9952 mapping incompatibility between message versions 9953 missing code 'full' (full invoiced amount) 9954 instruction for creditor agent missing 9956 instructing agent funding account suspended 9957 instructed agent funding account suspended 9964 invalid participant identification noat message type not supported or accepted usage note tch rtp error codes are returned in the statusreasoninformation element of pacs 002 (fitofipaymentstatusreport) messages or in admi 002 (administrationadvice) messages for technical rejections fednow specific error codes the fednow® service, operated by the federal reserve, uses its own set of proprietary error codes in addition to the standard iso 20022 reason codes these codes are organized into three series e series e3xx – e9xx operational and processing errors (e g , timeouts, profile issues, settlement errors) t series t5xx – t7xx technical validation errors (e g , message format, signature, field level validation) f series f0xx – f1xx fraud related codes (e g , negative list matches, velocity checks) e series error codes (general/system errors) code 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 e403 sender of the request is not authorized to receive message e411 transaction is still processing; retry after timeout clock has elapsed e420 rejected due to control set by correspondent e481 invalid dates included in the reporting from date and/or to date elements e500 internal processing error; contact the 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 e960 internal error contact the 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 the 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 time stamp that is in the future from when it was received by the fednow service this is not allowed t series error codes (technical/message validation errors) code description t501 iso message exceeds the maximum allowable size of 25,000 characters t504 invalid clearing system member id element 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 elements 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 include calendar date (ccyymmdd), connection party id (9 alphanumeric characters), reference sequence assigned by sender (up to 18 characters) t514 structured remittance information element 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) element 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) element 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) element 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 or rjct t524 invalid original message name identification or the message name referenced is not supported for the message type t525 invalid original interbank settlement amount format amount must be greater than $0 with 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 amount must be greater than $0 with maximum of two decimal places t529 invalid message signature on iso 20022 message signature must be signed with the key owner's private key that corresponds to an active public key previously validated by the fednow service t530 invalid country code see the officially assigned code list on www iso20022 org http //www iso20022 org t531 invalid original message name identification value t532 invalid interbank settlement amount format amount must be greater than $0 with maximum of two decimal places t533 invalid compensation amount amount must be greater than $0 with 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 begin with a c, b or g, followed by 3 alphanumeric characters t536 insufficient information if the iso 20022 message used reason code narr, additional information must be present 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 for abar, aatr, iatr or aadr reports, the member identification element must be the fednow service connection party identifier of the requestor and must match the "from" element 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 amount must be greater than $0 with maximum of two decimal places t550 invalid status confirmation code for the return request response message must contain ipay, rjcr, pdcr, or pecr t551 cancellation status reason information component is incorrect reason code is required if status confirmation code is "rjcr " only one instance allowed t553 proprietary under reason cannot be populated t554 invalid status code for the information request response message must be ipay, idup, info, ninf, or pdng t555 incorrect format in fnclockstart element, refer to the technical specification document for the correct format t556 invalid correction transaction component in information request response message if present, the status must be "ipay" t557 for aatr, aadr, catr, or cadr reports, reporting period is mandatory, and account type is not allowed t558 invalid requested message name identification in the camt 060 message t559 the expiry date must not be more than 365 days out in the future from the day the rfp is sent t560 invalid transaction status code must be actc, pres, rjct, or 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 cncl, rjcr, or 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 t567 invalid original instructed amount format maximum of two decimal places when there are trailing zeros t568 invalid instructed amount format maximum of two decimal places when there are trailing zeros t569 invalid accepted amount format maximum of two decimal places when there are trailing zeros 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 364 days in the future are not accepted t576 duplicate key all keys added must be unique t577 key indicated in revoke key message is not found t578 last active key cannot be revoked via mq message t579 key indicated in revoke key message is in revoked or expired state t580 event time future dated t581 error in event code element 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 hexadecimal (connection point id) t582 requested execution date cannot be in the past t583 expiry date (time) cannot be before the requested execution date (time) t584 at least one connection point must be connected per connection party t586 processing of request timed out if the problem persists, call support center t587 api request does not meet the specifications for one or multiple elements t588 unable to retrieve participant list for current cycle date, try again if the problem persists, call support center t589 internal error contact the support center if the issue continues t590 invalid fednow service profile as a result, the connection party is not eligible to send this request t591 invalid api request signature t592 invalid api request signature for time elapsed t594 invalid fednow endpoint id t595 connecting party not authorized please contact the support center for further assistance t596 invalid fednow service profile for the requested rtn as a result, api request is not allowed for this rtn t600 balance inquiry service not available at this time or balance inquiry not allowed for this account t613 invalid participant rtn t700 message not found t701 calendar date (ccyymmdd) of original message id is not within the current fednow service calendar day or seven prior calendar days t702 the proprietary id (id) does not match the connection party id in the business application header f series error codes (fraud/security errors) code description 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 f004 negative list processing did not complete (warning code) f008 transaction rejected due to sender fi's cumulative value criteria f009 transaction rejected due to sender fi's velocity criteria f010 account activity threshold processing did not complete (warning code) f011 negative list and account activity threshold processing did not complete (warning code) important notes e983 refer to the "network limits" section in the fednow service operating procedures (version 3 5, february 2026) for more information on lmt hours t506 details on current message versions supported can be found in the fednow service iso 20022 implementation guide on the swift mystandards platform t512 message id length may not exceed allowable character limits for fednow service iso 20022 messages error codes these errors are returned directly in the api response when your request fails validation or cannot be processed they indicate an issue on the request level the payment was not sent to the rail error 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 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 can not 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 can not 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 can not 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 2052 cannot check the status of a payment that was never transmitted 2053 reasoncode not valid for network platform 2054 debtor requires additional identifier 2055 payments of $3,000 or more require a complete creditor address 2056 usecase is missing or invalid 2057 industrycategory is missing or invalid 2058 senderid is missing or invalid 2059 return of a fednow payment request from partner must be initiated within the configured threshold period from the original payment date 2060 partners cannot respond to return requests flagged for fraud investigation 2061 return request of tch outbound payment must be requested within the configured threshold period from the payment initiated date 2062 discount must be less than amount 2063 reason code uapa only available for rtp v5 0 please use reason code frad 2064 purpose can only be utilized for rtp v5 0+ payments 2065 invalid purpose of payment code 2066 case creator name can only be used for fednow payments 2067 originator organization identifiers can only be used for fednow payments 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 for tch 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 product/account tch 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 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 creditor is not whitelisted for the specified debtor 2247 sender id is not a valid format 2248 enabling fednow credit transfer send requires fednow payment return receive to also be enabled 2249 disabling fednow credit transfer send requires fednow payment return receive to also be disabled 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 2352 integration already in requested state 2376 active/active integration is disabled 2377 cannot disable last active server 2378 site already in requested state 2401 sender product not found 2402 sender account not found 2403 sender account does not belong to sender product 2404 receiver product not found 2405 receiver account not found 2406 receiver account does not belong to receiver product 2407 wildcard exists for sender product remove it before adding non wildcard whitelist entries 2408 a whitelist entry already exists for the requested values 2409 receiver product required when receiver account specified 2410 invalid product/account configuration requested additional resources iso 20022 standard www iso20022 org https //www iso20022 org tch rtp documentation tch rtp message specification version 5 0 support contact your payment operations team or the respective network support center for assistance with recurring error codes