Webhook Solutions

Overview

Our webhook solution ensures that your system receives real-time notifications regarding specific events triggered within the NI system, based on your subscription to the different webhooks.

Integration

Our Webhooks solution relies on consumer defining a single API endpoint to receive all the notification types. Each message contains a common structure with:

  • id: Unique message id
  • type: type of notification. This is the key field to differentiate processing of the details payload
  • timestamp: timestamp of the message from NI systems
  • details: notification payload. Every message type will have its own payload specification and should be parsed and acted accordingly.

 

Security

The webhook endpoint is expected to be hosted through TLS/HTTPS to ensure secured data exchange. In addition to this, our webhook solution supports API authentication.
The preferred authentication strategy is oAuth2 where the consumer should provide NI with:

  • Authentication/Token management URL endpoint
  • client_id
  • client_secret

 

Pre-requisites

Our webhook API request will be using the POST verb.
To register a Webhook endpoint with us, please contact your relationship manager with:

  • Webhook URL Endpoint
  • Authentication mode
  • Security requirements
NI will ensure efficient management of authentication token and will include such in every webhook call.
To support different authentication method or integration strategy with us, please contact your relationship manager

 

 

 
Version

ThreeDS Webhook

Status:

Production

Version:

V2

Product:

Webhook Solutions

 

Overview


This webbook serves to instantly inform your system whenever an OTP message needs to be sent to the cardholder, this webhook is used when you need to send the OTP message from your side to the cardholder.

 

How It Works


When an OTP message needs to be sent to the cardholder, we will instantly send you a POST request to a specified endpoint, ensuring secure delivery of the OTP.
It communicates necessary details such as transaction amount, currency, masked pan, externalCardId
and mobile. Number. This mechanism ensures that the cardholder receives a timely and secure OTP for completing their transaction.
Once you receive this request you can send the message to the cardholder, so they can use the OTP.

 

 

/V2/webhook/3DSOTP

ThreeDS Webhook

Status:

Production

Version:

V2

Product:

Webhook Solutions
/V2/webhook/3DSOTP
curl --location --request POST '#{PARAM_URL}' --header 'Authorization: Bearer {{ access_token }}' {custom_headers} --data-raw '#{JSON_PAYLOAD}'
curl --location --request GET 'https://api-sandbox.network.global/v1/tokenkc/generate' \--data-raw '#{JSON_PAYLOAD}'
curl --location --request POST 'https://api-sandbox.network.global/v1/tokenkc/generate' \--data-raw '#{JSON_PAYLOAD}'

Node Child Node Type Length Description
Authorization* requiredBearer xxxx* requiredstringAuthorization Header (Bearer Token)
Content-Type* requiredapplication/json* requiredstringContent Type

Node TypeTypeLengthDescription
idstring12Unique identifer for the request
typestring10Type of the webhook
timestampstring30Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00
detailstransactionamountstring18Transaction Amount
currencystring3Amount Currency
merchantNamestring100Merchant Name
datestring30Request Timestamp - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00
timestring30Request Timestamp - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00
recipientmaskedCardNumberstring19Masked Card Number
externalCardIdstring20External Card ID
clientIdstring21Client ID
mobilePhonestring32Mobile Phone
emailstring255Email
languagestring3Language Indicator
OTPstring8OTP Value
referenceNumberstring12Reference Number
textMessagestring255Text Message

{
    "id": "688385602509",
    "type": "3DSOTP",
    "timestamp": "2023-10-05T08:03:41.283Z",
    "details": {
        "transaction": {
            "amount": "657.45",
            "currency": "AED",
            "merchantName": "Etisalat q",
            "date": "2023-10-05T08:03:41.280Z",
            "time": "2023-10-05T08:03:41.280Z",
            "recipient": {
                "maskedCardNumber": "433366XXXXXX89416714",
                "externalCardId": "43336612345605100000",
                "clientId": "1234625",
                "mobilePhone": "971553456789",
                "email": "vikas.mane@gmail.com",
                "language": "E"
            }
        },
        "OTP": "575866",
        "referenceNumber": "688385602509",
        "textMessage": "657.45 , 575866 , Etisalat q , AED"
    }
}

Node Child Node Type Length Description
Content-Typeapplication/jsonstringContent Type

Node TypeTypeLengthDescription
idstring36Unique identifer ID
typestring10Type of the webhook
timestampstring30Timestamp of the response - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00
responsestatuscodestring5Status code of the response
descriptionstring30Response Description

{
    "id": "b876d568-8411-4638-bdef-a1a188a4773b",
    "type": "SMS",
    "timestamp": "2020-07-20T06:49:02.366Z",
    "response": {
        "status": {
            "code": "00",
            "description": "successful"
        }
    }
}

Code Description
200Sample Description
400Bad Request
401Unauthorized
403Forbidden
500Internal Server Error
502Bad gateway
503Scheduled Maintenance
504Gateway Timeout
596Service Not Found