Notification Webhooks Best practises
Knowledge base | Novalnet Docs

 Knowledge base

Know more about the notification webhooks and information that can be vital in processing the notifications effectively.

Domain whitelisting

Based on your network and security setup, you might need to configure your firewalls' whitelist to receive notifications from us. To achieve this, you can either:

  • You do not need to add a long list of IP addresses from us; instead, whitelist our domain pay-nn.de if you are network configured using domain whitelisting.
  • Perform DNS lookup for the domain pay-nn.de regularly to resolve our IP addresses. We recommend not hardcoding the resolved IP addresses to the whitelist.

Retrial mechanism

Novalnet's inbuilt retrial process allows you to receive the webhook data even if the initial notification has failed. The failure could be for any reason, server unreachable, site maintenance, site errors, etc.; nevertheless, Novalnet's server identifies the failed notifications and resend the data at the end of the day.

A final retrial will be performed the next day if the notification still can't be notified to your webhook endpoint.

If you have any inquiries about the re-transmission of the failed notifications, please contact the Novalnet Support Team.

Authentication mechanism

It is certain that every notification reaching your webhook endpoint should be authenticated, which lowers the risk of data manipulation. The comparison against the event makes the authentication event.checksum received in the notification response. Here you need to re-generate your checksum value.

The checksum generation differs based on the notification event from Novalnet as mentioned below:

Transaction events:  Every notification event involves a transaction.

Non-transaction events: This category includes the events AFFILIATE_CREATION, AFFILIATE_ACTIVATION, CALL_N_PAY and PAY_BY_LINK, where no transaction is involved.

  1. Check if event.tid, event.type, result.status, event.checksum parameters are received in the notification response.
  2. Build a token string by concatenating the following parameters in the mentioned order,

    event.tid
    event.type
    result.status
    transaction.amount (if found in the request)
    transaction.currency (if found in the request)

    and string reverse of your stored payment access key.

  3. Generate your own checksum by using the SHA256 hashing over the token string.
  4. Compare the event.checksum received in the notification response with the generated checksum.
  5. If the checksum matches, then the authentication is successful else there could be a possible manipulation in the data.

  1. Check if event.type, merchant.vendor, affiliate.vendor, event.checksum parameters are received in the notification response.
  2. Build a token string by concatenating the following parameters in the mentioned order,

    event.type
    merchant.vendor
    affiliate.vendor

    and string reverse of your stored payment access key.

  3. Generate your own checksum by using the SHA256 hashing over the token string.
  4. Compare the event.checksum received in the notification response with the generated checksum.
  5. If the checksum matches, then the authentication is successful else there could be a possible manipulation in the data.

Sample Script

Please refer to the Novalnet sample pre-built solution