Skip to main content

Remit Transaction NOC

This event is triggered when NIUM receives a Notification of Change (NOC) from the ACH scheme for a US payout. It delivers a structured webhook containing the normalized reason for the change, the corrected value, and a recommended action — so clients can update their beneficiary or bank details before the next payment attempt.

HeaderValue
Content-Typeapplication/json

Request Example

curl --location --request POST 'https://<customerHost:Port>/webhook' \
-H 'content-type: application/json' \
-d '{
"template": "REMIT_TRANSACTION_NOC_WEBHOOK",
"clientHashId": "ecc9841c-c0df-c6e4-86f4-b320180d9859",
"customerHashId": "0f5a988e-c99a-4ce5-4ab7-b769e182de6f",
"walletHashId": "f46lb211-6e23-99ba-6356-8gb9t6s76458",
"systemReferenceNumber": "ZL1GX90938293",
"externalId": "Custom1245",
"beneficiaryAccountNumber": "xxxxxxxxxxxxxxxxxx4200",
"beneficiaryBankName": "Chase Bank",
"beneficiaryName": "John Smith",
"billingAmount": "1000.00",
"billingCurrency": "USD",
"transactionAmount": "1000.00",
"transactionCurrency": "USD",
"exchangeRate": "1.000000000",
"nocCode": "C02",
"nocReasonCode": "ROUTING_NUMBER_CHANGED",
"nocReasonDescription": "The routing/transit number for this account has changed. Update the routing number in your system using the correctedValue before initiating future payments to this beneficiary.",
"correctedValue": "021000021",
"tags": []
}'

Event Body

FieldDescriptionType
templateFixed value: REMIT_TRANSACTION_NOC_WEBHOOKString
clientHashIdThe unique client identifier generated and shared before API handshake.UUID
customerHashIdThe unique customer identifier generated on customer creation.UUID
walletHashIdThe unique wallet identifier generated with customer creation.UUID
systemReferenceNumberUnique system reference number generated by the platform for the affected transaction.String
externalIdUnique identifier provided by the client to track requests or transactions.String
beneficiaryAccountNumberThe bank account number of the beneficiary associated with the affected transaction.String
beneficiaryBankNameThe bank name of the beneficiary.String
beneficiaryNameThe name of the beneficiary.String
billingAmountThe source amount of the affected transaction.String
billingCurrencyThe three-letter ISO-4217 currency code for the wallet balance.String
transactionAmountThe destination amount of the affected transaction.String
transactionCurrencyThe three-letter ISO-4217 currency code for the transaction.String
exchangeRateExchange rate from source to destination currency.String
nocCodeThe raw NACHA NOC code received from the ACH scheme (e.g., C01, C02).String
nocReasonCodeNormalized NIUM reason code describing what changed (see NOC Code Mapping below).String
nocReasonDescriptionHuman-readable description of the change and the recommended action for the client.String
correctedValueThe corrected value provided by the receiving bank (e.g., updated routing number or account number).String
tagsCustom key-value pairs assigned to the transaction (max 15 pairs).Array

NOC Code Mapping

NACHA CodeNIUM Reason CodeDescription
C01ACCOUNT_NUMBER_UPDATEDThe account number is incorrect. Update the beneficiary account number using correctedValue.
C02ROUTING_NUMBER_CHANGEDThe routing/transit number is incorrect. Update the routing number using correctedValue.
C03ROUTING_AND_ACCOUNT_NUMBER_CHANGEDBoth the routing number and account number are incorrect. Update both fields; correctedValue contains the corrected account number. Contact NIUM support for the updated routing number.
C04BENEFICIARY_NAME_UPDATEDThe individual name or company name does not match bank records. Update the beneficiary name using correctedValue.
C05TRANSACTION_CODE_CHANGEDThe transaction code (checking vs. savings) is incorrect. Update the account type using correctedValue.
C06ACCOUNT_NUMBER_AND_TRANSACTION_CODE_CHANGEDBoth the account number and transaction code are incorrect. Update both fields using correctedValue.
C07ROUTING_ACCOUNT_AND_TRANSACTION_CODE_CHANGEDThe routing number, account number, and transaction code are all incorrect. Update all three fields.

When you receive a REMIT_TRANSACTION_NOC_WEBHOOK:

  1. Use systemReferenceNumber to identify the affected transaction.
  2. Read nocReasonCode to determine which field needs updating.
  3. Apply the correctedValue to the relevant beneficiary or bank detail in your system.
  4. Re-initiate the payment with the updated details to avoid a return.
note

NOC events are informational — the original transaction is not automatically re-submitted. If no action is taken and a subsequent payment is sent with the same incorrect details, NIUM will return the transaction.