Refer to the error codes technical documentation for error code information related to Ripple applications.
The following table describes the failure types that Members provide, according to the standards, for Member-initiated exceptions. For more information about business exceptions, see Chapter 4, Section 4.2.
| Type | Use |
|---|---|
RECEIVER_DATA_VALIDATION | Failures initiated by the Receiving Member based on the validation of the payment data |
RECEIVER_LOCK_FAILURE | General failure based on receiver processing prior to locking the payment and subsequent settlement |
SENDER_PROCESSING_FAILURE | General failure based on sender processing prior to initiating settlement |
RECEIVER_PROCESSING_ERROR | General failure based on the receiver processing the payment to the Beneficiary after settlement is complete |
The type RECEIVER_PROCESSING_ERROR is also used as the return reason type when the associated return is processed by the Receiving Member. In addition to this type value, the following types may also be used:
| Type | Use |
|---|---|
BENEFICIARY_RETURN | Returns performed based on a request from the Beneficiary |
SENDER_RETURN | Returns performed based on a request from the Originator |
Per the business exceptions defined in Chapter 4, Section 4.2, ISO 20022 status reasons (specifically, those defined in External Codeset 16) will be used as the failure codes and reason text. The following table describes a subset of status reason values that will be used for business exceptions for Ripple Payments. For more information about individual code details, see ExternalCodeSets_2Q2020_May2020_v1.xls.
Caution
Using codes outside these standards will result in partner compatibility issues. You can request additional codes through the change request process.
| Code | Definition (expected use for failure / return reason) | Error Handling |
|---|---|---|
| AC01 | Account number is invalid or missing. | N/A |
| AC02 | Debtor account number invalid or missing. | If the account number or IBAN is invalid, the Sending Member may repair the transaction by specifying a valid Originator account number. If the account number is missing from the payment message, the Originator may reissue the payment with the Originator account number or IBAN included. |
| AC03 | Creditor account number invalid or missing. | If the account number or IBAN is invalid, the Sending Member may repair the transaction by specifying a valid Creditor account number. If the account number is missing from the payment message, the Originator may reissue the payment with the Creditor account number or IBAN included. |
| AC04 | Account number specified has been closed on the Receiver's books. The Beneficiary may have closed their account since the last time the Originator made a payment transfer to this Beneficiary. | The Originator may contact the Beneficiary for their new account number. |
| AC06 | Account specified is blocked, prohibiting posting of transactions against it. The Account Servicer may have frozen the account for legal reasons, or on the Beneficiary's request. | The Originator may contact the Beneficiary for alternative account details. |
| AC08 | Branch code is invalid or missing. | If the branch code is invalid, the Sending Member may repair the transaction by specifying the complete branch code. If the branch code is missing, the Originator may reissue the payment with the correct branch code included. |
| AC09 | Account currency is invalid or missing. This error is likely caused by a technical or human error. This error may also occur if the Beneficiary provided incorrect information to the Originator. | In case of a technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not specify invalid account currency information. If the Beneficiary provided incorrect account information, the Originator may contact the Beneficiary for accurate information. |
| AC10 | Debtor account currency is invalid or missing. | If the account currency information is invalid, the Sending Member may repair the transaction by specifying a valid Originator account currency. If the account currency information is missing, the Originator may reissue the payment with the Originator account currency specified. |
| AC11 | Creditor account currency is invalid or missing. | If the account currency information is invalid, the Sending Member may repair the transaction by specifying a valid Beneficiary account currency. If the account currency information is missing, the Originator may reissue the payment with the Beneficiary account currency specified. |
| AC12 | Account type missing or invalid. Generic usage if cannot specify between group and payment information levels. | N/A |
| AC13 | Debtor account type missing or invalid. | If the account type information is invalid, the Sending Member may repair the transaction by specifying the correct Originator account type. If the account type information is missing, the Originator may reissue the payment with the Originator account type specified. |
| AC14 | Creditor account type missing or invalid. | If the account type information is invalid, the Sending Member may repair the transaction by specifying the correct Beneficiary account type. If the account type information is missing, the Originator may reissue the payment with the Beneficiary account type specified. |
| AC15 | The account details for the counterparty have changed. | N/A |
| AC16 | Credit or debit card number is invalid. | N/A |
| AG01 | Transaction forbidden on this type of account (formerly NoAgreement). | The Originator may contact the Beneficiary for details of an alternative account that can receive the transaction. |
| AG02 | Bank Operation code specified in the message is not valid for receiver. | If the bank code information is invalid, the Sending Member may repair the transaction by specifying the correct code. If the bank code information is missing, the Originator may reissue the payment with the bank code specified. |
| AG03 | Transaction type not supported/authorized on this account. | The Originator may contact the Beneficiary to agree on a different payment instrument. |
| AG05 | Debtor agent country code is missing or invalid. | If the country code information is invalid, the Sending Member may repair the transaction by specifying the correct Sender Agent country code. If the country code information is missing, the Originator may reissue the payment with the Sender Agent country code specified. |
| AG06 | Creditor agent country code is missing or invalid. | If the country code information is invalid, the Sending Member may repair the transaction by specifying the correct Beneficiary Agent country code. If the country code information is missing, the Originator may reissue the payment with the Beneficiary Agent country code specified. |
| AG12 | Payment orders made by transferring funds from one account to another at the same financial institution (bank or payment institution) are not allowed. | N/A |
| AG13 | Returned payments derived from previously returned transactions are not allowed. | N/A |
| AM01 | Specified message amount is equal to zero. | N/A |
| AM02 | Specific transaction/message amount is greater than allowed maximum. | The Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not transfer incorrect amounts. |
| AM03 | Specified message amount is a non-processable currency outside of existing agreement. | The Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not initiate payments in unsupported currency. |
| AM04 | Amount of funds available to cover specified message amount is insufficient. This error may occur due to the following reasons:
| If the Originator's account previously had insufficient funds, the Sending Member may reissue the payment after the Originator ensures that their account contains the funds required to process the payment. If the Sending/Originating Bank's nostro settlement account previously had insufficient funds, they can reissue the payment after ensuring that their settlement account contains sufficient funds to process the payment. |
| AM05 | Duplication | N/A |
| AM07 | Amount specified in message has been blocked by regulatory authorities. | N/A |
| AM09 | Amount received is not the amount agreed or expected. | The Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not transfer incorrect amounts. |
| AM11 | Transaction currency information is invalid or missing. | N/A |
| AM13 | Transaction amount exceeds limits set by clearing system. | The Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not transfer incorrect amounts. |
| AM14 | Transaction amount exceeds limits agreed between bank and client. | The Beneficiary may request the Originator to initiate a payment whose transaction amount is within the agreed limits. Further, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not transfer incorrect amounts. |
| AM15 | Transaction amount below minimum set by clearing system. | The Beneficiary may request the Originator to initiate a payment whose transaction amount is within the agreed limits. Further, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not transfer incorrect amounts. |
| AM21 | Transaction amount exceeds limits agreed between bank and client. | N/A |
| AM22 | 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 the account. If the rules of a service prohibit the use of zero amount payments, then code AM01 is used to report the error condition. | N/A |
| BE01 | Identification of end customer is not consistent with associated account number (formerly CreditorConsistency). This error typically occurs because the Originator entered an incorrect Beneficiary account number while initiating the payment. | The Sending Member may introduce additional prompts in the user interface during payment initiation to ensure that the Originator verifies the Beneficiary's account number. |
| BE04 | Specification of creditor's address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress). | If the Beneficiary address is invalid, the Sending Member may repair the transaction by providing the correct Beneficiary address. If the Beneficiary address is missing, the Originator may reissue the payment with the Beneficiary address specified. |
| BE05 | Party who initiated the message is not recognized by the end customer. | N/A |
| BE06 | End customer specified is not known at associated Sort/National Bank Code or does no longer exist in the books. | N/A |
| BE07 | Specification of debtor's address, which is required for payment, is missing/not correct. | If the Originator's address is invalid, the Sending Member may repair the transaction by providing the correct Originator address. If the Originator's address is missing, the Originator may reissue the payment with their address specified. |
| BE08 | Debtor name is missing. | If the Originator's name is invalid, the Sending Member may repair the transaction by providing the correct Originator name. If the Originator's name is missing, the Originator may reissue the payment with their name specified. |
| BE09 | Country code is missing or Invalid. Generic usage if cannot specifically identify debtor or creditor. | N/A |
| BE10 | Debtor country code is missing or invalid. | If the Originator's country code is invalid, the Sending Member may repair the transaction by providing the correct Originator country code. If the Originator's country code is missing, the Originator may reissue the payment with the country code specified. |
| BE11 | Creditor country code is missing or invalid. | If the Beneficiary's country code is invalid, the Sending Member may repair the transaction by providing the correct Beneficiary country code. If the Beneficiary's country code is missing, the Originator may reissue the payment with the Beneficiary country code specified. |
| BE12 | Country code of residence is missing or Invalid. This generic error code should be used only if the relevant party is not clearly identifiable or specified. | N/A |
| BE13 | Country code of debtor's residence is missing or Invalid. | If the country code for Originator's country of residence is invalid, the Sending Member may repair the transaction by providing the correct country code. If the country code for Originator's country of residence is missing, the Originator may reissue the payment with the country code specified. |
| BE14 | Country code of creditor's residence is missing or Invalid. | If the country code for Beneficiary's country of residence is invalid, the Sending Member may repair the transaction by providing the correct country code. If the country code for Beneficiary's country of residence is missing, the Originator may reissue the payment with the Beneficiary country code specified. |
| BE15 | Identification code missing or invalid. Generic usage if cannot specifically identify debtor or creditor. | N/A |
| BE16 | Debtor or Ultimate Debtor identification code missing or invalid. | If the Originator's identification code is invalid, the Sending Member may repair the transaction by providing the correct identification code. If the Originator's identification code is missing, the Originator may reissue the payment with the identification code specified. |
| BE17 | Creditor or Ultimate Creditor identification code missing or invalid. | If the Beneficiary's identification code is invalid, the Sending Member may repair the transaction by providing the correct identification code. If the Beneficiary's identification code is missing, the Originator may reissue the payment with the Beneficiary identification code specified. |
| BE18 | Contact details missing or invalid. | If the contact details are invalid, the Sending Member may repair the transaction by providing the correct contact details. If the contact details are missing, the Originator may reissue the payment with the contact details specified. |
| BE19 | Charge bearer code for transaction type is invalid. | If the charge bearer code is invalid, the Sending Member may repair the transaction by providing the correct charge bearer code. If the charge bearer code is missing, the Originator may reissue the payment with the charge bearer code specified. |
| BE20 | Name length exceeds local rules for payment type. | N/A |
| BE21 | Name missing or invalid. Generic usage if cannot specifically identify debtor or creditor. | N/A |
| BE22 | Creditor name is missing. | If the Beneficiary's name is invalid, the Sending Member may repair the transaction by providing the correct Beneficiary name. If the Beneficiary's name is missing, the Originator may reissue the payment with the Beneficiary's name specified. |
| BE23 | Phone number or email address, or any other proxy, used as the account proxy is unknown or invalid. | N/A |
| CERI | Credit transfer is not tagged as an Extended Remittance Information (ERI) transaction but contains ERI. | N/A |
| CH11 | Value in Creditor Identifier is incorrect. | N/A |
| CH12 | Creditor Identifier is ambiguous at Transaction Level. | N/A |
| CH13 | Original Debtor Account is not to be used. | N/A |
| CH14 | Original Debtor Agent is not to be used. | N/A |
| CH15 | Content Remittance Information/Structured includes more than 140 characters. | N/A |
| CH16 | Content is incorrect. | N/A |
| CH17 | Element is not allowed. | N/A |
| CH20 | Number of decimal points not compatible with the currency. | N/A |
| CH21 | Mandatory element is missing. | N/A |
| CNOR | Creditor bank is not registered under this BIC in the CSM. | N/A |
| CURR | Currency of the payment is incorrect. | N/A |
| CUST | Cancellation requested by the Debtor. | N/A |
| DS24 | Waiting time expired due to incomplete order. | The Originator may contact the Beneficiary and ask them to take the actions necessary to receive funds. If the payment is resubmitted, a new reference ID must be used. |
| DS25 | The order file was deleted by the bank server (for multiple reasons). | N/A |
| DNOR | Debtor bank is not registered under this BIC in the CSM. | N/A |
| DU01 | Message Identification is not unique. This error typically occurs when the Sending Member submits a transaction with a message ID that matches a previous transaction's message ID. | The Sending Member must resubmit the transaction with a unique message ID. The following measures may also be considered:
|
| DU02 | Payment Information Block is not unique. | N/A |
| DU03 | Transaction is not unique. | N/A |
| DU04 | End To End ID is not unique. This error typically occurs when the Sending Member submits a transaction with an end-to-end ID that matches a previous transaction's end-to-end ID. | The Sending Member must resubmit the transaction with a unique end-to-end ID. The following measures may also be considered:
|
| DU05 | Instruction ID is not unique. This error typically occurs when the Sending Member submits a transaction with an Instruction ID that matches a previous transaction's Instruction ID. | The Sending Member must resubmit the transaction with a unique Instruction ID. The following measures may also be considered:
|
| DUPL | Payment is a duplicate of another payment. This error typically occurs when the Sending Member submits a transaction with reference information that matches a previous transaction's reference information. | The Sending Member must resubmit the transaction with unique reference information. The following measures may also be considered:
|
| ED06 | Interbank settlement system not available. This error typically occurs when the connecting infrastructure of the local clearing rail at the Receiving Member is unavailable to process or transmit any payment messages. | The Sending Member may recommend that the Originator reissue the RippleNet payment at a later time. The Originator may contact the Beneficiary to determine an alternative solution to make the payment. |
| FF03 | Payment Type Information is missing or invalid. This generic error code should be used only if Service Level or Local Instrument code are not specified. | If the payment type information is invalid, the Sending Member may repair the transaction by providing the correct payment type information. If the payment type information is missing, the Originator may reissue the payment with the payment type information specified. |
| FF04 | Service Level code is missing or invalid. | If the service level code is invalid, the Sending Member may repair the transaction by providing the correct code. If the service level code is missing, the Originator may reissue the payment with the code specified. |
| FF05 | Local Instrument code is missing or invalid. | If the local instrument code is invalid, the Sending Member may repair the transaction by providing the correct code. If the local instrument code is missing, the Originator may reissue the payment with the code specified. |
| FF06 | Category Purpose code is missing or invalid. | If the category purpose code is invalid, the Sending Member may repair the transaction by providing the correct code. If the category purpose code is missing, the Originator may reissue the payment with the code specified. |
| FF07 | Purpose of payment is missing or invalid. | If the purpose of payment information is invalid, the Sending Member may repair the transaction by providing the correct information. If the purpose of payment information is missing, the Originator may reissue the payment with the purpose of payment specified. |
| FF08 | End to End Id missing or invalid. | If the end-to-end ID is invalid, the Sending Member may repair the transaction by providing the correct ID. If the end-to-end ID is missing, the Originator may reissue the payment with the ID specified. |
| FF10 | File or transaction cannot be processed due to technical issues at the bank side. | The Sending Member may recommend that the Originator reissue the RippleNet payment at a later time. The Originator may contact the Beneficiary to determine an alternative solution to make the payment. |
| G000 | The payment transfer is tracked. No further updates will follow from the Status Originator. | N/A |
| G001 | PaymentTransferredAndNotTracked | The payment transfer is tracked. No further updates will follow from the Status Originator. |
| MD06 | Return of funds requested by end customer. | N/A |
| MD07 | End customer is deceased. | N/A |
| MS02 | Reason has not been specified by end customer. | N/A |
| MS03 | Reason has not been specified by agent. | N/A |
| NARR | Reason is provided as narrative information in the additional reason information. | N/A |
| RB001 | The account number structure is valid but the account number does not correspond to the individual identified in the payment. This error typically occurs because the Originator specified the Beneficiary's account number incorrectly while initiating the payment. | The Sending Member may introduce prompts in the user interface during payment initiation to ensure that the Originator validates the Beneficiary's account number. |
| RB002 | The Sender has requested Receiver for return of the payment. This error typically occurs in business scenarios where the Originator contacts the Sending Member to indicate that they (the Originator) provided incorrect account information. | The Sending Member must contact the Receiving Member and obtain agreement that the payment should be returned. After obtaining agreement, the Receiving Member can initiate the return of the payment. |
| RB003 | The funds for the payment have not been collected by the Beneficiary within the set period. | The Originator must inform the Beneficiary that they should collect the funds within the prescribed time frame. The Receiving Member may also contact the Beneficiary to inform them of pending or uncollected funds. Further, the Receiving Member must ensure that the Sending Member includes the Beneficiary's contact information in the RippleNet Payment Object. |
| RB004 | Beneficiary's account is frozen due to specific action taken by the Receiver or by legal action. This error typically occurs when the Beneficiary's bank has frozen the account due to suspected misuse, or on the Beneficiary's request. | The Originator may contact the Beneficiary for alternative account information or to agree on an alternative payment mechanism. |
| RB005 | The Receiver has returned the payment due to one of the following reasons:
| In case of a technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not transfer the incorrect amount. The Beneficiary may contact the Originator and ask them to initiate a payment for the exact amount. |
| RB006 | The return payment has not been sent within the agreed timeframe. This error typically occurs when the sender of the original payment has declined the return payment because it was not sent within the agreed upon timeframe for return payments. | The member making the return payment may take measures to ensure that the return payment is initiated within the timeframe that the Sending and Receiving Members have agreed upon. |
| RB007 | The sender of the original payment has not agreed to accept the return payment or has not requested the return payment. This error typically occurs when the sender of the original payment declines the return payment for business or other reasons. | The Beneficiary Bank or the Receiving Member may contact the Originator's Bank or the Sending Member to enquire about the reason for the return payment. If required, the member making the return payment may request alternative mechanisms for returning the payment, or resubmit the return payment. |
| RB008 | Invalid account title or name prefix. This error typically occurs when the Beneficiary's title or name specified in the payment does not match the information associated with their account. | In case of a technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not provide the incorrect Beneficiary title or name. If the Beneficiary provided incorrect information, the Originator may contact the Beneficiary to obtain the correct information. |
| RB009 | Beneficiary's account is dormant. This error typically occurs because the Beneficiary's Bank has marked the account as dormant due to a lack of activity or financial transactions on the account. | The Originator may contact the Beneficiary for alternative account information or to agree upon a different payment mechanism. |
| RB010 | The minimum amount required has not been remitted. This error typically occurs because the Originator has initiated payment for an amount that is lower than the intended amount that they previously agreed upon with the Beneficiary. | In case of technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not specify incorrect amounts. |
| RB011 | The account is subject to litigation. This error typically occurs because the Beneficiary's Bank has frozen the account due to legal reasons, or under suspicion of misuse, or on the Beneficiary's request. | The Originator may contact the Beneficiary for alternative account information or to agree upon a different payment mechanism. |
| RB012 | The Originator is not known to the Recipient or Beneficiary. | In case of technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not initiate payments to unknown or unintended Beneficiary accounts. |
| RB013 | The Receiver has not authorized this credit entry to the Beneficiary's account. This error typically occurs because the Beneficiary's Bank has blocked the account due to legal reasons. | The Originator may contact the Beneficiary for alternative account information or to agree upon a different payment mechanism. |
| RB014 | Amount specified in the payment has been blocked by regulatory authorities. This error typically occurs when the amount specified in the payment has been blocked or seized by regulatory authorities due to anti-money laundering or compliance reasons. | The Originator may contact the Sending Member for more information. |
| RB015 | The payment is a suspicious payment. This error typically occurs when the payment screening rules or policies of the Receiving Member or the Beneficiary Bank flag the payment as a suspicious payment. | The Sending Member may work with the Receiving Member to support resolution of the issue. |
| RB016 | Know Your Customer (KYC) pending for the individual identified in the payment. This error typically occurs because the payment cannot be booked to the Beneficiary's account due to pending KYC. | The Originator may contact the Beneficiary to agree upon a different payment mechanism. |
| RB017 | Government or National ID of the individual identified in the payment is not mapped to the account number. This error typically occurs when the payment cannot be booked to the Beneficiary's account because their Government or National ID is not linked with their account. | The Originator may contact the Beneficiary to agree upon a different payment mechanism. |
| RB018 | Customer insolvent or other reason. | N/A |
| RB019 | Return amount does not match with original payment amount. This error typically occurs because the Receiving Member initiated return of an amount less than the original payment amount. This may occur because the Receiving Member deducted fees for the return. | The Receiving Member must return the amount per their bilateral agreement with the Sending Member. |
| RB020 | Return information does not match with the original payment information. | The Receiving Member must pass the required information with the return payment per their agreement with the Sending Member. |
| RB021 | Return or refund amount must be greater than zero. This error occurs because RippleNet does not allow return amounts less than zero. | N/A |
| RB022 | Return or refund amount must be less than the maximum limit. This error occurs because RippleNet does not allow the return amount to exceed the original payment amount. | N/A |
| RB023 | Beneficiary account name does not match Beneficiary account number. | In case of technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not specify incorrect Beneficiary name. If the account name was invalid, the Originator may contact the Beneficiary for correct information. |
| RB024 | Account is not in currency quoted. | In case of technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not specify incorrect account currency information. The Originator may request the Beneficiary to provide accurate information about their account currency. |
| RB025 | Originator account number closed. | The Originator may provide alternative account information. |
| RB026 | Beneficiary account number closed. | The Originator may contact the Beneficiary for alternative account information. |
| RB027 | Beneficiary does not support or accept this message or payment type. | In case of technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not specify the wrong payment type. The Beneficiary may request the Originator to re-initiate the payment with a supported payment type. |
| RB028 | Payment was not processed as Receiver is unavailable or offline. This error typically occurs when the RippleNet connection to and from the Receiving Member or Intermediary Bank is unavailable due to network issues. | The Sending Member may request the Originator to reissue the RippleNet payment at a later time. |
| RB029 | Invalid payment type. The payment type used is not allowed or enabled for this Bank. | In case of technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not specify the wrong payment type. The Beneficiary may request the Originator to re-initiate the payment with a valid payment type. |
| RB030 | Card is blocked, or lost, or hotlisted. This error typically occurs if the Beneficiary Bank has blocked the card account due to reported theft or other legal issues. | The Originator may contact the Beneficiary for alternative account details. |
| RB031 | Card is expired. | The Originator may contact the Beneficiary for alternative account details. |
| RB032 | Invalid card number. This error typically occurs either because the Originator entered an invalid card number while initiating the payment, or because the Beneficiary provided an invalid card number to the Originator. | In case of a technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not supply an invalid or incomplete card number. If the Beneficiary provided an incorrect card number, the Originator may contact the Beneficiary for the correct number. |
| RB033 | Transactions to the card are restricted. This error typically occurs because the Beneficiary Bank has restricted financial transactions on the card due to legal reasons or reports of fraudulent usage. | The Originator may request the Beneficiary to provide alternative account information. |
| RB034 | Beneficiary has exceeded the number of transactions allowed for a set time period. This error typically occurs due to failed velocity or fraud checks conducted by the Receiving Member. | N/A |
| RB035 | Beneficiary has exceeded the cumulative transaction amount allowed for a set time period. This error typically occurs due to failed velocity or fraud checks conducted by the Receiving Member. | N/A |
| RB036 | Originator has exceeded the number of transactions allowed for a set time period. This error typically occurs due to failed velocity or fraud checks conducted by the Receiving Member. | N/A |
| RB037 | Originator has exceeded the cumulative transaction amount allowed for a set time period. This error typically occurs due to failed velocity or fraud checks conducted by the Receiving Member. | N/A |
| RB038 | Beneficiary nationality is invalid. | If the Beneficiary nationality information is invalid, the Sending Member may repair the transaction by providing the correct information. If the Beneficiary nationality information is missing, the Originator may reissue the payment with the information specified. |
| RB039 | Beneficiary nationality is missing in the payment message. | If the provided Beneficiary nationality information is incomplete, the Sending Member may repair the transaction by completing the information. If the Beneficiary nationality information is missing, the Originator may reissue the payment with the information specified. |
| RB040 | Originator nationality is invalid. | If the Originator nationality information is invalid, the Sending Member may repair the transaction by providing the correct information. If the Originator nationality information is missing, the Originator may reissue the payment with the information specified. |
| RB041 | Originator nationality is missing in the payment message. | If the provided Originator nationality information is incomplete, the Sending Member may repair the transaction by completing the information. If the Originator nationality information is missing, the Originator may reissue the payment with the information specified. |
| RB042 | Wallet identifier is invalid. This error typically occurs because the Beneficiary provided invalid wallet information. It may also occur because the Originator specified incorrect Beneficiary wallet information while initiating the payment. | The Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not specify incorrect Beneficiary wallet identifier. |
| RB043 | Transaction amount will make the wallet balance exceed the allowed limit. | The Originator may contact the Beneficiary to agree upon a different payment mechanism. Alternatively, the Originator may contact the Beneficiary to confirm the maximum allowed wallet balance and then issue a payment that will not cause the Beneficiary's wallet balance to exceed the limit. |
| RB044 | Transactions to wallet are stopped or not allowed. This error typically occurs because the wallet servicer has restricted financial transactions on the wallet due to legal reasons or suspicious use. | The Originator may contact the Beneficiary to obtain alternative account information or agree upon a different payment mechanism. |
| RB045 | The relationship to debtor details are missing. | N/A |
| RB046 | The relationship to debtor details are invalid. | N/A |
| RB047 | The relationship to creditor details are missing. | N/A |
| RB048 | The relationship to creditor details are invalid. | N/A |
| RB049 | The date of issuance for the id provided for the Creditor is missing. | N/A |
| RB050 | The date of issuance for the id provided for the Creditor is invalid. | N/A |
| RB051 | The date of issuance for the id provided for the Creditor is in the future. | N/A |
| RB052 | The date of expiry for the id provided for the Creditor is missing. | N/A |
| RB053 | The date of expiry for the id provided for the Creditor is invalid. | N/A |
| RB054 | The date of expiry for the id provided for the Creditor has passed. | N/A |
| RB055 | The date of incorporation for the Creditor is missing. | N/A |
| RB056 | The date of incorporation for the Creditor is invalid. | N/A |
| RB057 | The date of incorporation for the Creditor is in the future. | N/A |
| RB058 | The country of incorporation for the Creditor is missing. | N/A |
| RB059 | The country of incorporation for the Creditor is invalid. | N/A |
| RB060 | The date of issuance for the id provided for the Debtor is missing. | N/A |
| RB061 | The date of issuance for the id provided for the Debtor is invalid. | N/A |
| RB062 | The date of issuance for the id provided for the Debtor is in the future. | N/A |
| RB063 | The date of expiry for the id provided for the Debtor is missing. | N/A |
| RB064 | The date of expiry for the id provided for the Debtor is invalid. | N/A |
| RB065 | The date of expiry for the id provided for the Debtor has passed. | N/A |
| RB066 | The date of incorporation for the Debtor is missing. | N/A |
| RB067 | The date of incorporation for the Debtor is invalid. | N/A |
| RB068 | The date of incorporation for the Debtor is in the future. | N/A |
| RB069 | The country of incorporation for the Debtor is missing. | N/A |
| RB070 | The country of incorporation for the Debtor is invalid. | N/A |
| RC01 | Bank identifier code specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode). | N/A |
| RC02 | Bank identifier is invalid or missing. Generic usage if cannot specify between debit or credit account. | N/A |
| RC03 | Debtor bank identifier is invalid or missing. | If the Debtor Bank identifier is invalid, the Originator Bank may repair the transaction by providing the correct identifier. If the Debtor Bank identifier is missing, the Originator may reissue the payment with the identifier specified. |
| RC04 | Creditor bank identifier is invalid or missing. | If the Creditor Bank identifier is invalid, the Sending Member may repair the transaction by providing the correct identifier. If the Creditor Bank identifier is missing, the Originator may reissue the payment with the identifier specified. |
| RC05 | BIC identifier is invalid or missing. This generic error code should be used only if the relevant party is not clearly identifiable or specified. | If the BIC is invalid, the Sending Member may repair the transaction by providing the correct identifier. If the BIC is missing, the Originator may reissue the payment with the BIC identifier specified. |
| RC06 | Debtor BIC identifier is invalid or missing. | If the Debtor Bank BIC is invalid, the Sending Member may repair the transaction by providing the correct identifier. If the Debtor Bank BIC is missing, the Originator may reissue the payment with the identifier specified. |
| RC07 | Creditor BIC identifier is invalid or missing. | If the Beneficiary's BIC identifier is invalid, the Sending Member may repair the transaction by providing the correct BIC identifier. If the Beneficiary's BIC identifier is missing, the Originator may reissue the payment with the BIC identifier specified. |
| RC08 | ClearingSystemMember identifier is invalid or missing. Generic usage if cannot specify between debit or credit account. | N/A |
| RC09 | Debtor ClearingSystemMember identifier is invalid or missing. | If the Originator's ClearingSystemMember identifier is invalid, the Sending Member may repair the transaction by providing the correct identifier. If the Originator's ClearingSystemMember identifier is missing, the Originator may reissue the payment with the identifier specified. |
| RC10 | Creditor ClearingSystemMember identifier is invalid or missing. | If the Beneficiary's ClearingSystemMember identifier is invalid, the Sending Member may repair the transaction by providing the correct identifier. If the Beneficiary's ClearingSystemMember identifier is missing, the Originator may reissue the payment with the identifier specified. |
| RC12 | Creditor Scheme Id is invalid or missing. | N/A |
| RECI | Further information regarding the intended recipient. | N/A |
| RF01 | Transaction reference is not unique within the message. | N/A |
| RR01 | Specification of the debtor's account or unique identification needed for reasons of regulatory requirements is insufficient or missing. | N/A |
| RR02 | Specification of the debtor's name and/or address needed for regulatory requirements is insufficient or missing. | N/A |
| RR03 | Specification of the creditor's name and/or address needed for regulatory requirements is insufficient or missing. | If the Beneficiary's name and/or address information is invalid, the Sending Member may repair the transaction by providing the correct information. If the Beneficiary's name and/or address information is missing, the Originator may reissue the payment with the Beneficiary's information specified. |
| RR04 | Regulatory Reason. This error typically occurs when there is a restriction due to Anti-Money Laundering (AML), embargo, or compliance reasons. | The Originator may contact the Sending Member to enquire about the reasons for the error and take remedial action as they see fit. |
| RR05 | Regulatory or Central Bank Reporting information missing, incomplete or invalid. | In case of a technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not supply invalid or incomplete information. If the Beneficiary provided incorrect information, the Originator may contact the Beneficiary for accurate information. |
| RR06 | Tax information missing, incomplete or invalid. | N/A |
| RR07 | Remittance information structure does not comply with rules for payment type. | N/A |
| RR10 | Character set supplied not valid for the country and payment type. | In case of a technical or human error, the Sending Member or the Originator must adapt their internal RippleNet payment initiation process to ensure they do not supply an invalid character set. If the Beneficiary provided incorrect information, the Originator may contact the Beneficiary for accurate information. |
| SL03 | Due to a specific service offered by the clearing system. | N/A |
| TK01 | Token is invalid. | N/A |
| TK02 | Token used for the sender does not exist. | N/A |
| TK03 | Token used for the receiver does not exist. | N/A |
| TK09 | Token required for request is missing. | N/A |
| TKCM | Token found with counterparty mismatch. | N/A |
| TKSG | Single Use Token already used. | N/A |
| TKSP | Token found with suspended status. | N/A |
| TKVE | Token found with value limit rule violation. | N/A |
| TKXP | Token expired. | N/A |