Notification of Change (NOC)
What is a Notification of Change?
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's NOC Process
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.
Note: There is be no change in transfer status, as a NOC can exist on a transfer of any status and will not trigger the transfer to fail.
Examples
In the event that a NOC occurs, the transfer response body will look like this:
"destination": {
"reason_code": "notification_of_change_1",
"reason_code_message": "Incorrect Account Number",
"network_reason_code": "CO1",
"network_reason_code_message": "Updated Info: 123456790",
"network_reason_code_rail_type": "ach"
}
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:
"destination": {
"reason_code": "string",
"reason_code_message": "string",
"network_reason_code": "string",
"network_reason_code_message": "string",
"network_reason_code_rail_type": "string"
Common NOC Reponses
network_reason_code | reason_code | reason_code_message | network_reason_code_message | Description |
---|---|---|---|---|
C01 | notification_of_change_1 | Incorrect bank account number | Correct customer information | Bank account number incorrect or formatted incorrectly |
C02 | notification_of_change_2 | Incorrect routing number | Correct customer information | Once valid transit/routing number must be changed |
C03 | notification_of_change_3 | Incorrect transit/routing number and bank account number | Correct customer information | Once valid transit/routing number must be changed and causes a change to bank account number structure |
C04 | notification_of_change_4 | Bank account name change | Correct customer information | Customer has changed name or ODFI submitted name incorrectly |
C05 | notification_of_change_5 | Incorrect payment code | Correct customer information | Entry posted to demand account should contain savings payment codes or vice versa |
C06 | notification_of_change_6 | Incorrect bank account number and transit code | Correct customer information | Bank account number must be changed and payment code should indicate posting to another account type (demand/savings) |
C07 | notification_of_change_7 | Incorrect transit/routing number, bank account number and payment code | Correct customer information | Changes required in three fields indicated |
Updated 5 months ago