Skip to main content

Payment Noc Update

Payment noc update webhook.

Definition

URL
https://<customerHost:Port>/webhook

Headers:

FieldDescription
Content-TypeThe Content-Type entity header is used to indicate the media type of the resource. Expected value is application/json.
x-api-keyf9be0d9e-6903-4862-8d69-5b2651426bf9

Example Request:

curl --location --request POST 'https://<customerHost:Port>/webhook' \\
--header 'Content-Type: application/json' \\
--header 'x-api-key: f9be0d9e-6903-4862-8d69-5b2651426bf9' \\
--data-raw '{
"reference_number": "1625203888",
"payment_id": "PREPY13906363",
"event": "NOC_RECEIVED",
"status": "SENT_TO_BANK",
"timestamp": "2026-06-03T11:27:35.753Z",
"noc_details": {
"noc_code": "C07",
"normalized_reason": "INCORRECT_ACCOUNT_DETAILS",
"description": "Multiple beneficiary account details are incorrect.",
"recommended_action": "Update all corrected fields before retrying the payment.",
"corrected_fields": {
"beneficiaryAccountNumber": "9876543210",
"routingNumber": "021000021",
"accountType": "2"
}
}
}'

Request Body:

FieldsDescriptionType
reference_numberUnique reference number for every payout sent by client.String
payment_idUnique Id for every payout generated by Nium.String
eventEvent name of the webhook. Here, it will be NOC_RECEIVEDString
statusPayment status values (IN_PROCESS, AWAITING_FUNDS, INFO_REQUESTED, COMPLIANCE_REJECTED, SENT_TO_BANK, PG_PROCESSING, PAID, RETURNED, REJECTED, CANCELLED)String
timestampDate and time of status change.String
noc_details.noc_codeThe raw NACHA NOC code received from the ACH scheme (e.g., C01, C02).String
noc_details.normalized_reasonNormalized NIUM reason code describing what changed (see NOC Code Mapping below).String
noc_details.descriptionHuman-readable description of the change and the recommended action for the client.String
noc_details.recommended_actionRefer Recommended Actions section below.String
noc_details.corrected_fieldsThe corrected value provided by the receiving bank (e.g., updated routing number or account number).Object

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.