Read and respond to Notification of Change (NOC) data on Increase ACH Transfer and Inbound ACH Transfer objects

Steps

1. On an outbound ACH Transfer object, check the notifications_of_change array field — if the receiving bank notified Increase that future transfers should use different account or routing details, those details appear here.
2. When notifications_of_change is populated, update the stored Counterparty/External Account details for that recipient before originating the next transfer, so you stop sending to stale details.
3. For transfers where your Increase account is the receiving side, monitor Inbound ACH Transfer objects; if the account or routing details on an inbound transfer need correction, call the 'Create a notification of change for an Inbound ACH Transfer' endpoint to originate the NOC back to the sending institution.
4. Subscribe to the ach_transfer.created and ach_transfer.updated webhook event categories so your system is notified as soon as an update (including an NOC) lands on a transfer, instead of relying on polling.
5. In sandbox, use the 'Create a Notification of Change for an ACH Transfer' simulation endpoint to generate a test NOC on an outbound transfer and verify your handling logic before going live.
6. Remember that Increase batches transfers and submits a file to the Federal Reserve roughly every 30 minutes, so NOC data will not appear until after a transfer has been submitted and the receiving institution has processed and returned it.