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.

FieldDescription
reason_codeA word-based code created by Orum to describe the reason for the failure. Orum reason codes are rail-agnostic.
reason_code_messageA human-readable description of the reason code.
network_reason_codeThe reason code sent by the network (ex: R01).
network_reason_code_messageThe message sent by the network.
network_reason_code_rail_typeThe 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_codereason_code_message
blocked_accountAn account in the transfer request was blocked or prohibits posting of transfers against it
blocked_cardThe card has been associated with potential fraud or security concerns
canceled_transferA transfer cancellation request was successful
closed_accountAccount number specified has been closed on the bank of account’s books
debit_blockedThe account owner has placed a stop payment on their account
deceased_partyOne of the parties in the transfer request was deceased
duplicated_transferDuplicate of a previous transfer request
enterprise_insufficient_fundsThere is an insufficient enterprise balance and the transfer request cannot be completed
expiration_invalidThe expiration date provided was either invalid or expired
insufficient_fundsThere was not enough money available to complete the transfer request
invalid_accountThe account number provided is invalid or does not exist
invalid_amountThe amount provided in the transfer request was invalid or missing
invalid_country_codeThe country code utilized was invalid
invalid_currencyThe currency provided in the transfer request was invalid or missing
invalid_fieldThere was erroneous, invalid, or missing data in the transfer request
invalid_routingThe routing number provided is invalid or does not exist
issuer_errorThere was an error at the issuer and efforts to remedy should be made with the issuer
limit_exceededA limit set for this card has been exceeded
network_error
regulatory_errorThe transfer could not be completed because of limitations imposed by a regulator
transfer_on_holdTransfer request was questionable or part of anomalous activity
unauthorized_transferA party in the transfer request was either unknown or did not authorize this request
unavailable_financial_institutionSending or receiving financial institution is currently not available or does not support this request type
unexpected_errorThere was an unexpected error with this transfer request
unsupported_transferTransfer type is not supported or forbidden
wire_returnedThe 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:

ParameterDetails
network_reason_codeNacha Correction Code (e.g. C01)
reason_code_messageNOC Reason Text that Orum gets from the processor (e.g. Incorrect account number)
network_reason_code_messageCorrection 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:

"destination": {  
          "reason_code": "string",  
          "reason_code_message": "string",  
          "network_reason_code": "string",  
          "network_reason_code_message": "string",  
          "network_reason_code_rail_type": "string"

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.

CodeMessageDescription
C01Incorrect bank account numberBank account number incorrect or formatted incorrectly
C02Incorrect routing numberOnce valid transit/routing number must be changed
C03Incorrect transit/routing number and bank account numberOnce valid transit/routing number must be changed and causes a change to bank account number structure
C04Bank account name changeCustomer has changed name or ODFI submitted name incorrectly
C05Incorrect payment codeEntry posted to demand account should contain savings payment codes or vice versa
C06Incorrect bank account number and transit codeBank account number must be changed and payment code should indicate posting to another account type (demand/savings)
C07Incorrect transit/routing number, bank account number and payment codeChanges required in three fields indicated

ACH Return Codes

CodeCategoryDescriptionAccount TypeTimeframe
R01StandardInsufficient FundsConsumer/Business2 Banking Days
R02AdministrativeAccount ClosedConsumer/Business2 Banking Days
R03AdministrativeNo Account/Unable to Locate AccountConsumer/Business2 Banking Days
R04AdministrativeInvalid Account NumberConsumer/Business2 Banking Days
R05UnauthorizedUnauthorized Debit to Consumer AccountConsumer60 Calendar Days
R06StandardReturned per ODFI RequestConsumer/BusinessNot Applicable
R07UnauthorizedAuthorization RevokedConsumer60 Calendar Days
R08StandardPayment StoppedConsumer/Business2 Banking Days
R09StandardUncollected FundsConsumer/Business2 Banking Days
R10UnauthorizedCustomer Advises Unauthorized, Improper, or IneligibleConsumer60 Calendar Days
R11StandardCustomer Advises Entry Not in Accordance with TermsConsumer60 Calendar Days
R12StandardBranch Sold to Another DFIConsumer/Business2 Banking Days
R13StandardRDFI Not Qualified to ParticipateConsumer/Business2 Banking Days
R14StandardRepresentative Payee Deceased or Unable to ContinueConsumer2 Banking Days
R15StandardBeneficiary or Account Holder DeceasedConsumer2 Banking Days
R16StandardAccount FrozenConsumer/Business2 Banking Days
R17StandardFile Record Edit CriteriaConsumer/Business2 Banking Days
R18StandardImproper Effective Entry DateConsumer/Business2 Banking Days
R19StandardAmount Field ErrorConsumer/Business2 Banking Days
R20StandardNon-Transaction AccountConsumer/Business2 Banking Days
R21StandardInvalid Company IdentificationBusiness2 Banking Days
R22StandardInvalid Individual ID NumberConsumer2 Banking Days
R23StandardCredit Entry Refused by ReceiverConsumer/Business2 Banking Days
R24StandardDuplicate EntryConsumer/Business2 Banking Days
R25StandardAddenda ErrorConsumer/Business2 Banking Days
R26StandardMandatory Field ErrorConsumer/Business2 Banking Days
R27StandardTrace Number ErrorConsumer/Business2 Banking Days
R28StandardRouting Number Check Digit ErrorConsumer/Business2 Banking Days
R29UnauthorizedCorporate Customer Advises Not AuthorizedBusiness2 Banking Days
R30StandardRDFI Not Participant in Check Truncation ProgramConsumer/Business2 Banking Days
R31StandardPermissible Return EntryBusinessNot Applicable
R32StandardRDFI Non-SettlementConsumer/Business2 Banking Days
R33StandardReturn of XCK EntryConsumer/Business2 Banking Days
R34StandardLimited Participation DFIConsumer/Business2 Banking Days
R35StandardReturn of Improper Debit EntryConsumer/Business60 Calendar Days
R36StandardReturn of Improper Credit EntryConsumer/Business2 Banking Days
R37StandardSource Document Presented for PaymentConsumer/Business2 Banking Days
R38StandardStop Payment on Source DocumentConsumer/Business2 Banking Days
R39StandardImproper Source Document/Presented for PaymentConsumer/Business2 Banking Days
R40StandardReturn of ENR Entry by Federal Government AgencyConsumer2 Banking Days
R41StandardInvalid Transaction CodeConsumer2 Banking Days
R42StandardRouting Number/Check Digit ErrorConsumer2 Banking Days
R43StandardInvalid DFI Account NumberConsumer2 Banking Days
R44StandardInvalid Individual ID NumberConsumer2 Banking Days
R45StandardInvalid Individual NameConsumer2 Banking Days
R46StandardInvalid Representative Payee IndicatorConsumer2 Banking Days
R47StandardDuplicate EnrollmentConsumer2 Banking Days
R50StandardState Law Affecting RCK AcceptanceConsumer60 Calendar Days
R51UnauthorizedItem is Ineligible, Notice Not Provided, Signature Not GenuineConsumer60 Calendar Days
R52StandardStop Payment on ItemConsumer2 Banking Days
R53StandardItem and ACH Entry Presented for PaymentConsumer2 Banking Days
R61StandardMisrouted ReturnConsumer/BusinessNot Applicable
R62StandardReturn of Erroneous or Reversing DebitConsumer/BusinessNot Applicable
R67StandardDuplicate ReturnConsumer/BusinessNot Applicable
R68StandardUntimely ReturnConsumer/BusinessNot Applicable
R69StandardField Error(s)Consumer/BusinessNot Applicable
R70StandardPermissible Return Entry Not AcceptedConsumer/BusinessNot Applicable
R71StandardMisrouted Dishonored ReturnConsumer/BusinessNot Applicable
R72StandardUntimely Dishonored ReturnConsumer/BusinessNot Applicable
R73StandardTimely Original Return Not ReceivedConsumer/BusinessNot Applicable
R74StandardCorrected ReturnConsumer/BusinessNot Applicable
R75StandardReturn Not a DuplicateConsumer/BusinessNot Applicable
R76StandardNo Errors FoundConsumer/BusinessNot Applicable
R80StandardIAT Entry Coding ErrorConsumer/Business2 Banking Days
R81StandardNon-Participant in IAT ProgramConsumer/Business2 Banking Days
R82StandardInvalid Foreign RDFI IdentificationConsumer/Business2 Banking Days
R83StandardForeign RDFI Unable to SettleConsumer/Business2 Banking Days
R84StandardEntry Not Processed by GatewayConsumer/Business2 Banking Days
R85StandardIncorrectly Coded Outbound International PaymentConsumer/Business2 Banking Days

Card Chargeback Network Reasons

Visa Chargeback Reason Codes

CodeCategoryDescriptionTimeframe
10.1FraudEMV Liability Shift Counterfeit Fraud120 Calendar Days
10.2FraudEMV Liability Shift Non-Counterfeit Fraud120 Calendar Days
10.3FraudOther Fraud - Card-Present Environment120 Calendar Days
10.4FraudOther Fraud - Card-Absent Environment120 Calendar Days
10.5MonitoringVisa Fraud Monitoring ProgramVaries
11.1AuthorizationCard Recovery Bulletin120 Calendar Days
11.2AuthorizationDeclined Authorization120 Calendar Days
11.3AuthorizationNo Authorization120 Calendar Days
12.1Processing ErrorLate Presentment120 Calendar Days
12.2Processing ErrorIncorrect Transaction Code120 Calendar Days
12.3Processing ErrorIncorrect Currency120 Calendar Days
12.4Processing ErrorIncorrect Account Number120 Calendar Days
12.5Processing ErrorIncorrect Amount120 Calendar Days
12.6.1Processing ErrorDuplicate Processing120 Calendar Days
12.6.2Processing ErrorPaid by Other Means120 Calendar Days
12.7Processing ErrorInvalid Data120 Calendar Days
13.1Consumer DisputeMerchandise/Services Not Received120 Calendar Days
13.2Consumer DisputeCancelled Recurring Transaction120 Calendar Days
13.3Consumer DisputeNot as Described or Defective Merchandise/Services120 Calendar Days
13.4Consumer DisputeCounterfeit Merchandise120 Calendar Days
13.5Consumer DisputeMisrepresentation120 Calendar Days
13.6Consumer DisputeCredit Not Processed120 Calendar Days
13.7Consumer DisputeCancelled Merchandise/Services120 Calendar Days
13.8Consumer DisputeOriginal Credit Transaction Not Accepted120 Calendar Days
13.9Consumer DisputeNon-Receipt of Cash or Load Transaction Value120 Calendar Days

Mastercard Chargeback Reason Codes

CodeCategoryDescriptionTimeframe
4515Consumer DisputeCardholder Denies Transaction Finalized120 Calendar Days
4807AuthorizationWarning Bulletin File120 Calendar Days
4808AuthorizationRequested/Required Authorization Not Obtained120 Calendar Days
4812AuthorizationAccount Number Not on File120 Calendar Days
4831Consumer DisputeDisputed Amount120 Calendar Days
4834Processing ErrorDuplicate Transaction120 Calendar Days
4837FraudNo Cardholder Authorization120 Calendar Days
4841Consumer DisputeCancelled Recurring Transaction120 Calendar Days
4842Processing ErrorLate Presentment120 Calendar Days
4846Processing ErrorCorrect Transaction Currency Code Not Provided120 Calendar Days
4849FraudQuestionable Merchant Activity120 Calendar Days
4853Consumer DisputeCardholder Dispute: Defective/Not as Described120 Calendar Days
4854Consumer DisputeCardholder Dispute: Not Elsewhere Classified (U.S.)120 Calendar Days
4855Consumer DisputeGoods or Services Not Delivered120 Calendar Days
4859Consumer DisputeServices Not Rendered120 Calendar Days
4860Consumer DisputeCredit Not Received120 Calendar Days
4863FraudCardholder does Not Recognize: Potential Fraud120 Calendar Days
4870FraudChip Liability Shift120 Calendar Days
4871FraudChip/Pin Liability Shift120 Calendar Days
4999Regional DisputeDomestic Chargeback Dispute (Europe Region Only)120 Calendar Days