Network & Reason Codes
Understand why a transfer failed.
Status Reasons
If a transfer fails, Orum will send a transfer_updated
webhook. The transfer object in the payload will have a status
of failed
and a status_reasons
array that explains why the transfer failed. status_reasons
will contain a source
and/or destination
item, depending on where the transfer failure occurred.
Field | Description |
---|---|
reason_code | A word-based code created by Orum to describe the reason for the failure. Orum reason codes are rail-agnostic. |
reason_code_message | A human-readable description of the reason code. |
network_reason_code | The reason code sent by the network (ex: R01). |
network_reason_code_message | The message sent by the network. |
network_reason_code_rail_type | The payment rail used in the transfer. Either RTP or ACH. |
The network_reason_code
and network_reason_message
fields are populated with what Deliver receives from the network. That network information is mapped to an Orum-created reason_code
and reason_code_message
, which give a higher-level and more human-readable explanation of the transfer failure.
Return Reason Codes
reason_code | reason_code_message |
---|---|
blocked_account | An account in the transfer request was blocked or prohibits posting of transfers against it |
blocked_card | The card has been associated with potential fraud or security concerns |
canceled_transfer | A transfer cancellation request was successful |
closed_account | Account number specified has been closed on the bank of account’s books |
debit_blocked | The account owner has placed a stop payment on their account |
deceased_party | One of the parties in the transfer request was deceased |
duplicated_transfer | Duplicate of a previous transfer request |
enterprise_insufficient_funds | There is an insufficient enterprise balance and the transfer request cannot be completed |
expiration_invalid | The expiration date provided was either invalid or expired |
insufficient_funds | There was not enough money available to complete the transfer request |
invalid_account | The account number provided is invalid or does not exist |
invalid_amount | The amount provided in the transfer request was invalid or missing |
invalid_country_code | The country code utilized was invalid |
invalid_currency | The currency provided in the transfer request was invalid or missing |
invalid_field | There was erroneous, invalid, or missing data in the transfer request |
invalid_routing | The routing number provided is invalid or does not exist |
issuer_error | There was an error at the issuer and efforts to remedy should be made with the issuer |
limit_exceeded | A limit set for this card has been exceeded |
network_error | |
regulatory_error | The transfer could not be completed because of limitations imposed by a regulator |
transfer_on_hold | Transfer request was questionable or part of anomalous activity |
unauthorized_transfer | A party in the transfer request was either unknown or did not authorize this request |
unavailable_financial_institution | Sending or receiving financial institution is currently not available or does not support this request type |
unexpected_error | There was an unexpected error with this transfer request |
unsupported_transfer | Transfer type is not supported or forbidden |
wire_returned | The wire was returned from the receiving bank because it was unable to be delivered to the desired destination |
Notification of Change (NOC)
A Notification of Change (NOC) is an alert used to notify the sender of an ACH payment to update details related to a customer’s bank account that have changed or are incorrect. NOCs are created by the Receiving Depository Financial Institution (RDFI) and sent to the Originating Depository Financial Institution (ODFI). NOCs help ensure that future transactions are processed accurately without any disruptions.
Orum automates the NOC process so you receive them directly via webhook. We relay the following information to you via the transfer response body:
- The Nacha correction code
- Detail of what needs to be changed
- Detail of what the new value needs to be
When a NOC is received, the transfer_updated
webhook event is sent.
There is no change in transfer status, as a NOC can exist on a transfer of any status and will not trigger the transfer to fail.
The Automated NOC will be conveyed via the existing parameters and corresponding details:
Parameter | Details |
---|---|
network_reason_code | Nacha Correction Code (e.g. C01) |
reason_code_message | NOC Reason Text that Orum gets from the processor (e.g. Incorrect account number) |
network_reason_code_message | Correction info that Orum gets from the processor (e.g. 123456789 |
If a NOC occurs on a transfer that has also incurred a return, Orum will notify you of both events. In this case, a separate transfer_updated
webhook will be sent for each event, but the events will always look like this:
NOC Reason Codes
Unlike the reason codes above, NOCs can exist on a transfer of anystatus
(i.e. it does not have to be failed
). The status_reasons
array will still explain why the NOC occurred.status_reasons
will contain a source
and/or destination
item, depending on where the NOC occurred.
Code | Message | Description |
---|---|---|
C01 | Incorrect bank account number | Bank account number incorrect or formatted incorrectly |
C02 | Incorrect routing number | Once valid transit/routing number must be changed |
C03 | Incorrect transit/routing number and bank account number | Once valid transit/routing number must be changed and causes a change to bank account number structure |
C04 | Bank account name change | Customer has changed name or ODFI submitted name incorrectly |
C05 | Incorrect payment code | Entry posted to demand account should contain savings payment codes or vice versa |
C06 | Incorrect bank account number and transit code | Bank account number must be changed and payment code should indicate posting to another account type (demand/savings) |
C07 | Incorrect transit/routing number, bank account number and payment code | Changes required in three fields indicated |
ACH Return Codes
Code | Category | Description | Account Type | Timeframe |
---|---|---|---|---|
R01 | Standard | Insufficient Funds | Consumer/Business | 2 Banking Days |
R02 | Administrative | Account Closed | Consumer/Business | 2 Banking Days |
R03 | Administrative | No Account/Unable to Locate Account | Consumer/Business | 2 Banking Days |
R04 | Administrative | Invalid Account Number | Consumer/Business | 2 Banking Days |
R05 | Unauthorized | Unauthorized Debit to Consumer Account | Consumer | 60 Calendar Days |
R06 | Standard | Returned per ODFI Request | Consumer/Business | Not Applicable |
R07 | Unauthorized | Authorization Revoked | Consumer | 60 Calendar Days |
R08 | Standard | Payment Stopped | Consumer/Business | 2 Banking Days |
R09 | Standard | Uncollected Funds | Consumer/Business | 2 Banking Days |
R10 | Unauthorized | Customer Advises Unauthorized, Improper, or Ineligible | Consumer | 60 Calendar Days |
R11 | Standard | Customer Advises Entry Not in Accordance with Terms | Consumer | 60 Calendar Days |
R12 | Standard | Branch Sold to Another DFI | Consumer/Business | 2 Banking Days |
R13 | Standard | RDFI Not Qualified to Participate | Consumer/Business | 2 Banking Days |
R14 | Standard | Representative Payee Deceased or Unable to Continue | Consumer | 2 Banking Days |
R15 | Standard | Beneficiary or Account Holder Deceased | Consumer | 2 Banking Days |
R16 | Standard | Account Frozen | Consumer/Business | 2 Banking Days |
R17 | Standard | File Record Edit Criteria | Consumer/Business | 2 Banking Days |
R18 | Standard | Improper Effective Entry Date | Consumer/Business | 2 Banking Days |
R19 | Standard | Amount Field Error | Consumer/Business | 2 Banking Days |
R20 | Standard | Non-Transaction Account | Consumer/Business | 2 Banking Days |
R21 | Standard | Invalid Company Identification | Business | 2 Banking Days |
R22 | Standard | Invalid Individual ID Number | Consumer | 2 Banking Days |
R23 | Standard | Credit Entry Refused by Receiver | Consumer/Business | 2 Banking Days |
R24 | Standard | Duplicate Entry | Consumer/Business | 2 Banking Days |
R25 | Standard | Addenda Error | Consumer/Business | 2 Banking Days |
R26 | Standard | Mandatory Field Error | Consumer/Business | 2 Banking Days |
R27 | Standard | Trace Number Error | Consumer/Business | 2 Banking Days |
R28 | Standard | Routing Number Check Digit Error | Consumer/Business | 2 Banking Days |
R29 | Unauthorized | Corporate Customer Advises Not Authorized | Business | 2 Banking Days |
R30 | Standard | RDFI Not Participant in Check Truncation Program | Consumer/Business | 2 Banking Days |
R31 | Standard | Permissible Return Entry | Business | Not Applicable |
R32 | Standard | RDFI Non-Settlement | Consumer/Business | 2 Banking Days |
R33 | Standard | Return of XCK Entry | Consumer/Business | 2 Banking Days |
R34 | Standard | Limited Participation DFI | Consumer/Business | 2 Banking Days |
R35 | Standard | Return of Improper Debit Entry | Consumer/Business | 60 Calendar Days |
R36 | Standard | Return of Improper Credit Entry | Consumer/Business | 2 Banking Days |
R37 | Standard | Source Document Presented for Payment | Consumer/Business | 2 Banking Days |
R38 | Standard | Stop Payment on Source Document | Consumer/Business | 2 Banking Days |
R39 | Standard | Improper Source Document/Presented for Payment | Consumer/Business | 2 Banking Days |
R40 | Standard | Return of ENR Entry by Federal Government Agency | Consumer | 2 Banking Days |
R41 | Standard | Invalid Transaction Code | Consumer | 2 Banking Days |
R42 | Standard | Routing Number/Check Digit Error | Consumer | 2 Banking Days |
R43 | Standard | Invalid DFI Account Number | Consumer | 2 Banking Days |
R44 | Standard | Invalid Individual ID Number | Consumer | 2 Banking Days |
R45 | Standard | Invalid Individual Name | Consumer | 2 Banking Days |
R46 | Standard | Invalid Representative Payee Indicator | Consumer | 2 Banking Days |
R47 | Standard | Duplicate Enrollment | Consumer | 2 Banking Days |
R50 | Standard | State Law Affecting RCK Acceptance | Consumer | 60 Calendar Days |
R51 | Unauthorized | Item is Ineligible, Notice Not Provided, Signature Not Genuine | Consumer | 60 Calendar Days |
R52 | Standard | Stop Payment on Item | Consumer | 2 Banking Days |
R53 | Standard | Item and ACH Entry Presented for Payment | Consumer | 2 Banking Days |
R61 | Standard | Misrouted Return | Consumer/Business | Not Applicable |
R62 | Standard | Return of Erroneous or Reversing Debit | Consumer/Business | Not Applicable |
R67 | Standard | Duplicate Return | Consumer/Business | Not Applicable |
R68 | Standard | Untimely Return | Consumer/Business | Not Applicable |
R69 | Standard | Field Error(s) | Consumer/Business | Not Applicable |
R70 | Standard | Permissible Return Entry Not Accepted | Consumer/Business | Not Applicable |
R71 | Standard | Misrouted Dishonored Return | Consumer/Business | Not Applicable |
R72 | Standard | Untimely Dishonored Return | Consumer/Business | Not Applicable |
R73 | Standard | Timely Original Return Not Received | Consumer/Business | Not Applicable |
R74 | Standard | Corrected Return | Consumer/Business | Not Applicable |
R75 | Standard | Return Not a Duplicate | Consumer/Business | Not Applicable |
R76 | Standard | No Errors Found | Consumer/Business | Not Applicable |
R80 | Standard | IAT Entry Coding Error | Consumer/Business | 2 Banking Days |
R81 | Standard | Non-Participant in IAT Program | Consumer/Business | 2 Banking Days |
R82 | Standard | Invalid Foreign RDFI Identification | Consumer/Business | 2 Banking Days |
R83 | Standard | Foreign RDFI Unable to Settle | Consumer/Business | 2 Banking Days |
R84 | Standard | Entry Not Processed by Gateway | Consumer/Business | 2 Banking Days |
R85 | Standard | Incorrectly Coded Outbound International Payment | Consumer/Business | 2 Banking Days |
Card Chargeback Network Reasons
Visa Chargeback Reason Codes
Code | Category | Description | Timeframe |
---|---|---|---|
10.1 | Fraud | EMV Liability Shift Counterfeit Fraud | 120 Calendar Days |
10.2 | Fraud | EMV Liability Shift Non-Counterfeit Fraud | 120 Calendar Days |
10.3 | Fraud | Other Fraud - Card-Present Environment | 120 Calendar Days |
10.4 | Fraud | Other Fraud - Card-Absent Environment | 120 Calendar Days |
10.5 | Monitoring | Visa Fraud Monitoring Program | Varies |
11.1 | Authorization | Card Recovery Bulletin | 120 Calendar Days |
11.2 | Authorization | Declined Authorization | 120 Calendar Days |
11.3 | Authorization | No Authorization | 120 Calendar Days |
12.1 | Processing Error | Late Presentment | 120 Calendar Days |
12.2 | Processing Error | Incorrect Transaction Code | 120 Calendar Days |
12.3 | Processing Error | Incorrect Currency | 120 Calendar Days |
12.4 | Processing Error | Incorrect Account Number | 120 Calendar Days |
12.5 | Processing Error | Incorrect Amount | 120 Calendar Days |
12.6.1 | Processing Error | Duplicate Processing | 120 Calendar Days |
12.6.2 | Processing Error | Paid by Other Means | 120 Calendar Days |
12.7 | Processing Error | Invalid Data | 120 Calendar Days |
13.1 | Consumer Dispute | Merchandise/Services Not Received | 120 Calendar Days |
13.2 | Consumer Dispute | Cancelled Recurring Transaction | 120 Calendar Days |
13.3 | Consumer Dispute | Not as Described or Defective Merchandise/Services | 120 Calendar Days |
13.4 | Consumer Dispute | Counterfeit Merchandise | 120 Calendar Days |
13.5 | Consumer Dispute | Misrepresentation | 120 Calendar Days |
13.6 | Consumer Dispute | Credit Not Processed | 120 Calendar Days |
13.7 | Consumer Dispute | Cancelled Merchandise/Services | 120 Calendar Days |
13.8 | Consumer Dispute | Original Credit Transaction Not Accepted | 120 Calendar Days |
13.9 | Consumer Dispute | Non-Receipt of Cash or Load Transaction Value | 120 Calendar Days |
Mastercard Chargeback Reason Codes
Code | Category | Description | Timeframe |
---|---|---|---|
4515 | Consumer Dispute | Cardholder Denies Transaction Finalized | 120 Calendar Days |
4807 | Authorization | Warning Bulletin File | 120 Calendar Days |
4808 | Authorization | Requested/Required Authorization Not Obtained | 120 Calendar Days |
4812 | Authorization | Account Number Not on File | 120 Calendar Days |
4831 | Consumer Dispute | Disputed Amount | 120 Calendar Days |
4834 | Processing Error | Duplicate Transaction | 120 Calendar Days |
4837 | Fraud | No Cardholder Authorization | 120 Calendar Days |
4841 | Consumer Dispute | Cancelled Recurring Transaction | 120 Calendar Days |
4842 | Processing Error | Late Presentment | 120 Calendar Days |
4846 | Processing Error | Correct Transaction Currency Code Not Provided | 120 Calendar Days |
4849 | Fraud | Questionable Merchant Activity | 120 Calendar Days |
4853 | Consumer Dispute | Cardholder Dispute: Defective/Not as Described | 120 Calendar Days |
4854 | Consumer Dispute | Cardholder Dispute: Not Elsewhere Classified (U.S.) | 120 Calendar Days |
4855 | Consumer Dispute | Goods or Services Not Delivered | 120 Calendar Days |
4859 | Consumer Dispute | Services Not Rendered | 120 Calendar Days |
4860 | Consumer Dispute | Credit Not Received | 120 Calendar Days |
4863 | Fraud | Cardholder does Not Recognize: Potential Fraud | 120 Calendar Days |
4870 | Fraud | Chip Liability Shift | 120 Calendar Days |
4871 | Fraud | Chip/Pin Liability Shift | 120 Calendar Days |
4999 | Regional Dispute | Domestic Chargeback Dispute (Europe Region Only) | 120 Calendar Days |
Was this page helpful?