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 paymentrails, 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. Look at the resultAdditionalInfo field in the Reject webhooks event for additional information that may be provided by the rejecting FI
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.
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.

API Error Codes by category

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.

Payment operations (2001-2068)

Errors related to instant payment processing, status management, and validation.

Code	Description	Resolution
2001	Payment not found	Verify the payment ID is correct
2002	Invalid payment status	Check current payment status; verify the requested operation is valid for the current status
2003	Original payment not found	Verify the original payment ID is correct; ensure the referenced payment exists
2004	Return request must be inbound and in pending state to be rejected	Only inbound return requests in pending status can be rejected
2005	Credit transfers must be outbound in hold status to be rejected	Only outbound credit transfers in hold status can be rejected
2006	Payment type cannot be rejected	This payment type does not support rejection operations
2007	Direction not inbound	Operation requires inbound payment; verify payment direction
2008	Direction not outbound	Operation requires outbound payment; verify payment direction
2009	Payment cannot be canceled	Payment status does not allow cancellation
2010	Payment must be outbound	Operation requires payment to be outbound; verify payment direction
2011	Payment must be inbound	Operation requires payment to be inbound; verify payment direction
2012	Payment cannot be completed	Payment status or conditions do not allow completion
2013	Routing number isn't valid RTP participant	Verify routing number is an active RTP participant
2014	Payment doesn't meet criteria to be resent	Payment cannot be resent in its current state; verify payment status
2015	Payment had already been refunded	Payment has already been refunded; cannot refund again
2016	Ultimate debtor can only be used when account is business account	Ultimate debtor field requires business account classification
2017	Payments of $3,000+ require complete debtor address	Include complete debtor address for payments of $3,000 or more (travel rule compliance)
2018	Invalid debtor	Debtor information is invalid or incomplete
2019	Return cannot be requested for credit transfer due to payment status	Credit transfer status does not allow return request
2020	Return cannot be requested for inbound credit transfer	Return requests only apply to outbound credit transfers
2021	Only credit transfers can be refunded	Refund operations only apply to credit transfer payment types
2022	Payment already has existing return of funds in process	Cannot initiate new return while existing return is processing
2023	Payment must be return response	Operation requires payment to be a return response type
2024	Payment must be awaiting response	Operation requires payment to be in awaiting response status
2025	Return request was not found	Verify return request ID is correct; check if return request exists
2026	Credit transfer was not found	Verify credit transfer ID is correct; check if credit transfer exists
2027	Cannot manually update payment, funds will be returned through RTP network	System will automatically process return through network; manual update not allowed
2028	Simulator credit transfer must be inbound	Simulator operations require inbound credit transfers
2029	Payment has already been accepted	Payment has been accepted; cannot accept again
2030	Credit transfer status must be completed	Operation requires credit transfer to be in completed status
2031	Payment already has existing payment ack in process	Cannot initiate new payment acknowledgment while existing ack is processing
2032	Payment cannot manually be updated with funds received from alternate rail	Funds received via alternate rail cannot be manually updated
2037	Invalid amount specified	Payment amount is invalid; verify amount is positive and within limits
2038	Payment has expired	Payment has passed expiry date/time; cannot process expired payments
2039	Reason code is missing or invalid	Provide a valid reason code from the allowed list
2040	Additional info cannot be used with specified reason code	Remove additional info field; not applicable to this reason code
2041	Payment must be credit transfer	Operation requires payment to be a credit transfer type
2042	Additional info is required for specified reason code	Include additional info field for this reason code
2043	Invalid creditor	Creditor information is invalid or incomplete
2044	Expiry date exceeds configured max RFP expiry days	Reduce expiry date to be within configured maximum days for request for payment
2045	Receiver does not support request for payment	Recipient does not accept request for payment messages
2046	Payment type must be request for payment	Operation requires payment to be a request for payment type
2047	Requested execution date cannot be after expiry date	Execution date must be before or equal to expiry date
2048	Requested queued payment expires at date has already passed	Expiry date for queued payment has passed; provide future date
2049	Participant is not active	Routing number participant is not active in the network
2050	Debtor does not support return payment	Debtor does not accept return payment messages
2051	Unsupported message type on specified network platform	Message type not supported on TCH RTP or FedNow; verify platform capabilities
2052	Cannot check status of payment that was never transmitted	Payment must be transmitted before status can be checked
2053	Reason code not valid for network platform	Reason code not supported on TCH RTP or FedNow; use platform-specific codes
2054	Debtor requires additional identifier	Include additional identifier for debtor (required by recipient)
2055	Payments of $3,000+ require complete creditor address	Include complete creditor address for payments of $3,000 or more (travel rule compliance)
2056	Use case is missing or invalid	Provide a valid use case identifier for the payment
2057	Industry category is missing or invalid	Provide a valid industry category code
2058	Sender ID is missing or invalid	Provide a valid sender identifier
2059	Return of FedNow payment request from partner must be initiated within threshold	FedNow return requests must be submitted within configured threshold days from original payment
2060	Partners cannot respond to return requests flagged for fraud investigation	Return requests under fraud investigation cannot be responded to by partners
2061	Return request of TCH outbound payment must be requested within threshold	TCH return requests must be submitted within configured threshold days from payment initiation
2062	Discount must be less than amount	Discount amount must be less than payment amount
2063	Reason code UAPA only available for RTP v5.0	Use reason code FRAD for earlier RTP versions; UAPA requires RTP v5.0+
2064	Purpose can only be utilized for RTP v5.0+ payments	Purpose field requires RTP v5.0 or later
2065	Invalid purpose of payment code	Provide a valid purpose of payment code
2066	Case creator name can only be used for FedNow payments	Case creator name field only applicable to FedNow payments
2067	Originator organization identifiers can only be used for FedNow payments	Originator organization ID fields only applicable to FedNow payments

Configuration (2200-2267)

Errors related to product, account, and global configuration management.

Code	Description	Resolution
2200	Global profile change not pending	Operation requires global profile change to be in pending status
2201	Global profile not found or is invalid	Verify global profile ID is correct and profile exists
2202	Global change not approved	Global configuration change must be approved before applying
2203	Global config change approval requires dual control	Have a second authorized user approve the global configuration change
2212	Account has not been enabled to send credit transfers for TCH	Enable TCH credit transfer send in account configuration
2213	Account config change approval requires dual control	Have a second authorized user approve the account configuration change
2220	Product config required	Include product configuration object in the request
2224	Daily total dollar amount sent limit exceeded	Daily outbound payment dollar limit reached; wait until next day or increase limit
2225	Daily total dollar amount received limit exceeded	Daily inbound payment dollar limit reached; wait until next day or increase limit
2226	Daily sent transfer count limit exceeded	Daily outbound payment count limit reached; wait until next day or increase limit
2227	Daily received transfer count limit exceeded	Daily inbound payment count limit reached; wait until next day or increase limit
2230	Enabling payment request receive requires credit transfer send also enabled	Enable credit transfer send before enabling payment request receive
2231	Enabling payment request send requires credit transfer receive also enabled	Enable credit transfer receive before enabling payment request send
2232	Account has not been enabled to send payment requests	Enable payment request send in account configuration
2234	Daily sent payment request count limit exceeded	Daily outbound payment request count limit reached; wait until next day or increase limit
2236	Enabling FedNow payment request receive requires FedNow credit transfer send enabled	Enable FedNow credit transfer send before enabling FedNow payment request receive
2237	Enabling FedNow payment request send requires FedNow credit transfer receive enabled	Enable FedNow credit transfer receive before enabling FedNow payment request send
2238	Outbound FedNow payments are globally disabled	FedNow outbound payments are disabled at global level; contact administrator
2239	FedNow integration globally disabled	FedNow integration is disabled at global level; contact administrator
2241	Product/account not enabled to send FedNow credit transfers	Enable FedNow credit transfer send in product or account configuration
2242	Product/account FedNow max payment amount exceeded	Reduce payment amount to be within FedNow maximum limit for product/account
2243	Account has not been enabled to send CRNow credit transfers	Enable CRNow credit transfer send in account configuration
2244	Creditor account has not been enabled to receive CRNow credit transfers	Recipient account must have CRNow credit transfer receive enabled
2245	Product/account CRNow max payment amount exceeded	Reduce payment amount to be within CRNow maximum limit for product/account
2246	CRNow creditor is not whitelisted for specified debtor	Add creditor to debtor's CRNow whitelist before sending payment
2247	Sender ID is not valid format	Provide sender ID in correct format
2248	Enabling FedNow credit transfer send requires FedNow payment return receive enabled	Enable FedNow payment return receive before enabling FedNow credit transfer send

Holds (2300-2302)

Errors related to payment hold management.

Code	Description	Resolution
2300	Hold is not active	Hold must be in active status for this operation
2301	Hold is not evaluating	Hold must be in evaluating status for this operation
2302	Manual holds can only be placed when payment already has status of hold	Payment must already be on hold before manual hold can be placed

Integration management (2352, 2376-2378)

Errors related to network integration configuration.

Code	Description	Resolution
2352	Integration already in requested state	Integration is already in the requested state; no change needed
2376	Active/active integration is disabled	Active/active integration is not enabled; contact administrator
2377	Cannot disable last active server	At least one active server must remain enabled
2378	Site already in requested state	Site is already in the requested state; no change needed

Whitelist management (2401-2410)

Errors related to CRNow whitelist configuration.

Code	Description	Resolution
2401	Sender product not found	Verify sender product ID is correct and product exists
2402	Sender account not found	Verify sender account number is correct and account exists
2403	Sender account does not belong to sender product	Ensure sender account is associated with specified sender product
2404	Receiver product not found	Verify receiver product ID is correct and product exists
2405	Receiver account not found	Verify receiver account number is correct and account exists
2406	Receiver account does not belong to receiver product	Ensure receiver account is associated with specified receiver product
2407	Wildcard exists for sender product	Remove wildcard entry before adding specific whitelist entries
2408	Whitelist entry already exists for requested values	Whitelist entry already exists; cannot create duplicate
2409	Receiver product required when receiver account specified	Include receiver product when specifying receiver account
2410	Invalid product/account configuration requested	Product/account whitelist configuration is invalid; verify configuration rules

Additional Resources

ISO 20022 Standard: 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.