Remit Transaction NOC

This event is triggered when NIUM receives a Notification of Change (NOC) from the ACH scheme for a US remittance payout. The webhook tells you what changed on the beneficiary's bank details, gives you the corrected values, and recommends an action, so you can update your records before the next payment.

Webhook name: NOC_RECEIVED_WEBHOOK

Header

Header	Value
Content-Type	application/json

Request Example

curl --location --request POST 'https://<customerHost:Port>/webhook' \
-H 'content-type: application/json' \
-d '{
  "template": "NOC_RECEIVED_WEBHOOK",
  "clientHashId": "b56c4998-7970-4c1a-a36c-3d990a19c8fc",
  "customerHashId": "0f43707b-0d81-4d5f-b756-4fa85bedfd14",
  "walletHashId": "a46a0875-5e5c-47a3-942f-48ed98cb3e1a",
  "beneficiaryHashId": "6a0302c7506a1a44f0949cca",
  "systemReferenceNumber": "RT0022528086",
  "nocReason": "ACCOUNT_AND_ROUTING_CHANGED",
  "description": "Both the beneficiary account number and routing number have changed.",
  "recommendedAction": "Update both the account number and routing number for this beneficiary.",
  "correctedFields": {
    "routingNumber": "021000021",
    "beneficiaryAccountNumber": "123456789",
    "accountType": ""
  }
}'

Event Body

Field	Description	Type
template	Fixed value: NOC_RECEIVED_WEBHOOK.	String
clientHashId	The unique client identifier generated and shared before API handshake.	UUID
customerHashId	The unique customer identifier generated on customer creation.	UUID
walletHashId	The unique wallet identifier generated with customer creation.	UUID
beneficiaryHashId	The unique identifier of the beneficiary whose details need to be updated.	String
systemReferenceNumber	Unique system reference number generated by the platform for the affected transaction.	String
nocReason	NIUM's normalized reason describing what changed (see NOC Reasons).	String
description	Human-readable description of what changed.	String
recommendedAction	The action you should take to correct the beneficiary details.	String
correctedFields	Object containing the corrected values received from the receiving bank.	Object
correctedFields.routingNumber	The corrected routing number. Populated only when the routing number changed.	String
correctedFields.beneficiaryAccountNumber	The corrected beneficiary account number. Populated only when the account number changed.	String
correctedFields.accountType	The corrected account type. Populated only when the account type changed; otherwise empty.	String

NOC Reasons

The nocReason value maps to the NACHA NOC code received from the ACH scheme.

NACHA Code	nocReason	Description	Fields in correctedFields
C01	INCORRECT_ACCOUNT_NUMBER	The beneficiary account number is incorrect.	beneficiaryAccountNumber
C02	INCORRECT_ROUTING_NUMBER	The routing number is incorrect.	routingNumber
C03	ACCOUNT_AND_ROUTING_CHANGED	Both the beneficiary account number and routing number have changed.	beneficiaryAccountNumber, routingNumber
C05	INCORRECT_ACCOUNT_TYPE	The bank account type (checking or savings) is incorrect.	accountType
C06	ACCOUNT_NUMBER_AND_TYPE_CHANGED	Both the beneficiary account number and account type have changed.	beneficiaryAccountNumber, accountType
C07	ROUTING_ACCOUNT_AND_TYPE_CHANGED	The routing number, account number and account type have all changed.	routingNumber, beneficiaryAccountNumber, accountType
C08	ACCOUNT_CLOSED	The beneficiary account has been closed.	None
C09	ACCOUNT_HOLDER_INFO_CHANGED	The account holder information has changed, for example a name change or the account holder is deceased.	None

Recommended Actions

When you receive a NOC_RECEIVED_WEBHOOK:

1. Use systemReferenceNumber to identify the affected transaction and beneficiaryHashId to identify the beneficiary.
2. Read nocReason and recommendedAction to see what needs to change.
3. Apply the non-empty values in correctedFields to the beneficiary's bank details in your system.
4. Use the updated details for all future payments to this beneficiary.

Note: A NOC is informational. The original transaction is not automatically re-submitted.